Google Trends Scraper — Interest, Regions & Related Queries

🔗 Part of the Apify actors collection — 6 reliable, tested scrapers & data tools.

Export Google Trends data as clean, flat JSON / CSV / Excel — three capabilities over public, aggregated, anonymous data (mostly 0–100 interest indices; see Reading the values), no login:

• interest_over_time — how popular keyword(s) are over a time range
• interest_by_region — how popular keyword(s) are by geography
• related_queries — top & rising related searches for a keyword

Every record carries its query context (geo, timeframe, category) and a real ISO-8601 timestamp, so the output drops straight into a dashboard, a database or an AI agent — no post-processing.

Quick start

Set keywords, pick a mode, run:

{ "mode": "interest_over_time", "keywords": ["bitcoin", "ethereum"], "timeframe": "today 12-m", "geo": "US" }

Input reference

Field	What it does
mode	interest_over_time · interest_by_region · related_queries
keywords	Terms to analyze (max 200; extras ignored). For interest_over_time / interest_by_region, up to 5 share one 0–100 scale per request; more are split into groups — values are only comparable within the same chunkGroup (see Output). related_queries queries each keyword on its own.
timeframe	today 12-m, today 5-y, now 7-d, or YYYY-MM-DD YYYY-MM-DD.
geo	Two-letter country code (US, PL) — empty = worldwide.
category	Google Trends category id (0 = all categories).
maxItems	Cap on delivered records (0 = up to the safety limit of 50 000). Enforced — a run stops at this many records.
onlyNew	Emit only records not seen in previous runs with the same input — turns any scrape into a change monitor / alert.
stateKey	Optional explicit key for the onlyNew memory store (else derived from the input).
proxyConfiguration	Proxy for the requests. A RESIDENTIAL proxy is strongly recommended — Google blocks datacenter IPs (HTTP 429), so without one most runs will be rate-limited.

Output

Flat records, one per data point. Examples:

{ "mode": "interest_over_time", "keyword": "bitcoin", "timestamp": 1700000000,
  "date": "2023-11-14T22:13:20+00:00", "formattedDate": "Nov 14, 2023", "value": 78,
  "chunkGroup": 0, "geo": "US", "timeframe": "today 12-m", "category": 0 }

{ "mode": "interest_by_region", "keyword": "bitcoin", "geoName": "Poland", "geoCode": "PL",
  "value": 64, "chunkGroup": 0, "geo": "US", "timeframe": "today 12-m", "category": 0 }

{ "mode": "related_queries", "keyword": "bitcoin", "related_query": "bitcoin etf",
  "value": 250, "formattedValue": "+150%", "rank_type": "rising",
  "chunkGroup": 0, "geo": "US", "timeframe": "today 12-m", "category": 0 }

Reading the values:

• value for interest_over_time / interest_by_region and for rank_type: "top" is a 0–100 index, comparable only within the same chunkGroup (Google rescales each group of ≤5 keywords independently).
• For rank_type: "rising" value is a growth figure that can exceed 100; formattedValue may read "Breakout" for very large spikes.

Download from the run's Dataset tab as JSON, CSV, Excel, or pull via the Apify API.

Monitoring (onlyNew)

Set onlyNew: true and schedule the run — each run returns only data points unseen since the previous run with the same input. Wire it to related_queries for rising-trend alerts on a timer.

Notes & fair use

• Data is public, aggregated and anonymous (interest indices, not personal data). This actor uses Google Trends' public endpoints and does not log in or bypass access controls.
• Google blocks datacenter IPs — use a RESIDENTIAL proxy for reliable runs (see proxyConfiguration). The actor backs off on HTTP 429 automatically.
• You are responsible for using exported data in line with Google's terms and applicable law.