# Google Trends Pro: Unlimited Keywords on One Scale (`jeanswiegers/google-trends-pro`) Actor

- **URL**: https://apify.com/jeanswiegers/google-trends-pro.md
- **Developed by:** [Jean Swiegers](https://apify.com/jeanswiegers) (community)
- **Categories:** SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 Pro: Unlimited Keywords on One Scale

**Reliable Google Trends data for as many keywords as you need, all on one comparable 0-100 scale.** Google Trends only lets you compare 5 terms at a time and rescales every comparison. This Actor chains batches through a shared anchor keyword, so 7, 20 or 100 keywords end up directly comparable. Built-in session rotation, exponential backoff and residential fallback handle Google's rate limits, so runs finish instead of failing.

### What you get

- **Interest over time** per keyword: full timeline plus average, latest, peak, peak date and trend change %.
- **More than 5 keywords on one scale** (anchor-keyword normalization).
- **Interest by region** (country, region, city or metro).
- **Related queries** (top and rising). **Related topics** are in beta: Google often withholds them from automated requests, and empty results are free.
- **Monitor mode**: schedule it and see how each keyword moved since the last run, plus newly rising queries.
- Any country or worldwide, any time range, web, image, news, YouTube or Shopping search.

### Who it's for

SEO and content teams choosing topics, e-commerce and dropshipping product research, market and brand analysts tracking competitors, and AI agents that need trend data without an unreliable scraper.

### Example input

```json
{
  "keywords": ["shopify", "woocommerce", "wix", "squarespace", "bigcommerce", "magento", "etsy"],
  "geo": "",
  "timeframe": "today 12-m",
  "includeInterestByRegion": true,
  "includeRelatedQueries": true
}
```

### Output

| Field | Example | Notes |
|---|---|---|
| type | `interestOverTime` | Also `interestByRegion`, `relatedQueries`, `relatedTopics` |
| keyword | `etsy` | |
| geo / timeframe | `US` / `today 12-m` | |
| averageInterest | `66.71` | On the shared 0-100 scale |
| latestInterest / peakInterest / peakDate | `55` / `100` / `2025-12-01` | |
| trendChangePct | `13.2` | Last quarter of the period vs. first quarter |
| timeline | `[{"date": "2026-07-19", "value": 42}]` | |
| scale | `anchored to "shopify"` | How values were normalized |
| regions | `[{"geoCode": "GB", "geoName": "United Kingdom", "value": 75}]` | Region rows |
| top / rising | `[{"query": "etsy shop", "value": 100}]` | Related rows |
| changeSincePreviousRun / newRisingSincePreviousRun | `-11` / `["smeg air fryer price"]` | Monitor mode |

### Pricing

Pay per event: one charge per keyword report (time series) and a smaller charge per add-on (region breakdown, related queries, related topics). Failed keywords are free.

### FAQ

**How can more than 5 keywords be comparable?** Every batch contains the same anchor keyword. Each batch is rescaled so its anchor matches the first batch, then everything is renormalized to a maximum of 100. Small keywords compared with a very large anchor lose precision (Google rounds to whole numbers), so pick an anchor of similar size if you can.

**Why do region values differ from the Trends website?** Region breakdowns are relative to the keywords compared in the same request, as on the website.

**Is there an official API?** Google's Trends API is still an invite-only alpha.

### Limits

- Related topics (beta) are often empty because Google withholds them from automated sessions; you are not charged for empty blocks.
- Rising queries are sampled by Google and can change between identical requests.
- Very low-volume keywords return zeros.

# Actor input Schema

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

Search terms to compare. More than 5 are stitched onto one comparable scale through an anchor keyword.

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

Country or region code (US, GB, ZA, US-CA…). Empty = worldwide.

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

Google Trends time string: 'now 7-d', 'today 1-m', 'today 3-m', 'today 12-m', 'today 5-y', 'all' or '2025-01-01 2025-12-31'.

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

Google Trends category (0 = all).

## `property` (type: `string`):

Which Google search to measure.

## `anchorKeyword` (type: `string`):

Keyword included in every batch to put all keywords on one scale. By default the strongest keyword of the first batch is used.

## `includeInterestByRegion` (type: `boolean`):

Add-on: regional breakdown per keyword.

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

Leave empty for Google's default.

## `includeRelatedQueries` (type: `boolean`):

Add-on: top and rising related searches per keyword.

## `includeRelatedTopics` (type: `boolean`):

Beta add-on: top and rising related topics per keyword. Google currently often withholds topics from automated requests; empty results are not charged.

## `monitorMode` (type: `boolean`):

Compare with the previous run with the same settings (stored in the named key-value store 'google-trends-pro-state'): change in latest interest and new rising queries.

## `monitorKey` (type: `string`):

Optional name for this watch list.

## `language` (type: `string`):

Interface language for Google Trends (hl), e.g. en-US.

## `proxyConfiguration` (type: `object`):

Google Trends blocks most cloud IPs. The Actor rotates sessions and falls back to Apify residential proxy automatically.

## Actor input object example

```json
{
  "keywords": [
    "chatgpt",
    "gemini"
  ],
  "geo": "US",
  "timeframe": "today 3-m",
  "category": 0,
  "property": "",
  "includeInterestByRegion": false,
  "includeRelatedQueries": false,
  "includeRelatedTopics": false,
  "monitorMode": false,
  "language": "en-US",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

One row per keyword.

## `all` (type: `string`):

Time series, regions and related queries/topics.

## `runSummary` (type: `string`):

Counts, retries, anchor used.

# 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",
        "gemini"
    ],
    "geo": "US",
    "timeframe": "today 3-m",
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("jeanswiegers/google-trends-pro").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",
        "gemini",
    ],
    "geo": "US",
    "timeframe": "today 3-m",
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("jeanswiegers/google-trends-pro").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",
    "gemini"
  ],
  "geo": "US",
  "timeframe": "today 3-m",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call jeanswiegers/google-trends-pro --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jeanswiegers/google-trends-pro"
        }
    }
}
```

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/yygEvSGpaXe6cxaER/builds/vSa2mbjjmxGL1GXiI/openapi.json