Google Trends API & Scraper: Interest, Regions, Queries avatar

Google Trends API & Scraper: Interest, Regions, Queries

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Google Trends API & Scraper: Interest, Regions, Queries

Google Trends API & Scraper: Interest, Regions, Queries

Google Trends API and scraper: interest over time, interest by region and related queries in one JSON result, with up to 5 terms compared. $0.005 per result; errors are never charged.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Vasilis Linakis

Vasilis Linakis

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Features

Limited permissions

Share

A Google Trends API and Google Trends scraper that returns clean JSON. Get interest over time, interest by region, related queries and related topics for each search term, or compare up to 5 terms in one chart, with all sections together in one result.

Use it to track demand for a product category, compare brands, time content and campaigns, or find rising queries in a market.

Why this actor

  • Everything in one result. One record per term (or per comparison group) holds the time series, the regional breakdown, related queries and related topics you asked for. Compare up to 5 terms with values scaled together, as on trends.google.com.
  • You pay only for data. $0.005 per result on every Apify plan. Errors, terms with no data and the closing summary record are never charged, and platform usage is included.
  • Clear error records. Each term (or comparison group) runs in isolation, so one failure never fails the run. Every failure is an error record with a code (rate_limited, no_data, blocked and others), a message and the HTTP status.
  • Honest about gaps. If Google does not provide a section for a request, the record says so in warnings instead of returning silent empty data.
  • Polite. The Actor checks robots.txt at the start of every run and honours it. It uses only the Trends data API (/trends/api/...), never the explore pages, sends at most one request per second, and identifies itself with a descriptive User-Agent. No proxy rotation, no headless browser.

How it compares

The two most-used Actors returned by an Apify Store search for "google trends". Facts are from their public Store pages and the public Apify API (/v2/acts/<user>~<name>), checked on 2026-10-26. Prices change; check each page before you decide.

This ActorGoogle Trends Scraper (apify)Google Trends Scraper (data_xplorer)
Price per 1,000 results$5 on every plan$3 (Free), $1 (Bronze), $0.50 (Silver), $0.30 (Gold), $0.15 (Platinum), $0.10 (Diamond)$2 (Free), $1 (Bronze), $0.75 (Silver), $0.50 (Gold and above)
What one result holdsOne term, or a comparison group of up to 5 terms, with every section you selectedNot stated on its Store pageNot stated on its Store page
Start fee$0.00005None listed$0.025
Platform usageIncludedPaid by the user, in additionNot billed separately, per its pricing record
Charged for failed terms?No: each gets a free error recordNot stated on its Store pageNot stated on its Store page
Sources and sectionsTrends data API: interest over time, by region, related queries and topicsInterest over time, by subregion and city, related queries and topicsTrending searches in 125 countries; keyword interest over time and by region
Access methodAllowed /trends/api paths only, robots.txt checked, no proxy rotationNot stated on its Store pageProxy rotation, IP diversity and browser fingerprinting, per its Store page
Personal dataNone: aggregated, anonymised Trends dataNot addressed on its Store pageNot addressed on its Store page

The other Actors cost less per result and data_xplorer also covers daily trending searches. This one is built for a narrower job: every section for a term, or a comparison of up to 5 terms, in one record, with an explicit and free record for every failure, from the paths Google's robots.txt allows.

How to use

  1. Enter one or more Search terms. Turn on Compare terms in one chart to compare up to 5 terms.
  2. Pick a time range (or exact dates), a country or region, and the sections you need.
  3. Run it, or schedule it. Read the results in the Overview tab, export them, or fetch them through the API.

Ready-made examples in Python, JavaScript and n8n (including a weekly scheduled workflow): reliable-apps-examples on GitHub. Step-by-step tutorial: Google Trends data as JSON, and what to do about 429s.

Example input, comparing two terms worldwide over the past 90 days:

