Google Trends Scraper - Trending Now, Search Volume & Trend Duration

Unofficial tool. Orbots is not affiliated with, sponsored by, or endorsed by Google. "Google" and "Google Trends" are trademarks of Google LLC, used here only to describe the public data this Actor collects.

Get what the world is searching right now, with estimated search volume, for 100+ countries, plus interest-over-time and interest-by-region for any keyword. No browser, no login, no item cap. You only pay for results that are actually delivered.

Why this Actor

Google retired the old dailytrends and realtimetrends endpoints. They now return 404, and tools still built on them silently return nothing for trending data. This Actor uses the endpoint that powers the current Google Trends interface, so Trending Now keeps working.

• High volume per run. Large markets return the most: US ~370, JP ~360, GB/DE/IN ~315 trending terms. Most countries land in the 100-200 range (Brazil ~180). Three countries returned 873 rows in 26 seconds in our benchmark. Yield depends on how much is actually trending in that market, so we publish the measured numbers rather than a flattering range.
• Search volume included, on every term. Volume was present on 100% of 2,415 rows in our latest cross-market benchmark (for example 100000, 500000). Related searches come along when Google provides them: about a quarter of terms in a live US pull (large markets more: US-CA 31%, GB 28%; small ones less: FR-75 8%). Most trending scrapers return only the term.
• Category, rank and explore link on every term. Each row is classified into Google's own topic categories (Sports, Entertainment, Business and Finance, and more), carries its position in the feed and a direct link to the term's Google Trends page. Filter to one vertical with the categories input, no post-processing needed.
• Active trends vs ended trends, with trend duration. Every term says whether it is still trending right now (is_active) and, once it has ended, exactly how long it lasted (duration_minutes, plus started_at and ended_at). A ranked list alone cannot tell a two-hour spike from a two-day story. Measured on a live pull: of 421 US terms in the 24-hour window, 123 were still active and 298 had ended, median life 2 hours. In the 48-hour window for GB, 530 of 615 had already ended. Field coverage is complete on ended terms.
• Built for schedules. Turn on onlyNew and each run returns only trends you have not received before, per country and window. A daily schedule stops handing you the same list, and you stop paying for it twice.
• No item cap. Some competitors cap at 1,000 items per run. This one does not.
• Honest billing. maxItems is respected exactly, and nothing is charged for a result that was not returned.

Reliability, measured

• 27 of 27 third-party runs succeeded. That is every run ever started by another account on this Actor, lifetime, as the public run stats show (as of 2026-08-25). The denominator is small and we publish it anyway: that is one scheduled user running daily, not a crowd. Still, 100% is what the platform shows because it is what happened.
• The design behind that number: when Google throttles part of a request, the run delivers the countries that answered and names the ones that did not, instead of failing everything; a quiet day with onlyNew finishes as a success with a message, not a fake failure; the session and the IP are rotated together whenever Google refuses one.
• For scale comparison, the same public stat on memo23/google-trends-scraper reads 94.8% (513 of 541 runs, last 30 days, as of 2026-08-20). Every Actor's success rate is public on its page. Check it before you put anything on a schedule.

What you get

Trending Now mode (default)

{
  "type": "trending_now",
  "term": "japan earthquake",
  "rank": 3,
  "geo": "US",
  "started_at": 1785224400,
  "ended_at": 1785238800,
  "is_active": false,
  "duration_minutes": 240,
  "search_volume": 200000,
  "formatted_volume": "200K+",
  "growth": 1000,
  "category": "Law and Government",
  "categories": ["Law and Government"],
  "related_terms": ["japan earthquake today", "earthquake japan", "kumamoto"],
  "trends_url": "https://trends.google.com/trends/explore?q=japan+earthquake&date=now+1-d&geo=US&hl=en-US",
  "window_hours": 24,
  "scraped_at": "2026-07-29T12:53:25Z"
}

