Google Trends Reliable API

Fast, structured Google Trends data for SEO, research, content discovery, and market analysis.

This Actor supports two workflows:

• Keyword analysis — compare up to five terms and extract interest over time, interest by region, related queries, and related topics.
• Trending now — fetch current Google trending searches for a selected country.

The Actor is designed to finish cleanly instead of hanging. Temporary Google errors use bounded retries, request timeouts, cookie warm-up, and optional proxy rotation.

Why use this Actor?

Many Google Trends scrapers fail in ways that waste time: endless retries, empty runs with no explanation, inconsistent output, or rate-limit errors.

This Actor is built around predictable behavior:

• Strict input validation before any expensive work starts
• Bounded retries for HTTP 403/408/429/5xx responses
• Configurable per-request timeout
• Cookie/session warm-up before Google Trends API calls
• Optional Apify/custom proxy support
• Normalized dataset rows for JSON, CSV, Excel, and API use
• Clean success with zero rows when Google legitimately returns an empty section
• No browser required for the normal data path

Keyword analysis

Example input:

{
  "mode": "explore",
  "keywords": ["bitcoin", "ethereum"],
  "geo": "US",
  "timeRange": "today 3-m",
  "property": "",
  "includeInterestOverTime": true,
  "includeInterestByRegion": true,
  "includeRelatedQueries": true,
  "includeRelatedTopics": true
}

Supported Google properties:

• Web Search
• Image Search
• News Search
• YouTube Search
• Google Shopping

Common time ranges include today 3-m, today 12-m, today 5-y, and all. Custom Google Trends date ranges can also be supplied.

Trending now

Example input:

{
  "mode": "trending",
  "geo": "US",
  "trendingLimit": 50
}

Trending rows include the search term, approximate traffic, publication time, source URL, image when available, and related news items.

Output

The default Dataset uses normalized row types:

• interest_over_time — one row per time point with values for each compared keyword
• interest_by_region — one row per region with values for each compared keyword
• related_query — top/rising related searches
• related_topic — top/rising related topics when Google provides them
• trending — current trending searches

Google may legitimately omit related topics or other optional sections for some terms. That is treated as a valid empty result, not as a failed run.

Reliability controls

Use requestTimeoutSecs and retries to control how aggressively the Actor waits for Google. Defaults are intentionally conservative: 20 seconds per request and 3 attempts.

If Google rate-limits your traffic, enable proxyConfiguration. The Actor can rotate through multiple Apify/custom proxy sessions between retries.

Important notes about Google Trends data

Google Trends values are normalized interest scores, typically on a 0–100 scale. They are not absolute monthly search volumes.

Comparing multiple keywords in one request is usually preferable to running separate requests because Google normalizes the compared terms against the same time/geo context.

Google Trends is an external service with undocumented internal endpoints. This Actor uses defensive parsing and bounded failures, but Google can change its responses without notice.

Good use cases

• SEO keyword comparison
• Content and editorial research
• Brand or product demand tracking
• Regional market research
• YouTube search trend analysis
• News/topic discovery
• Scheduled trend monitoring
• Data pipelines through the Apify API

Support

If a run fails, include the run ID, input, and the final error message. Do not include private API tokens or proxy passwords in issue reports.