Google Trends Scraper
Pricing
from $120.00 / 1,000 keyword results
Google Trends Scraper
Interest over time, interest by region, and related queries from Google Trends. Cookie-primed sessions and proxy rotation for reliable runs.
Pricing
from $120.00 / 1,000 keyword results
Rating
0.0
(0)
Developer
Cassidy Rice
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Pull Google Trends data as clean, structured rows: interest over time, interest by region, and top & rising related queries — for any keyword, region, and timeframe.
Built for runs that actually finish. Google rate-limits Trends aggressively, and most scrapers hand you an empty dataset when it does. This one primes a real browser session before every request and rotates proxy sessions on a 429, so you get data instead of a failed run.
What you get
| Output | What it contains |
|---|---|
| Interest over time | Relative search interest (0–100) at each point in your timeframe, with partial-period flagging |
| Interest by region | Interest broken down by country or sub-region (e.g. US states) |
| Related queries | Top and rising related searches, including Breakout terms |
Input
| Field | Description |
|---|---|
searchTerms | Keywords to look up. Up to 100 per run. |
geo | US, GB, DE, or a sub-region like US-CA. Empty = worldwide. |
timeframe | Preset range, from the past hour to 2004–present. |
customTimeframe | Exact range as YYYY-MM-DD YYYY-MM-DD. Overrides the preset. |
keywordType | Search term (literal text) or Topic (Google's entity — groups spellings, synonyms and languages). |
compareTerms | Off: each term gets its own 0–100 scale. On: all terms share one scale, like the Trends comparison view (max 5). |
category | Trends category ID. 0 = all. |
property | Web, Images, News, YouTube, or Shopping. |
proxyConfiguration | Use residential proxies. This is the single biggest factor in run reliability. |
Example input
{"searchTerms": ["electric bike", "e-bike"],"geo": "US","timeframe": "today 12-m","interestOverTime": true,"relatedQueries": true,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Output
Every row is flat and CSV-friendly, tagged with a resultType.
{"resultType": "interest_over_time","searchTerm": "electric bike","geo": "US","timeframe": "today 12-m","date": "Jun 21","timestamp": 1782000000,"value": 62,"isPartial": false}
{"resultType": "related_queries","searchTerm": "electric bike","bucket": "rising","query": "e bike under 1000","value": 5000,"formattedValue": "Breakout"}
Export as JSON, CSV, Excel, or pull from the API.
Understanding the numbers
Google Trends values are relative, not absolute. 100 is the peak point in your chosen window, and everything else is scaled against it. Changing the timeframe or region changes every number. Trends never reports raw search volume, so these figures show shape and direction, not counts.
With compareTerms off, each term is scaled independently — so a 100 for one term and a 100 for another say nothing about which is bigger. Turn compareTerms on when you need terms measured against each other.
Notes and limits
- Related topics are not offered. Google's related-topics endpoint currently returns an empty list for every caller, entity or not. Rather than ship a switch that silently produces nothing, it's left out. If Google restores it, it'll be added.
- Residential proxies matter. Datacenter IPs get 429'd constantly. The actor retries and re-primes, but residential proxies are what make long runs dependable.
- Very rare keywords legitimately return no data — Trends suppresses low-volume terms.
- Hourly timeframes (
now 1-H,now 4-H) only support short windows and return finer-grained points.
Local development
python3 test_actor.py # offline checks, no networkapify run # needs the Apify CLI