Google Trends Scraper avatar

Google Trends Scraper

Pricing

from $2.50 / 1,000 results

Go to Apify Store
Google Trends Scraper

Google Trends Scraper

A reliable pytrends alternative: scrape Google Trends without login. Get interest-over-time and top/rising related queries as clean JSON, by country and time range. Paced + residential proxy so it won't 429 like pytrends. For SEO, market research, and Python data pipelines.

Pricing

from $2.50 / 1,000 results

Rating

0.0

(0)

Developer

Koen Christiaens

Koen Christiaens

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Pull Google Trends data — interest-over-time and rising/top related queries — for any list of keywords, as clean structured JSON. No login, no browser, no Google account. Runs over residential proxy so it works at scale.

What it does

Give it keywords; it returns, per keyword:

  • Interest over time — the 0–100 relative search-interest series (weekly points for the selected range), with human-readable dates.
  • Related queries — the top and rising searches associated with each keyword, with their relative values and direct Trends links (great for SEO, market research, trend spotting).

Data is public, aggregate, non-personal search-interest data straight from Google Trends' own endpoints.

Input

FieldTypeDefaultDescription
keywordsstring[]["bitcoin","ozempic","labubu"]Search terms to pull.
geostring"US"Two-letter country code, or empty for worldwide.
timestring"today 12-m"Trends range token: today 12-m, today 3-m, now 7-d, etc.
proxyGroupstring"RESIDENTIAL"Apify proxy group. Residential recommended.

Example

{
"keywords": ["electric vehicles", "solid state battery"],
"geo": "US",
"time": "today 12-m",
"proxyGroup": "RESIDENTIAL"
}

Output

Each dataset item is one data point:

{ "keyword": "bitcoin", "kind": "interest_over_time", "time": "1752969600",
"formattedTime": "Jul 20 – 26, 2025", "value": 45, "geo": "US", "timeRange": "today 12-m" }
{ "keyword": "ozempic", "kind": "related_query", "query": "ozempic price",
"value": 200, "formattedValue": "+200%", "link": "/trends/explore?q=ozempic+price...", "geo": "US" }

The run also stores a RUN_STATS record in the key-value store with per-keyword coverage, schema-valid counts, and any rate-limit blocks encountered — full transparency, no silent drops.

Notes on reliability

Google rate-limits its Trends endpoints per IP. This actor paces requests, backs off exponentially on 429, and rotates residential proxy sessions to stay within limits.

Up to 10 keywords per run — soak-tested for ~100% coverage on both widgets at that size. The actor rejects larger batches rather than return partial data, so every run that starts gives you complete results. Running more? Split into batches of 10; each run is independent and cheap. (Interest-over-time is the most robust signal; related-queries is the first to be throttled once Google's per-IP limit is hit, which is exactly why the cap exists.)

Use cases

  • SEO & content research (rising related queries)
  • Market / demand research and trend monitoring
  • Feeding dashboards or models with search-interest signals