{
"searchTerms": ["python", "javascript"],
"compareMode": true,
"timeRange": "today 3-m",
"geo": "",
"interestOverTime": true,
"interestByRegion": true,
"relatedQueries": true
}

Each dataset item has a type field: result, error or summary.

The result record for that input, shortened to one time point, one region and one related query per list (the full record has every point and region, and a relatedQueries entry for each term):

{
"type": "result",
"searchTerm": "python vs javascript",
"searchTerms": ["python", "javascript"],
"comparison": true,
"geo": "",
"timeRange": "today 3-m",
"timeRangeResolved": "2026-07-25 2026-10-25",
"category": 0, "gprop": "web", "hl": "en-US", "tz": 0,
"interestOverTime": {
"resolution": "DAY",
"averages": {"python": 39, "javascript": 7},
"points": [{"time": "2026-07-25T00:00:00Z", "formattedTime": "Jul 25, 2026", "isPartial": false, "values": {"python": 53, "javascript": 14}}]
},
"interestByRegion": {
"resolution": "COUNTRY",
"regions": [{"geoCode": "CN", "geoName": "China", "values": {"python": 96, "javascript": 4}}]
},
"relatedQueries": {
"python": {
"top": [{"query": "python code", "value": 100, "formattedValue": "100", "link": "https://trends.google.com/trends/explore?q=python+code&date=today+3-m"}],
"rising": [{"query": "learn python for beginners", "value": 200, "formattedValue": "+200%", "link": "https://trends.google.com/trends/explore?q=learn+python+for+beginners&date=today+3-m"}]
}
},
"warnings": [],
"exploreUrl": "https://trends.google.com/trends/explore?q=python%2Cjavascript&date=today+3-m&hl=en-US",
"scrapedAt": "2026-10-25T10:02:11Z"
}

In a comparison, region values are each term's share of interest in that region.

An error record (not charged), here from a one-term run in which Google rate-limited the term:

{
"type": "error",
"searchTerm": "web crawler",
"searchTerms": ["web crawler"],
"geo": "US",
"timeRange": "today 12-m",
"error_code": "rate_limited",
"message": "HTTP 429 after 3 tries",
"http_status": 429,
"scrapedAt": "2026-10-25T09:54:31Z"
}

The summary record that closes every run (not charged), here from a one-term run:

{
"type": "summary",
"groups_total": 1,
"results_output": 1,
"errors": 0,
"stopped_on_charge_limit": false,
"stopped_reason": null,
"requests_made": 6,
"duration_seconds": 8.22,
"finished_at": "2026-10-25T09:53:59Z"
}

Input

FieldWhat it does
searchTermsRequired. Terms to look up, e.g. ["web scraping"]. Topic ids such as /m/05z1_ also work.
compareModeOff (default): one record per term, each scaled 0-100 on its own. On: terms compared in groups of up to 5, one record per group, with values scaled together.
timeRangenow 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m (default), today 5-y or all.
customTimeRangeExact dates, "YYYY-MM-DD YYYY-MM-DD". Overrides timeRange.
geoCountry or region code (US, GB, US-CA). Empty = worldwide.
categoryGoogle Trends category id; 0 = all (default).
gpropweb (default), images, news, froogle (Shopping) or youtube.
interestOverTimeTime series. On by default.
interestByRegionInterest by subregion. On by default.
relatedQueriesTop and rising related queries. On by default.
relatedTopicsTop and rising related topics. Off by default (see Limitations).
hlLanguage for labels and region names, default en-US.
tzUTC offset in minutes, Google's convention (300 = UTC-5), default 0.

Output

  • result is one term or one comparison group, with the sections you asked for.
  • error is one term or group that failed. It has an error_code (invalid_input, robots_disallowed, robots_unavailable, rate_limited, blocked, consent_required, http_error, network_error, bad_response, parse_error, no_data or skipped) and a message. You are not charged for it.
  • summary is one per run, with counts, the number of requests made and the duration.

