# Google Trends Scraper (Keyless)

The Google Trends Scraper returns four widget types per keyword: interest over time as 0 to 100 timeline rows, related queries and related topics in TOP and RISING lists, and interest by region. It compares up to 5 keywords per call and up to 100 per run, with no API key, browser or captcha. Keywords cost $2.50 per 1,000 on the Free plan, or $0.27 on Gold. Run it from Apify Console or the API.

## Key facts

- Price: from $0.0025 per keyword trends bundle, $2.50 per 1,000, down to $0.00027 on higher Apify plans
- Pricing model: Pay per event
- Output: JSON, CSV, Excel, XML, RSS via Apify datasets
- Access: Apify Console, REST API, Python and JS clients, MCP tool google_trends
- Version: Updated Nov 2026, build 0.1.13
- Usage: 96.4% successful runs (30 days)
- Actor: subimpact/google-trends-scraper-keyless

## Who it is for

- SEO teams validating demand seasonality before writing content
- Brand strategists comparing interest in a category across markets
- Content planners timing launches around rising queries
- Market researchers mapping regional interest without a paid Trends vendor

## Use cases

### Check seasonality before a campaign

Set keywords to your terms, timeRange to today 5-y and geo to MY, then read the timeline rows of recordType timeline. Each row is a period with a 0 to 100 value, which shows whether demand peaks at Ramadan, Christmas or a school holiday. includeTimeseries is on by default, so a plain run already returns this series.

### Harvest rising queries for content

Turn on includeRelatedQueries and each keyword returns relatedQuery rows with TOP and RISING lists and a rank. Set maxRelatedItems to 25, which is what Google usually returns. The RISING list is where new phrasing shows up first, so it is the cheapest way to find long-tail terms your keyword research tool has not indexed yet.

### Break interest down by region

Enable includeGeoMap and every keyword also returns geo rows with a region code, region name and 0 to 100 value for the states or provinces of the target geo. Pair it with geo MY or US to see which regions over-index on a term, which is useful for planning delivery areas, local ads or a store rollout.

### Compare categories on the same scale

Keywords are compared inside one Trends call, up to 5 at a time, so their timeline values share a scale. Add a fixed reference keyword to every batch, such as a category leader, to make separate runs comparable. category filters to a Google Trends category, and property switches the surface to images, news, youtube or froogle.

### Watch a term across several markets

The geo field takes one country per run, so the pattern is one task per market with the same keyword list, all on a weekly schedule. Compare the timeline shape rather than raw values between markets, since each run normalises to its own peak, and keep tzOffset set to the market's offset so daily buckets line up.

## Price events

- Keyword trends bundle (`keyword-trends-bundle`): $0.0025, lowest tier $0.00027. One keyword's full Trends data: interest-over-time + related queries/topics + interest-by-region. Charged only for keywords delivered; failed batches are not charged.

Prices from the Apify Store. Apify shows the final price before each run.

## How it compares with other Apify actors

Price per 1,000 keyword bundles at Apify Store list prices, checked 20 Nov 2026.

