Google Trends API & Scraper – Regions & Related Queries avatar

Google Trends API & Scraper – Regions & Related Queries

Pricing

from $1.00 / 1,000 keyword trends

Go to Apify Store
Google Trends API & Scraper – Regions & Related Queries

Google Trends API & Scraper – Regions & Related Queries

Google Trends that does not break: interest over time, interest by region and top and rising related queries and topics for any keywords, up to 5 compared on one scale. Licensed data, no captchas or rate limits, pay per use.

Pricing

from $1.00 / 1,000 keyword trends

Rating

0.0

(0)

Developer

Rowfeed

Rowfeed

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Security

Limited permissions

Share

Get Google Trends data for any keywords: interest over time with the average, peak, latest value and trend already worked out, interest by region, and top and rising related queries and topics. Up to 5 keywords are compared on one shared scale. Built for marketers, analysts, content teams, traders and AI agents who need Google Trends data in a spreadsheet or pipeline. The data is fetched through a licensed data provider (DataForSEO), not by scraping Google Trends, so runs do not fail on rate limits or captchas.

What you get

  • One row per keyword with the full timeline (0–100 per period) plus average_interest, latest_interest, peak_interest with its period, and trend_pct.
  • Fair comparisons: up to 5 keywords per lookup share one 0–100 scale, just like the Google Trends website. With more keywords you get several comparison groups.
  • Any time range and property: past hour up to 2004–today, web, news, YouTube, images or Google Shopping, worldwide or any country or region.
  • Interest by region for every keyword (states or countries, 0–100, highest first).
  • Related queries and topics, top and rising, per keyword: the searches people combine with your keyword and the ones growing fastest.
  • A link to the same chart on Google Trends for every row.

Example output row

A real row from a run with the default input (United States, past 12 months, timeline shortened here):

{
"keyword": "price tracking",
"average_interest": 59,
"latest_interest": 12,
"latest_period": "2026-10-11",
"peak_interest": 100,
"peak_period": "2026-03-08",
"trend_pct": -18.2,
"has_data": true,
"timeline": [
{ "date_from": "2025-10-19", "date_to": "2025-10-25", "value": 27, "partial": false },
{ "date_from": "2025-10-26", "date_to": "2025-11-01", "value": 41, "partial": false },
"... 49 more weeks ...",
{ "date_from": "2026-10-11", "date_to": "2026-10-17", "value": 12, "partial": false },
{ "date_from": "2026-10-18", "date_to": "2026-10-21", "value": 11, "partial": true }
],
"compared_with": ["web scraping", "data extraction"],
"comparison_group": 1,
"time_range": "past_12_months",
"search_type": "web",
"location": "United States",
"regions": [
{"geo_id": "US-ND", "region": "North Dakota", "value": 86},
{"geo_id": "US-AK", "region": "Alaska", "value": 82},
"... 49 more ..."
],
"related_queries_top": [{"query": "price tracking app", "value": 100}, {"query": "tracking number", "value": 85}, "..."],
"related_queries_rising": [{"query": "spacex stock price", "value": 25050}, "..."],
"related_topics_top": [{"topic": "Price", "type": "Topic", "value": 100}, "..."],
"related_topics_rising": [{"topic": "2026", "type": "Topic", "value": 1750}, "..."],
"google_trends_url": "https://trends.google.com/trends/explore?hl=en&geo=US&date=today%2012-m&q=web%20scraping,data%20extraction,price%20tracking",
"checked_at": "2026-10-13T07:31:04+00:00"
}

partial: true marks a period that is not finished yet; it is kept in the timeline but left out of latest, peak and trend. trend_pct compares the last 4 complete periods with the 4 before.

Input

FieldWhat it does
keywordsSearch terms, 2–100 characters each, up to 100 per run.
timeRangepast_hour, past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years, 2004_present (web) or 2008_present.
locationUnited States, Germany, California,United States ... Empty = worldwide.
searchTypeweb, news, youtube, images or froogle (Google Shopping).
compareTogetherOn (default): groups of 5 share one scale. Off: every keyword gets its own 0–100 scale.
includeRelatedOn (default): related queries and topics, top and rising, per keyword. Free when each keyword has its own lookup; with compared keywords Google gives them per keyword, so each keyword takes one extra lookup.

Pricing

Pay per event, no subscription:

  • $0.001 per keyword row with data (the full timeline included). Keywords Google has too little data for come back with has_data: false and are free.
  • $0.02 per Google Trends lookup of up to 5 keywords. Failed lookups, and lookups where Google has no data, are free.
  • $0.001 per run start.

Examples: 1 keyword with regions and related queries costs about $0.022. 5 compared keywords cost about $0.026 without related queries, or about $0.126 with them (one extra lookup per keyword). With compareTogether off, every keyword is its own lookup with regions and related queries included: about $0.022 each.

Try it for $0.001: the pre-filled example is answered from a saved snapshot of a real lookup (rows carry from_snapshot: true) and costs only the $0.001 run start. Change anything and the lookup runs live.

Free Apify plan: the pre-filled example works on any plan. Live lookups need a paid Apify plan (any plan), because each one costs real money at the data provider; on the free plan the run returns a paid_plan_required row and charges nothing beyond the start.

You can cap the cost of a run with the maximum charge setting. The Actor checks your budget before each lookup, charges a lookup only when it succeeds, and stops after the first failed lookup.

Good to know

  • Google Trends values are relative (0–100), not search counts. For monthly search volumes use a keyword volume tool.
  • Values from different comparison groups are on different scales; compare within one comparison_group.
  • A value of 0 means Google had too little data for that period. A small term compared with very popular ones can come out as all zeros (has_data: false, not charged); look it up on its own or with similar-sized terms.
  • Error rows carry error and errorMessage and are never charged.

More SEO tools from Rowfeed

Not affiliated with Google.