# Google Trends Trending Now (Official RSS) (`southern-data/google-trends-tracker`) Actor

Official Google Trends trending-now RSS for one or more countries. New-trend monitor. No flaky compare scrapers in v1.

- **URL**: https://apify.com/southern-data/google-trends-tracker.md
- **Developed by:** [Southern Data](https://apify.com/southern-data) (community)
- **Categories:** News, AI, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 trend returneds

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 Trending Now (Official RSS)

Fetch **Google Trends “trending now”** topics from Google’s **official RSS feed** for one or more countries. Optional **new-trend mode** remembers what you already saw so a daily schedule only returns fresh topics.

Built for reliability first. We intentionally do **not** scrape interest-over-time, compare, or rising queries in version 1.

### Limits (read these first)

1. **Trending-now RSS only.** Version 1 does **not** support interest-over-time charts, keyword compare, related queries, or “rising” scrapes. Those paths are blocked by design until they can hit ~99% success (competitors often fail ~19% on full Trends scrapers).
2. **About 10 topics per country** — whatever Google puts on that day’s RSS feed.
3. **Official public RSS.** No login, no CAPTCHA bypass, no residential-proxy Trends HTML scrape. You are still responsible for lawful use of the data.
4. **Not every geo is verified.** US, AU, GB and CA were probed successfully. Other ISO codes are best-effort; failed feeds are free.

### Quick start

```json
{
  "geos": ["US", "AU"],
  "mode": "all"
}
```

Daily new-trends monitor:

```json
{
  "geos": ["US"],
  "mode": "new",
  "monitorName": "us-trending-daily"
}
```

### Output fields

| Field | Meaning |
|---|---|
| `title`, `geo` | Topic and country |
| `approxTraffic`, `approxTrafficMin` | Google’s traffic label (e.g. `200+`) |
| `pubDate`, `pictureUrl`, `pictureSource` | When / image |
| `newsItems`, `newsCount` | Related news from the RSS |
| `isNew` | Set in `mode=new` |
| `trendId`, `rssUrl`, `checkedAt` | Ids and provenance |

### Pricing (pay per event)

| Event | Price | When |
|---|---|---|
| `actor-start` | $0.0005 | Once per run, after the first successful feed load |
| `geo-check` | $0.002 | Each country RSS feed loaded |
| `trend` | $0.001 | Each trend row returned |

**Store discount tiers:** free-plan and Bronze users pay the prices above. Silver gets 10% off and Gold (and higher) gets 20% off.

**Free:** invalid input (exit 0), failed feed loads, already-seen topics in `mode=new`, duplicates in the same run.

Typical cost for US+AU returning ~20 topics: **$0.0005 + 2×$0.002 + 20×$0.001 = $0.0245**.

### Self-test

Set `"selfTest": true` for fixture checks plus one live US RSS fetch.

# Actor input Schema

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

Country codes for Google's official trending-now RSS, e.g. US, AU, GB, CA. Each geo loads one feed (~10 topics). Confirmed: US, AU, GB, CA.

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

all = every topic on the feed. new = only topics not seen in earlier runs (set monitorName for schedules). Interest-over-time / compare / rising are NOT in v1.

## `monitorName` (type: `string`):

Stable name for the seen-trends memory, e.g. "us-trending-daily".

## `maxTrends` (type: `integer`):

Hard cap on rows returned (and charged). Default 200.

## `selfTest` (type: `boolean`):

Offline fixture checks plus one live US RSS fetch. Leave off for normal use.

## Actor input object example

```json
{
  "geos": [
    "US",
    "AU"
  ],
  "mode": "all",
  "maxTrends": 200,
  "selfTest": false
}
```

# Actor output Schema

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

One row per trending topic returned.

## `geos` (type: `string`):

GEOS record: per-country feed status.

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

RUN_SUMMARY record.

## `selfTest` (type: `string`):

SELF_TEST record when selfTest: true.

# 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",
        "AU"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("southern-data/google-trends-tracker").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",
        "AU",
    ] }

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

```

## MCP server setup

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

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/G5h7ufH1Oq8e477Pg/builds/F1yVGAn8pE3OJdtru/openapi.json