Google Trends Scraper & Keyword Monitor
Pricing
from $9.00 / 1,000 keywords
Enter keywords, get Google Trends interest over time, related queries and interest by region as flat rows, plus one summary row per keyword: latest value, change vs previous period, change since your last run, spike flag. No browser. Pay per keyword that returns data; no start fee.
Search terms to look up on Google Trends, one per item, in any language. Example: ["bitcoin", "nvidia", "다이소"] (다이소 = Daiso, a Korean retail chain). Write the term as people type it into Google; do not add operators or quotes. Max 100 characters per keyword; duplicates are removed. Each keyword is looked up on its own 0-100 scale unless "Compare keywords" is on. You pay one "keyword" event per keyword and geo that completes with data.
Where the searches come from. "worldwide" (default) or a two-letter ISO country code in upper case: "US", "GB", "DE", "KR" (South Korea), "JP" (Japan), "TW" (Taiwan). Several countries: one string separated by commas, e.g. "US,KR,JP" - every keyword is then looked up (and billed) once per country. A region code such as "US-CA" (California) also works. Country names such as "Korea" are not accepted.
How far back to look. Use exactly one of: "now 1-H" (past hour), "now 4-H" (past 4 hours), "now 1-d" (past day), "now 7-d" (past 7 days), "today 1-m" (past 30 days), "today 3-m" (past 90 days, default), "today 12-m" (past 12 months), "today 5-y" (past 5 years), "all" (2004 - present). The range decides the resolution: past hour / 4 hours = per minute, past day = 8 minutes, past 7 days = hourly, past 30 / 90 days = daily, past 12 months / 5 years = weekly, all = monthly. For daily monitoring use "today 1-m" or "today 3-m"; for hourly monitoring "now 7-d".
Which detail rows to output, as an array. "interestOverTime" (default) = one row per point in time. "relatedQueries" = top and rising related searches (up to 25 each per keyword). "interestByRegion" = one row per country / region with data. Example: ["interestOverTime", "relatedQueries"]. The keywordSummary row (latest value, changes, spike flag) is always output; pass an empty array [] to get only summary rows - the smallest output, good for AI agents. The price per keyword is the same whatever you include.
[ "interestOverTime"]false (default): every keyword gets its own 0-100 scale, where 100 is that keyword's own peak - use this for monitoring. true: keywords are sent to Google in groups of up to 5 (in list order) and share one scale, where 100 is the peak of the most searched keyword in the group - use this to see which keyword is searched more. Google allows at most 5 keywords per comparison; values from different groups, or from compare on and off, are not comparable.
Optional. Two dates as "YYYY-MM-DD YYYY-MM-DD" (start, space, end), for example "2026-01-01 2026-06-30". The start must be before the end. When set, it overrides "Time range".
Optional Google Trends category ID as a string, to narrow an ambiguous word such as "apple" or "jaguar". "0" = all categories (default). Examples: "7" Finance, "18" Shopping, "71" Food & Drink, "44" Beauty & Fitness, "5" Computers & Electronics, "67" Travel. Only the listed top-level categories are accepted.
Name of the key-value store that remembers the latest value of every keyword, so the next run can report the change since your last run and flag spikes. Letters, digits and hyphens, 3-63 characters, e.g. "my-brand-keywords-daily". Runs that use the same name share one history; use different names for separate schedules. Set to an empty string "" to turn the comparison off. Default: "google-trends-monitor-history".
The summary row gets spike = true when the latest value is at least this many percent - and at least 10 points - above the value at your last run (on a first run: above the previous period). Integer from 1 to 1000. Example: 50 flags a rise from 40 to 60 or more. Default 50.
"auto" (default, recommended): datacenter proxies first; retries and any rate-limited stretch go through residential proxies. "datacenter": datacenter proxies only - Google rate-limits a small proxy pool after about 100 keywords. "residential": every request through residential proxies. Proxy traffic is included in the price per keyword.
Optional safety limit: the maximum number of HTTP requests in this run, retries included (integer, minimum 10, e.g. 200). Leave empty for an automatic limit of about 3x what the keywords need. Keywords that do not fit get status "budgetLimited" and are not charged.