Google Trends Scraper - Keywords, Regions & Rising Queries
Pricing
from $1.00 / 1,000 results
Google Trends Scraper - Keywords, Regions & Rising Queries
Scrape Google Trends without an API key. Get interest over time, interest by region, top and rising related queries, related topics, breakout detection, and SEO opportunity scores for Web, News, YouTube, Images, and Shopping.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
Group Oject
Maintained by CommunityActor stats
1
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Scrape real Google Trends data without an API key. Submit keywords in bulk and receive one complete trend report per keyword with interest over time, regional demand, top and rising related searches, related topics, breakout terms, and an actionable SEO opportunity score.
The default HTTP mode uses a persistent Google Trends session and does not launch a browser. Run the Actor from Apify Console, API, schedules, webhooks, or an MCP-connected AI agent, then export results as JSON, CSV, Excel, XML, or RSS.
What you get
- Full interest-over-time timeline with dates and Google's normalized 0-100 values
- Interest by country or subregion, ranked by relative demand
- Top and rising related queries with values, Breakout flags, and Trends links
- Top and rising related topics when Google makes them available
- Web, News, YouTube, Image, and Google Shopping search surfaces
- Time ranges from the past hour through all available history since 2004
- Breakout, rising, stable, declining, volatile, or insufficient-data classification
- Growth, momentum, volatility, confidence, and composite TrendPulse scores
- Content-angle suggestions and a recommended action for every successful keyword
- Error isolation and zero billable dataset records for failed or empty keywords
Quick start
{"keywords": ["chatgpt", "claude ai", "ai agents"],"geo": "US","timeRange": "today 12-m","searchType": "web","includeRelatedQueries": true,"includeRelatedTopics": true}
No API key or proxy is required for the default mode. Start with one to five keywords. For larger jobs, keep the default four-second delay and concurrency of one to reduce Google rate limiting.
Input
| Field | Default | Description |
|---|---|---|
keywords | sample terms | Search terms to analyze |
keywordsText | empty | Newline- or comma-separated bulk keyword input |
geo | US | Google geo code; empty means Worldwide |
language | en | Result language or locale |
timeRange | today 12-m | Past hour, 4 hours, day, week, month, 3 months, year, 5 years, or all history |
category | 0 | Google Trends category ID; 0 means all categories |
searchType | web | web, images, news, youtube, or shopping |
includeRelatedQueries | true | Include top and rising queries |
includeRelatedTopics | true | Include top and rising topic entities |
includeContentAngles | true | Generate deterministic content recommendations |
maxKeywords | 500 | Maximum normalized keywords accepted |
requestDelayMs | 4000 | Delay between keyword reports |
maxConcurrency | 1 | Parallel keyword workers |
fetchMode | http | No-key HTTP, auto, browser, Apify upstream, or SerpApi |
proxyConfiguration | disabled | Optional Apify or custom proxy |
Output
One successful keyword creates one dataset record. A report contains compact fields for filtering and complete nested datasets:
{"keyword": "chatgpt","geo": "US","timeRange": "today 12-m","trendStatus": "rising","trendPulseScore": 78.4,"growthPercentage": 34.2,"latestInterest": 92,"topRegion": "California","regionsCount": 51,"interestOverTime": [{ "time": "2026-08-30T00:00:00.000Z", "value": 92, "formattedValue": "92" }],"interestByRegion": [{ "geoCode": "US-CA", "geoName": "California", "value": 100, "rank": 1 }],"relatedQueriesDetailed": {"top": [{ "query": "what is chatgpt", "value": 100 }],"rising": [{ "query": "chatgpt agent", "value": 450, "isBreakout": false }]},"recommendedAction": "Prioritize now"}
Failed and empty keywords are written to the ERRORS key-value-store record, not the paid dataset. SUMMARY, TOP_RISING_KEYWORDS, TOP_DECLINING_KEYWORDS, RUN_METADATA, and OUTPUT are also saved for automation.
High-value workflows
- Compare regional product demand before choosing inventory or ad markets
- Find rising SEO keywords and breakout content opportunities
- Validate YouTube topics using the YouTube Search surface
- Track brand and competitor demand on a daily or weekly schedule
- Feed current demand signals into dashboards, RAG pipelines, or AI agents
- Identify seasonality from full timelines instead of a single score
Fetch modes
| Mode | API key | Best for |
|---|---|---|
http | No | Recommended fast, low-cost Google Trends reports |
auto | No | HTTP with browser fallback for difficult sessions |
browser | No | Troubleshooting a blocked HTTP environment |
serpapi | Yes | Buyers with an existing SerpApi account |
apify-scraper | No | Buyers allowed to call Apify's upstream Trends Actor |
The HTTP provider warms a cookie session and keeps the same request identity across the Explore and widget endpoints. A proxy can help some high-volume workloads, but rotating IPs between widget requests can invalidate the session, so the Actor uses a sticky proxy session when enabled.
Pricing
The Actor is priced per successful trend report, not per timeline point or regional row. One report can contain dozens of dates, regions, and related searches. Use Apify's maximum charge control and maxKeywords to cap a run.
Limitations
Google Trends values are relative indices, not absolute search volumes. A value of 100 is the peak for the selected keyword, geography, surface, and time range. Compare values only within a compatible Google Trends request.
Google can change or rate-limit its public endpoints. The Actor retries transient failures and isolates per-keyword errors, but very large runs should use conservative concurrency and delay settings. Related topics can be empty when Google does not provide that widget data.
This Actor accesses publicly available trend data. Use it in accordance with applicable law, Google policies, and Apify's platform rules.