# Google Trends Explorer – Interest Over Time, Reliable API (`rowfeed/google-trends-explorer`) Actor

Google Trends interest over time for any keywords: compare up to 5 on one scale, with average, peak, latest value and trend. Licensed data, no blocked runs, pay per use.

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

## Pricing

from $1.00 / 1,000 keyword trends

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 – Interest Over Time, Reliable API

Get Google Trends interest over time for any keywords, with the average, peak, latest value and trend already worked out, and up to 5 keywords compared on one shared scale.
Built for marketers, analysts, content teams, traders and AI agents who need Google Trends data in a spreadsheet or pipeline.
The data is fetched through a licensed data provider (DataForSEO), not by scraping Google Trends, so runs do not fail on rate limits or captchas.

### What you get

- **One row per keyword** with the full timeline (0–100 per period) plus `average_interest`, `latest_interest`, `peak_interest` with its period, and `trend_pct`.
- **Fair comparisons**: up to 5 keywords per lookup share one 0–100 scale, just like the Google Trends website. With more keywords you get several comparison groups.
- **Any time range and property**: past hour up to 2004–today, web, news, YouTube, images or Google Shopping, worldwide or any country or region.
- A link to the same chart on Google Trends for every row.

### Example output row

A real row from a run with the default input (United States, past 12 months, timeline shortened here):

```json
{
  "keyword": "price tracking",
  "average_interest": 59,
  "latest_interest": 12,
  "latest_period": "2026-10-04",
  "peak_interest": 100,
  "peak_period": "2026-03-15",
  "trend_pct": -21.4,
  "has_data": true,
  "timeline": [
    { "date_from": "2025-10-12", "date_to": "2025-10-18", "value": 28, "partial": false },
    { "date_from": "2025-10-19", "date_to": "2025-10-25", "value": 26, "partial": false },
    "... 49 more weeks ...",
    { "date_from": "2026-10-04", "date_to": "2026-10-10", "value": 12, "partial": false },
    { "date_from": "2026-10-11", "date_to": "2026-10-13", "value": 10, "partial": true }
  ],
  "compared_with": ["web scraping", "data extraction"],
  "comparison_group": 1,
  "time_range": "past_12_months",
  "search_type": "web",
  "location": "United States",
  "google_trends_url": "https://trends.google.com/trends/explore?hl=en&geo=US&date=today%2012-m&q=web%20scraping,data%20extraction,price%20tracking",
  "checked_at": "2026-10-13T07:31:04+00:00"
}
```

`partial: true` marks a period that is not finished yet; it is kept in the timeline but left out of latest, peak and trend. `trend_pct` compares the last 4 complete periods with the 4 before.

### Input

| Field | What it does |
|---|---|
| `keywords` | Search terms, 2–100 characters each, up to 100 per run. |
| `timeRange` | `past_hour`, `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years`, `2004_present` (web) or `2008_present`. |
| `location` | `United States`, `Germany`, `California,United States` ... Empty = worldwide. |
| `searchType` | `web`, `news`, `youtube`, `images` or `froogle` (Google Shopping). |
| `compareTogether` | On (default): groups of 5 share one scale. Off: every keyword gets its own 0–100 scale. |

### Pricing

Pay per event, no subscription:

- **$0.001 per keyword row** with data (the full timeline included). Keywords Google has too little data for come back with `has_data: false` and are free.
- **$0.02 per Google Trends lookup** of up to 5 keywords. Failed lookups, and lookups where Google has no data, are free.
- $0.001 per run start.

Examples: 1 keyword costs about $0.022. 5 compared keywords cost about $0.026. 100 keywords compared in groups of 5 cost about $0.50 (with `compareTogether` off, every keyword is its own lookup: about $0.022 each).

**Try it for $0.001:** the pre-filled example is answered from a saved snapshot of a real lookup (rows carry `from_snapshot: true`) and costs only the $0.001 run start. Change anything and the lookup runs live.

**Free Apify plan:** the pre-filled example works on any plan. Live lookups need a paid Apify plan (any plan), because each one costs real money at the data provider; on the free plan the run returns a `paid_plan_required` row and charges nothing beyond the start.

You can cap the cost of a run with the maximum charge setting. The Actor checks your budget before each lookup, charges a lookup only when it succeeds, and stops after the first failed lookup.

### Good to know

- Google Trends values are relative (0–100), not search counts. For monthly search volumes use a keyword volume tool.
- Values from different comparison groups are on different scales; compare within one `comparison_group`.
- A value of 0 means Google had too little data for that period. A small term compared with very popular ones can come out as all zeros (`has_data: false`, not charged); look it up on its own or with similar-sized terms.
- Error rows carry `error` and `errorMessage` and are never charged.

### Related tools

- [Google Search Results API](https://apify.com/rowfeed/google-serp-api) – Google results for any query and country, with your domain's rank. $4 per 1,000 searches.
- [Google News Monitor](https://apify.com/rowfeed/google-news-monitor) – Google News articles for any query, with a monitor mode for new articles only.
- [Keyword Search Volume](https://apify.com/rowfeed/keyword-search-volume) – monthly Google search volume, CPC and competition for any keyword list, or keyword ideas from seeds.
- [Competitor Keywords](https://apify.com/rowfeed/competitor-keywords) – every Google keyword a domain ranks for, with position, URL, volume, difficulty and traffic.

Not affiliated with Google.

# Actor input Schema

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

Search terms to look up (2-100 characters each, up to 100 per run). Up to 5 are compared on one shared 0-100 scale per lookup.

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

Period of the interest-over-time timeline.

## `location` (type: `string`):

Country or region as Google names it, e.g. "United States", "Germany", "California,United States". Leave empty for worldwide.

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

Which Google property the interest is measured on.

## `compareTogether` (type: `boolean`):

On: keywords are looked up in groups of 5 sharing one 0-100 scale (like the Google Trends website). Off: every keyword gets its own 0-100 scale and its own lookup.

## Actor input object example

```json
{
  "keywords": [
    "iphone 17",
    "pixel 10",
    "galaxy s26"
  ],
  "timeRange": "past_12_months",
  "location": "United States",
  "searchType": "web",
  "compareTogether": true
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("rowfeed/google-trends-explorer").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("rowfeed/google-trends-explorer").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 '{}' |
apify call rowfeed/google-trends-explorer --silent --output-dataset

```

## MCP server setup

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

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/zzFt5t2wigRqjYJVa/builds/VSY4GOh9dDmcVGfwB/openapi.json
