# Google Trends Scraper — Keyword History API (`monkey.d.scraping/google-trends-keyword-analysis`) Actor

Extract Google Trends keyword history by country and period. Export interest-over-time data, dates and availability flags to JSON, CSV or Excel for SEO research, seasonality and n8n workflows. Simple input; no Google login or Google API key.

- **URL**: https://apify.com/monkey.d.scraping/google-trends-keyword-analysis.md
- **Developed by:** [Monkey D. Scraping](https://apify.com/monkey.d.scraping) (community)
- **Categories:** SEO tools, Marketing
- **Stats:** 2 total users, 1 monthly users, 93.8% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 keyword histories

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 Scraper — Keyword History API

Extract **Google Trends keyword history and interest over time** by country and date range. Get the available timeline points for each search term, with dates, interest values, data availability and partial-period flags. Export JSON, CSV or Excel, or use the Apify API in n8n, Make, Zapier and scheduled research workflows.

This independent Actor is built for keyword history: SEO research, seasonal content planning, brand interest monitoring and market research. It uses a simple three-field input and requires no Google login or Google API key.

> **Launch scope:** one to five keywords per run. Google can restrict requests; a run can return partial results. Always inspect `RUN_SUMMARY` when a keyword is missing. This Actor provides interest over time, not absolute search volume or Trending Now data.

**Example cost: $0.0025 for one keyword with available data, or $0.0045 for five.** Platform usage is included. Each keyword history counts once, regardless of the number of dates; the $0.002 startup charge also applies when no usable data is returned. See Pricing for the active rate.

### Is this the right Google Trends scraper for your task?

| Your goal | Supported here |
|---|---|
| Export keyword history for SEO and seasonal planning | Yes: dated interest-over-time points in JSON, CSV or Excel |
| Track a brand's relative interest in a selected country | Yes: each keyword is normalized independently |
| Compare several keywords on one shared scale | No: separate keyword series are not a multi-term comparison |
| Collect related queries, regional rankings or Trending Now | No: this Actor focuses on historical timelines |

### Ready-to-run Google Trends example

Open the example below and choose **Try for free** to create your own task in Apify Console. Keep `coffee` or replace it with your keyword, choose a country and period, and check the current **Pricing** tab before starting.

| Public task | Saved settings | Output and export | Example charge per run |
|---|---|---|---:|
| [Coffee search seasonality](https://apify.com/monkey.d.scraping/google-trends-keyword-analysis/examples/google-trends-coffee-seasonality) | One keyword: `coffee`; Worldwide; past five years | One keyword record with dated interest-over-time points. Use **Timeline** to export date rows as CSV or Excel; check `RUN_SUMMARY` for coverage. | $0.0025 with available data; $0.002 startup only without usable data |

The saved example uses 128 MB and a **$0.01 spending cap**. The cap is a limit, not the example charge. The prices above include platform usage. Adding keywords changes the total; every timeline date stays inside its keyword's single result charge. Repeated runs take new snapshots and can include the same dates. Scheduling your own task does not provide change-only output or a shared comparison scale between keywords.

### Quick start

1. Enter **Search terms**, one keyword per line. Start with one term such as `coffee`.
2. Select **Country**, or keep Worldwide.
3. Select **Time period**, then start the Actor.

```json
{
  "keywords": ["coffee"],
  "geo": "IT",
  "timeRange": "today 3-m"
}
```

Country options: Worldwide (`""`), Italy (`IT`), United States (`US`), United Kingdom (`GB`), Germany (`DE`), France (`FR`) and Spain (`ES`). Periods: past month (`today 1-m`), three months (`today 3-m`), twelve months (`today 12-m`) and five years (`today 5-y`).

Each keyword is measured separately. Values from separate requests do not share the comparison scale used by a multi-term chart on Google Trends.

### Pricing: a whole keyword history counts once

The launch price is **$0.002 per run start + $0.0005 per keyword with available data**, with platform usage included. Check the Actor's Pricing tab for the active rate before starting a run.

| Run result | Charge |
|---|---:|
| One keyword with data | $0.0025 |
| Five keywords with data | $0.0045 |
| No usable keyword data | $0.002 startup charge only |

A five-year series containing hundreds of dates is **one keyword result**, not hundreds of billable results. Empty/no-data series and failed keywords do not incur the keyword charge. The startup charge still applies when Google returns no usable results. No charge is added for CSV exports or the Timeline view.

Set a maximum run cost in Apify to control spending. The Actor checks the remaining budget before collecting each keyword and stops when it cannot cover the next usable series.

### Output and exports

The default dataset contains one record for each completed keyword:

| Field | Meaning |
|---|---|
| `keyword` | Search term supplied in the input |
| `geo` | Country code, or an empty string for Worldwide |
| `timeRange` | Requested Google Trends date range |
| `status` | `ok` when points have available data; otherwise `no_data` |
| `pointCount` | Number of timeline points |
| `fetchedAt` | Collection time in UTC |
| `trendsUrl` | Link to the corresponding Google Trends Explore page |
| `timeline` | Dates, timestamps, interest values, `hasData` and `isPartial` flags |

Choose **Keyword overview** to review keyword availability. Choose **Timeline** to export individual dates as CSV or Excel rows. Both views use the same saved records; expanding timeline points does not add keyword charges.

#### Real keyword-history excerpt

Owner verification observed on 19 October 2026: `caffè`, Italy, past twelve months. The full record contained 53 points; only the first two are shown below. `pointCount` retains the original full count and must not be treated as the length of this shortened example.

```json
{
  "keyword": "caffè",
  "geo": "IT",
  "timeRange": "today 12-m",
  "status": "ok",
  "pointCount": 53,
  "fetchedAt": "2026-10-19T12:22:30.598348+00:00",
  "trendsUrl": "https://trends.google.com/trends/explore?q=caff%C3%A8&geo=IT&date=today+12-m",
  "timeline": [
    {
      "date": "2025-10-19T00:00:00+00:00",
      "timestamp": 1760832000,
      "interest": 77,
      "hasData": true,
      "isPartial": false
    },
    {
      "date": "2025-10-26T00:00:00+00:00",
      "timestamp": 1761436800,
      "interest": 82,
      "hasData": true,
      "isPartial": false
    }
  ]
}
```

These are dated observations, not current values. Interest is Google's relative 0–100 index within the series, not search volume or a shared scale between separately collected keywords. `hasData` and `isPartial` describe the source flags for each point. Actual series length and resolution depend on Google Trends and the selected period.

### Practical use cases

- **SEO and content calendars:** identify seasonal interest in products, destinations or topics.
- **Brand research:** follow changes in relative interest for a brand within the same country and period.
- **Market research:** retrieve country-specific keyword histories for reports and spreadsheets.
- **n8n, Make and Zapier:** schedule collection and pass dataset exports into automated reporting.
- **AI agents and retrieval workflows:** use structured historical interest data through the Apify API or MCP; retain the country, period and collection timestamp when citing a result.

### Google Trends scraper FAQ

#### Does this return Google search volume?

No. Google Trends reports relative search interest on a 0–100 scale, not the number of searches. A value of 100 marks the peak within that keyword's requested country and time range. Sampling and source availability can change values between runs. [Google explains Trends data](https://support.google.com/trends/answer/4365533).

#### Does it include related queries, regions or today's trending searches?

It returns interest-over-time timelines only. Related queries, related topics, regional breakdowns, keyword comparisons and Trending Now are outside this Actor's scope.

#### Why can a run have fewer keyword results than requested?

Google may block or limit requests, or a timeline can be unavailable. The Actor attempts one bounded recovery and preserves completed series. Failed and skipped keywords appear in `RUN_SUMMARY`; it never creates invented data for them. A successful platform run can still have a partial summary.

#### Do I pay for failed keywords or dates inside a timeline?

The keyword event is charged only for a saved series with available data. Failed and no-data keywords do not incur that event. Every run has the startup charge, including runs without usable data. Individual timeline dates are not charged separately.

#### Can I collect more than five keywords?

Split the list into batches of at most five. Space runs out when Google limits requests. Higher concurrency is not a reliability guarantee.

#### Can I use it as a Google Trends API alternative?

Yes, for the historical keyword timelines supported here. Run it through the Apify API and retrieve the default dataset. You need Apify API authentication for programmatic calls; no Google account credentials are required in the input.

### Other Actors from this publisher

| Actor | When to use it |
|---|---|
| [Google News Scraper](https://apify.com/monkey.d.scraping/google-news-scraper-lite) | Collect recent headlines across 13 supported editions, with optional direct article URLs, descriptions and images |
| [Telegram Keyword Search & Channel Scraper](https://apify.com/monkey.d.scraping/telegram-keyword-search-channel-scraper) | Find publicly indexed Telegram posts for a topic and retain source URLs |

### Support

Open an Actor issue with the run ID and a non-sensitive description of the missing result. Include the keyword, country and period when appropriate. Never post tokens, cookies or private account credentials.

This is an independent community Actor and is not affiliated with Google. Source limits and availability affect results; no uptime or universal success-rate guarantee is claimed.

# Actor input Schema

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

Enter one to five search terms, one per line. Each term is analysed separately. Start with one term; smaller batches are less likely to be interrupted by source limits.

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

Choose the country whose search interest you want to analyse.

## `timeRange` (type: `string`):

Choose how far back the analysis should go.

## Actor input object example

```json
{
  "keywords": [
    "coffee"
  ],
  "geo": "",
  "timeRange": "today 3-m"
}
```

# Actor output Schema

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

One saved record per completed keyword, including country, requested period, ok/no_data status, point count, collection time and Google Trends source URL. Failed keywords are listed in the run summary rather than invented as results.

## `timeline` (type: `string`):

Date-level timeline perspective of the same keyword records, expanded using the timeline dataset view. Each point has a timestamp, relative interest from 0 to 100, data-availability and partial-period flags. Resolution is chosen by Google Trends; keywords are measured separately and do not share a comparison scale. Expanding dates adds no keyword charge.

## `summary` (type: `string`):

RUN_SUMMARY records requested, completed, failed and skipped keywords and coverage/budget outcomes. Check it even when the platform run succeeds: source limits can produce partial results.

# 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": [
        "coffee"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("monkey.d.scraping/google-trends-keyword-analysis").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": ["coffee"] }

# Run the Actor and wait for it to finish
run = client.actor("monkey.d.scraping/google-trends-keyword-analysis").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": [
    "coffee"
  ]
}' |
apify call monkey.d.scraping/google-trends-keyword-analysis --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,monkey.d.scraping/google-trends-keyword-analysis"
        }
    }
}
```

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/dmAGNi6SIjekDcmgi/builds/qtWBJJrwQbI4NhFOa/openapi.json