values are keyed by search term, so a comparison record holds every term's value in each point and region. Values are Google's relative 0-100 index, not search counts. In a comparison, region values are each term's share in that region. A null value means Google has no data for that point. The Output tab has two views: Overview and Errors and summary.

Pricing

Pay per event: $0.005 per result record ($5 per 1,000 results), plus a $0.00005 start fee per run (Apify's standard start event, charged once per GB of run memory). You pay nothing for error or summary records, and there is no extra charge for platform usage. If you set a maximum cost per run, the Actor stops cleanly at that limit and makes no further requests to Google.

FAQ

How much does it cost? $0.005 per result on every Apify plan, plus $0.00005 per run start. One result is one term, or one comparison group of up to 5 terms, with every section you selected. Errors and the summary are free, and platform usage is included.

What if a term fails? It gets one error record with a code, a message and the HTTP status, and the run moves on to the next term. Error records are never charged.

What about Google rate limits (HTTP 429)? Google limits how often Trends can be queried, most of all from shared cloud IP addresses. On a 429 the Actor waits as long as Google asks (Retry-After) or backs off exponentially, up to 3 tries per term, then writes a rate_limited error. If two terms in a row are rate-limited, it skips the remaining terms (as free skipped errors) instead of adding load. It does not rotate proxies or IP addresses. Smaller batches and spacing runs out work best.

What is the difference between single and comparison mode? Single mode scales each term 0-100 on its own. Comparison mode puts up to 5 terms on one chart, so their values are comparable to each other, and costs one result per group. Related topics are not available in comparisons.

How fresh is the data? Each run requests the data from Google Trends at that moment. timeRangeResolved shows the exact dates Google used, and the most recent point can be marked isPartial while the period is still running.

Can I schedule it? Yes. Create an Apify Schedule (for example weekly) with your input to build a time series of trends for your terms.

Can I use it from the API, n8n, Make or Zapier? Yes. Start a run and read the dataset through the Apify API (or the "run Actor synchronously and get dataset items" endpoint), or use Apify's integrations for n8n, Make and Zapier.

Is it legal and responsible to use? The Actor uses only the Trends data API that Google's robots.txt allows, circumvents nothing, and returns aggregated, anonymised data with no personal data. You remain responsible for complying with Google's terms; see Responsible use below.

Responsible use

  • Allowed paths only. The Actor uses the Trends data API, which Google's robots.txt allows. It never requests /explore or /trends/explore pages, which robots.txt disallows, and it checks every URL against the live robots.txt before requesting it.
  • No circumvention. It never rotates IP addresses or sessions, uses no headless browser and fakes no browser fingerprint. A captcha, an "unusual traffic" page, a 401 or 403 response or a consent wall stops that term at once, with no retry, and the Actor then skips the rest of the run rather than keep trying. After two terms fail on rate limiting, it skips the remaining terms too.
  • Aggregate data only. Google Trends data is anonymised, aggregated search interest. It holds no personal data.
  • You are responsible for your use. Comply with applicable law and with Google's terms. Google Trends data is a sample, normalised to 0-100, so treat it as a relative signal, not as search volume.
  • Contact: open an issue on the Issues tab of this Actor's page (https://apify.com/reliable-apps/google-trends-reliable/issues).

Limitations

  • Rate limits. Google limits how often Trends can be queried, and it limits shared cloud IP addresses most. By design the Actor does not work around this, so large batches can end with rate_limited errors. Smaller batches and longer gaps between runs help. You are never charged for those errors.
  • Related topics are not available in comparison mode, and Google often returns the list empty. In that case the record carries a warning.
  • Comparisons hold at most 5 terms. Longer lists are split into groups of 5, and values are comparable only within a group.
  • Values are relative (0-100) and Google samples them, so two runs can differ slightly.

This Actor was built with AI-assisted development; its request building and parsing are covered by automated tests.