# Google Trends Trending Now – Trending Searches by Country (`rowfeed/google-trends-trending-now`) Actor

Google Trends Trending Now as JSON: hundreds of trending searches per country or US state with search volume, growth %, start time, categories and related queries. No login, no proxy.

- **URL**: https://apify.com/rowfeed/google-trends-trending-now.md
- **Developed by:** [Rowfeed](https://apify.com/rowfeed) (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 $1.00 / 1,000 trends

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

Get Google Trends "Trending Now" as clean JSON: the searches that are spiking right now in any country or US state, with search volume, growth, start time, category and related searches.
Built for SEO and content teams, newsrooms, marketers, researchers and AI agents that need a daily list of what people are searching for, without a Google account, API key or proxy.
One run covers as many regions as you list. Hundreds of trends per large region (about 300 for the US in 24 hours, about 1,900 in 7 days), sorted by search volume.

### What you get

- **Search volume and growth:** how many searches in the window (Google reports steps such as 1,000, 20,000, 1,000,000) and how fast interest is growing, in percent.
- **When and what:** the exact start time, an end time once the trend is over, a `still trending` flag, category names such as Sports, Politics or Entertainment, and the related searches Google groups under the trend.
- **Filters that save money:** pick the time window (4 hours, 24 hours, 48 hours, 7 days), categories, a minimum search volume, still-trending only, and the top N per region.

### Example row

```json
{
  "rank": 1,
  "query": "wnba playoffs",
  "geo": "US",
  "search_volume": 2000000,
  "growth_percent": 1000,
  "started_at": "2026-09-29T12:10:00+00:00",
  "ended_at": null,
  "is_active": true,
  "categories": ["Sports"],
  "category_ids": [17],
  "related_queries": ["lynx vs liberty", "minnesota lynx", "wnba 2026"],
  "news_article_count": 42,
  "trend_url": "https://trends.google.com/trends/explore?q=wnba%20playoffs&geo=US",
  "window_hours": 24,
  "language": "en-US",
  "source": "trending_now",
  "scraped_at": "2026-09-30T12:03:13+00:00"
}
```

### Input

| Field | What it does |
|---|---|
| `geos` | Region codes: countries (`US`, `GB`, `DE`, `NO`, `JP`) or US states (`US-CA`). Default `US`. |
| `hours` | Window: 4, 24 (default), 48 or 168 hours. |
| `maxTrendsPerGeo` | Keep the top N per region by search volume. Default 50. |
| `categories` | Only these categories (Sports, Politics, Entertainment, Business & Finance, Technology, and more). Empty = all. |
| `minSearchVolume` | Skip small trends. Default 0. |
| `activeOnly` | Keep only trends that have not ended yet. |
| `language` | Google's interface language, for example `en-US` or `nb-NO`. |

`rank` is the trend's position in its region by search volume before your filters, so a filtered run keeps the true rank.

### Pricing

Pay per event: **$1 per 1,000 trends** ($0.001 per trend), plus a start fee of $0.001 per run. The default run (top 50 for the US) costs about $0.05. Error rows, such as an unknown region code, are never charged. A run where every region code is unknown ends as failed, with the reason in the error rows.

### Good to know

- Data comes from Google's public Trending Now page, with no login and no proxy. If Google ever changes that page, the Actor falls back to Google's public Trending Now feed, which lists 10 searches per region; those rows have `"source": "rss_fallback"`, no growth, category or related searches, and volume in rough steps. Fallback rows always cover about the last 24 hours and are not filtered by category.
- Search volume, growth and categories are Google's own numbers and labels: volume is rounded, `growth_percent` tops out at 1000, and a category can be debatable (a match between two national teams may be filed under Other).
- In the 7-day window a term can appear twice with different start times when it trended in two separate episodes. About two thirds of rows have an empty `related_queries` list: Google groups no other searches under them.
- Trending terms are public search phrases. Some are names of public figures in the news; the Actor returns the phrase only and no profile data.
- `trend_url` opens the term in Google Trends in a browser. This Actor does not return interest-over-time charts.
- Not affiliated with Google. Google Trends is a trademark of Google LLC.
- Schedule it daily and diff the results to spot what is new. Sorted output makes the biggest movers easy to pick up first.

# Actor input Schema

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

Google Trends region codes: a country code such as US, GB, DE, NO or JP, or a state code such as US-CA. Each region is fetched once. An unknown code becomes an unbilled error row instead of stopping the run.

## `hours` (type: `string`):

How far back to look: searches that started trending in the last 4, 24, 48 or 168 hours (7 days).

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

Keep the top N trends per region, ranked by search volume (fastest growth breaks ties). Each trend is one `trend` event ($1 per 1,000).

## `categories` (type: `array`):

Only keep trends in these categories. Leave empty for all categories.

## `minSearchVolume` (type: `integer`):

Skip trends whose search volume (Google reports it in steps such as 1000, 5000, 20000, 1000000) is below this number. 0 keeps everything.

## `activeOnly` (type: `boolean`):

Keep only trends that have not ended yet. Off by default, so ended trends in the window are included with an `ended_at` time.

## `language` (type: `string`):

Interface language for Google's answer, for example en-US, de-DE or nb-NO. The trending searches themselves stay in each region's own language.

## Actor input object example

```json
{
  "geos": [
    "US",
    "GB",
    "DE"
  ],
  "hours": "24",
  "maxTrendsPerGeo": 50,
  "categories": [],
  "minSearchVolume": 0,
  "activeOnly": false,
  "language": "en-US"
}
```

# Actor output Schema

## `results` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("rowfeed/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 = {}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rowfeed/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/cDrgbTw9u0klh2AAZ/builds/S3BMWYcebUEBVutlf/openapi.json