Google Trends API – Bulk Keywords, Compare & Trending Now avatar

Google Trends API – Bulk Keywords, Compare & Trending Now

Pricing

from $0.25 / 1,000 keyword rows

Go to Apify Store
Google Trends API – Bulk Keywords, Compare & Trending Now

Google Trends API – Bulk Keywords, Compare & Trending Now

Google Trends data as clean rows: interest over time, interest by region, top and rising related queries for hundreds of keywords per run. Compare more than 5 keywords on one scale, plus Trending Now by country. pytrends alternative, pay per keyword, no start fee.

Pricing

from $0.25 / 1,000 keyword rows

Rating

0.0

(0)

Developer

Jindrich Klimes

Jindrich Klimes

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

37 minutes ago

Last modified

Categories

Features

Limited permissions

Share

Get Google Trends data as clean rows: interest over time, interest by region and top and rising related queries for hundreds of keywords in one run. Compare more than 5 keywords on one shared scale (Google stops at 5), and pull Trending Now searches with traffic and news for any country. A hosted pytrends alternative: no code, no 429 headaches, export to JSON, CSV or Excel or call it as an API.

What you get

  • Interest over time – the full timeline (0–100) plus ready-made summary columns: average, peak and peak date, latest value, change % and trend direction (rising / falling / stable)
  • Interest by region – countries, states, cities or US metro areas (DMA), highest first
  • Related queries – top and rising, with Breakout flags
  • Compare mode – 2 to 50 keywords on one 0–100 scale, chained through shared anchor keywords, with a rank column
  • Trending Now – today's trending searches per country with approximate traffic, start time, picture and news articles
  • Bulk – up to 500 keywords × up to 50 geos per run; every row also links to the same view on trends.google.com
  • Empty and failed keywords are free – rows with no_data or error are never charged

Modes

ModeUse it forRows
keywordKeyword research, seasonality, regional demand, related queriesOne per keyword × geo, each scaled 0–100 on its own
compareWhich of these keywords is searched most?One per keyword, all on one shared scale
trendingNowWhat is trending right now in the US, CZ, DE …?One per trending search

Input