Every term arrives ranked (1 = hottest), classified into Google's own topic categories (Sports, Entertainment, Business and Finance, and more), with the volume both as a number you can sort by and as the label the interface shows (200K+), plus a ready-made link to the term's explore page. Windows: past 4 hours, 24 hours, 48 hours or 7 days. Pass several countries in one run.

is_active is true while the term is still trending and ended_at is null; once Google closes the trend, ended_at is filled and duration_minutes tells you how long it held. Sort by duration_minutes to separate a passing spike from a story with legs, or keep is_active == true to act only on what is live at this minute.

Want just one vertical? Set categories (e.g. ["Sports"]) and only trends in those categories are delivered: the same 19 topic categories Google itself assigns, matched with no post-processing on your side. A term Google did not categorise is excluded while the filter is on, and rows skipped by the filter are never charged. If the filter eats every row, the run still succeeds, with a message saying exactly that.

Only what is new: onlyNew

Set onlyNew: true and the Actor remembers, per country and per window, which trends it has already delivered to you, and returns only the ones it has not. A daily schedule then behaves the way you would want it to: the first run gives you the whole list, and every run after that gives you the additions.

A term that trends again later counts as new, because history is keyed by term and start time, so a recurring topic is not swallowed. History is kept for 7 days in your own account, one entry per country and window. If a run finds nothing new, it finishes successfully with a message saying so, and charges you nothing: no rows, no start fee. Leave onlyNew off to always get the full list.

Keywords mode

{ "type": "interest_over_time", "keyword": "chatgpt", "date": "Jul 27 - Aug 2, 2025", "timestamp": 1753574400, "value": 91, "is_partial": false, "property": "web" }
{ "type": "interest_by_region", "keyword": "chatgpt", "region": "California", "region_code": "US-CA", "value": 5, "property": "web" }

Compares up to 5 terms at a time; longer keyword lists are split into groups of 5 automatically. Time ranges from the past hour to 2004-present. Interest can be measured on five Google surfaces (regular Web Search, Image Search, News, YouTube or Shopping, via the property input), which most tools in this category do not expose.

Read this before choosing Keywords mode. Google throttles keyword queries far more aggressively than Trending Now: one IP is blocked after roughly ten queries, so a long keyword list can exhaust a whole pool of addresses and return partial data or none at all. Trending Now, by contrast, returns hundreds of rows from a single request and is what this Actor is built around. Use Keywords mode for short lists, keep the RESIDENTIAL proxy group on, and expect it to be slower and less reliable than Trending Now. A run that collects nothing costs you nothing (see Pricing).

Sub-regions, not just countries

geo and trendingGeos also accept sub-region codes, which most tools in this category do not expose: US-CA (California), US-NY, FR-75 (Paris), GB-ENG, BR-SP. A sub-region returns a narrower, more local list. In our tests US-CA returned 242 trending terms and FR-75 returned 23.

Input

Field	What it does
mode	trending (default) or keywords
trendingGeos	Country codes for Trending Now, e.g. ["US","BR","GB"]
trendingHours	4, 24, 48 or 168
categories	Trending mode: keep only trends in these Google topic categories (19 available, the ones Google itself assigns). Empty = all
keywords	Terms to analyse in keywords mode
geo	Country code; empty means worldwide
timeframe	Time range for keyword analysis
property	Surface to measure: web (default), images, news, youtube, shopping
dataTypes	interest_over_time, interest_by_region
onlyNew	Trending mode: return only trends not delivered in an earlier run. Made for schedules
maxItems	Hard cap, respected exactly, never charged beyond
proxyConfiguration	Keep proxy enabled (see below)

When a run returns nothing

Zero rows is not always an error, and this Actor does not pretend otherwise:

Situation	Run status	Charged
Google throttled every country you asked for	Failed	nothing
Some countries throttled, the rest answered	Succeeded: the reachable countries are delivered, the throttled ones are named in the log	only the delivered rows
The endpoint answered but returned no data at all	Failed	nothing
onlyNew is on and nothing is new since your last run	Succeeded, with a message saying so	nothing

