# Google Trends Trending Now RSS — Country Snapshots (`kaz_kakyo/google-trends-trending-now`) Actor

Current Google Trends public RSS snapshots for newsroom briefs and SEO planning. Query, approximate traffic bucket, publication time and linked headlines. Bounded country batches; RSS subset only, no keyword-interest history. Pay per nonempty country snapshot.

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

## Pricing

from $3.00 / 1,000 current country rss snapshots

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 Trending Now RSS — Country Snapshots

Get a small current-topic brief from Google's public Trending Now RSS export. Useful for a newsroom researcher choosing stories or an SEO content planner checking emerging queries across markets. Each dataset record is one country snapshot with nested trend queries, approximate traffic buckets, publication dates and linked news headlines.

This is the **current RSS subset**, which can be smaller than Google's full Trending Now page. No keyword-interest charts, historical backfill, interest-by-region, growth percentage, active-status filter, categories or inferred popularity score. It never retrieves news article bodies, contact details or personal profiles. A query can mention a public person; it represents aggregate search activity.

### Input

```json
{"countries":["US","DE","JP"],"maxItemsPerCountry":20,"maxResults":3}
```

- `countries`: 1–10 uppercase codes from US, GB, SG, CA, AU, DE, FR, JP, IN, BR, ES, IT, NL, SE, NO, DK, FI, KR, NZ, MX. Duplicate codes are collapsed. US, Germany and Japan were checked on October 5, 2026; other listed feeds have not been verified in that check and may be empty or unavailable.
- `maxItemsPerCountry`: 1–50, default 20. Retains Google RSS order; asking for more does not enlarge the source feed.
- `maxResults`: maximum delivered country snapshots, 1–10, default 10. Also set Apify's maximum cost per run to cap your budget.

No Google login, API key or proxy. One upstream request per valid country, no retries, at most 10 source requests/run. Invalid country entries produce free statuses while valid countries continue. Unsupported options, including dates and keywords, return free status information without fetching.

### Output

Each country row includes `country`, `recordId` (country code within this run), `source`, `sourceUrl`, `fetchedAt`, `availableItems`, `returnedItems`, `truncated` and `trends`. Each trend includes `query`, `trafficLabel`, `trafficLowerBound`, `publishedAt` and up to five `articles` with `title`, `url` and `source`.

`trafficLowerBound` converts a label such as `1000+` to 1000. It is an **approximate bucket lower bound**, not an exact search count or an interest score. `publishedAt` is the source item's time; `fetchedAt` is when the snapshot was collected. News language is chosen by the source and may differ from the country language. Article metadata can be absent; no separate news charge applies. Google decides which queries and articles enter its feed and when it refreshes them.

The default dataset contains snapshots only. The individual trending-query export expands those same nested results into one record per trend; billing remains per country snapshot. Errors, empty feeds, budget stops and the run summary go into a separate free status dataset; `OUTPUT` identifies its dataset ID and says whether work completed. Source failures in one country do not charge for that country and allow remaining countries to proceed. If any item lacks required query/date/traffic fields, the entire country is declined without a snapshot charge.

### Price

Work event: `country-snapshot`, **$0.003 per nonempty country snapshot ($3 per 1,000 snapshots)**. A snapshot includes all returned trends up to your cap and its linked headlines. Three nonempty countries cost $0.009 in work events. Apify's platform-set `apify-actor-start` event is additional; the runtime does not manually charge it again.

No snapshot fee for empty feeds, errors, unsupported input or free status rows. Repeating a run collects and bills a fresh snapshot even if Google has not changed its feed. There is no shared historical archive or cross-run deduplication. Within the same resurrected run, durable pending delivery is recovered without another work-event charge. A possible duplicate row is preferable to silently losing a possibly paid result; there is no cross-run exactly-once guarantee.

Check the Store pricing tab for the currently registered prices before starting a run. A repeated snapshot is a fresh collection job, not a new-trend-only alert.

### Attribution and use

Data attribution is included in every row: **Google Trends Trending Now RSS**, with the exact source feed URL and publisher attribution on every linked article. This actor is independently maintained and unaffiliated with Google. Google's RSS export is described in [Google Trends Help](https://support.google.com/trends/answer/3076011?hl=en). Review Google's [Terms](https://policies.google.com/terms) for your use; public accessibility is not a legal clearance claim. No access-denial bypass is used.

# Actor input Schema

## `countries` (type: `array`):

1–10 distinct uppercase country codes: US, GB, SG, CA, AU, DE, FR, JP, IN, BR, ES, IT, NL, SE, NO, DK, FI, KR, NZ, MX. US/DE/JP live verified; other feed availability can vary.

## `maxItemsPerCountry` (type: `integer`):

Keeps feed order. RSS is a current subset; requesting more cannot enlarge the upstream feed.

## `maxResults` (type: `integer`):

Hard cap on paid snapshots; free status rows use a separate dataset.

## Actor input object example

```json
{
  "countries": [
    "US"
  ],
  "maxItemsPerCountry": 20,
  "maxResults": 10
}
```

# Actor output Schema

## `snapshots` (type: `string`):

Paid nonempty RSS country snapshots with nested current trends.

## `trends` (type: `string`):

Country snapshots expanded into individual trend records for JSON/CSV export; billing remains per country snapshot.

## `summary` (type: `string`):

Completion, caps and failures in OUTPUT; OUTPUT contains a separate status dataset ID.

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

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

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

```

## MCP server setup

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

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/OsDpscbkBEhFl5WSi/builds/vc48ZjZVGyHp7wwQV/openapi.json