Google Trends Scraper
Pricing
from $1.99 / 1,000 search results
Google Trends Scraper
Scrapes Google Trends for any keyword. Extracts the full set of trends-vertical fields: interest-over-time / interest-by-region, related queries / topics / articles, value, percentage, rank, delta, growth rate, breakout flag, suggestions, time range, geo, category, and more.
Pricing
from $1.99 / 1,000 search results
Rating
0.0
(0)
Developer
Search API
Maintained by CommunityActor stats
0
Bookmarked
10
Total users
6
Monthly active users
12 days ago
Last modified
Categories
Share
Extract source-backed structured data from Google Trends Explore: interest over time, interest by region, related queries, and related topics. The Actor does not substitute ordinary Google web results when Trends data is unavailable.
Modes
single: collect onequery.batch: collectqueryplus up to 19 deduplicatedqueriesconcurrently.dataTypes: choose any ofinterestOverTime,interestByRegion,relatedQueries, andrelatedTopics.
The global maxItems limit is divided fairly across queries and available data types. Timeline samples span the complete requested date range, while related-query samples include both top and rising terms when Google exposes them.
Input
| Field | Purpose | Default |
|---|---|---|
query | Keyword or topic | required |
mode, queries | Single or multiple independent searches | single |
dataTypes | Structured Trends widgets to collect | all four |
geo | Two-letter country code; empty means worldwide | US |
language | Google locale | en-US |
timeRange | Preset Google time window | today 12-m |
startDate, endDate | Optional custom YYYY-MM-DD range | — |
category | Google Trends category ID | 0 |
searchType | web, images, news, shopping, or youtube | web |
maxItems | Global record limit | 100 |
maxConcurrency | Parallel query jobs | 2 |
maxRequestRetries | Temporary-error retries | 2 |
requestTimeoutSecs | Per-endpoint timeout | 45 |
timezoneOffsetMinutes | Trends timezone offset | 0 |
proxyConfiguration | Apify or custom proxy configuration | optional |
Example:
{"mode": "batch","query": "artificial intelligence","queries": ["machine learning"],"dataTypes": ["interestOverTime", "interestByRegion", "relatedQueries"],"geo": "US","timeRange": "today 3-m","maxItems": 60,"maxConcurrency": 2,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"],"countryCode": "US"}}
Output
The dataset schema defines 38 possible fields. Normal records include the shared query, result, and provenance fields, plus only the type-specific values available in the returned Google Trends widget; absent optional values are omitted. Every normal record has at least 21 populated fields, with no placeholder values added to meet that count. Type-specific fields include:
- Timeline:
date,formattedTime,hasData,isPartial. - Region:
rank,geoCode,geoName. The rank follows the numbered order shown in the Google Trends region panel. - Related query/topic:
rank,rankType,growthPercentage,isBreakout,topicId,topicType.
Optional values not supplied by Google are omitted instead of stored as null, empty strings, or fabricated defaults. Widget tokens, request signatures, cookies, proxy credentials, and raw API responses are never stored.
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Proxy behavior
Direct datacenter traffic can receive HTTP 429. For production Apify Cloud runs, use RESIDENTIAL or an authorized custom proxy. The specialized GOOGLE_SERP group is suitable for Google Search result pages, but Google Trends widget endpoints return HTTP 400 through that group, so it is not the right transport for this Actor.
The Actor validates status codes and content types before parsing, preserves cookies for each query, retries only temporary failures with bounded backoff, and never attempts to solve CAPTCHA or bypass authentication/access controls.
Performance
A representative single query with four requested data types completes in a few seconds of application time. A two-query batch normally completes well below three minutes, subject to proxy and target latency.