# Google Trends Daily Trending Searches (`xtracto/google-trends-daily`) Actor

Get currently trending Google searches per country with traffic estimates and the related news articles. Keyless RSS source, any number of countries per run, no login.

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

## Pricing

from $1.33 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 — Daily Trending Searches by Country

The searches trending right now in any country, with Google's traffic estimate and the news stories
driving each one. Keyless RSS source, any number of countries per run, no login and no browser.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `geos` | array | `["US"]` | Two-letter country codes — `US`, `GB`, `DE`, `ID`, `JP`, `BR`, `IN`… |
| `maxTrendsPerGeo` | integer | all | Google returns exactly ten per country, so this only lowers that |

### Output

```jsonc
{
  "_input": "US",
  "_source": "S1-trends-rss",
  "_scrapedAt": "2026-09-12T11:04:18Z",

  "geo": "US",
  "rank": 1,
  "query": "austin weather",
  "exploreUrl": "https://trends.google.com/trends/explore?q=austin+weather&geo=US",

  "approxTrafficLabel": "500+",
  "approxTrafficFloor": 500,
  "startedAt": "2026-09-11T21:30:00Z",

  "pictureUrl": "…", "pictureSource": "KXAN Austin",

  "topNewsTitle": "Second arrest made in connection with 24-year-old Austin man's death",
  "topNewsUrl": "https://www.kxan.com/news/crime/…",
  "topNewsSource": "KXAN Austin",
  "newsItems": [
    { "title": "…", "url": "…", "source": "…", "pictureUrl": "…" }
  ],
  "newsItemCount": 3
}
```

### Three things worth knowing

**Every filter parameter you might expect is ignored.** `hours=168`, `category=b`,
`sort=search-volume` and `hl=en` each returned byte-identical output to the bare `geo=US` call. They
mirror the filters the Trends web UI offers, but the RSS feed does not implement them — so this
actor does not offer them either, rather than accept settings that quietly do nothing.

**`approxTrafficFloor` is a floor, not a count.** Google publishes a bucket: `200+`, `500+`,
`1000+`. The parsed number is the bottom of that bucket, named so that nobody sums a column of them
and calls the result search volume. The original label ships alongside it.

**There is no history in this feed — it is a snapshot of now.** Tracking how a trend rises or fades
means running this actor on a schedule and keeping what it returns. The interactive endpoint behind
the Trends charts (`/trends/api/explore`) answers `429` to anonymous callers, which is why this is
built on the RSS feed instead.

### Coverage and gaps

Ten trends per country, each with up to three related articles. Verified returning 10 items for US,
GB, DE, ID, JP, BR and IN; an unknown code gets a clean `400` and becomes an `unknown_geo` row.

Three trends in twenty carried no news articles and no picture at all — Google surfaces those
fields only when it has them, so an empty `topNewsTitle` is a fact about that trend, not a parse
failure. `ht:news_item_snippet` is always empty (111 instances across four countries, every one
self-closing), so it is not emitted at all.

### Errors

| `_error` | Meaning |
|---|---|
| `unknown_geo` | Google rejected the country code with a 400 |
| `empty_feed` | 200 with no `<item>` elements — the format changed |
| `unexpected_shape` | An item with no title |
| `blocked` | The feed returned nothing usable |
| `network_error` | Never reached the server |

If no country returns trends, the run fails rather than reporting success over an empty dataset.

# Actor input Schema

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

Two-letter country codes, e.g. US, GB, DE, ID, JP, BR, IN. One request per country; each returns that country's ten current trends.

## `maxTrendsPerGeo` (type: `integer`):

Google's feed returns exactly ten per country, so this only lowers that.

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

Optional and not needed. This is a public RSS feed with no anti-bot layer.

## Actor input object example

```json
{
  "geos": [
    "US",
    "ID"
  ]
}
```

# Actor output Schema

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

One row per scraped record, stored in the run's default dataset.

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

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

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

```

## MCP server setup

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

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/3S1sWkm1NvyYHytMe/builds/lblGtLtgVg4oaCLxx/openapi.json