# Google Trends Scraper & API with Search Volume (`vncntlabs/google-trends-search-volume`) Actor

Google Trends scraper that adds estimated absolute searches per day, week or month to the 0-100 index (Trends x Google Ads volume). Interest over time, by region, related queries and topics (rising + top), compare up to 5 keywords and batch thousands. Web, YouTube, News, Images and Shopping.

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

## Pricing

from $10.00 / 1,000 keyword reports

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 Scraper & API with Search Volume

**A Google Trends scraper that tells you how many people actually searched.** Google Trends only shows a relative 0-100 index; this Actor scales each keyword's Trends curve to its Google Ads monthly volume, so you get 'about 152,000 searches in the week of 12 April' instead of '100'. Get interest over time, interest by region, rising and top related queries and topics, and compare up to 5 keywords, for one keyword or thousands, on Web, YouTube, News, Images or Shopping search.

Each keyword report has:

- **Interest over time**: Google's 0-100 index for every point, plus `estimatedSearches` for that hour, day, week or month.
- **Totals and averages**:
  - `estimatedTotalSearches` for the period
  - `estimatedMonthlySearches` (average per month)
  - peak, latest value, change % and the last month's Google Ads volume
- **Interest by region**: states or regions (or countries for Worldwide), ranked 0-100.
- **Related queries and related topics**, top and rising, with a Breakout flag.
- **Comparisons**: put 2-5 keywords on one line separated by commas, e.g. `pickleball, padel, tennis`. You get Google's comparison chart and region winners. When every keyword has an estimate, you also get its absolute searches and a **share of search %**.
- Any **location**: countries, states and regions (`US-CA`), or Worldwide. **Timeframes** from the past hour to 2004-present, or custom dates.
- **Search types**: web, YouTube, News, Images and Google Shopping. Optional Trends **category**.
- **Batches**: up to 500 keywords x 10 locations per run.

Data comes through DataForSEO's licensed Google Trends API, so there are no proxies, captchas or blocks. A run usually takes 1-3 minutes, because requests go through a queue.

### Input example

```json
{
  "keywords": ["pickleball, padel, tennis", "golf"],
  "locations": ["United States", "United Kingdom"],
  "timeframe": "past_12_months"
}
```

### Output example (keyword report, shortened)

```json
{
  "type": "keyword", "keyword": "pickleball", "location": "United States", "timeframe": "past_12_months",
  "granularity": "week", "status": "ok",
  "estimatedMonthlySearches": 681568, "estimatedTotalSearches": 8150829, "estimateConfidence": "high",
  "googleAdsMonthlyVolume": 673000, "googleAdsMonth": "2026-09",
  "averageInterest": 68.85, "peakInterest": 100, "peakDate": "2026-04-12", "latestInterest": 57, "changePct": 11.5,
  "interestOverTime": [{"date": "2025-10-12", "dateTo": "2025-10-18", "value": 54, "estimatedSearches": 120668,
                        "isPartial": false}],
  "estimate": {"method": "direct", "scalePerIndexPoint": 9896.05, "calibrationMonths": ["2025-11", "...", "2026-09"],
               "fitErrorPct": 8.6, "confidence": "high", "volumeSource": "google_ads_via_dataforseo_labs"},
  "interestByRegion": [{"geoId": "US-WY", "geoName": "Wyoming", "value": 100}],
  "relatedQueries": {"top": [{"query": "pickleball paddle", "value": 100}],
                     "rising": [{"query": "pilla pickleball glasses", "growthPct": 3550, "isBreakout": false}]},
  "relatedTopics": {"top": [{"topicId": "/m/063wkj", "title": "Pickleball", "topicType": "Sports", "value": 100}]},
  "trendsUrl": "https://trends.google.com/trends/explore?hl=en&geo=US&date=today%2012-m&q=pickleball"
}
```

Use the **Keyword reports** and **Comparisons** views for tables. Turn on *one row per data point* to get flat rows
(keyword, date, value, estimatedSearches) for spreadsheets and charts.

### How the estimates work

1. Google Trends gives each keyword a relative index. 100 is the busiest point in the chart.
2. Google Ads gives the exact keyword's absolute monthly searches. We fetch about 7 years of monthly volumes for countries, or 4 years for Worldwide and regions.
3. For each keyword we take the latest 12 complete months that both sources cover and compute:

   `scale = sum of Google Ads monthly volumes ÷ sum of monthly average Trends index`

   This is the number of monthly searches per index point.
4. Each point becomes searches for its own period. Every day in the point adds `scale × index ÷ days in that month`, so a weekly point is the sum of its 7 days.
5. **Short timeframes** (7, 30 or 90 days, or custom ranges under 4 months) don't cover enough whole months to calibrate directly. They are *bridged*:
   - a 270-day daily series of the same keyword is calibrated as above;
   - the short series is then matched to it over the complete days both series cover.
6. **Disagreeing months are left out.** Sometimes Google Trends shows a spike that Google Ads does not, for example a viral moment. When a month's index-to-volume ratio is more than 2.5x away from the median ratio, it is not used for the scale. It is listed in `estimate.outlierMonths`, with a note, and confidence is lowered.
7. **Quality signals**, so you can judge every estimate:
   - `fitErrorPct` is the average difference between our monthly fit and Google Ads. About 10% is typical, because Google Ads volumes are rounded buckets.
   - `confidence` is high, medium or low. It is lowered for short (bridged) timeframes, for category filters, and when fewer than 6 months could be calibrated.
   - `estimate.calibration` lists the month-by-month fit.

**Limits:**