That distinction matters if you run this on a schedule: a quiet day should not page you, and a real breakage should.

Proxy is required, not optional

Google rate-limits by IP. In Keywords mode a single address is throttled after roughly ten queries and stays blocked for more than 15 minutes (we measured it). Trending Now is much lighter (one request per country), but a throttled address still costs you that country's list. Either way, this Actor rotates to a fresh IP whenever it is throttled and re-establishes the session from scratch, which is why it keeps returning data where simpler scrapers fail.

Recommended: Apify Proxy with the RESIDENTIAL group. Datacenter addresses are rejected by Google almost immediately.

Notes and limits

• Related queries and related topics are not included. Google's relatedsearches endpoint rejects automated access even from fresh residential addresses (we tested twelve). We would rather ship what works than advertise a field that returns empty.
• Trending Now is far faster and cheaper per row than keyword analysis; if you need breadth, start there.
• Data is public, aggregated search interest. No personal data is collected.

Pricing: what a run actually costs

Pay per event: $0.01 per run, charged only when the first row is delivered, plus a per-result fee that scales down with your Apify plan tier (FREE/BRONZE/SILVER $0.0005, GOLD $0.0003, PLATINUM $0.00015, DIAMOND $0.0001). Platform compute is on us: nothing lands on your Apify bill beyond these events. A run that delivers zero rows costs $0.00: no rows, no start fee.

What you run	Items	Cost at FREE to SILVER tiers
Typical single-country pull (US, 24h window)	~371	about $0.20
Daily schedule with onlyNew on (only the additions, most days)	~25-40 new terms/day	about $0.02-0.03/day
Full daily list, no onlyNew, for 30 days	~371/day	about $5.87/month
A run that delivers zero rows	0	$0.00

At GOLD / PLATINUM / DIAMOND the typical pull above drops to about $0.12 / $0.066 / $0.047.

Compared honestly (public pricing pages, as of 2026-08-20)

	This Actor	apify/google-trends-scraper	memo23/google-trends-scraper
Per item, FREE tier	$0.0005	$0.003 (6x ours)	$0.003
Per item, BRONZE tier	$0.0005	$0.001 (2x ours)	$0.003
Per item, SILVER to DIAMOND	$0.0005 down to $0.0001	same as ours	$0.003 flat
Start fee	$0.01, only if rows are delivered	none	$0.005
Platform compute	included	billed to your account on top	included
Typical 371-item run, FREE tier	about $0.20	about $1.11 + compute	about $1.12
Typical 371-item run, SILVER tier	about $0.20	about $0.19 + compute	about $1.12

Read that table the honest way: on FREE and BRONZE, where most schedules start, our per-item price is the lowest of the three. From SILVER up, the official Actor's per-item price equals ours, and its zero start fee can make a single large run cheaper there before compute; its compute is then billed to you, and ours is not. memo23 charges $0.003 per item at every tier. A blanket "cheapest" claim would be false, so we are not making one.

Changelog

• 0.1.20 (2026-08): categories input (keep only trends in the topic categories you ask for, straight from the feed's own classification; runs where the filter matches nothing succeed with a message and cost nothing); pricing table with dated competitor comparison; measured reliability section; real example input for API and MCP callers.
• 0.1.19 (2026-08-13): resilience. A partially throttled request no longer fails the run (the countries that answered are delivered, the refused ones are named in the log); IP rotation now also covers session warm-up and the trending feed; README numbers re-measured on live pulls.
• 0.1.18 (2026-07-30): onlyNew cross-run memory, per country and window, kept 7 days; trend lifecycle fields started_at, ended_at, is_active, duration_minutes; zero-row semantics split: real breakage fails the run, "nothing new" succeeds with a message.
• 2026-07-29: first public release. Trending Now with estimated volume for 100+ geos and sub-regions, keyword interest over time and by region.