Google Trends Scraper

Get Google Trends data as clean JSON: interest over time, interest by region, related queries, and related topics — for up to 100 search terms per run, any country, any time range, web/YouTube/news/images/shopping.

Built for one thing above all: runs that finish. Google rate-limits Trends aggressively, and most Trends scrapers fail a large share of their runs because of it. This actor treats reliability as the product:

• 🔄 Automatic session rotation — every retry gets a fresh browser fingerprint, fresh cookies, and (on the platform) a fresh proxy IP.
• ⏳ Exponential backoff with jitter instead of hammering until blocked.
• 🧩 Per-term isolation — one blocked keyword never kills the other 99. You get every result that could be fetched, plus an honest RUN_SUMMARY listing anything that couldn't.
• 🚫 No fake successes — a run that produced zero data exits as FAILED, so your monitoring and schedules can trust the run status.

What you get

Data type	Description
Interest over time	The Trends curve (0–100) at the finest resolution Google offers for your range: hourly, daily, or weekly points
Interest by region	Scores per country, region, or city
Related queries	Top + rising queries, with "Breakout" markers and links
Related topics	Top + rising topics with topic types
Trending Now	Today's live trending searches per country (40+ geos) with approximate traffic and related news articles

One actor for both jobs. Most Google Trends actors do either keyword research or the trending feed — this does both in a single run: analyze specific keywords and pull the live Trending Now list, together.

Input example

{
    "searchTerms": ["bitcoin", "ethereum", "solana"],
    "geo": "US",
    "timeRange": "today 12-m",
    "dataTypes": ["TIMESERIES", "RELATED_QUERIES"],
    "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

• trendingNowGeos — country codes for the live Trending Now feed, e.g. ["US","GB","DE"] (works with or without searchTerms)
• geo — country (US, DE, NL…), region (US-NY), or empty for Worldwide
• timeRange — now 1-H … today 5-y, all, or a custom "2024-01-01 2024-12-31" via customTimeRange
• category — any Google Trends category id (0 = all)
• property — web (default), youtube, news, images, or froogle (Shopping)
• languageCode — localizes related queries/topics (en-US, de-DE, pt-PT, …)

Output example (one dataset item per term per data type)

{
    "searchTerm": "bitcoin",
    "geo": "US",
    "timeRange": "today 12-m",
    "dataType": "TIMESERIES",
    "timeline": [
        { "date": "Aug 24 – 30, 2025", "timestamp": 1724457600, "value": 29, "isPartial": false }
    ]
}

Related queries items carry top and rising arrays with values, formatted values (+250%, Breakout), and deep links back to Google Trends.

Use cases

• SEO & content research — spot rising queries before they peak; feed keyword pipelines.
• Market & brand monitoring — track demand for brands, products, or tickers per country on a schedule.
• Data science & forecasting — clean numeric time series for models, dashboards (Looker, Power BI), or spreadsheets.
• E-commerce — seasonality curves per product category and region.

Reliability tips

• Use residential proxies (the default proxy setting) — datacenter IPs get rate-limited by Google far more often.
• Keep runs under a few hundred term×datatype combinations; schedule bigger jobs as multiple runs.
• Check the RUN_SUMMARY key-value record: it lists per-term failures explicitly instead of hiding them.

FAQ

Why do values max at 100? Google Trends reports relative interest, scaled so the range's peak = 100. That's the same data the Trends UI shows.

Can it compare terms on one scale? Each term is currently fetched independently (own 0–100 scale). Cross-term comparison on a shared scale is on the roadmap — until then, comparisons can be approximated by normalizing on overlapping periods.

Is scraping Google Trends legal? This actor only accesses publicly available data, the same data anyone sees at trends.google.com. You're responsible for using the data in line with applicable laws and Google's terms.