Menhly ToolsAll tools

Google Trends Scraper & API - Interest, Regions, Queries

Google Trends scraper for a list of search terms, $2 per 1,000: interest over time, interest by country or region, and related queries (top and rising). One flat row per term and country, every field always present, never null. Only complete rows are billed.

This tool runs on Apify: pay only for the results you get, with a free monthly credit on new accounts.

Try it on Apify

Give it search terms, get Google Trends back: interest over time, interest by country or region, and related queries (top and rising). One flat row per search term and country, every field always present, never null. Built to be called from pipelines, n8n/Make/Zapier flows and AI agents.

$1 per 1,000 search terms on paid plans, down to $0.60 on Gold, plus $0.0005 per run. No platform usage on top. Rows that fail or have no data are free.

Why this one

Input

Field Default What it does
searchTerms — Search terms, one per item. Required. Each term is looked up on its own, so every row has its own 0–100 scale.
geos worldwide Country codes (US, DE, VN) or regions (US-CA). Every term is fetched once per entry.
timeRange today 12-m Past hour, 4 hours, day, 7 days, 30 days, 90 days, 12 months, 5 years, or since 2004.
customTimeRange — YYYY-MM-DD YYYY-MM-DD; overrides timeRange.
category 0 Google Trends category ID (e.g. 71 Food & Drink).
property web images, news, froogle (Shopping) or youtube search instead of web search.
interestOverTime / interestByRegion / relatedQueries true Switch sections off to get faster rows. A row is complete when every section you left on was fetched.
language en-US Language for region names.
{
  "searchTerms": ["coffee", "matcha"],
  "geos": ["US", "GB"],
  "timeRange": "today 12-m"
}

Output

One row per search term × country, in completion order. inputIndex lines rows up with your input.

{
  "inputIndex": 0,
  "searchTerm": "coffee",
  "geo": "US",
  "timeRange": "today 12-m",
  "category": 0,
  "property": "",
  "status": "ok",
  "subStatus": "complete",
  "error": "",
  "averageInterest": 76,
  "peakInterest": 100,
  "peakDate": "2026-04-12T00:00:00.000Z",
  "latestInterest": 65,
  "interestOverTime": [{ "date": "2026-10-18T00:00:00.000Z", "value": 65, "isPartial": false }],
  "interestByRegion": [{ "geoCode": "US-WY", "geoName": "Wyoming", "value": 100 }],
  "relatedQueriesTop": [{ "query": "coffee near me", "value": 100, "formattedValue": "100" }],
  "relatedQueriesRising": [{ "query": "home workout routines", "value": 6050, "formattedValue": "Breakout" }],
  "missing": [],
  "trendsUrl": "https://trends.google.com/trends/explore?q=coffee&date=today+12-m&hl=en&geo=US",
  "scrapedAt": "2026-10-26T07:57:10.837Z"
}

This is a real row from 2026-10-26, shortened: interestOverTime has 53 weekly points for 12 months. The odd rising query is what trends.google.com itself shows for "coffee" in the US that day.

Status

status subStatus Charged
ok complete: every requested section fetched yes
partial section_failed: one section failed after retries; missing names it free
no_data low_search_volume: Google has too few searches for this term there free
failed blocked, network_error, invalid_request, timeout, bad_response, cost_limit_reached, free_work_limit free

Pricing

Event Price When
search-term $1.00 per 1,000 on Bronze, down to $0.60 per 1,000 on Gold ($2.00 per 1,000 on the free plan) A row with status: "ok"

The only other charge is a start fee of $0.0005 per run, which covers the fixed cost of opening a residential proxy session. No platform usage is added on top. A run stops starting new terms when your maximum cost per run is reached, and marks the rest cost_limit_reached, uncharged.

Fair use

Failed and no-data rows are free, so a run that spends its proxy traffic on terms that keep failing stops starting new ones. The rest come back as failed / free_work_limit, uncharged, and can be resubmitted. Ordinary lists never get near this. Up to 5,000 term × country pairs per run.

What it does not do (yet)

Use it from AI agents (MCP)

This Actor is a tool on the Apify MCP server, so Claude, Cursor, VS Code or any MCP client can call it to check how a topic is trending. Load only this tool: a short tool list keeps the agent from picking the wrong one.

Recommended: hosted server, OAuth sign-in (nothing secret on disk). Add to your MCP client config (claude_desktop_config.json, .cursor/mcp.json, …):

{
  "mcpServers": {
    "google-trends": {
      "url": "https://mcp.apify.com?tools=sumitr_mardy/google-trends-scraper"
    }
  }
}

With an API token instead (clients without OAuth, or unattended setups):

{
  "mcpServers": {
    "google-trends": {
      "url": "https://mcp.apify.com?tools=sumitr_mardy/google-trends-scraper",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Local server (stdio):

{
  "mcpServers": {
    "google-trends": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server@latest", "--tools", "sumitr_mardy/google-trends-scraper"],
      "env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
    }
  }
}

The hosted server also gives the agent this Actor's output schema, so it knows every field before the first call. apify mcp install <client> writes the config for you if you use the Apify CLI. Get a token at Apify Console → API & Integrations, and never commit it.

Tips for agents:

Use it from code

from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("sumitr_mardy/google-trends-scraper").call(run_input={
    "searchTerms": ["coffee", "matcha"],
    "geos": ["US"],
})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row["searchTerm"], row["status"], row["latestInterest"], row["peakDate"])
curl -X POST "https://api.apify.com/v2/acts/sumitr_mardy~google-trends-scraper/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["coffee"], "geos": ["US"]}'