Google Trends Scraper

Get Google Trends data for any keyword: interest over time, interest by region and related queries (top and rising). It also returns Trending Now, the daily trending searches for any country. Results come back as clean JSON, ready for a spreadsheet, a dashboard or an AI agent.

You only pay for terms that succeed. When Google blocks a request, the scraper retries on a fresh proxy session, with a cap on the number of retries. A term that still can't be fetched is listed in the FAILED_TERMS record and never charged. Runs don't hang until a timeout and don't bill you for empty rows.

What you can use it for

• SEO and content planning: find rising queries before your competitors do, and check whether a topic is growing or fading.
• Market and product research: compare up to 5 brands, products or ideas on one chart, the way Google Trends' compare view does.
• Regional targeting: see which states, metro areas or countries search for something most.
• E-commerce and seasonality: use 5-year history and Google Shopping search interest to time inventory and campaigns.
• News and social monitoring: pull today's Trending Now searches, with their news articles, on a schedule.
• AI agents and automations: a small, predictable JSON output with one result per keyword.

How to use it

1. Enter one or more search terms.
2. Optionally pick a location (e.g. US, GB, US-CA), a time range and a search type (web, images, news, Shopping, YouTube).
3. Turn on Compare terms to put up to 5 terms on one chart. Values are then relative to each other.
4. Click Start. Each term, or each comparison group, produces one result.

For daily trending searches, set Mode to Trending Now and choose a country.

Example input

{
  "searchTerms": ["chatgpt", "claude", "gemini"],
  "compareTerms": true,
  "geo": "US",
  "timeRange": "today 3-m"
}

Output

One result per term (or per comparison group):

{
  "searchTerm": null,
  "searchTerms": ["chatgpt", "claude", "gemini"],
  "geo": "US",
  "timeRange": "today 3-m",
  "category": 0,
  "searchProperty": "web",
  "averages": { "chatgpt": 67, "claude": 18, "gemini": 28 },
  "interestOverTime": [
    { "date": "2026-10-26T00:00:00+00:00", "formattedTime": "Oct 26, 2026",
      "values": { "chatgpt": 78, "claude": 24, "gemini": 36 }, "isPartial": true }
  ],
  "interestByRegion": [
    { "geoCode": "US-CA", "geoName": "California", "values": { "chatgpt": 57, "claude": 18, "gemini": 25 } }
  ],
  "relatedQueries": {
    "chatgpt": {
      "top":    [{ "query": "chatgpt ai", "value": 100, "formattedValue": "100" }],
      "rising": [{ "query": "chatgpt student offer", "value": 500, "formattedValue": "+500%" }]
    }
  },
  "hasData": true,
  "scrapedAt": "2026-10-26T13:58:06+00:00"
}

For a single term, relatedQueries is { "top": [...], "rising": [...] } directly.

Trending Now results contain rank, title, approxTraffic, pubDate, picture and the related news articles.

All values are Google's 0–100 relative interest index, exactly as Google Trends shows them.

Pricing

You pay per result: one result per term, comparison group or trending search. Runs where every term fails cost nothing. See the Pricing tab for current rates.

Tips

• Proxy: Apify datacenter proxies (the default) work for Google Trends. If you see repeated 429 responses on large runs, switch the proxy group to RESIDENTIAL.
• Large lists: keep Parallel requests at 2–3. Raising it makes runs faster but triggers more rate limits and retries.
• Hourly ranges (now 1-H to now 7-d) use the Timezone offset setting.
• Related topics: as of October 2026 Google returns an empty related-topics list to automated requests, so the option is off by default. Related queries work normally.

FAQ

Why do numbers differ slightly between runs? Google Trends samples its data, so small differences between runs are normal and also appear in the Google Trends website.

Is this data public? Yes. This Actor reads the same aggregated, anonymous search-interest data the Google Trends website shows. It collects no personal data.

Something broke? Open an issue on the Issues tab with your run ID. Fixes are usually live the same day.