Google Trends Scraper: Interest & Queries avatar

Google Trends Scraper: Interest & Queries

Pricing

$15.00 / 1,000 trend reports

Go to Apify Store
Google Trends Scraper: Interest & Queries

Google Trends Scraper: Interest & Queries

Scrape Google Trends data reliably: interest over time, related & rising queries, related topics, geo breakdowns. 95%+ success, zero charge on failure. Multi keyword compare, all timeframes. Use in Claude, ChatGPT & any MCP agent for SEO & trend research.

Pricing

$15.00 / 1,000 trend reports

Rating

0.0

(0)

Developer

The Mine Works

The Mine Works

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

πŸ“ˆ Google Trends Scraper: Interest, Queries & Geo API

Overview

Google Trends Scraper pulls interest-over-time, related and rising queries, related topics, and geographic breakdowns for any keyword directly from Google Trends. Feed it iphone and samsung galaxy, pick a timeframe from the last hour to five years, choose a country, and get back clean structured JSON ready for SEO research, market analysis, or RAG pipelines.

Google Trends has no official public API and the front-end is aggressively rate-limited by data-centre IPs. This actor solves both problems: it uses the same widgetdata endpoints the Trends UI calls, but through a residential proxy pool that returns ~95%+ success rates. Blocked, empty, or failed keyword lookups are never charged: only a keyword that actually returned data results in a billed event.

βœ… No API key | βœ… Residential proxy included | βœ… Zero charge on failure | βœ… MCP-ready for AI agents

Features

Every timeframe. From now 1-H to all (5 years and back to 2004). Multi-keyword compare. Query several keywords in one run for side-by-side interest data. Four data types. Interest over time, related queries, related topics, interest by region. Geo scoped. Any ISO country code, or blank for worldwide. Reliable. Residential proxy plus retries, zero cost on failure so you only pay for data.

How it works

The actor hits the same trends.google.com/trends/api/widgetdata/* endpoints that the Google Trends front-end uses when you interact with the site. Each keyword is submitted as its own request, and the four data types (interest over time, related queries, related topics, interest by region) are fetched only if you ask for them so you don't pay for data you don't need.

Every request goes through Apify's residential proxy pool because data-centre IPs get 429-rate-limited within a handful of requests. Failed keywords retry with backoff, and if a keyword still cannot be fetched the result is skipped without charge, so you only pay for records that made it into the dataset.

🧾 Input configuration

{
"keywords": ["iphone", "samsung galaxy"],
"timeframe": "today 12-m",
"geo": "US",
"includeInterestOverTime": true,
"includeRelatedQueries": true,
"includeRelatedTopics": false,
"includeInterestByRegion": true
}

πŸ“€ Output format

{
"keyword": "iphone",
"geo": "US",
"timeframe": "today 1-m",
"interest_over_time": [
{ "date": "2026-06-15T00:00:00.000Z", "value": 77, "formatted_value": "77" },
{ "date": "2026-06-16T00:00:00.000Z", "value": 82, "formatted_value": "82" }
],
"related_queries": {
"top": [{ "query": "iphone 17", "value": 100 }],
"rising": [{ "query": "apple iphone 18 pro thickness", "value": "Breakout" }]
},
"interest_by_region": [
{ "region_code": "US-KS", "region_name": "Kansas", "value": 100 },
{ "region_code": "US-WY", "region_name": "Wyoming", "value": 94 }
]
}

Every keyword record contains these fields:

FieldDescription
πŸ”Ž keywordThe keyword the record covers
🌍 geoCountry code (e.g. US, IN) or empty string for worldwide
⏱️ timeframeTime range requested (e.g. today 12-m)
πŸ“ˆ interest_over_timeArray of {date, value, formatted_value}
🧡 related_queriesObject with top and rising arrays of related searches
🧠 related_topicsObject with top and rising arrays of related topics
πŸ—ΊοΈ interest_by_regionArray of {region_code, region_name, value}

πŸ’Ό Common use cases

SEO & content planning Find rising queries adjacent to a target keyword and build content briefs around them. Track seasonality and pick the right week to publish or update a piece.

Product & market research Compare interest in a competitor and your product over time and by region. Spot breakout queries in an emerging category before the market catches on.

Ads & performance Time paid pushes to interest peaks per region. Reallocate budget to states or cities where demand is climbing fastest.

AI agents & RAG Give a research or planning agent a fresh interest signal for any topic on demand. Feed weekly trend snapshots into a market-intel report the agent writes for you.

πŸš€ Getting started

  1. Open the actor and add one or more keywords.
  2. Pick a timeframe (today 1-m, today 12-m, today 5-y, all) and a geo (US, IN, GB).
  3. Toggle the data types you want: interest over time, related queries, related topics, interest by region.
  4. Leave the residential proxy on (required for reliable widgetdata calls).
  5. Click Start. Download as JSON, CSV, or Excel, or pull via API or MCP.

FAQ

Why do I need a residential proxy? The Google Trends widgetdata endpoints return 429 to almost every data-centre IP within a handful of requests. Residential IPs from real consumer ISPs are the only reliable way to fetch this data at scale, which is why the actor ships with RESIDENTIAL as the default.

How does "zero charge on failure" work? You are charged per successful keyword result written to the dataset. If a keyword fails after retries, no dataset row is written and you are not charged for that keyword.

Can I compare keywords in a single chart? Each keyword is fetched independently so the returned time series are directly comparable when plotted together. If you need Google's own normalised "compare" view (all keywords indexed to the peak of the highest one), request them together and use the max value across records as the shared scale.

Can I use it in an AI agent? Yes. It's exposed as an MCP tool. See below.

Use in Claude, ChatGPT & any MCP agent

https://mcp.apify.com/?tools=themineworks/google-trends-pro

Or call it programmatically with the Apify client:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('themineworks/google-trends-pro').call({
keywords: ['iphone', 'samsung galaxy'],
timeframe: 'today 12-m',
geo: 'US',
includeInterestOverTime: true,
includeRelatedQueries: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

πŸ› οΈ Complete your SEO & market intel pipeline

Got the trend signal. Now act on it with the rest of the suite:

Typical flow: google-trends surfaces the demand, meta-ad-library shows the creative response, trustpilot-reviews reveals what customers actually feel.

Questions or need a custom field set? Reach out through the Apify profile.