# Google Trends Scraper — Interest, Regions & Related Queries (`technicaldost/google-trends-explorer-interest-related-queries`) Actor

Google Trends data as JSON without 429 errors: interest over time, interest by country/state/city and related queries (top and rising). Compare up to 5 keywords; any country, timeframe, category or YouTube/News/Shopping search. Residential proxies built in.

- **URL**: https://apify.com/technicaldost/google-trends-explorer-interest-related-queries.md
- **Developed by:** [Technical Dost Solutions](https://apify.com/technicaldost) (community)
- **Categories:** SEO tools, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Google Trends Explorer gets the data behind **trends.google.com/explore** for any keywords: **interest over time** (the full series with peak, average, latest value and % change), **interest by region** (countries, states, cities or metro areas), and **related queries** (top and rising, with breakout %). Search **worldwide or any country/state**, over any **timeframe** from the past hour to 2004, in any **category**, on **Web, YouTube, News, Images or Google Shopping** search. **Compare up to 5 keywords on one scale**, exactly like the website. Google blocks Trends requests from data centers, so this Actor uses **Apify residential proxies with automatic IP rotation** to keep runs reliable.

> **pytrends / Google Trends API giving 429 Too Many Requests?** Google answers Trends requests from cloud and data-center IPs with HTTP 429. This Actor sends them through Apify residential proxies, keeps one session and cookie per IP and rotates IPs automatically when Google pushes back, so runs finish without 429 errors. No Python, no proxy setup.

### What you get

- 3 data types: interest over time, interest by region, related queries (top and rising).
- Compare mode: up to 5 keywords on one 0-100 scale (like the website), or each keyword on its own scale.
- Any geo (worldwide, US, US-CA...), any timeframe (past hour to 2004, or a custom date range), any category, and Web, YouTube, News, Images or Shopping search.
- Region resolution: countries, states/regions, cities or US metro areas (DMA).
- Ready-made stats per series: average, peak and peak date, latest value, % change between the two halves of the period.
- Reliable: residential proxies with IP rotation when Google rate-limits; keywords below Google's volume threshold are reported and not charged.

### How to use Google Trends Explorer

1. Enter **Keywords** (e.g. `chatgpt`, `claude`) and choose **Compare keywords** if they should share one scale.
2. Pick **Data types**, **Geo**, **Timeframe**, and optionally **Category** and **Search type**.
3. Run and export to JSON, CSV or Excel, or send results to Google Sheets, a dashboard or an AI agent.

### Input example

```json
{
  "keywords": [
    "chatgpt",
    "claude",
    "gemini"
  ],
  "compareKeywords": true,
  "dataTypes": [
    "interestOverTime",
    "interestByRegion",
    "relatedQueries"
  ],
  "geo": "US",
  "timeframe": "today 12-m"
}
```

All fields are described in the **Input** tab.

### Output example

```json
{
  "type": "interestOverTime",
  "keyword": "chatgpt",
  "average": 61,
  "peak": 100,
  "peakDate": "2026-09-07T00:00:00.000Z",
  "latest": 74,
  "changePercent": 12.4,
  "points": [
    {
      "date": "2026-08-03T00:00:00.000Z",
      "label": "Aug 3 – 9, 2026",
      "value": 58,
      "isPartial": false
    },
    {
      "date": "2026-08-10T00:00:00.000Z",
      "label": "Aug 10 – 16, 2026",
      "value": 61,
      "isPartial": false
    }
  ],
  "comparedWith": [
    "chatgpt",
    "claude",
    "gemini"
  ],
  "geo": "US",
  "timeframe": "today 3-m",
  "category": 0,
  "searchType": "web",
  "scrapedAt": "2026-11-01T21:00:00.000Z"
}
```

#### Output fields

| Field | Description |
|---|---|
| `type` | interestOverTime, interestByRegion or relatedQueries. |
| `keyword` | Keyword. |
| `comparedWith` | Keywords on the same scale (compare mode). |
| `average` | Average interest over the period. |
| `peak` | Highest value. |
| `peakDate` | Date of the peak. |
| `latest` | Latest value. |
| `changePercent` | % change, second half vs first half of the period. |
| `points` | Time series: date, label, value (0-100), isPartial. |
| `regions` | Regions: geoCode, name, value (0-100). |
| `top` | Top related queries. |
| `rising` | Rising related queries (value = % growth; Breakout = >5000%). |
| `geo` | Geo used. |
| `timeframe` | Timeframe used. |
| `category` | Category ID. |
| `searchType` | Search type. |
| `scrapedAt` | When the row was scraped. |

Export results as JSON, CSV, Excel, XML or HTML, or read them with the API.

### Use cases

- SEO and content planning: rising queries and topics to write about.
- Market research: compare brands, products or competitors over time and by region.
- E-commerce: seasonality and demand by state before stocking or advertising.
- Finance and data science: search interest as a signal for nowcasting models.
- YouTube and news: what people search for on YouTube or in Google News.

### How much does Google Trends Explorer cost?

This Actor uses **pay-per-event** pricing: **$0.004 per result** ($4 per 1,000). Platform usage is included. A result is one data type for one keyword (e.g. the full interest-over-time series of "chatgpt"). There is no start fee, and keywords with too little search volume are free.

Set **Maximum cost per run** in the run options to cap your spend; the Actor stops when the limit is reached.

### Use Google Trends Explorer with AI agents (MCP)

Give Claude, ChatGPT, Cursor or any MCP client this Actor as a tool through the hosted [Apify MCP server](https://mcp.apify.com):

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/google-trends-explorer-interest-related-queries" --header "Authorization: Bearer YOUR_APIFY_TOKEN"
```

Or in a JSON MCP config:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/google-trends-explorer-interest-related-queries",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}
```

The tool is named `technicaldost--google-trends-explorer-interest-related-queries`. Ask your agent, for example, to *"run Google Trends Explorer with {"keywords": \["chatgpt", "claude", "gemini"], "compareKeywords": true, "dataTypes": \["interestOverTime", "interestByRegion", "relatedQueries"], "geo": "US", "timeframe": "today 12-m"}"*.

### Run Google Trends Explorer via API

```bash
curl -X POST "https://api.apify.com/v2/acts/technicaldost~google-trends-explorer-interest-related-queries/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["chatgpt", "claude", "gemini"], "compareKeywords": true, "dataTypes": ["interestOverTime", "interestByRegion", "relatedQueries"], "geo": "US", "timeframe": "today 12-m"}'
```

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/google-trends-explorer-interest-related-queries").call(run_input={"keywords": ["chatgpt", "claude", "gemini"], "compareKeywords": True, "dataTypes": ["interestOverTime", "interestByRegion", "relatedQueries"], "geo": "US", "timeframe": "today 12-m"})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/google-trends-explorer-interest-related-queries').call({"keywords": ["chatgpt", "claude", "gemini"], "compareKeywords": true, "dataTypes": ["interestOverTime", "interestByRegion", "relatedQueries"], "geo": "US", "timeframe": "today 12-m"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

### Integrations

Schedule runs (daily, hourly) in Apify Console and send results to Google Sheets, Slack, Make, Zapier, n8n, Airbyte or your own webhook.

### FAQ

#### What do the numbers mean?

Google Trends reports relative interest, not search counts: 100 is the peak in the selected time and place, 50 is half as popular. In compare mode all keywords share one scale; otherwise each keyword is scaled to its own peak.

#### Why do some keywords return nothing?

Google hides values below a privacy threshold (shown as 0). Use a longer timeframe or a wider geo. Such keywords are listed in the ERRORS record and are not charged.

#### Why are residential proxies needed?

Google answers Trends requests from data-center IPs with HTTP 429. The Actor rotates residential IPs automatically, which is why it keeps working where many Trends scrapers fail.

#### Which geo codes can I use?

Leave empty for worldwide, a country code (US, GB, IN), or a region (US-CA, GB-ENG).

#### How is it priced?

$0.004 per result (one data type for one keyword). For example, interest over time plus related queries for 10 keywords is 20 results = $0.08. No start fee.

#### Why no related topics?

Google returns the related-topics list empty to automated clients, so the Actor does not offer it rather than return empty rows. Related queries, regions and timelines are unaffected.

#### Is it legal to scrape this data?

The Actor collects publicly available information only and does not log in or bypass access controls. Use the data in line with the website's terms and the laws that apply to you, especially when processing personal data.

### Related Actors

More tools from the same developer that work well together with this one:

- [Google Trends Daily Scraper API](https://apify.com/technicaldost/google-trends-scraper): Get daily Google trending searches (RSS) and interest-over-time timelines for keywords.
- [Google Autocomplete Keyword Scraper](https://apify.com/technicaldost/google-autocomplete-keywords): Expand seed keywords into hundreds of long-tail keyword ideas from Google Autocomplete.
- [Google Search Results Scraper](https://apify.com/technicaldost/google-search-results-scraper): Get organic search results for any keyword: title, URL, snippet and position.
- [Reddit Post Scraper](https://apify.com/technicaldost/reddit-public-content-scraper): Get the newest public Reddit posts from any subreddit, user, search or post URL: title, text, author, subreddit, link, flair and date.

# Actor input Schema

## `keywords` (type: `array`):

Search terms or topics, e.g. chatgpt, iphone 17, bitcoin.

## `compareKeywords` (type: `boolean`):

Put keywords (up to 5 per group) on one shared 0-100 scale, like the website's compare view.

## `dataTypes` (type: `array`):

What to fetch for each keyword.

## `geo` (type: `string`):

Empty = worldwide; country code (US) or region (US-CA).

## `timeframe` (type: `string`):

Preset, or Custom date range (then set the custom dates below).

## `customStartDate` (type: `string`):

YYYY-MM-DD, used when Timeframe is Custom date range.

## `customEndDate` (type: `string`):

YYYY-MM-DD.

## `category` (type: `integer`):

Google Trends category, e.g. 0 all, 5 Computers & Electronics, 7 Finance, 71 Food & Drink, 18 Shopping, 958 Jobs.

## `searchType` (type: `string`):

Which Google search.

## `regionResolution` (type: `string`):

For interest by region. Default: countries for worldwide, regions/states for a country.

## Actor input object example

```json
{
  "keywords": [
    "chatgpt",
    "claude"
  ],
  "compareKeywords": true,
  "dataTypes": [
    "interestOverTime",
    "relatedQueries"
  ],
  "geo": "US",
  "timeframe": "today 3-m",
  "category": 0,
  "searchType": "web",
  "regionResolution": "auto"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "chatgpt",
        "claude"
    ],
    "compareKeywords": true,
    "dataTypes": [
        "interestOverTime",
        "relatedQueries"
    ],
    "geo": "US",
    "timeframe": "today 3-m"
};

// Run the Actor and wait for it to finish
const run = await client.actor("technicaldost/google-trends-explorer-interest-related-queries").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "chatgpt",
        "claude",
    ],
    "compareKeywords": True,
    "dataTypes": [
        "interestOverTime",
        "relatedQueries",
    ],
    "geo": "US",
    "timeframe": "today 3-m",
}

# Run the Actor and wait for it to finish
run = client.actor("technicaldost/google-trends-explorer-interest-related-queries").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "chatgpt",
    "claude"
  ],
  "compareKeywords": true,
  "dataTypes": [
    "interestOverTime",
    "relatedQueries"
  ],
  "geo": "US",
  "timeframe": "today 3-m"
}' |
apify call technicaldost/google-trends-explorer-interest-related-queries --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,technicaldost/google-trends-explorer-interest-related-queries"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8oxz6h12VbmnAIZ2O/builds/w66q1dpnUNrSRsHdx/openapi.json