# Google Trends Scraper & API - Trending Now, Related Queries (`kalilfagundes.w/google-trends-scraper`) Actor

\[Limited Launch Offer $1/1K] Google Trends without an API key: interest over time, compare up to 5 keywords, interest by region and city, rising related queries and the full Trending Now list of trending searches with news, many countries per run.

- **URL**: https://apify.com/kalilfagundes.w/google-trends-scraper.md
- **Developed by:** [Scrape With Me](https://apify.com/kalilfagundes.w) (community)
- **Categories:** SEO tools, Marketing, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 keywords

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 Scraper Pro - Multi-Country, Related Queries, Trending Now, CSV

Get Google Trends data without a Google account or API key: **interest over time**, **comparisons of up to 5 keywords**, **interest by country, state or city**, **top and rising related queries**, and **every Trending Now search with news articles** - for **many countries in one run**. Results come as clean dataset rows (JSON, CSV, Excel) plus **ready-made CSV time series** you can drop into Excel, Google Sheets, pandas or a BI tool.

It talks to Google Trends' own JSON endpoints - no headless browser - so a keyword usually takes about 4-5 small requests and a few seconds.

### Why this one

- **Several countries per run.** Put `US`, `BR`, `DE` in *Several countries (geos)* and every keyword is fetched for each country - one row per keyword and country. Trending Now works the same way.
- **Spreadsheet-ready time series.** Each keyword run also writes two CSV files: `TIMESERIES` (long format: keyword, geo, date, value) and `TIMESERIES_WIDE` (one column per keyword, one row per date).
- **The full Trending Now list, not just the RSS top 10.** For example, 480 trending searches for the United States and 144 for Brazil in the past 24 hours (2026-10-04), with search volume, growth, start/end time, topics, related searches and news. If Google's list call fails, the actor retries, then fetches the list without news, and only then falls back to the RSS feed - and tells you which one you got.
- **Built for reliability.** One session per keyword (Google ties its tokens to the IP), paced requests, a retry after HTTP 429, and fresh sessions on new IPs. In `auto` mode it starts without a proxy and moves to Apify datacenter and then residential proxies only when Google throttles; choose `residential` to use residential IPs from the first request.
- **You only pay for data.** A keyword Google has no data for is not saved and not charged; the run summary says why.

### What can I get?

| Report (`mode`) | One row per | Data |
|---|---|---|
| `keywords` (default) | keyword × country | Interest over time (0-100), interest by region, top & rising related queries |
| `compare` | keyword × country | 2-5 keywords on **one shared scale**, plus Google's average per keyword |
| `trending` | trending search | Every Trending Now search for the past 4, 24, 48 hours or 7 days, with news |
| `suggestions` | keyword | The topics (and topic ids) Google matches a word to |

Any search type (web, News, Images, YouTube, Shopping), any country or worldwide, any of Google's categories, preset periods from the past hour to 2004-present, or two custom dates.

### Input examples

Several keywords in several countries:

```json
{
  "mode": "keywords",
  "searchTerms": ["chatgpt", "gemini", "claude"],
  "geos": ["US", "BR", "DE"],
  "timeRange": "today 12-m"
}
```

A comparison straight from a Google Trends link (keywords, country, dates, category and search type are read from the URL):

```json
{
  "mode": "compare",
  "searchTerms": ["https://trends.google.com/trends/explore?q=iphone,samsung&geo=BR&date=today%203-m"]
}
```

Trending Now in two countries, 50 trends each, 2 news articles per trend:

```json
{ "mode": "trending", "geos": ["US", "GB"], "trendingHours": "24", "newsPerTrend": 2, "maxItems": 50 }
```

### Output example

A `keywords` row (arrays shortened):

```json
{
  "keyword": "bitcoin",
  "keywordType": "Search term",
  "geo": "US",
  "geoName": "United States",
  "timeRange": "today 3-m",
  "startDate": "2026-07-04",
  "endDate": "2026-10-04",
  "step": "day",
  "interestOverTime": [
    { "date": "2026-07-04", "value": 77, "isPartial": false },
    { "date": "2026-10-04", "value": 39, "isPartial": true }
  ],
  "regionLevel": "region",
  "interestByRegion": [
    { "regionName": "Kansas", "regionCode": "US-KS", "value": 100 },
    { "regionName": "Nevada", "regionCode": "US-NV", "value": 83 }
  ],
  "relatedQueries": {
    "top": [{ "query": "bitcoin price", "value": 100 }, { "query": "bitcoin stock", "value": 21 }],
    "rising": [{ "query": "suriname meaning", "value": 3900, "growth": "+3,900%" }]
  },
  "missing": [],
  "trendsUrl": "https://trends.google.com/trends/explore?q=bitcoin&date=today%203-m&geo=US",
  "scrapedAt": "2026-10-04T18:12:57+00:00"
}
```

A `trending` row:

```json
{
  "term": "como votar nas eleições do brasil",
  "geo": "BR",
  "trendingHours": "24",
  "isActive": true,
  "startedAt": "2026-10-04T02:00:00+00:00",
  "searchVolume": 1000000,
  "increasePercent": 1000,
  "categories": ["Politics"],
  "relatedSearches": ["como votar nas eleições do brasil", "ate que horas pode votar", "titulo de eleitor"],
  "news": [{ "title": "Radar da eleição: acompanhe a votação do primeiro turno", "source": "UOL Notícias", "url": "https://noticias.uol.com.br/...", "publishedAt": "2026-10-04T17:38:44+00:00" }]
}
```

`TIMESERIES_WIDE` (key-value store) for two keywords in two countries:

```csv
date,bitcoin (US),ethereum (US),bitcoin (BR),ethereum (BR)
2026-07-04,77,63,47,27
2026-07-05,84,66,46,25
```

The `OUTPUT` record holds the run summary: every keyword and country with its status (`ok`, `partial`, `skipped`), the reason in plain English, and how many requests were made.

### Run it on a schedule and connect it to your tools

**Schedule:** in Apify Console open *Schedules → Create*, pick this actor and your input, and set it to run
every Monday at 07:00 (your time zone) for a fresh dataset on a fixed day. Each run returns the full, current result set as a new dataset.

**Integrations** (Actor → *Integrations* tab, no code):

- **Google Sheets** — append every run's rows to a sheet.
- **Make, Zapier, n8n** — start the actor from a scenario/zap/workflow and use the rows in the next steps.
- **Webhook** — get a POST to your endpoint when a run succeeds, then download the dataset.
- **Slack / email** — notify your team when a scheduled run finishes.

**AI agents (MCP)** — Claude, ChatGPT, Cursor, VS Code or any MCP client can run it as a tool: add the Apify MCP
server `https://mcp.apify.com?actors=kalilfagundes.w/google-trends-scraper` (sign in with your Apify account) and ask for the data in
plain language. The agent fills the input from the input schema and reads the dataset back.

**API** — call it from your code (`pip install apify-client` / `npm i apify-client`):

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("kalilfagundes.w/google-trends-scraper").call(run_input={
    "mode": "keywords",
    "searchTerms": [
        "chatgpt",
        "gemini",
        "claude"
    ],
    "geos": [
        "US",
        "BR",
        "DE"
    ],
    "timeRange": "today 12-m",
    "proxyMode": "residential"
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('kalilfagundes.w/google-trends-scraper').call({
  "mode": "keywords",
  "searchTerms": [
    "chatgpt",
    "gemini",
    "claude"
  ],
  "geos": [
    "US",
    "BR",
    "DE"
  ],
  "timeRange": "today 12-m",
  "proxyMode": "residential"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

### Pricing

Pay per event, platform usage included - see the **Pricing** tab for the current prices:

- `keyword` - one keyword × country with interest over time and/or interest by region
- `related-queries` - added when Google returned related queries for that keyword
- `trend` - one Trending Now search
- `suggestions` - one keyword looked up for topic suggestions

Keywords without data are not charged. Set a maximum cost per run in the run options to cap spending; the actor stops cleanly when it is reached.

### FAQ

**Are the values search counts?** No. Google Trends gives a 0-100 index relative to the highest point in the chosen period and place. To compare keywords fairly, use `compare` mode so they share one scale.

**Why is the last point `isPartial`?** The current day/week is not finished yet; Google marks it as partial.

**What time zone are the dates in?** UTC.

**Do I need a proxy?** No configuration is needed. `auto` handles Google's throttling by moving to Apify proxies when needed; `residential` uses residential IPs from the start for large or scheduled runs.

**Why are related topics missing?** The endpoints this actor uses return related *queries* reliably; related *topics* came back empty in tests, so they are not included rather than returned empty.

**How do I monitor trends every day?** Save your input as a task and add an Apify Schedule; each run writes fresh rows and CSV files.

**Can I call it from code or an AI agent?** Yes - through the Apify API, the Python/JS clients, Make, n8n, Zapier, or the Apify MCP server.

### Limitations

- Countries only for `geo`/`geos` (no state- or city-level *filter*; states and cities are available as *results* via `regionLevel`).
- Up to 50 countries per run; compare is limited to 5 keywords per comparison (Google's own limit).
- Google can change its endpoints at any time; the actor reports exactly what failed in `OUTPUT`.

### Related actors

- [Meta Threads Scraper - Posts, Replies, Profiles & Hashtags](https://apify.com/kalilfagundes.w/threads-scraper)
- [Reddit Scraper - Posts, Comments, Subreddits, No API Key](https://apify.com/kalilfagundes.w/reddit-scraper)
- [Weibo Scraper - Hot Search, Posts, Comments & Profiles 微博](https://apify.com/kalilfagundes.w/weibo-scraper)

### Feedback

If this actor saves you time, a quick rating on its Store page helps other people find it. Something not working? Open an issue in the **Issues** tab and it gets fixed fast.

# Actor input Schema

## `mode` (type: `string`):

Choose the report type. keywords: each keyword on its own 0 to 100 scale. compare: 2 to 5 keywords on one shared scale, like typing them side by side on trends.google.com. trending: every Trending Now search in a country. suggestions: the topics Google matches each keyword to.

## `searchTerms` (type: `array`):

Type the keywords to look up, one per line, for example bitcoin. "bitcoin, ethereum" on one line counts as two keywords, and you can paste a Google Trends link: its keywords, country and dates are used. In compare mode, enter 2 to 5. Not needed for Trending Now. Technical: search terms or topic ids such as /m/05p0rrx (Bitcoin); same as kw_list in pytrends and q in SerpApi.

## `geo` (type: `string`):

Pick a country, or leave it on Worldwide (WW). You can also type a country name such as India or a two-letter code such as IN. Trending Now uses United States when this is empty. Technical: Google Trends geo, ISO 3166-1 alpha-2; states and cities are not supported.

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

Optional. Run the same keywords (or Trending Now) for several countries in one run, for example US, BR, DE. Each keyword is looked up once per country and comes back as its own row, so a row is billed per keyword and country. Use WW for worldwide. When filled in, it replaces Country (geo). Up to 50 countries.

## `timeRange` (type: `string`):

Pick the time period to look at, or type your own dates as two YYYY-MM-DD dates with a space, such as 2024-01-01 2024-06-30. Google picks the step: minutes for the past hour, hours for 7 days, days for 3 months, weeks for 12 months. Same as timeframe in pytrends and date in SerpApi.

## `dataTypes` (type: `array`):

Choose the data to fetch for each keyword: interest over time, interest by region and related queries (top and rising). All three by default. Related queries are billed as their own event per keyword, see Pricing. Fewer parts also finish sooner. Same idea as data_type in SerpApi.

## `property` (type: `string`):

Pick the search type to measure: web search (the default), News, Images, YouTube or Google Shopping. Same as gprop in pytrends and SerpApi (froogle is Google's own code for Shopping).

## `category` (type: `integer`):

Enter a subject area number to count only searches about one subject, or 0 for all subjects (the default). These are Google Trends category ids, for example 7 Finance, 5 Computers & Electronics, 71 Food & Drink, 20 Sports, 3 Arts & Entertainment. Same as cat in pytrends and SerpApi.

## `regionLevel` (type: `string`):

Choose the region detail for interest by region: countries, states or provinces, or cities. auto lets Google choose: countries for worldwide, states or provinces inside one country. Same as resolution in pytrends.

## `trendingHours` (type: `string`):

Pick the trending period for Trending Now: the past 4, 24 or 48 hours, or the past 7 days (168 hours). Used only in trending mode. Same as hours in SerpApi's Trending Now API.

## `trendingCategory` (type: `string`):

Pick a trend topic to keep only the trends Google files under it, such as sports, technology or politics. all keeps every trend (the default). These are Google's 19 Trending Now topics, a different list from the subject area numbers. Used only in trending mode. Same as category_id in SerpApi's Trending Now API, which takes Google's numbers (18 is technology).

## `newsPerTrend` (type: `integer`):

Enter how many news stories to attach to each trend, from 0 to 10. Default 3. News is included in the trend price. Used only in trending mode.

## `maxItems` (type: `integer`):

Enter the number of trends to save at most per country, to cap what a Trending Now run costs. 0 saves every trend (the default). Used only in trending mode.

## `proxyMode` (type: `string`):

auto (recommended): starts without a proxy, moves to Apify datacenter and then residential proxies only when Google throttles, so runs stay cheap and fast. residential: every request goes through Apify residential proxies from the start - the most reliable choice for large or scheduled runs.

## Actor input object example

```json
{
  "mode": "keywords",
  "searchTerms": [
    "bitcoin",
    "chatgpt"
  ],
  "geo": "WW",
  "geos": [
    "US",
    "BR",
    "DE"
  ],
  "timeRange": "today 12-m",
  "dataTypes": [
    "interestOverTime",
    "interestByRegion",
    "relatedQueries"
  ],
  "property": "web",
  "category": 0,
  "regionLevel": "auto",
  "trendingHours": "24",
  "trendingCategory": "all",
  "newsPerTrend": 3,
  "maxItems": 0,
  "proxyMode": "auto"
}
```

# Actor output Schema

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

Every row of the run in the default dataset: one per keyword, per Trending Now search or per suggestions lookup. Export as JSON, CSV or Excel.

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

The OUTPUT record in the default key-value store: every keyword you typed with its status (ok, partial or skipped), the reason in plain English and the parts Google left empty.

## `timeseries` (type: `string`):

keyword, geo, geoName, date, value, isPartial - one line per point of interest over time. Pivot-table and BI friendly. Written for keywords and compare runs.

## `timeseriesWide` (type: `string`):

One line per date and one column per keyword (keyword (GEO) with several countries). Ready to chart in Excel or Google Sheets.

# 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 = {
    "searchTerms": [
        "bitcoin",
        "chatgpt"
    ],
    "geos": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("kalilfagundes.w/google-trends-scraper").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 = {
    "searchTerms": [
        "bitcoin",
        "chatgpt",
    ],
    "geos": [],
}

# Run the Actor and wait for it to finish
run = client.actor("kalilfagundes.w/google-trends-scraper").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 '{
  "searchTerms": [
    "bitcoin",
    "chatgpt"
  ],
  "geos": []
}' |
apify call kalilfagundes.w/google-trends-scraper --silent --output-dataset

```

## MCP server setup

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

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/adboyevLkpBPQGtaS/builds/42dg7RncmnSrxVLcn/openapi.json