# Google Trends Scraper - Trending Searches by Country (`gganbukim/google-trends-scraper`) Actor

Scrape Google trending searches for any country with approximate search traffic, the news stories driving each trend, and optional autocomplete expansion into related queries. Built on the stable RSS feed rather than the explore API, so scheduled runs do not fail.

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

## Pricing

from $2.00 / 1,000 trending search delivereds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Google Trends Scraper — Daily Trending Searches by Country with News & Traffic

What a country is searching for **right now**, with approximate traffic, the news stories driving each trend, and optionally the autocomplete queries people type next.

Works for every country Google publishes trends for — US, GB, KR, DE, IN, JP, BR and the rest — in one run.

### Built on the boring endpoint, on purpose

Google exposes trends two ways: the `/trends/api/explore` widget flow, and a plain RSS feed.

Explore is the one most scrapers use, and it is fragile — it returned **HTTP 429 on the very first unauthenticated call** during our testing, and it needs a two-step token handshake that breaks whenever Google reshuffles its widget IDs. The most-used Google Trends actor on this store currently runs a **23.2% failure rate at 3.64★**, which is what that fragility looks like in production.

This one reads the RSS feed: a small, stable, cacheable document. Choosing the boring endpoint is the entire competitive move.

### Input

```jsonc
{
  "geos": ["US", "GB", "KR"],
  "minTraffic": 5000,
  "includeNews": true,
  "expandWithAutocomplete": true,
  "mustContain": ["ai", "crypto"]
}
```

### Output

```json
{
  "geo": "US",
  "keyword": "extreme heat warning",
  "approxTraffic": "500+",
  "approxTrafficNumber": 500,
  "pubDate": "Tue, 12 Aug 2026 09:40:00 -0700",
  "scrapedAt": "2026-08-12T17:05:11.402Z",
  "news": [
    {
      "title": "UK heatwave live: Burnham considers ban on disposable barbecues",
      "url": "https://…",
      "source": "The Guardian"
    }
  ],
  "relatedQueries": ["extreme heat warning today", "extreme heat warning meaning", "…"]
}
```

`scrapedAt` is stamped on every row so scheduled runs build a clean time series.

### Common uses

- **Newsjacking** — schedule it hourly with `mustContain` on your category and publish while a trend is live.
- **Content calendars** — `expandWithAutocomplete` turns a bare trend into actual article angles.
- **Market monitoring** — track when your brand, a competitor, or a category breaks into a country's trends.
- **Trend datasets** — run daily across many countries and accumulate history.
- **Ad targeting** — catch rising terms before the keyword tools update.

### Pricing

Pay per trend delivered. Trends removed by your traffic or keyword filters **cost nothing**.

Starting a run costs $0.00004 — the platform's $0.00001 minimum, charged once per GB of memory, and these Actors run on 4 GB. That is four cents per thousand runs, and it is the only charge not tied to a row you received.

### FAQ

**How many trends per country?** Google publishes roughly 10–20 per country per day in this feed.

**Can I get historical interest-over-time?** Not from this actor. That data only exists behind the explore API, which is the unreliable path this deliberately avoids.

**How fresh is it?** As fresh as Google's feed, which updates through the day. `pubDate` tells you when the trend started.

**Can I run it on a schedule?** Yes — that is the main use. Apify Schedules, webhooks, or the API. Also available over MCP for AI agents.

# Actor input Schema

## `geos` (type: `array`):

ISO-3166 country codes, e.g. US, GB, KR, DE, IN. One row per trending search per country.

## `minTraffic` (type: `integer`):

Google reports traffic in buckets like "20,000+". Drop trends below this number. Filtered rows are not billed.

## `mustContain` (type: `array`):

Keep only trends containing one of these substrings — useful for brand or category monitoring on a schedule. Case-insensitive.

## `includeNews` (type: `boolean`):

Attach the news headlines, URLs and sources Google associates with each trend. This is what tells you why something is trending.

## `expandWithAutocomplete` (type: `boolean`):

For each trend, also pull Google autocomplete suggestions for it. Turns a bare trend into a content angle. Costs one extra request per trend.

## `concurrency` (type: `integer`):

Countries fetched in parallel.

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

Leave the default. Trends rate-limits per IP; the actor starts on cheap datacenter proxies and escalates only if blocked.

## Actor input object example

```json
{
  "geos": [
    "US"
  ],
  "minTraffic": 0,
  "includeNews": true,
  "expandWithAutocomplete": false,
  "concurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per trending search, with its traffic estimate and the news stories behind it.

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

Counts for this run: rows delivered, rows filtered, items that failed, the proxy tier used, and whether the run stopped at its charge limit.

# 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 = {
    "geos": [
        "US"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("gganbukim/google-trends-scraper").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 = { "geos": ["US"] }

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

```

## MCP server setup

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

```

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/UbMJkMu6jn6k2b4SJ/builds/2kRjI7lupe0bh0Zba/openapi.json