Google Trends Scraper — Fast, Unlimited Keyword Comparison

Get Google Trends data as clean JSON, CSV or Excel: interest over time, interest by region (countries, states, cities, US metro areas) and related queries (top and rising). No browser, so runs are fast and cheap — hundreds of keywords in minutes.

⭐ Compare more than 5 keywords on one scale

On trends.google.com you can only compare 5 terms at once, and every new comparison is scaled differently. This Actor's Compare mode chains comparisons through a shared anchor keyword, so any number of terms ends up on one common 0–100 scale (100 = the highest point of any term). Perfect for ranking 50 brands, products, competitors or topics against each other.

Checked against Google's own comparison: chained values match within a few percent.

What you get for each search term

Field	Description
averageInterest	Average interest over the period (0–100)
peak / latest	Highest and most recent value with date
timeline	Full time series: date, value, isPartial for the unfinished last period
regions	Interest by country / state / city / DMA
relatedQueries	top and rising related searches incl. "Breakout" terms

Features

• Any country or region (US, DE, GB, US-CA …) or worldwide
• Any time range: past hour up to 2004–today, or a custom date range
• Web, Image, News, Google Shopping or YouTube search
• Category filter (e.g. Finance, Food & Drink)
• Built-in proxy rotation and retries — Google's rate limits are handled for you
• Pay only for delivered terms — failed terms are listed with the reason and never charged

Use cases

• SEO & content planning: find rising queries before competitors do
• Market research: compare brands, products or competitors across countries
• E-commerce & dropshipping: spot seasonal demand and trending products (Shopping search)
• YouTube creators: see what people search on YouTube
• Finance & crypto: search interest as a sentiment signal
• Data science: clean time series ready for pandas, BigQuery or Sheets

Input example

{
  "searchTerms": ["bitcoin", "ethereum", "solana", "dogecoin", "cardano", "ripple", "tron"],
  "mode": "compare",
  "geo": "US",
  "timeRange": "today 12-m",
  "includeRegions": true,
  "includeRelatedQueries": true
}

Output example (real run, lists shortened)

{
  "searchTerm": "ripple",
  "geo": "US",
  "timeRange": "today 12-m",
  "category": 0,
  "property": "web",
  "mode": "compare",
  "anchorTerm": "solana",
  "lowPrecision": false,
  "averageInterest": 3.38,
  "peak": {
    "date": "2025-12-14T00:00:00.000Z",
    "value": 6.13
  },
  "latest": {
    "date": "2026-10-18T00:00:00.000Z",
    "value": 2.54
  },
  "timeline": [
    {
      "date": "2025-10-26T00:00:00.000Z",
      "label": "Oct 26 \u2013 Nov 1, 2025",
      "value": 2.63,
      "isPartial": false
    }
  ],
  "regions": [
    {
      "geoCode": "US-IN",
      "geoName": "Indiana",
      "value": 100
    }
  ],
  "relatedQueries": {
    "top": [
      {
        "query": "the ripple",
        "value": 100,
        "formattedValue": "100"
      }
    ],
    "rising": [
      {
        "query": "ripple needoh",
        "value": 32600,
        "formattedValue": "Breakout"
      }
    ]
  },
  "error": null
}

Pricing

$0.002 per search term — all requested data (time series, regions, related queries) included. 1,000 keywords cost $2. Failed terms are free.

Tips

• Separate vs Compare: use Separate to see each term's own trend shape; use Compare to see which term is searched more.
• lowPrecision: true means the term was tiny next to the others in its group, so Google's integer rounding makes its values approximate. Compare it with terms of similar size for better precision.
• Google Trends values are relative (0–100), not absolute search volumes.
• The last data point is often partial (isPartial: true) because the period is not over yet.

FAQ

Is there an official Google Trends API? Google offers no public API for this data. This Actor reads the same data the Google Trends website shows.

Why are related topics missing? Google currently returns no related topics through this interface, so the Actor only delivers related queries — rather than empty fields.

Something not working? Open an issue on the Actor page with your input; fixes are usually quick.