# Google Trends Rising Search Monitor - Country Watchlists (`maydit/google-trends-rising-search-monitor`) Actor

Monitor Google Trending Now RSS by country. Keep search terms, approximate traffic labels and related news with saved comparisons. No exact search volumes or interest-over-time history.

- **URL**: https://apify.com/maydit/google-trends-rising-search-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 saved observations

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 Rising Search Monitor - Country Watchlists

**Keep the original traffic bucket and related-news evidence together, and compare changes using stable country/query identities.**

Collect current Google Trending Now RSS searches by country with source traffic labels, related news and saved comparisons. Simple country inputs, CSV/JSON exports and readable reports. No API key.

### Start in under a minute

1. Paste country codes into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose **Start**.
3. Open **Observations**, **Scope and diagnostics**, or the **Readable run report** in Output. Export CSV or JSON from the dataset.

```json
{
  "countries": [
    "US"
  ],
  "maxResults": 5,
  "itemsPerQuery": 3
}
```

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

### Who this helps

SEO teams and editors deciding which emerging searches deserve investigation.

### What you receive

One row per unique confirmed observation. Keyword filters inspect titles and taglines within the current feed window; they do not expand source coverage. Source timestamps that merely refresh do not create a change by themselves. Every row includes a stable `recordId`, title, source URL and observation time.

| Field | Meaning |
|---|---|
| `country` | Source-reported country; missing optional values remain null. |
| `trafficLabel` | Source-reported traffic label; missing optional values remain null. |
| `publishedAt` | Source-reported published at; missing optional values remain null. |
| `relatedNews` | Source-reported related news; missing optional values remain null. |
| `comparisonStatus` | not_requested, new, changed or unchanged |
| `changedFields` | Fields different from your last saved observation |
| `previous` | Previous saved source values when comparison is enabled |

### Saved comparisons

Enable **Compare with saved observations**, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable **Save only new or changed observations** for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

### Scope and limitations

Current Trending Now RSS feed for supported country codes. Traffic labels are approximate source buckets, not exact volumes or forecasts. Feed order is not a popularity rank. No keyword interest-over-time history or percent growth calculation.

At most ten input values and five hundred saved rows per run. Each input performs one bounded public source request. Set Results requested per query to widen the feed window, up to 100 where available; the default is five. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

### Pricing

The configured base price is **$0.001 per saved observation**, plus **$0.00005 per start** at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

### Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

### Examples

1. **Country codes: US** — A bounded US observation sample. Review source evidence and export rows or compare them in a later run.
2. **Country codes: GB** — A bounded GB observation sample. Review source evidence and export rows or compare them in a later run.
3. **Country codes: CA** — A bounded CA observation sample. Review source evidence and export rows or compare them in a later run.

### Source and support

[Official source documentation](https://support.google.com/trends/answer/3076011?hl=en). This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.

# Actor input Schema

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

Up to ten values. Blank uses US.

## `keywords` (type: `array`):

Optional case-insensitive OR filter on title and tagline within the returned source window; this is not a source-wide search.

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

Global saved-row cap across this run. Does not promise complete source coverage.

## `itemsPerQuery` (type: `integer`):

One source page per input. No pagination or full search coverage.

## `comparePrevious` (type: `boolean`):

First comparison run establishes a baseline. Reuse the same inputs and snapshot name. One writer per snapshot.

## `onlyChanges` (type: `boolean`):

Enables comparison. An unchanged run can correctly return zero rows.

## `snapshotName` (type: `string`):

1–80 letters, numbers, underscores or hyphens. Use a distinct name for independent workflows.

## `maxRunSeconds` (type: `integer`):

Requests share the remaining time budget. The platform timeout may stop work earlier.

## Actor input object example

```json
{
  "countries": [
    "US"
  ],
  "keywords": [],
  "maxResults": 5,
  "itemsPerQuery": 5,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 60
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/google-trends-rising-search-monitor").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("maydit/google-trends-rising-search-monitor").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 maydit/google-trends-rising-search-monitor --silent --output-dataset

```

## MCP server setup

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

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/JVkBetNupFfKvh6mE/builds/9ODTb8pF7urAYkH1d/openapi.json