Google Trends by Region

Google rate-limits Trends requests hard. This Actor backs off, opens a fresh session on every rate limit and uses a residential proxy only when needed; keyword groups still blocked are named in the run status.

This Actor costs $1.50 per 1,000 results on the free plan and $0.90 on paid plans, plus a $0.0075 start fee, with no platform usage on top. apify/google-trends-scraper costs $3.00 and $1.00 plus platform usage at 4 GB default memory, and its 30-day run success was 56.5% when we checked; data_xplorer/google-trends-fast-scraper costs $2.00 and $1.00 with a $0.025 start fee and takes one keyword per run. This Actor takes any number of keywords on one 0-100 scale.

Two ways. For a fixed workflow, add Apify's n8n or Make node, choose **Run Actor**, enter aurelix/google-trends-scraper and map the dataset to the next step. For an AI agent (Claude, ChatGPT, Cursor or an n8n AI Agent node), add https://mcp.apify.com/?tools=aurelix/google-trends-scraper as an MCP server and ask for trends in plain words; setup for each client is in the section above. Runs bill your own Apify account at the same per-result price.

$1.50 per 1,000 results ($0.90 on paid Apify plans), billed through your Apify account; you pay only for results. Apify's free plan includes $5 of credit a month, enough for about 3,333 results.

Everything for one keyword: the interest-over-time timeline, interest by region, top and rising related queries (and related topics when Google returns them), plus summary fields. A trending search is also one result.

Yes. Paste explore links such as https://trends.google.com/trends/explore?q=air%20fryer,instant%20pot&geo=US&date=today%2012-m into 'Google Trends URLs'. Each link's terms, location, time range, category and search type are used for that link, and you can mix links with 'Keywords'. A link that is not a Trends explore link, or has an unsupported setting, is skipped and named in the run status; the rest of the run continues.

Google compares at most 5 keywords at once and scales each comparison to its own peak of 100. The Actor puts your first keyword in every group of 5 and rescales each group so that keyword matches across groups, then sets the overall peak to 100. Choose a first keyword of middling popularity: a very rare one gives coarse values, a very popular one pushes small keywords to 0.

With 'Put all keywords on one scale' on, values are relative to every keyword in the run, not to that keyword alone. Turn it off to get each keyword on its own 0-100 scale, exactly like a single search on the Trends page. Google also samples its data, so repeated runs can differ by a few points.

Any country code (US, GB, DE) or sub-region code (US-CA, CA-ON), or empty for worldwide. Region level can be country, sub-region, US metro area (DMA) or city. If Google does not offer the level you chose for that location, the Actor uses Google's default level and says so in the run status.

Rising related queries whose searches grew by more than 5,000% in the period. They are marked growth 'Breakout' and is_breakout true.

Yes. On every 'too many requests' answer it waits with exponential backoff and starts a fresh session; if the datacenter proxy keeps getting limited, the rest of the run moves to Apify's residential proxy. Results already read are kept.

Yes. Give 'keywords' and 'geo'; it works through Apify's MCP server and API.

It reads only public data any logged-out visitor can see: aggregated Google Trends search-interest data. It goes at a polite pace, never logs in and never solves CAPTCHAs. It returns aggregate, anonymous search statistics; no personal data. To have a record removed, open an issue on this Actor's Issues tab; if Google formally asks us to stop, this Actor will stop. You are responsible for using the data lawfully, incl. anti-spam and privacy laws; this is not legal advice.

Nothing for that keyword. Keywords with too little search volume, comparison groups Google kept refusing, and the anchor keyword repeated in later groups are never charged. A run that returns nothing costs only the $0.0075 start fee, and its status message names the keywords that had no data.

Each request is tried up to 8 times with growing waits and a fresh session. After 6 rate limits in a row on the datacenter proxy, the rest of the run moves to Apify's residential proxy. If 3 comparison groups in a row still end blocked, the run stops, keeps every result already read, and names the keywords it could not read.

About 2 to 3 Google requests per keyword at a polite pace, with up to 3 comparison groups running at once. In our test 300 keywords with timelines, regions and related queries took about 12 minutes. If the run nears its timeout, it stops cleanly and keeps the results already read.

No. Keywords are de-duplicated without regard to case, so air fryer and Air Fryer are read once. Keywords longer than 100 characters are skipped and named in the run status.

Yes. Leave Keywords empty and add countries under Trending searches. Each trending search is one result, up to Max trending per country (1 to 1,000, in the order Google's Trending now page lists them), over the past 4, 24 or 48 hours or 7 days.

They summarise the timeline on the same 0-100 scale as its values: the mean over the period, the highest point (with peak_time), and the last complete point. A point for a period still running is marked is_partial in interest_over_time and is not used as the latest value.

Yes. Save the input as a task and add a weekly schedule. Each run reads the full time range again, so compare runs by keyword; Google samples its data, so expect a few points of difference between runs.