Pull Google Trends signals as structured JSON — interest-over-time series, related and rising queries, and the geographic breakdown of search demand for any term.
Google Trends reports relative search interest rather than result links, returning a normalized 0-to-100 interest-over-time series, related and breakout queries, and a region-by-region demand map for each term. The Google Trends Scraper API resolves these series, the rising-topics list, and the geo breakdown into validated JSON keyed to your keyword and timeframe.
Demand forecasters, trend analysts, and content strategists use this data to spot rising interest early and compare demand across markets. Set the timeframe and category, target a country or sub-region, schedule recurring pulls, and diff snapshots to watch momentum build or fade across terms.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.googletrends.com/search?q=structured+web+data",
"geo": "us",
"device": "desktop"
}'
// ← response
{
"status": "ok",
"data": {
"query": "structured web data",
"organic": [
{ "position": 1, "title": "…", "url": "https://…", "snippet": "…" }
],
"features": { "ads": 3, "answer_box": true }
}
}Google Trends data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Interest-over-time demand forecasting
Rising and breakout query discovery
Cross-region search-demand comparison
Keyword momentum monitoring over time
We return the normalized 0-to-100 interest-over-time series, related and rising or breakout queries, and the region-by-region interest breakdown for your term and timeframe.
Yes. You can scope a term to a country or sub-region and pull the geographic breakdown, making cross-market demand comparison straightforward.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.