Google Trends Scraper & API: interest, regions, related queries
Pricing
from $2.00 / 1,000 search terms
Google Trends Scraper & API: interest, regions, related queries
Scrape Google Trends for any keyword or a comparison of up to 5: interest over time, interest by region, top and rising related queries, in any country, time range, category or Google property. Plus Trending Now searches by country, with their news. $2 per 1,000 terms.
Pricing
from $2.00 / 1,000 search terms
Rating
0.0
(0)
Developer
Spyridon Pikoulas
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 hours ago
Last modified
Share
Google Trends Scraper & API
Get everything Google Trends shows for a search term in one result:
- Interest over time: hourly, daily, weekly or monthly, depending on the time range.
- Interest by region: states, provinces or countries.
- Related queries: both the top ones and the rising ones, for example "+2,300%" or "Breakout".
Put up to five terms on one line to compare them. You then get their interest side by side, and related queries for each.
Any country or region, any time range from the past hour to 2004, custom date ranges, categories, and web, image, news, shopping or YouTube search are all supported.
It also gets trending now: today's trending searches in any country, with approximate traffic and the news behind them.
It costs $2 per 1,000 search terms, and trending searches are $0.50 per 1,000.
What people use it for
- SEO and content: find rising queries before they peak and pick topics with growing demand.
- Market research: compare brands, products or competitors by region and over time.
- E-commerce: seasonality from Google Shopping interest.
- Newsrooms and social media: what is trending right now, and why.
- Data science: Trends time series as a feature for forecasting.
How to use it
{"searchTerms": ["bitcoin", "chatgpt, gemini, claude"],"geo": "US","timeRange": "today 3-m","trendingNow": ["US", "GB"]}
timeRange takes now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m,
today 12-m, today 5-y or all. For exact dates, use customTimeRange, for example
2025-01-01 2025-06-30.
Output
A comparison:
{"type": "search","searchTerm": "chatgpt, gemini, claude","geo": "US","timeRange": "today 3-m","category": 0,"property": "web","interestOverTime": [{"date": "2026-09-25", "chatgpt": 62, "gemini": 29, "claude": 17, "isPartial": false},{"date": "2026-09-26", "chatgpt": 49, "gemini": 23, "claude": 13, "isPartial": true}],"interestByRegion": [{"geoCode": "US-CA", "region": "California", "chatgpt": 56, "gemini": 24, "claude": 20}],"related": [{"term": "claude","topQueries": [{"query": "claude ai", "value": 100}, {"query": "claude code", "value": 67}],"risingQueries": [{"query": "kimi k3", "increase": "Breakout"}],"topTopics": [],"risingTopics": []}]}
A trending search:
{"type": "trending","geo": "GB","title": "police service of northern ireland","approxTraffic": "500+","startedAt": "2026-09-26T09:50:00+00:00","news": [{"title": "Police Federation welcomes ‘sensible precautionary measure’ …", "source": "The Irish News", "url": "https://www.irishnews.com/…"}]}
Use it as an API
One call runs it and returns the results as JSON (for runs under 5 minutes; longer ones start a run and read its dataset). Apify's Python and JavaScript clients, and its Make, Zapier and n8n integrations, work the same way.
curl -X POST "https://api.apify.com/v2/acts/innocent_archipelago~google-trends/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"searchTerms": ["bitcoin", "chatgpt, gemini"], "geo": "US", "timeRange": "today 3-m", "trendingNow": ["US"]}'
Pricing
You pay $0.002 per search term or comparison, which is $2 per 1,000. Trending searches cost
$0.0005 each. A term Google refuses comes back with an error field and costs nothing. Runs that go
through Apify's residential proxy also pay its traffic, $0.0012 per 100 KB. There are no monthly
fees.
Good to know
- Values are Google's relative interest, from 0 to 100, and not search volumes.
- Related topics come back empty: Google's Trends API gave none for any term we tried (September 2026). The fields stay, in case it serves them again.
- Google rate-limits Trends hard. When it refuses the run's IP, the actor switches to Apify residential proxy by itself and retries, with its traffic charged as above. After two terms in a row are refused, the run skips the rest.