# Google Trends Scraper: Interest, Regions, Related & Trending (`rimulabs/google-trends-insights`) Actor

Google Trends data for any keyword, country and time range: interest over time, interest by region, related queries and topics, and today's trending searches. Every keyword comes with a plain-language trend summary (rising/falling, recent change, peak) that's ready for spreadsheets and AI agents.

- **URL**: https://apify.com/rimulabs/google-trends-insights.md
- **Developed by:** [Rimu Labs](https://apify.com/rimulabs) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 keyword reports

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: interest, regions, related queries & trending now

Get Google Trends data for any keyword, country and time range as clean structured data:

- **interest over time**
- **interest by region**
- **related queries** (top and rising)
- **today's trending searches**

Every keyword also gets a plain-language **trend summary**: rising, falling or stable, the recent change in %, the average and the peak date. It's ready for spreadsheets, dashboards and AI agents without post-processing.

You need no Google account or API key.

### What you get for each keyword

| Field | Example |
|---|---|
| `insights.trend` | `falling` (`rising`, `falling` or `stable`) |
| `insights.recentChangePct` | `-44`: latest quarter of the range vs the quarter before |
| `insights.averageInterest`, `latestInterest`, `peakInterest`, `peakDate` | 66.8 · 37 · 100 · 2026-06-21 |
| `interestOverTime` | `[{ date, label, value, isPartial }]`, weekly for 12 months |
| `interestByRegion` | `[{ geoCode: "US-WY", geoName: "Wyoming", value: 100 }, …]` |
| `relatedQueries.top` / `.rising` | `best crm` (100), `what is crm` (62) · rising queries with % growth |
| `trendsUrl` | Link to the same view on trends.google.com |

#### A real result (US, past 12 months, October 2026), shortened

```json
{
  "keyword": "crm",
  "geo": "US",
  "insights": { "averageInterest": 66.8, "latestInterest": 37, "peakInterest": 100, "peakDate": "2026-06-21", "recentChangePct": -44, "trend": "falling" },
  "interestOverTime": [{ "date": "2026-10-04", "label": "Oct 4 – 10, 2026", "value": 37, "isPartial": false }],
  "interestByRegion": [{ "geoCode": "US-WY", "geoName": "Wyoming", "value": 100 }],
  "relatedQueries": { "top": [{ "query": "best crm", "value": 100 }, { "query": "what is crm", "value": 62 }] },
  "trendsUrl": "https://trends.google.com/trends/explore?q=crm&geo=US&date=today+12-m"
}
```

### Modes

- **Keyword trends:** one report per keyword. Turn on **Compare keywords on one scale** to put up to 5 keywords on the same 0–100 scale, as on the Trends website.
- **Trending now:** today's trending searches for any countries, with approximate search volume and the news articles behind each one. It's useful for newsjacking, content calendars and alerting.

Filters:

- **Location:** country, region or worldwide.
- **Time range:** from the past hour to 2004–present, or a custom date range.
- **Search type:** web, image, news, Google Shopping or YouTube search.
- **Category:** a category ID to disambiguate terms like "apple" or "crm".

### Use cases

- **SEO and content planning:** pick topics that are rising, and time content to seasonal peaks.
- **Product and market research:** compare brands, products or categories over 5 years and by region.
- **E-commerce:** Shopping-search trends for inventory and campaign timing.
- **YouTube creators:** see what people are searching for on YouTube right now.
- **AI agents and automations:** call it through Apify's API or MCP server. The `insights` summary gives agents a direct answer ("is X growing?") without parsing charts.
- **Scheduled monitoring:** run it weekly with Apify Schedules and send results to Google Sheets, Slack or a webhook.

### Pricing

| Event | Price |
|---|---|
| Keyword report (all sections included) | **$3.00 per 1,000 keywords** ($0.003 each) |
| Trending search (Trending now mode) | **$0.50 per 1,000 trending searches** |

Apify also charges a small fee each time a run starts. A run analysing 20 keywords costs about **$0.06**.

### FAQ

**Why are values 0–100?** Google Trends normalises interest to 100 at the peak of the selected range and location. Values compare popularity, not absolute search volume.

**Why do rising queries sometimes look unrelated?** They are Google's own "rising" list. Short or ambiguous terms (e.g. "crm") pull in unrelated searches. Use a category ID or a more specific keyword.

**Why can a run take a little while?** Google rate-limits Trends heavily. The Actor paces its requests and retries automatically, so you get complete data instead of errors.

**Where are related topics?** Google currently returns an empty related-topics list to automated requests, so this section is off by default. You can still switch it on under Sections; it costs nothing extra.

**Something missing or broken?** Open an issue on the Issues tab. We answer within 24 hours.

***

Built and maintained by Rimu Labs ([rimulabs.com](https://rimulabs.com)).

# Actor input Schema

## `mode` (type: `string`):

Keyword trends returns one report per keyword. Trending now returns today's trending searches with approximate traffic and news links.

## `searchTerms` (type: `array`):

Keywords or topics to analyse, e.g. "crm", "electric bikes".

## `compare` (type: `boolean`):

Compares up to 5 keywords together, so the interest values are relative to each other, as on the Trends website. Charged per keyword.

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

Country code (US, GB, NZ), region code (US-CA, AU-NSW), or empty for worldwide.

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

Ignored when a custom start and end date are set.

## `startDate` (type: `string`):

Optional. Set both start and end date for a custom range.

## `endDate` (type: `string`):

Optional. Set both start and end date for a custom range.

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

Which Google property's searches to analyse.

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

Optional Google Trends category ID to disambiguate a term (0 = all categories).

## `sections` (type: `array`):

All sections are included in the per-keyword price. Fewer sections run faster.

## `trendingGeos` (type: `array`):

Country codes for Trending now mode, e.g. US, GB, NZ, AU, DE.

## `maxTrendingPerGeo` (type: `integer`):

Upper limit of trending searches returned per country.

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

Google Trends rate-limits single IPs; a proxy keeps runs reliable.

## Actor input object example

```json
{
  "mode": "keywords",
  "searchTerms": [
    "crm",
    "project management software"
  ],
  "compare": false,
  "geo": "",
  "timeRange": "past-12-months",
  "searchType": "web",
  "category": 0,
  "sections": [
    "interestOverTime",
    "interestByRegion",
    "relatedQueries"
  ],
  "trendingGeos": [
    "US"
  ],
  "maxTrendingPerGeo": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `keywords` (type: `string`):

One report per keyword: trend summary, interest over time, by region, related queries and topics.

## `trending` (type: `string`):

Today's trending searches per country with approximate traffic and news links.

## `summary` (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 = {
    "searchTerms": [
        "crm",
        "project management software"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("rimulabs/google-trends-insights").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 = {
    "searchTerms": [
        "crm",
        "project management software",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("rimulabs/google-trends-insights").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 '{
  "searchTerms": [
    "crm",
    "project management software"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call rimulabs/google-trends-insights --silent --output-dataset

```

## MCP server setup

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

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/mVTR3xZ5MncWFDsg3/builds/hrdhZ0INadtg7cL1u/openapi.json