Google Trends Scraper - Reliable Trends Data API

Reliable Google Trends data API for interest over time, related queries, and interest by region — with consistent cross-query scaling and no charges for empty results. Built for teams who got burned by Trends scrapers that break silently, never retry, and bill you for blank rows.

Compare up to 5 search terms on one valid 0–100 scale, export to CSV/JSON/Excel, or pull via API into n8n, Make, and Zapier. No coding required.

🆚 Why Choose This Google Trends Scraper?

	This Actor	Typical Trends Scrapers
Retries & backoff	✅ Automatic, residential IP rotation	❌ Fail on first 429
Charges for empty results	✅ Never — no_data rows are free	❌ Bill you for blanks
Cross-term scaling	✅ All terms in one request (valid)	❌ Separate requests (invalid)
Browser-grade requests	✅ Real TLS fingerprint, gets through	❌ Plain HTTP, blocked
Null-free output	✅ Empty arrays, never null	❌ Inconsistent shapes

✨ Key Features

• Interest over time — normalized 0–100 search interest as a clean time series.
• Related queries — top and rising queries (rising = early demand signal).
• Interest by region — per-country/region interest, sorted high to low.
• Consistent scaling — compare up to 5 terms on one shared 0–100 scale.
• Reliability first — retries, exponential backoff, country-matched residential proxies.
• Fair billing — you only pay for terms that return real data.

🎯 Use Cases

SEO & Content Strategy

{
  "searchTerms": ["ai writing", "ai seo"],
  "geo": "US",
  "timeRange": "today 12-m",
  "dataTypes": ["relatedQueries"]
}

Result: Spot rising queries before they peak and build content around real, growing demand.

Market Research & Brand Comparison

{
  "searchTerms": ["nike", "adidas", "new balance"],
  "geo": "US",
  "timeRange": "today 5-y",
  "dataTypes": ["interestByRegion"]
}

Result: Compare brands on one valid 0–100 scale and see where each is strongest by region.

Product Validation & Trading Signals

{
  "searchTerms": ["bitcoin", "ethereum"],
  "geo": "",
  "timeRange": "today 3-m",
  "dataTypes": ["relatedQueries"]
}

Result: Track worldwide attention and momentum for tickers, products, or themes over time.

📥 Input Configuration

Parameter	Type	Default	Description
searchTerms	array (1–5)	["coffee","tea"]	Required. Terms to fetch/compare.
geo	string	"" (Worldwide)	Location: Worldwide, a country, or a region code (e.g. US-CA).
timeRange	string	today 3-m	now 1-d … today 5-y, or all (since 2004).
category	string	0 (All)	Restrict to a Google Trends category.
dataTypes	array	both	relatedQueries, interestByRegion. Interest over time is always included.
customTimeRange	string	–	(Advanced) Overrides timeRange, e.g. 2024-01-01 2024-06-30.
language	string	en-US	Locale for labels and date bucketing.
proxyConfiguration	object	residential	(Advanced) Defaults to country-matched Apify residential proxies.

Why max 5 terms? Google Trends only normalizes up to 5 terms together in a single request. Comparing terms across separate requests is not statistically valid, so this actor caps at 5 by design — your comparisons stay meaningful.

📤 Output Schema

One flat record per search term. No field is ever null — missing data is an empty array, and numeric summaries default to 0 (the status field tells you which).

{
  "searchTerm": "coffee",
  "geo": "US",
  "geoLabel": "United States",
  "timeRange": "today 12-m",
  "category": 0,
  "status": "ok",
  "scalingBasis": "Values are normalized 0-100 across all compared terms (coffee, tea) over today 12-m. Cross-term comparison is valid because every term was fetched in a single request.",
  "interestOverTime": [{ "date": "2025-07-06", "value": 71 }],
  "averageInterest": 69.5,
  "latestInterest": 68,
  "relatedQueries": {
    "top": [{ "query": "iced coffee", "value": 100, "link": "https://trends.google.com/trends/explore?q=iced+coffee" }],
    "rising": [{ "query": "coffee near me", "value": "Breakout", "link": "https://trends.google.com/trends/explore?q=coffee+near+me" }]
  },
  "interestByRegion": [{ "geoName": "Hawaii", "geoCode": "US-HI", "value": 100 }],
  "scrapedAt": "2026-06-30T12:00:00.000Z"
}

