# Google Trends Interest by Region Scraper (`steadydata/google-trends-regions`) Actor

Where in the world, or where in a country, a keyword is searched: Google Trends interest by region for up to 200 keywords per run. Worldwide gives the countries with a score, a country code gives its regions or cities, each scored 0 to 100. One row per keyword, pay per keyword.

- **URL**: https://apify.com/steadydata/google-trends-regions.md
- **Developed by:** [Steadydata Team](https://apify.com/steadydata) (community)
- **Categories:** SEO tools, Marketing
- **Features:** Limited permissions
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.28 / 1,000 keyword mappeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Interest by Region Scraper

Where a keyword is searched: Google Trends' interest by region for **up to 200 keywords
per run**. Worldwide gives every country with a score (up to 250), a country code gives
its regions or its cities, each scored 0 to 100 the way Google Trends scores them. One
row per keyword with the full ranked breakdown inside it. **You only pay for keywords
that come back with data.**

### Why this scraper

- **The map as a table.** The Trends page shows interest by region as a coloured map you
  cannot export in bulk. This returns the numbers behind it, ranked, for a whole keyword
  list at once.
- **Three levels of detail.** Worldwide by country, or inside one country by region
  (states, provinces) or by city. Pick the level per run.
- **No noise rows.** Google lists every region it knows, including those with too little
  volume to score. Those are dropped by default, so the table holds only regions with a
  real score. Switch them on if you want the complete list.
- **Lightweight route.** Two requests per keyword; in testing on 13-09-2026 a worldwide
  breakdown was 30 KB and a country breakdown 1.5 KB, which is where the price comes from.
- **Only delivered keywords are charged.** A keyword without enough search volume comes
  back as a clear error record at no cost.

### Who this is for

Market researchers sizing where demand for a product or topic sits. SEO and content teams
choosing which countries or regions to localise for. Anyone comparing a keyword list
across geographies without clicking through the Trends page keyword by keyword.

### Who this is not for

This actor gives **where** a keyword is searched, not **how much** or **when**. Values are
Google's relative 0 to 100 index per region, not search counts, and they cannot be
compared across different keywords or runs. For interest over time and related queries
per keyword, use the Google Trends Batch Scraper from the same publisher; for what is
trending right now per country, Google Trends Trending Searches by Country.

### Input fields

| Field | Type | Required or default | What it does |
|---|---|---|---|
| `keywords` | list of text | required | Search terms, one per row. Each keyword is one input and one charged event; a keyword without enough search volume comes back as a free error record. |
| `geo` | text |  | Leave empty for a worldwide breakdown by country. Give a two-letter country code (US, GB, NL, DE ...) for a breakdown within that country. |
| `resolution` | text (REGION, CITY) | REGION | Used only when a country is set: REGION gives states or provinces, CITY gives cities. Worldwide is always by country. |
| `timeframe` | text (now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, all) | today 12-m | The period the interest is measured over. |
| `includeZeroRows` | true/false | false | Google lists every region, also those with too little search volume (value 0, no data). Off by default so the list holds only regions with a real score. |
| `language` | text | en-US | Language of the region names (hl), e.g. en-US, nl, de. |

### Input example

```json
{
    "keywords": ["bitcoin", "electric bike", "yoga"],
    "geo": "",
    "resolution": "REGION",
    "timeframe": "today 12-m",
    "includeZeroRows": false,
    "language": "en-US"
}
```

`geo` empty means worldwide by country. `geo: "NL"` with `resolution: "REGION"` gives the
twelve Dutch provinces; `resolution: "CITY"` gives cities.

### Output example

| Field | Type | What it holds | Example |
|---|---|---|---|
| `keyword` | text | The term the interest was measured for. | `electric bike` |
| `geo` | text | The area that was measured in; empty means worldwide. | `worldwide` |
| `resolution` | text | How finely it was broken down: by country, by region or by city. | `COUNTRY` |
| `timeframe` | text | The period that was measured, in Google's own notation, for example "today 3-m". | `today 12-m` |
| `regionCount` | number | How many areas returned a figure. | `40` |
| `topRegionCode` | text | The code of the area with the most interest. | `PK` |
| `topRegionName` | text | The name of that area. | `Pakistan` |
| `regions` | list | Every area with its score on Google's scale of 0 to 100, where 100 is the area searching most. | `[{"regionCode": "PK", "regionName": "Pakistan", "value":...` |

```json
{
    "keyword": "bitcoin",
    "geo": "NL",
    "resolution": "REGION",
    "timeframe": "today 12-m",
    "regionCount": 12,
    "topRegionCode": "NL-NH",
    "topRegionName": "North Holland",
    "regions": [
        {"rank": 1, "regionCode": "NL-NH", "regionName": "North Holland", "value": 100, "hasData": true},
        {"rank": 2, "regionCode": "NL-FL", "regionName": "Flevoland", "value": 83, "hasData": true},
        {"rank": 3, "regionCode": "NL-ZH", "regionName": "South Holland", "value": 83, "hasData": true}
    ],
    "status": "ok"
}
```

A keyword that returns nothing produces an error record instead, and is **not** charged:

```json
{
    "input": "qzxwv nonsense 99999",
    "status": "error",
    "errorCode": "NO_DATA",
    "error": "No region has enough search volume for 'qzxwv nonsense 99999' in this scope and timeframe"
}
```

Error codes: `BAD_QUERY`, `NO_DATA`, `BLOCKED`. `INPUT_TRUNCATED` appears once when your input is longer than this actor accepts.

### Related actors from steadydata

- [google-trends-batch](https://apify.com/steadydata/google-trends-batch): interest over time for the same keywords
- [google-trends-compare](https://apify.com/steadydata/google-trends-compare): several keywords on one scale

### Pricing

Pay per event: one `keyword-mapped` event per keyword delivered with data, whatever the
number of regions inside it. No charge for keywords that fail, no separate
platform-usage surcharge.

**Free Apify plan:** this actor delivers up to 25 rows per run for accounts on the Apify free
plan, and then stops with a message. That limit is set by us, not by Apify. It exists so the
actor keeps paying for itself for the people who do pay. Any paid Apify plan runs it at full
size, billed per delivered row, with failed rows never charged.

**Reviews:** if this actor saves you time, a short review on this page is the one thing that
helps most. Ratings are what other buyers look at first, and we have no other way to ask.

### Use with AI agents

AI assistants such as Claude, ChatGPT or Cursor can run this actor through Apify's own MCP server. Ask for the actor `steadydata/google-trends-regions` by its full name, so the assistant does not pick a different one, and start from this minimal input:

```json
{
  "keywords": [
    "bitcoin",
    "electric bike",
    "yoga"
  ]
}
```

The assistant can read the price per event from the Pricing section above before the first paid run. Failed input comes back as an error row, as described above.

### FAQ

**What does the value mean?**
Google's own index: 100 is the region where the keyword takes the largest share of all
searches in that region, and every other region is scaled against it. It measures
popularity relative to local search volume, not absolute counts. A small region can score
100 with fewer searches than a large region scoring 40.

**Why do some regions have no data?**
Too little search volume for Google to report. They are dropped by default; set
`includeZeroRows` to true to get them with value 0 and `hasData` false.

**Can I compare values between keywords?**
No. Each keyword is scaled on its own, so 60 for one keyword and 60 for another are not
the same amount of interest. Compare regions within a keyword, not keywords with each other.

**How many regions will I get?**
Worldwide: the countries with data; in testing on 13-09-2026 that was 40 to 66 of the
250 Google lists, depending on the keyword. Within a country: its first-level regions
(12 for the Netherlands, 51 for the United States) or up to 200 cities.

**Is personal data collected?**
No. Google Trends publishes aggregate, anonymised search interest; nothing about any
individual is involved.

**What happens when Google changes something?**
Internal routes shift from time to time. The actor is monitored daily and fixed fast, and
while it is broken you are not charged, because only delivered keywords cost anything.

**Can I call it from my own code, like an API?**
Yes. Every run is available through the Apify API: start it with one HTTP request, then read
the results as JSON, CSV or Excel from the dataset endpoint, or use the official Python and
JavaScript clients. The input is the same JSON as in the input example above, so a scheduled
script, a Make or Zapier step or an AI agent can call it without any changes.

# Changelog

This Actor's version history is a separate document: https://apify.com/steadydata/google-trends-regions/changelog.md

# Actor input Schema

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

Search terms, one per row. Each keyword is one input and one charged event; a keyword without enough search volume comes back as a free error record.

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

Leave empty for a worldwide breakdown by country. Give a two-letter country code (US, GB, NL, DE ...) for a breakdown within that country.

## `resolution` (type: `string`):

Used only when a country is set: REGION gives states or provinces, CITY gives cities. Worldwide is always by country.

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

The period the interest is measured over.

## `includeZeroRows` (type: `boolean`):

Google lists every region, also those with too little search volume (value 0, no data). Off by default so the list holds only regions with a real score.

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

Language of the region names (hl), e.g. en-US, nl, de.

## Actor input object example

```json
{
  "keywords": [
    "bitcoin",
    "electric bike",
    "yoga"
  ],
  "geo": "",
  "resolution": "REGION",
  "timeframe": "today 12-m",
  "includeZeroRows": false,
  "language": "en-US"
}
```

# 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": [
        "bitcoin",
        "electric bike",
        "yoga"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadydata/google-trends-regions").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": [
        "bitcoin",
        "electric bike",
        "yoga",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("steadydata/google-trends-regions").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": [
    "bitcoin",
    "electric bike",
    "yoga"
  ]
}' |
apify call steadydata/google-trends-regions --silent --output-dataset

```

## MCP server setup

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

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/QcotfEXhAp0wRzghG/builds/foldKJoHegRDnFLa1/openapi.json
