Google Trends Daily Trending Searches
Pricing
from $1.33 / 1,000 results
Google Trends Daily Trending Searches
Get currently trending Google searches per country with traffic estimates and the related news articles. Keyless RSS source, any number of countries per run, no login.
Pricing
from $1.33 / 1,000 results
Rating
0.0
(0)
Developer
Farhan Febrian Nauval
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Google Trends — Daily Trending Searches by Country
The searches trending right now in any country, with Google's traffic estimate and the news stories driving each one. Keyless RSS source, any number of countries per run, no login and no browser.
Input
| Field | Type | Default | Description |
|---|---|---|---|
geos | array | ["US"] | Two-letter country codes — US, GB, DE, ID, JP, BR, IN… |
maxTrendsPerGeo | integer | all | Google returns exactly ten per country, so this only lowers that |
Output
{"_input": "US","_source": "S1-trends-rss","_scrapedAt": "2026-09-12T11:04:18Z","geo": "US","rank": 1,"query": "austin weather","exploreUrl": "https://trends.google.com/trends/explore?q=austin+weather&geo=US","approxTrafficLabel": "500+","approxTrafficFloor": 500,"startedAt": "2026-09-11T21:30:00Z","pictureUrl": "…", "pictureSource": "KXAN Austin","topNewsTitle": "Second arrest made in connection with 24-year-old Austin man's death","topNewsUrl": "https://www.kxan.com/news/crime/…","topNewsSource": "KXAN Austin","newsItems": [{ "title": "…", "url": "…", "source": "…", "pictureUrl": "…" }],"newsItemCount": 3}
Three things worth knowing
Every filter parameter you might expect is ignored. hours=168, category=b,
sort=search-volume and hl=en each returned byte-identical output to the bare geo=US call. They
mirror the filters the Trends web UI offers, but the RSS feed does not implement them — so this
actor does not offer them either, rather than accept settings that quietly do nothing.
approxTrafficFloor is a floor, not a count. Google publishes a bucket: 200+, 500+,
1000+. The parsed number is the bottom of that bucket, named so that nobody sums a column of them
and calls the result search volume. The original label ships alongside it.
There is no history in this feed — it is a snapshot of now. Tracking how a trend rises or fades
means running this actor on a schedule and keeping what it returns. The interactive endpoint behind
the Trends charts (/trends/api/explore) answers 429 to anonymous callers, which is why this is
built on the RSS feed instead.
Coverage and gaps
Ten trends per country, each with up to three related articles. Verified returning 10 items for US,
GB, DE, ID, JP, BR and IN; an unknown code gets a clean 400 and becomes an unknown_geo row.
Three trends in twenty carried no news articles and no picture at all — Google surfaces those
fields only when it has them, so an empty topNewsTitle is a fact about that trend, not a parse
failure. ht:news_item_snippet is always empty (111 instances across four countries, every one
self-closing), so it is not emitted at all.
Errors
_error | Meaning |
|---|---|
unknown_geo | Google rejected the country code with a 400 |
empty_feed | 200 with no <item> elements — the format changed |
unexpected_shape | An item with no title |
blocked | The feed returned nothing usable |
network_error | Never reached the server |
If no country returns trends, the run fails rather than reporting success over an empty dataset.