Google Trends APIFetch Google Trends interest and breakout queries as structured JSON with one SocialCrawl API key. Same success envelope and credit model as every other platform. Reads are priced in credits.
2 active endpoints. Advanced tier, 5 credits each.
Two live read endpoints for public Trends signals. Head-to-head interest over time for up to five keywords, plus rising and top related queries for a single term. Data API only. No Trends UI session, no unofficial scraper stack.
/v1/google_trends/exploreCompare 1-5 keywords as CSV. Returns series of dated 0-100 points per keyword plus per-keyword averages. Scope with location, timeframe, and category. Values are relative within the request set.
keywords (1-5 CSV), location, timeframe, category
/v1/google_trends/risingExpand one keyword into rising breakouts and top related queries. Rising rows carry growth percent. Top rows use a 0-100 relative value. Pair with explore to size a trend and find drivers.
keyword, location, timeframe
Returns Google Trends interest over time for up to five keywords: dated points scored 0 to 100 per keyword, plus each keyword's average over the window.
Use it to size a search term or compare several terms head to head over a chosen period, region, and category.
keywords · 1-5 comma-separated keywords (e.g. 'reverse audio,voice changer'). With multiple keywords the 0-100 values are normalised across the set for direct comparison.
$ curl https://www.socialcrawl.dev/v1/google_trends/explore?keywords=uv+index&timeframe=past_90_days \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key — hit "Try it" to see an example responseGoogle Trends is a normal SocialCrawl surface. You call GET /v1/google_trends/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second Trends vendor key. No OAuth.
Send your key in the x-api-key header. The same key works for social reads, Universal Search, Tavily, and the rest of the catalog.
Both routes are GET. Pass keywords (1-5 CSV) on explore, or a single keyword on rising. Optional location, timeframe, and category (explore) are validated before charging.
Each live miss costs 5 credits (advanced tier). Cache hits cost 0. Empty or hard failures refund. Bad params return 400 with no charge.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Explore and rising land as Analytics payloads under data.
Most products size a keyword set first, then pull breakouts for the winners, then re-run explore with a tighter location or window.
GET /v1/google_trends/explore?keywords=…series[] and averages[] for 1-5 keywords
Relative 0-100 scores show which term leads in the window.
GET /v1/google_trends/rising?keyword=…rising[] growth and top[] related queries for one keyword
Drivers and adjacent language sit next to the interest curve.
GET /v1/google_trends/explore?keywords=…&location=…Same explore shape filtered by location (and optional timeframe)
Country or region views catch demand that global windows hide.
GET /v1/google_trends/explore
?keywords=chatgpt,claude
&timeframe=past_12_months
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/google_trends/rising?keyword=electric+vehicles{
"success": true,
"data": {
"series": [],
"averages": []
},
"credits_used": 5,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Both endpoints use the Analytics archetype. Field names stay stable so dashboards and agents do not relearn a Trends-only schema.
series[] per keyword with dated points { date, value }; averages[] mean score per keyword over the window
rising[] breakout queries with growth percent; top[] related queries with 0-100 relative value
Same request lifecycle as every other /v1 platform endpoint. Google Trends is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds google_trends/explore or google_trends/rising. Keyword count and format checks run first. Invalid input returns 400 with no charge. Valid calls debit 5 credits atomically before upstream work.
A deterministic cache key is built from platform, resource, and params. Hit: return immediately, credits_used = 0. Miss: live DataForSEO Google Trends explore. Typical billed refresh is a few seconds. Exact repeats may hit the short search cache.
Upstream Trends payload is mapped into the Analytics shape (series and averages, or rising and top), wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
Google Trends is public search-interest analytics. We normalize it into SocialCrawl Analytics so your code does not own a separate DataForSEO client.
Relative search interest and related-query breakouts. Research, demand sizing, and content planning. Not absolute search volume and not Google Ads auction data.
DataForSEO Google Trends Explore in live mode. Synchronous server-side call. You never hold DFS credentials for these two routes.
A unified JSON envelope: success, data, credits_used, request_id, cached. Explore returns series and averages. Rising returns rising and top related buckets.
No Trends UI automation. No multi-keyword related-queries on rising (upstream is single-keyword). No write or alert endpoints.
The jobs this API is most often used for.
Keyword comparison and breakout discovery
Callers run explore on short keyword sets, then rising on the winning term. Location-scoped re-runs show up when global windows are too coarse. Two Trends primitives on the same SocialCrawl key and envelope. Head-to-head explore plus breakout rising without a second vendor integration.
Billed DataForSEO refreshes typically take a few seconds (often 3-8s). Exact repeats may serve from the short search cache at 0 credits.
The jobs Google Trends data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Common ways teams put this data to work, and the stack each one tends to run.
Compare candidate topics with explore, then rising for adjacent queries before committing to a brief.
Track relative interest by location and timeframe. Export series into dashboards next to social volume.
Agents call explore then rising in one workflow. Same key as Universal Search and social reads.
Each live Trends call is 5 credits. Cache hits are free. Explore takes 1-5 keywords. Rising takes one keyword.
curl "https://www.socialcrawl.dev/v1/google_trends/explore?keywords=chatgpt,claude&timeframe=past_12_months" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/google_trends/rising?keyword=electric+vehicles" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Google Trends data, two very different paths. Auth, rate limits, schema, and cost — side by side.
| Feature | SocialCrawl | Scraping Google Trends yourself |
|---|---|---|
| Access | One GET request returns structured JSON | No official API; scrape the site or export CSVs by hand |
| Keyword comparison | Up to 5 keywords, scores normalised across the set | Manual compare-view exports, one screenshot at a time |
| Rising queries | Breakout list with growth percentages in the response | Fragile DOM scraping that breaks on layout changes |
| Freshness | Current public results; billed refreshes typically take 3-8 seconds, exact repeats may use the 2-minute cache | Whenever your scraper last survived |
| Pricing | Advanced-tier credits, one balance across 48 platforms | Proxy and maintenance costs plus blocked-request retries |
Access
Keyword comparison
Rising queries
Freshness
Pricing
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl