Use a Google Trends API — an API for Google Trends data — to track search demand, trending terms, interest over time, regional interest, related and rising queries, plus Google Suggest discovery, as structured JSON for demand research and trend monitoring.
Structured output
Use Crawlora's Google Trends API to collect public search-demand data — interest over time, interest by region, related and rising queries, and trending terms — without maintaining your own scraper, proxy routing, retries, or response normalization layer. The endpoints return structured JSON for keyword demand research, content planning, market trend dashboards, and AI workflows.
SERP workflows
Crawlora helps teams measure how search interest changes over time and across regions, discover rising and top related queries, and feed demand signals into content, SEO, and market-research workflows.
SERP monitoring workflowsRequest schema
These parameters come from the active Google Trends explore data catalog entry.
| Parameter | Type | Required | Description | Example |
|---|
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"keywords": [
"chatgpt"
],
"geo": "US",
"time_range": "today 12-m",
"type": "web",
"interest_over_time": [
{
"time": "1777075200",
"formatted_time": "Apr 2026",
"values": [
{
"keyword": "chatgpt",
"value": 87,
"formatted_value": "87",
"has_data": true
}
]
}
],
"top_queries": [
{
"keyword": "chatgpt",
"items": [
{
"query": "chatgpt login",
"value": 100,
"formatted_value": "100"
}
]
}
],
"rising_queries": [
{
"keyword": "chatgpt",
"items": [
{
"query": "chatgpt alternatives",
"formatted_value": "Breakout"
}
]
}
]
}
}Endpoint catalog
/google/suggestReturns Google autosuggest query completions from the public unauthenticated suggest JSON endpoint.
/google/trends/categoriesReturns supported top-level Google Trends category ids and labels for Trending Now category filters.
/google/trends/enumsReturns supported Google Trends enum values for explore/trending filters, including locations, date ranges, search types, categories, statuses, and sort modes.
/google/trends/exploreReturns normalized Google Trends keyword analytics from internal Trends widget requests: interest over time, interest by region, related queries, and related topics when available.
/google/trends/explore/interest-by-regionReturns only the interest-by-region widget from the Google Trends Explore widget flow. Supports multiple comparison terms and returns an empty interest_by_region array when Google returns no rows.
/google/trends/explore/interest-over-timeReturns only the interest-over-time timeline from the Google Trends Explore widget flow. Supports multiple comparison terms.
Managed execution
Crawlora wraps request handling, proxy-aware collection, response parsing, and documented error behavior behind a stable API surface for supported public Google Trends and Suggest pages.
Endpoint-specific request logic for Google Trends explore, trending, categories, and locations data
Google Suggest query-completion endpoint in the same group
Proxy-aware collection and retry-aware execution where supported
Normalized JSON responses with Playground-tested examples
Credit-based usage tied to documented endpoint costs
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML.
Build or buy
Use this comparison to decide whether to maintain scraping infrastructure internally or call a managed endpoint.
| Requirement | Building internally | Crawlora |
|---|---|---|
| Proxy rotation | Buy, test, rotate, and monitor proxy pools. | Use managed proxy-aware collection where supported. |
| Parser maintenance | Maintain Trends request signing and parsing as Google changes. | Use endpoint-specific parsers maintained behind the API. |
| Schema normalization | Design and version your own response model. | Receive documented JSON fields from the catalog. |
| Retries and error classification | Classify rate limits, empty responses, and upstream failures yourself. | Receive documented errors for unusable upstream responses. |
| Endpoint docs | Write and maintain internal API documentation. | Use generated Docs pages from the active endpoint catalog. |
| Playground testing | Build a test console for developers. | Test the same endpoints in Playground before shipping. |
| Usage billing | Create your own metering and limits. | Use credit-based usage and plan limits. |
| Monitoring | Instrument request volume and failures from scratch. | Use Crawlora's documented status and usage workflow. |
Google's official Google Trends API launched in 2025 but remains in application-gated alpha with limited quotas, so it is not generally available; the unofficial pytrends wrapper is unmaintained and breaks. Crawlora provides structured public web data extraction endpoints for supported Google Trends and Suggest pages as a no-waitlist JSON alternative. Data may be delayed, normalized, or change when upstream pages change. Customers are responsible for ensuring their use complies with applicable laws, third-party rights, platform terms, and Crawlora terms.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Pair search-demand data with Google SERP rank tracking.
OpenAdd Bing SERP data to cross-engine monitoring workflows.
OpenAdd Brave Search results to discovery and monitoring workflows.
OpenTrack keyword rankings, result changes, and search visibility.
OpenBuild keyword tracking dashboards from recurring search result snapshots.
OpenCheck keyword positions and ranking URLs with structured result snapshots.
OpenInterest over time, rising and top queries, and trending terms via API, with runnable code.
OpenReview plans, credits, limits, and usage options.
OpenBrowse the full active endpoint catalog.
OpenFAQ
Answers for developers evaluating Crawlora for supported public search result pages.
Yes. Crawlora provides Google Trends endpoints — including explore (interest over time, interest by region, related and rising queries), trending, categories, and locations — for supported public Google Trends pages, returning normalized JSON through documented API routes.
Google launched an official Google Trends API in 2025, but it is in restricted alpha — application-only, with limited quotas and endpoints — so most developers cannot get access yet, and the long-used pytrends wrapper is unofficial and breaks often. Crawlora provides structured public Google Trends data as normalized JSON now, with no waitlist, as an alternative for developers who need Trends data today.
Google's official Trends API is in application-gated alpha, so there is no general Google Trends API key to sign up for yet. With Crawlora you use your Crawlora API key (sent as the x-api-key header) to call the Trends explore, trending, categories, and locations endpoints right away.
The catalog includes explore data (interest over time, interest by region, related topics, rising and top queries), trending-now terms and detail, categories, locations, and enum metadata where supported, plus the Google Suggest query-completion endpoint in the same group.
The explore endpoints accept keywords, geo (region), hl (language), time_range, category, property, and type. Trending endpoints accept geo, window, time_range, category, sort_by, and limit.
Yes. Teams use it to measure keyword demand over time, compare interest across regions, discover rising queries, and plan SEO and content. Pair it with the Google Search API and SERP monitoring use case to connect demand with rankings.
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML. Customers should handle errors, retries, and upstream availability changes in their integrations.
Test the Google Trends explore endpoint in Playground, inspect the current response schema in Docs, and compare credit-based usage on the pricing page.