Google Trends Scraper — Google Trends Data, Interest Over Time
Pricing
from $2.25 / 1,000 trend reports
Google Trends data as JSON: interest over time, related queries and region breakdown by default; compare, related topics (billed as its own report) and trending now on request. One row per keyword and surface, API and MCP ready. No start fee, no minimum, never charged for a failed or empty fetch.
Keywords to look up, one per entry, e.g. ["bitcoin", "ethereum"] — up to 300 per run. A failed, blocked or empty fetch is never charged; it is named in the run's ERRORS record. Leave this empty and set "Category ID" instead and the run explores that whole category rather than a keyword. Send more than 300 and the run still starts: it uses the first 300 and writes one uncharged row saying what you asked for and what bound it, so run the rest separately. Each term is fetched independently unless Compare is on. Pricing: you are billed at most one trend report per term — one keyword's full timeline, its complete related-queries set and its region table settle together as ONE report, however many of those three you ask for, so all three cost the same as one. Related topics is a separate event, billed on its own. Omit the field entirely (an API call with no input) and the run takes a real, small sample instead — one example keyword ("bitcoin") on the three default surfaces, worldwide, over the last 12 months, inside a three-minute window, charged like any run at one trend report. Change a setting but still leave this empty and you get that SAME live sample, run under what you set — your location, time range, category, search property and choice of surfaces — with one uncharged note naming the settings it ran under. The one thing it cannot do is compare, which needs 2-5 of your own terms: that asks you for search terms on an uncharged row instead.
Which Trends surfaces to fetch per term. Defaults to the three shown. A category-only run (a category with no search terms) is served interestOverTime and relatedQueries only — Google offers no region table and no topics without a search term, and the run ships one uncharged row naming what it left out. relatedQueries is the surface Google most often has nothing for: it is computed only where a term carries enough search volume, so lower-volume keywords — and any keyword narrowed to a smaller region or a shorter time window — frequently have none at all. That is an honest no-data answer rather than a fault: the keyword is named in the run's ERRORS record, nothing is charged for it, and re-running the same term returns the same answer. interestOverTime is charted for terms far below the level related queries needs, so keep it selected and a term with no related queries still comes back with its trend line. relatedTopics is opt-in — add it to also get the top + rising topic entities (with knowledge-graph ids) for each term. Google serves its topics feed to a limited number of lookups at a time, so this one surface can come back empty on a busy moment: it is never charged when it does, and a re-run a minute or two later normally delivers.
[ "interestOverTime", "relatedQueries", "interestByRegion"]Scores 2-5 terms on one shared 0-100 scale, exactly like the Trends UI compare view. Related queries are per-term and therefore unavailable in compare mode.
ISO country/region code, e.g. US, GB, US-CA, DE. Leave empty for worldwide. A country's three-letter code (IND), English name (India) or its own name in its own language (Deutschland) is read too, and the run tells you on an uncharged note row which market it used. Region codes are passed to Google exactly as typed.
A Google preset — now 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 a custom range like 2025-01-01 2025-06-01. Shorthand that names one preset, like 12m or 7 days, is read as that preset.
Google Trends category ID. Set it with NO search terms and the run explores that category itself — Google's own category view, billed as ONE trend report: the interest-over-time series and the top 25 and rising 25 queries for the whole category. Interest by region and related topics are not served without a search term, and one uncharged row says so. Set it beside search terms and it simply narrows them. Common IDs: 7 Finance, 45 Health, 12 Business, 16 News. 0 = all categories.
Which Google property to measure interest on.
Also fetch the current trending searches for a country (at most 1 trend report per trend returned, with traffic estimate and news links). A trending feed has no keyword to belong to, so each trending row is its own report rather than riding on a keyword's.
Country code for trending now, e.g. US, GB, SA, JP. A three-letter code (IND), the country's English name (India) or its own name in its own language (Deutschland) is read too, on an uncharged note row naming the market used.