Google Trends Scraper & API (fast, no browser)

Get Google Trends data for any number of search terms or Google Trends URLs: interest over time, interest by region and city, related queries (top and rising) and related topics, plus side-by-side comparisons of up to 5 terms.

It talks to Google Trends' own data endpoints directly instead of driving a browser, so a term takes seconds instead of minutes. Items that Google blocks are retried on fresh IPs (and on residential IPs if needed) until they deliver, and you only pay for items that actually come back with data.

What you get per search term

Field	What it is
interestOverTime_timelineData	Search interest 0-100 for each time step (hour, day, week or month depending on the range)
interestOverTime_averages	Average interest per term (when comparing terms)
interestBySubregion	Interest by country (worldwide) or by state/region (inside a country)
interestByCity	Interest by city (when a country is set and Google has city data)
relatedQueries_top / relatedQueries_rising	Most popular and fastest-rising related searches
relatedTopics_top / relatedTopics_rising	Related topics (Google often returns these empty for automated access; filled when it gives them)
byTerm	When comparing terms: region map and related queries/topics for each term separately
terms, geo, timeRange, category, property, scrapedAt	The query the item belongs to

Field names match the most used Google Trends actor in the Store, so you can switch without changing your pipeline.

How to use

• Search terms: one per line. Each line gives one dataset item.
• Compare terms: switch it on and write up to 5 terms in one line separated by commas (iphone, samsung). They are measured on the same 0-100 scale.
• Google Trends URLs: paste any trends.google.com/trends/explore?... link; its terms, country/region, dates, category and property are used as-is (regions like US-CA work here).
• Country, time range, category, Google property (web, images, news, YouTube, Shopping), custom date range (2024-01-01 2024-06-30) and language of names.

Example input

{
  "searchTerms": ["chatgpt, gemini, claude", "bitcoin, ethereum"],
  "isMultiple": true,
  "geo": "US",
  "timeRange": "today 3-m"
}

Use it as a Google Trends API

There is no official Google Trends API, so this actor works as one: call it from your code and get JSON back in one request.

curl -X POST "https://api.apify.com/v2/acts/mvkdata~google-trends-fast/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["bitcoin", "ethereum"], "timeRange": "today 12-m", "geo": "US"}'

It also works from the Apify Python and JavaScript clients, Make, Zapier, n8n and as an MCP tool for AI agents.

Pricing

Pay per result: you are charged only for dataset items that contain data. Failed terms are not charged; they are listed in the run's key-value store record FAILED_QUERIES.

Reliability

• Each term has its own retry budget (12 by default); every retry uses a new IP.
• With the default Apify Proxy, a term Google blocks three times moves to residential IPs (switch off with Residential fallback).
• The run's status line shows results, failures and retries live.

FAQ

Why are related topics sometimes empty? Google decides per request whether to return them and often leaves them out for automated access; related queries are almost always present.

Why only a few cities? Google only reports cities with enough search volume; small countries and niche terms often have none.

Is scraping Google Trends legal? The data is public and aggregated (no personal data). Check your own use case and local rules.