- Estimates are for web search only, because Google Ads measures web searches. YouTube, News, Images and Shopping return the index only.
- Timeframes under 7 days return the index only.
- Keywords too rare for Google Ads, and periods before Google Ads history, return the index only, with a note.
- Keywords for which Google Ads withholds volumes return the index only. Google reports 0 for some topics, such as crypto (e.g. "bitcoin").
- Trends counts searches *containing* the term, while Google Ads counts the exact keyword. The scale absorbs this difference, but a strong shift in how people phrase searches can bias older periods.
- With a category filter, the level is still anchored to all searches for the keyword.

### Pricing (pay per event)

| Event | When it is charged |
|---|---|
| Actor start | once per run |
| `keyword-trend` | one keyword × location report with Trends data. It includes interest over time, absolute estimates, regions and related queries/topics. |
| `comparison` | one comparison chart (2-5 keywords) × location |
| `volume-lookup` | one Google Ads volume lookup for a country (up to 700 keywords), only when used for estimates |
| `volume-lookup-live` | one live Google Ads lookup for Worldwide or a region (up to 1,000 keywords), only when used for estimates |

You are not charged for:

- keywords with no Trends data;
- failed requests;
- skipped inputs;
- flat data-point rows;
- anything beyond your run's maximum charge. The run stops cleanly and lists what it didn't process.

**Apify free plan:** up to 3 keywords, 1 location and 1 comparison per run. Absolute estimates are available for
countries only on the free plan.

### FAQ

**Why do numbers differ from trends.google.com?** Google samples Trends data, so two requests can differ slightly. The Actor returns exactly what Google returned for that request; `trendsUrl` opens the same chart.

**Why are comparison values small for some keywords?** In a comparison, every keyword shares one scale, set by the biggest keyword's peak. Each keyword's own report uses its own 0-100 scale and has full resolution. The absolute estimates come from those per-keyword reports.

**Is this the official Google Trends API?** No. Google's Trends API is still a closed alpha. This Actor uses DataForSEO's licensed API. It is not affiliated with or endorsed by Google.

# Actor input Schema

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

One keyword per line, up to 500. Every keyword gets its own report (interest over time, estimated absolute searches, regions, related queries and topics). <b>To compare</b>, put 2-5 keywords on one line separated by commas (e.g. <code>pickleball, padel, tennis</code>): you also get a comparison chart on Google's shared scale.

## `locations` (type: `array`):

Country (<code>United States</code>, <code>DE</code>), region (<code>California, United States</code> or <code>US-CA</code>) or <code>Worldwide</code>, one per line, up to 10. Every keyword runs in every location. Absolute estimates use Google Ads volumes: one lookup per country, or a live lookup for Worldwide and regions (priced higher).

## `timeframe` (type: `string`):

Same choices as Google Trends. Absolute estimates need 7 days or longer.

## `startDate` (type: `string`):

YYYY-MM-DD. Setting it switches to a custom range. Google gives daily points up to ~9 months, weekly up to ~5 years, monthly beyond. Data starts 2004-01-01 (web) / 2008 (others).

## `endDate` (type: `string`):

YYYY-MM-DD, default today.

## `searchType` (type: `string`):

Which Google property. Absolute search estimates are available for web search only (Google Ads volumes measure web searches).

## `category` (type: `string`):

Optional Google Trends category name or code, e.g. <code>Sports</code>, <code>Shopping</code> or <code>20</code>. Default: all categories.

## `absoluteVolume` (type: `boolean`):

Add estimated searches per point (week, day, hour or month), total and average monthly searches, calibrated on Google Ads monthly volumes. See 'How estimates work' in the README.

## `includeRegions` (type: `boolean`):

States/regions (or countries for Worldwide) ranked by interest, 0-100.

## `includeRelatedQueries` (type: `boolean`):

Top and rising related searches (rising = growth %, Breakout = +5000% or more).

## `includeRelatedTopics` (type: `boolean`):

Top and rising related topics (Knowledge Graph entities).

## `maxRelatedItems` (type: `integer`):

Per list (top / rising queries and topics).

## `maxRegions` (type: `integer`):

Regions kept per keyword, highest interest first.

## `timeseriesRows` (type: `boolean`):

Adds flat rows (keyword, location, date, value, estimatedSearches) for spreadsheets and charts. These rows are free.

## `volumeLanguage` (type: `string`):

Optional language code for the Google Ads volumes, e.g. <code>en</code>. Default: the country's main language.

## Actor input object example

```json
{
  "keywords": [
    "pickleball, padel",
    "golf"
  ],
  "locations": [
    "United States"
  ],
  "timeframe": "past_12_months",
  "searchType": "web",
  "absoluteVolume": true,
  "includeRegions": true,
  "includeRelatedQueries": true,
  "includeRelatedTopics": true,
  "maxRelatedItems": 25,
  "maxRegions": 50,
  "timeseriesRows": false
}
```

# Actor output Schema

## `keywords` (type: `string`):

No description

## `comparisons` (type: `string`):

No description

## `all` (type: `string`):

No description

## `summary` (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 = {
    "keywords": [
        "pickleball, padel",
        "golf"
    ],
    "locations": [
        "United States"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vncntlabs/google-trends-search-volume").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 = {
    "keywords": [
        "pickleball, padel",
        "golf",
    ],
    "locations": ["United States"],
}

# Run the Actor and wait for it to finish
run = client.actor("vncntlabs/google-trends-search-volume").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 '{
  "keywords": [
    "pickleball, padel",
    "golf"
  ],
  "locations": [
    "United States"
  ]
}' |
apify call vncntlabs/google-trends-search-volume --silent --output-dataset

```

## MCP server setup

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

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/3Z8hUeFIyPuBD78RY/builds/ardzhc8LeXDLsJasD/openapi.json