Google Trends Scraper
Pricing
Pay per usage
Reliable Google Trends data: interest over time, interest by region, related queries/topics and daily trending searches, with automatic retries, session/proxy rotation and honest error reporting instead of silent failures.
Up to 5 terms are compared directly in one request (Google Trends' own limit). More than 5 are automatically split into batches that share a common "anchor" term (see anchorTerm) so the 0-100 values stay comparable across batches. Leave empty to only fetch trendingNow.
[ "apify", "web scraping"]Only relevant with more than 5 searchTerms. This term is repeated in every batch and used to rescale the other batches onto the same 0-100 scale. Defaults to the first search term if left blank.
Two-letter country code (e.g. "US", "LV"), a region code (e.g. "US-CA"), or empty for worldwide.
Preset time range, or "custom" to use customTimeframeStart/customTimeframeEnd.
Required when timeframe is "custom".
Required when timeframe is "custom".
Google Trends category ID to restrict results to (0 = All categories). See Google's published category list.
Which Google search vertical to pull trends from.
Search interest over time, as long-format rows (one per term per date).
Search interest broken down by region, as long-format rows (one per term per location).
Granularity for interest-by-region: COUNTRY (worldwide/multi-country geo), REGION (state/province within one country), CITY, or DMA (US media markets only).
Top and rising related search queries per term.
Top and rising related topics per term. Always issues one extra single-term request per term regardless of batching (Google Trends only returns this widget for single-term explores). See README limitations: Google's related-topics widget has been observed returning no data even for popular terms.
Fetch today's trending searches for trendingNowGeo (independent of searchTerms).
Two-letter country code for the trending-now feed.
Google Trends throttles aggressively; using Apify Proxy (residential recommended for larger runs) spreads requests across IPs and makes retries far more likely to succeed. Optional for small/light runs.
{ "useApifyProxy": false}How many times to retry a single Trends request (with exponential backoff + a fresh session/identity) before giving up and recording an error for that piece of data.