# Google Trends Trending Now Scraper : by country, volume, CSV (`tallyrake/google-trends-trending-now`) Actor

The Trending Now list from Google Trends as flat rows: title, country, start time, approximate search volume, growth percent, related queries and category ids, for the past 4 hours to 7 days, any country. $0.25 per 1,000 rows.

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

## Pricing

$0.25 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Google Trends Trending Now Scraper: by country, volume, CSV

The Trending Now list from Google Trends as flat rows. Pick countries and a time window (past 4 hours, 24 hours, 48 hours or 7 days) and get each trending search with its start time, approximate search volume, growth percent, related queries and category ids. One row per trend with a stable `id`. $0.25 per 1,000 dataset rows; $0.50 from 28 Sep 2026.

See today's list (top 20 per country, free) at https://tallyrake.com/trending/.

### What you get

| Field | Example |
|---|---|
| `id` | `8d31c922ab747290` (stable per country, window, title and start time) |
| `type` | `trend` (or `relatedQuery` when that option is on) |
| `geo` | `US` |
| `position` | `1` (order on the Trending Now list) |
| `title` | `lil durk` |
| `startedAt` | `2026-09-11T23:10:00.000Z` |
| `endedAt` | `null` while the trend is active |
| `isActive` | `true` |
| `searchVolume` | `200000` (Google's bucketed estimate for the window) |
| `growthPercent` | `1000` |
| `relatedQueries` | `["is lil durk free", "lil durk trial", ...]` |
| `relatedQueryCount` | `27` |
| `categoryIds` | `[10, 4]` |
| `newsArticleCount` | `12` |
| `hours` | `24` |
| `fetchedAt` | ISO timestamp |

`explodeRelatedQueries` also outputs one `relatedQuery` row per related query, for spreadsheets that want one phrase per line. It multiplies the bill: one trend with `relatedQueryCount` 27 is 28 billed rows (1 + 27). The 2026-09-11 US snapshot was not run with this option on, so there is no sourced exploded row count or dollar figure yet. Leave it off unless you need the flat form.

### Where this sits on the shelf

Apify Store search for "trending now", the 11 Google Trends listings in the top results on 2026-09-11, read from the Store API. Price is the pay-per-event charge per dataset item, converted to per 1,000 rows; users, runs and the failed-or-timed-out share are the Store's 30-day public stats for each listing.

| Listing | Users (30d) | Runs (30d) | Failed or timed out | Price per 1,000 rows |
|---|---|---|---|---|
| data\_xplorer/google-trends-trending-now | 44 | 1,797 | 0% | free |
| memo23/google-trends-scraper | 5 | 329 | 11% | $3.00 |
| habit.zhou/google-trends-discovery | 3 | 56 | 0% | $0.50 |
| ballast/google-trends-scraper | 3 | 51 | 39% | $2.00 |
| ryyos/google-trends-indonesia-trending | 2 | 29 | 0% | $1.00 |
| glitchbound/google-trends-scraper | 2 | 34 | 3% | free |
| scrapesignal\_labs/google-trends-trending-now | 1 | 14 | 0% | $0.10 |
| scrapersdelight/google-trends-trending-now-scraper | 1 | 15 | 0% | $2.00 |
| peerless\_columbine/google-trends-scraper-api | 1 | 3 | 0% | free |
| automation\_craft/google-trends-scraper | 0 | 30 | 0% | $20.00 |
| orbots/google-trends-scraper | 0 | 51 | 6% | $10.00 |
| tallyrake/google-trends-trending-now (this actor) | 0 | 1 | 0 of 1 | $0.25 ($0.50 from 28 Sep 2026) |

### Recipes

**Daily trend digest for one country.** `geos` = `US`, `hours` = 24, schedule at 06:00 local. One 24-hour US snapshot on 2026-09-11 was 378 rows (GB in the same run: 368). Re-run for a few days before you plan on a range.

**Breaking trends every hour.** `hours` = 4, `minSearchVolume` = 20000, schedule hourly. Only the spikes; the row count depends on the day.

**Cross-country comparison.** `geos` = `US`, `GB`, `DE`, `IN`, `BR`, `hours` = 48. One request per country; rows carry the country code so the dataset merges cleanly.

**Content calendar from related queries.** Any window with `explodeRelatedQueries` on. Filter `type = relatedQuery` in the dataset view.

### Reliability and cost

Measured 2026-09-11 with Apify datacenter proxy, one run: `geos` = US, GB, `hours` = 24 produced 378 US trends + 368 GB trends = 746 dataset rows; 3 requests (1 session warm-up + 1 per country); 0 of 3 rate-limited; 27 s wall; platform usage $0.00013. At $0.25 per 1,000 rows that run bills $0.19 in results. (From 28 Sep 2026 the price is $0.50 per 1,000 rows; the same 746 rows would then be $0.37.)

Each country and window is one request after a one-time session warm-up. The code rotates its session and retries on a 429 or 403; that path was not exercised in the measured run (0 of 3). Single-country duration was not timed separately.

### Cost limit

If a run reaches the "Maximum total charge per run" you set, it stops in process rather than being aborted by the platform: the run ends with status SUCCEEDED, and the run status message on the run detail says how many rows were written and how many were found but not written and not billed. Re-running the same input writes and bills the same prefix again, so raise the cap before re-running if you want the rest.

### Limits

This is the Trending Now surface only, the list Google publishes per country. For interest over time, interest by region and related queries for your own search terms, use the companion Google Trends Scraper actor. Search volume is Google's bucketed estimate, not an exact count.

# Actor input Schema

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

Two-letter country codes, one per line (US, GB, DE, IN, BR, JP ...). One request per country.

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

Trends that started in the last 4, 24, 48 or 168 hours (the same choices as the Trending Now page).

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

Only trends that are still rising. Off returns trends that already peaked in the window too.

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

Drop trends below this approximate search volume (Google buckets: 1000, 2000, 5000, 10000, 20000, 50000, 100000, 200000 ...). 0 keeps all.

## `maxItemsPerGeo` (type: `integer`):

0 = all trends in the window (a 24 hour US window is a few hundred).

## `explodeRelatedQueries` (type: `boolean`):

Also output a relatedQuery row for every related query (type = relatedQuery), for CSV users who want one query per line.

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

Interface language for titles, e.g. en, de, es, ja.

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

Google Trends rate-limits by IP. Apify Proxy is recommended; the run rotates its session on a 429.

## `pacingMs` (type: `integer`):

Base jittered delay between requests; 0 disables pacing.

## Actor input object example

```json
{
  "geos": [
    "US"
  ],
  "hours": "24",
  "activeOnly": true,
  "minSearchVolume": 0,
  "maxItemsPerGeo": 0,
  "explodeRelatedQueries": false,
  "language": "en",
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "pacingMs": 500
}
```

# Actor output Schema

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

Rows of type trend (one per trending search per country).

## `relatedQueries` (type: `string`):

Rows of type relatedQuery when that option is on.

## `csv` (type: `string`):

All rows as CSV.

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

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

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

```

## MCP server setup

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