{
"mode": "keyword",
"keywords": ["matcha", "chai", "oat milk"],
"geos": ["US", "GB"],
"timeRange": "today 12-m",
"includeRegions": true,
"includeRelatedQueries": true
}
FieldDefaultDescription
modekeywordkeyword, compare or trendingNow
keywords—Search terms (500 max in keyword mode, 50 in compare mode). Duplicates are removed.
startUrls—Google Trends explore URLs; keywords, geo, date, category and property are read from each link
geosworldwideCountry codes (US, CZ), sub-regions (US-CA) or empty for worldwide. Trending Now defaults to US.
timeRangetoday 12-mnow 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, all or 2025-01-01 2025-06-30
category0Google Trends category id (cat= in a Trends URL)
propertywebweb, images, news, youtube or shopping
includeRegionstrueAdd interest by region
regionResolutionautoauto, COUNTRY, REGION, CITY or DMA
includeRelatedQueriestrueAdd top and rising related queries
includeRelatedTopicsfalseBest-effort: Google often returns related topics empty for automated requests
maxTrendingItems50Trending searches per country (Google's feed currently lists about 10)
maxSessions2Parallel Google sessions (1–3)
proxyConfigurationApify ProxyDatacenter proxy works well; each session gets its own IP
residentialFallbackfalseRetry a still-rate-limited keyword once through residential proxy

Output

Keyword mode (arrays shortened):

{
"mode": "keyword",
"keyword": "matcha",
"geo": "US",
"time_range": "today 3-m",
"status": "ok",
"average_interest": 72.42,
"peak_value": 100,
"peak_date": "2026-09-05",
"latest_value": 65,
"latest_date": "2026-11-16",
"latest_is_partial": true,
"change_percent": -19.2,
"trend_direction": "falling",
"timeline": [{ "date": "2026-08-16", "value": 93, "is_partial": false }],
"regions": [{ "geo_code": "US-HI", "name": "Hawaii", "value": 100 }],
"related_queries_top": [{ "query": "matcha me", "value": 100 }],
"related_queries_rising": [{ "query": "rok matcha nyc", "value": 10250, "formatted_value": "Breakout", "is_breakout": true }],
"trends_url": "https://trends.google.com/trends/explore?q=matcha&geo=US&date=today+3-m&hl=en-US"
}

Compare mode adds rank, compared_keywords, anchor_keyword, precision and comparison_group. Trending Now rows have geo, rank, title, approx_traffic, approx_traffic_min, started_at, picture and news.

status is ok, no_data (Google has too little search volume for that keyword, geo and time range) or error (with error.code such as rate_limited). A run summary is saved to the OUTPUT record.

Google Trends compares at most 5 terms at a time, and every comparison is rescaled to its own 0–100. In compare mode this Actor first sizes all keywords, sorts them, and then runs batches of 5 that each share one keyword with the previous batch. The shared keyword links the batches, so all values end up on one scale where the biggest keyword peaks at 100. Keywords too small to measure next to much bigger ones are re-measured in a later batch with similar-sized keywords; anything still below Google's resolution is flagged precision: "low".

Paste hundreds of keywords and several countries in keyword mode. Each keyword gets its own 0–100 timeline plus average_interest, change_percent and trend_direction, so you can sort a whole keyword list by momentum in a spreadsheet and spot seasonal peaks. Rising related queries (including Breakout ones) are a quick source of new content ideas.

trendingNow returns Google's Trending Now feed for each country in geos: the search, approximate traffic (e.g. 20000+), when it started, a picture and up to a few news articles. Schedule it hourly or daily on Apify to build your own trend history.

Looking for a pytrends alternative?

pytrends is unmaintained and hits 429 errors quickly. This Actor keeps a cookie session per proxy IP, paces itself to about one request per second, honours Retry-After, backs off, switches to a fresh session after repeated rate limits and retries still-blocked keywords later in the run. You get the same data (interest over time, by region, related queries) as rows, without running Python or managing proxies, and you can call it from any language through the Apify API.

Ready-made example tasks

Open one, check the prefilled input, and run it in one click:

Use cases

  • Keyword and content research: which topics are rising, where and when
  • Product and market research: seasonality and regional demand
  • Brand monitoring: your brand vs competitors on one scale
  • News and social teams: what is trending right now per country
  • Data pipelines and dashboards: scheduled runs, JSON/CSV exports, API access

Pricing

Pay per result: $0.25 per 1,000 keyword rows (about 6 CZK; $0.00025 per keyword × geo, or per keyword in a comparison) and $0.10 per 1,000 Trending Now rows. No start fee. no_data and error rows are free.

  • Example: 500 keywords in 2 countries = 1,000 rows = $0.25
  • Quick test: 20 keywords = $0.005

FAQ

Are the numbers search volumes? No. Google Trends gives relative interest (0–100) within the chosen geo and time range, not absolute searches. Use compare mode to see keywords relative to each other.

Why do my values differ slightly from the website? Google samples its data, so repeated requests can differ by a few points, especially for small keywords.

Why are related topics empty? Google often withholds related topics from automated requests. Related queries are returned reliably; related_topics_available shows whether topics came back.

How fast is it? Roughly 5–6 seconds per keyword per session (several Google requests each, paced to avoid rate limits). With 2 sessions, 100 keywords take about 5 minutes. Turn off regions or related queries to go faster.

How is change_percent calculated? It compares the average of the last quarter of the timeline with the first quarter. For seasonal keywords over 12 months (e.g. last year's Black Friday in the first quarter) use a shorter timeRange or look at peak_date and the timeline.

Why are Wyoming or Kansas at the top of so many US region lists? That is what Google Trends itself returns right now, from every network we tested. A likely cause is automated and data-center search traffic, which weighs heavily in small states. Use regionResolution: "DMA" or compare relative values instead of reading only the first region.

What happens when Google rate-limits? Each session waits (honouring Retry-After), backs off and switches to a fresh cookie and IP. A keyword that is still blocked goes to the back of the queue and is retried after a cooldown, up to two more times. Only then does it return a free error row.

What does no_data mean? Google has too little search volume for that keyword in that geo and time range. These rows are free.

Support

Found a keyword or geo that fails? Open an issue on the Actor page with the input you used.