| Actor | Price per 1,000 keyword bundles (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Google Trends Scraper (Keyless) (this API) | $2.50 | $0.27 | None | Paid separately | 2 | No reviews yet | 18 Nov 2026 |
| [Google Trends Scraper](https://apify.com/apify/google-trends-scraper) | Bills per dataset item, so a keyword that returns many timeline or region rows costs several events. | Same unit, see the first price column | $0.00005 | Included | 20,243 | 4.2 (33 reviews) | 18 Nov 2026 |
| [Google Trends Scraper](https://apify.com/data_xplorer/google-trends-fast-scraper) | Charges per dataset item, so cost follows the number of rows a keyword produces. | Same unit, see the first price column | $0.025 | Included | 7,051 | No reviews yet | 18 Nov 2026 |
| [Google Trends Scraper — Interest, Regions & Queries](https://apify.com/khadinakbar/google-trends-scraper) | One charge per result item, so each timeline, region or related row is billed separately. | Same unit, see the first price column | $0.00005 | Included | 800 | No reviews yet | 10 Nov 2026 |
| [Google Trends Scraper](https://apify.com/agenscrape/google-trends-scraper) | Charges per dataset item, with each timeline, region or related row as its own item. | Same unit, see the first price column | $0.025 | Included | 1,665 | No reviews yet | 22 Dec 2025 |

### Where Google Trends Scraper is stronger

- Far larger user base and more monthly runs than the other trends actors here
- Maintained by Apify, with Google Sheet input and output support
- Accepts Google Trends URLs as well as plain search terms

### Where this API is stronger

- One event per keyword bundle rather than one per dataset row
- No API key, browser or captcha step in the pipeline
- Timeline, related queries and region map arrive in the same bundle

### Where Google Trends Scraper is stronger

- Larger user base than most trends actors listed here
- Also returns daily trending searches by country
- Regional data can be switched on or off per run

### Where this API is stronger

- Bills per keyword bundle, so many timeline points do not add events
- Related queries and topics are fields in one row, not extra rows
- No API key or captcha step in the pipeline

### Where Google Trends Scraper — Interest, Regions & Queries is stronger

- Covers all five trends data types, including daily trending searches
- Separate row types make timeline, region and related rows easy to filter
- MCP and API ready output

### Where this API is stronger

- One event per keyword bundle, so row count does not drive the cost
- Related queries, topics and region map come back with the same bundle
- Plain HTTP with no browser step for the trends endpoints

### Where Google Trends Scraper is stronger

- Data type toggles let you narrow a run to the outputs you need
- Handles multiple keywords and custom time ranges
- Listing states that no browser is needed for the core endpoints

### Where this API is stronger

- One charge per keyword bundle instead of one per result row
- Region map data and related items are included in the bundle
- Plain HTTP with no captcha step in the pipeline

Google Trends is well served on the Store, and every actor listed here bills per dataset item, so a keyword that returns many timeline or region rows costs more than one event. apify and data_xplorer have the largest audiences, khadinakbar covers all five trends data types, and agenscrape exposes data type toggles. Ours bills one event per keyword bundle.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

## Input

- `keywords` (array, required): Keywords to track. Up to 5 are compared in one Trends call; more are split into batches. Max 100.
- `geo` (string, optional): Two-letter country code (US, MY, GB...). Leave empty for worldwide.
- `timeRange` (string, optional): Trends time range. For a custom range, run via API with 'YYYY-MM-DD YYYY-MM-DD'.
- `category` (integer, optional): Google Trends category id (0 = all categories).
- `property` (string, optional): Web search (''), images, news, youtube, or froogle (Google Shopping).
- `includeTimeseries` (boolean, optional): Emit timeline rows (0-100 interest per period).
- `includeRelatedQueries` (boolean, optional): Emit TOP + RISING related queries per keyword.
- `includeRelatedTopics` (boolean, optional): Emit related topics (may be empty on some egress IPs).
- `includeGeoMap` (boolean, optional): Emit per-region interest rows (states/provinces of the target geo).
- `maxRelatedItems` (integer, optional): Cap per TOP/RISING list (Google returns ~25).
- `tzOffset` (integer, optional): e.g. -480 for UTC+8. Affects hourly/daily bucketing.
- `delaySeconds` (number, optional): Politeness delay. Raise if you see 429 warnings.
- `batchSize` (integer, optional): Max keywords compared per Trends call (Google allows up to 5).
- `proxyConfiguration` (object, optional): Optional. Add RESIDENTIAL proxy if datacenter IPs get throttled (HTTP 429).

### Example input

```json
{
  "keywords": [
    "coffee",
    "iced coffee"
  ],
  "geo": "US",
  "timeRange": "today 12-m",
  "category": 0,
  "property": "",
  "includeTimeseries": true,
  "includeRelatedQueries": false,
  "includeRelatedTopics": false,
  "includeGeoMap": false,
  "maxRelatedItems": 25,
  "tzOffset": 0,
  "delaySeconds": 1.5,
  "batchSize": 5
}
```

## Sample output

Trimmed from one of our own test runs. Personal data is redacted.

```json
[
  {
    "recordType": "timeline",
    "keyword": "coffee",
    "keywords": [
      "coffee"
    ],
    "geo": "US",
    "timeRange": "today 3-m",
    "date": "Aug 20, 2026",
    "dateAxis": "Aug 20",
    "timestamp": "1787184000",
    "isPartial": false,
    "points": [
      {
        "keyword": "coffee",
        "value": 72,
        "formattedValue": "72",
        "hasData": true
      }
    ],
    "value": 72,
    "scrapedAt": "2026-11-20T02:38:25.929572+00:00"
  },
  {
    "recordType": "timeline",
    "keyword": "coffee",
    "keywords": [
      "coffee"
    ],
    "geo": "US",
    "timeRange": "today 3-m",
    "date": "Aug 21, 2026",
    "dateAxis": "Aug 21",
    "timestamp": "1787270400",
    "isPartial": false,
    "points": [
      {
        "keyword": "coffee",
        "value": 73,
        "formattedValue": "73",
        "hasData": true
      }
    ],
    "value": 73,
    "scrapedAt": "2026-11-20T02:38:25.929594+00:00"
  }
]
```

## How to run it

1. Put up to 100 keywords in the keywords array, for example ["coffee", "iced coffee"]. Up to 5 are compared per Trends call and the rest are batched.
2. Set geo to a two-letter code such as US or MY, or leave it empty for worldwide, and set timeRange such as today 12-m or today 5-y.
3. Enable the widgets you need: includeTimeseries, includeRelatedQueries, includeRelatedTopics and includeGeoMap, and cap lists with maxRelatedItems.
4. Raise delaySeconds if you see 429 warnings, and add a residential proxy if datacenter addresses keep getting throttled.
5. Run the actor, then read timeline, relatedQuery, relatedTopic, geo and error rows in the dataset, or export them as JSON or CSV.

### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/subimpact~google-trends-scraper-keyless/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["coffee","iced coffee"],"geo":"US","timeRange":"today 12-m","category":0,"property":"","includeTimeseries":true,"includeRelatedQueries":false,"includeRelatedTopics":false,"includeGeoMap":false,"maxRelatedItems":25,"tzOffset":0,"delaySeconds":1.5,"batchSize":5}'
```

### Python

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/google-trends-scraper-keyless").call(run_input={
      "keywords": [
        "coffee",
        "iced coffee"
      ],
      "geo": "US",
      "timeRange": "today 12-m",
      "category": 0,
      "property": "",
      "includeTimeseries": true,
      "includeRelatedQueries": false,
      "includeRelatedTopics": false,
      "includeGeoMap": false,
      "maxRelatedItems": 25,
      "tzOffset": 0,
      "delaySeconds": 1.5,
      "batchSize": 5
    })

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)
```

### JavaScript

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/google-trends-scraper-keyless').call({
  "keywords": [
    "coffee",
    "iced coffee"
  ],
  "geo": "US",
  "timeRange": "today 12-m",
  "category": 0,
  "property": "",
  "includeTimeseries": true,
  "includeRelatedQueries": false,
  "includeRelatedTopics": false,
  "includeGeoMap": false,
  "maxRelatedItems": 25,
  "tzOffset": 0,
  "delaySeconds": 1.5,
  "batchSize": 5
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);
```

### MCP

```bash
claude mcp add subimpact-data -e APIFY_TOKEN=<YOUR_APIFY_TOKEN> -- npx -y @subimpact/data-mcp

# Then ask your agent to use the google_trends tool.
```

### n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/google-trends-scraper-keyless
Input JSON: paste the example input below.

## Limits

- Interest is normalised per comparison, so values from separate runs are not directly comparable.
- Related topics can come back empty from some egress addresses.
- Google rate limits aggressively, so 429s mean raising the delay or adding a residential proxy.
- Each call compares at most 5 keywords, which is Google's own limit.

## FAQ

### What does 1,000 keywords cost?

A keyword bundle costs $0.0025 on the Free plan, so $2.50 per 1,000 bundles, and the tiered price drops to $0.27 per 1,000 on Gold and above. A bundle covers interest over time, related queries, related topics and interest by region for one keyword. Failed batches and keywords with no delivered data are not charged.

### Do I need a Google API key or account?

No. The actor warms up a Trends page for its cookie and then calls Google's internal trends endpoints over plain HTTP. There is no key, no login, no browser and no captcha solving, which is why the compute cost of a run stays small.

### How many keywords can I compare at once?

Up to 5 per Trends call, which is Google's own limit, and up to 100 keywords per run. More than 5 are split into batches automatically, with batchSize controlling the split. Keywords compared in the same call share a scale, so keep a reference term in each batch if you need to compare runs.

### Why is my related topics list empty?

Google sometimes returns no related topics for an egress address, and the actor treats that as no data rather than a failure, so the run continues and nothing is charged for it. Related queries are the more reliable widget; try those first, or add a residential proxy and re-run.

### What do the 0 to 100 values mean?

Interest is normalised inside each Trends call, where 100 is the highest point in that comparison and 0 is the lowest or no data. That means values from different runs are not directly comparable unless they share at least one keyword. Compare shapes over time rather than absolute values.

### Can I get data for a custom date range?

Yes, pass timeRange as a start and end date pair separated by a space, in YYYY-MM-DD form, through the API rather than the Console field. The named ranges such as now 7-d, today 3-m, today 12-m, today 5-y and all also work, and category narrows the query to one Google Trends category.

### What happens if every batch is throttled?

The run does not succeed with an empty dataset. It emits an explained error row carrying the reason and sets a run status message, which is uncharged. Raise delaySeconds, add a residential proxy, or retry later, since a persistent 429 usually means the egress address is throttled.

## Links

- Page: https://subimpact.net/apis/google-trends-scraper-keyless/
- Category: https://subimpact.net/apis/category/search-seo/
- Run on Apify: https://apify.com/subimpact/google-trends-scraper-keyless
- All data APIs: https://subimpact.net/apis/
- Catalogue JSON: https://subimpact.net/apis/catalogue.json