Field	Type	Description
searchTerm	string	The term this record reports on.
geoLabel / geo	string	Human-readable location / geo code.
timeRange	string	Time range used.
status	string	ok (has data, billed) or no_data (free, never charged).
scalingBasis	string	What the 0–100 values are normalized against.
interestOverTime	array	{ date, value } time series (0–100).
averageInterest / latestInterest	number	Mean and most-recent interest (0 if no data).
relatedQueries	object	{ top[], rising[] } with query, value, link.
interestByRegion	array	{ geoName, geoCode, value }, sorted high to low.

📊 Dataset Views

The run page ships three ready-made views: Overview (key columns), Interest Timeline (one row per date for charting), and Full Data.

💰 Pricing

Pay per result. You are charged once per term that returns real interest-over-time data — so a successful 5-term comparison is 5 results. Empty (no_data) terms and failed runs are never charged. Standard Apify platform usage (compute + residential proxy bandwidth) is billed separately by Apify.

🛡️ Reliability & Anti-Blocking

Google Trends rate-limits and fingerprints aggressively. This actor is built to get through:

• Browser-grade requests with a real TLS fingerprint (not plain HTTP that Google blocks).
• Country-matched residential proxies — the exit IP matches your geo, which Google blocks far less.
• Automatic retries with exponential backoff and a fresh IP per attempt, so transient 429s recover instead of failing.
• Single-request comparison keeps your 0–100 scale valid across terms.
• Schema canary — if Google changes its internal API, the run fails loudly (and free) instead of returning empty rows.

📅 Recommended Scheduling

Use Apify Schedules to track trends over time:

• SEO/content: weekly, with relatedQueries to catch rising terms early.
• Market research: monthly brand comparisons on today 12-m.
• Trading signals: daily on now 7-d for short-term momentum.

❓ FAQ

Is this legal? It accesses the same public Google Trends data your browser sees. You are responsible for complying with Google's Terms and applicable law.

Why do I need residential proxies? Google Trends throttles datacenter IPs within a few requests. Country-matched residential IPs are what keep runs reliable.

Can I compare more than 5 terms? No — Google only normalizes 5 terms together. Comparing across requests is invalid, so the actor caps at 5 to protect your data quality.

What happens when a term has no data? You get a record with status: "no_data" — and you are not charged for it.

Can I use this with n8n, Make, or Zapier? Yes. The flat, null-free output maps cleanly into automation tools, Google Sheets, and BigQuery.

🔗 Related Actors

Actor	Description
Reddit Scraper Pro	Posts, comments & sentiment for audience and demand research.
Event Scraper Pro	Multi-platform event aggregation with webhooks.

---

🏷️ SEO Keywords

google trends scraper, google trends api, google trends data, scrape google trends, google trends api alternative, interest over time api, related queries scraper, rising queries, interest by region, keyword trend data, search trends api, google trends export csv, google trends json, pytrends alternative, serpapi google trends alternative, market research api, seo trend analysis, product validation data, google trends automation, n8n google trends, google trends scheduler

---

📬 Custom Solutions & Enterprise

Need a custom data feed, modified output, or enterprise integration?

Contact: Furkanc58@gmail.com

• Daily/weekly data feeds (Snowflake, S3, BigQuery, Google Sheets)
• Custom scrapers for platforms not yet covered
• White-label solutions for agencies
• Priority support and SLAs

Response within 24–48 hours.

Leave a review

Is this actor saving you time? A quick review on the Store helps other people find it — and tells us which fields to add next. Rate this actor →

Legal Disclaimer

This actor is a general-purpose tool for analyzing publicly accessible web data. The user bears sole responsibility for ensuring their specific use complies with applicable laws (including GDPR/DSGVO and copyright law), the target website's Terms of Service, and Apify's Terms of Service. The provider (webdatalabs) expressly disclaims liability for any unauthorized or unlawful use.

---

This tool is not affiliated with or endorsed by Google. "Google Trends" and "Google" are trademarks of Google LLC. All trademarks belong to their respective owners.