Google Trends Rising Topics — Discover Trends in 56 Countries avatar

Google Trends Rising Topics — Discover Trends in 56 Countries

Pricing

$50.00 / 1,000 country processeds

Go to Apify Store
Google Trends Rising Topics — Discover Trends in 56 Countries

Google Trends Rising Topics — Discover Trends in 56 Countries

Discover rising and trending Google searches across 56 countries. Get structured trend data for market research, SEO, content ideas, product research and trend monitoring.

Pricing

$50.00 / 1,000 country processeds

Rating

5.0

(3)

Developer

Emir Llonviche

Emir Llonviche

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 days ago

Last modified

Share

Google Trends Rising Searches — Track New & Trending Topics in 56 Countries

Get the trending Google searches for up to 56 countries in a single run — and, unlike a plain snapshot, detect what is new, what is climbing, and what is trending across multiple countries at once.

Unofficial. This Actor is not affiliated with, endorsed by, or sponsored by Google LLC. "Google" and "Google Trends" are trademarks of Google LLC. This Actor reads the Trending Now RSS feed that Google publishes publicly.

Built on Google's official Trending Now RSS feed — not a headless browser, not a reverse-engineered private endpoint. That is why this Actor runs in about two seconds per country, needs no proxies, and does not depend on Google's front-end implementation.


What makes it different

It detects what just started trending, not just what is trending. Google's feed is a snapshot with no memory. This Actor compares every run against your previous one and adds isNew, rankChange, firstSeenAt and hoursTrending to each row. A term that entered the list twenty minutes ago and a term that has been trending for several hours no longer look identical.

It tracks trends across countries. Because every requested country is fetched in the same run, each row carries alsoTrendingIn and countryCount: the other markets where the exact same term is trending right now. This lets you distinguish a local trend from a topic spreading across multiple countries.

One run, up to 56 countries. Countries are fetched in parallel batches, so a full 56-country sweep typically takes well under a minute.

News articles attached. Each trend can include up to three articles Google associates with it: title, URL, source, image and snippet.

Built for the current Google Trending Now feed. The widely-referenced trends.google.com/trends/api/dailytrends endpoint was retired and now returns 404. This Actor reads Google's Trending Now RSS feed, which Google publicly serves for automated consumption. No headless browser and no proxies are required.

Built to fail loudly, not silently. Countries are fetched independently, so one failure never aborts the rest. Three retries with exponential backoff are used for network errors and 5xx responses. Every run writes a RUN_SUMMARY that reports successful and failed countries.

On your first run, there is no previous run to compare against, so isNew, rankChange and hoursTrending come back null. The Actor will not claim that a term is new when there is no history available. Run it a second time and the movement data becomes available. Schedule it hourly or daily to build your own trend history.


What you can use it for

SEO and content research — detect rising searches and identify topics worth publishing about before they become saturated.

News monitoring — see what people are searching for right now and get related news articles alongside each trend.

Social and brand monitoring — detect when a brand, product, person or event suddenly appears in Google's trending searches.

Market research across borders — compare what is trending in France, Germany, the UK, the US and other markets in a single dataset.

Breaking-trend detection — schedule the Actor hourly and filter on isNew to detect searches that have just entered a country's trending list.

Cross-market trend discovery — filter on countryCount > 1 to find topics that are trending across multiple countries at the same time.


What you get

One row per trending search, per country:

{
"country": "FR",
"countryName": "France",
"rank": 1,
"term": "météo",
"isNew": false,
"rankChange": 3,
"firstSeenAt": "2026-08-25T08:00:00.000Z",
"hoursTrending": 3,
"alsoTrendingIn": ["BE", "CH"],
"countryCount": 3,
"trafficLabel": "50000+",
"trafficMin": 50000,
"publishedAt": "Sun, 23 Aug 2026 21:50:00 -0700",
"imageUrl": "https://encrypted-tbn3.gstatic.com/images?q=tbn:AAA",
"imageSource": "Le Monde",
"newsCount": 3,
"news": [
{
"title": "Canicule : alerte orange dans douze départements",
"url": "https://www.lemonde.fr/meteo/article/canicule",
"source": "Le Monde",
"imageUrl": "https://encrypted-tbn3.gstatic.com/images?q=tbn:BBB",
"snippet": null
}
],
"scrapedAt": "2026-08-24T19:30:00.000Z",
"sourceUrl": "https://trends.google.com/trending/rss?geo=FR"
}

trafficLabel is Google's own traffic threshold (100+, 1000+, 50000+). trafficMin is that threshold as a number, so you can sort and filter on it programmatically.


Input

{
"countries": ["FR", "GB", "DE", "US"],
"maxItemsPerCountry": 10,
"includeNews": true,
"minTraffic": 1000
}
FieldDefaultWhat it does
countries["FR"]Country codes to fetch. Each country is fetched independently.
maxItemsPerCountry10Maximum number of trends to return per country. Google publishes up to 10.
includeNewstrueAttach related news articles to each trend.
minTraffic0Keep only trends above this Google traffic threshold.
languageISO 639-1 code for related news (fr, en, de…).
timeoutSecs30Per-country request timeout.

Supported countries:

AR AT AU BE BG BR CA CH CL CO CZ DE DK EG ES FI FR GB GR HK HR HU ID IE IL IN IT JP KE KR LT LV MA MX MY NG NL NO NZ PE PH PL PT RO RS SA SE SG SK TH TR TW UA US VN ZA

An unrecognised country code is reported before any request is made, so you do not pay for a run that was doomed from the start.


Historical trend detection

Google's Trending Now feed provides the current snapshot, but it does not provide the historical movement data used by this Actor.

This Actor builds that history from your own successive runs.

On the first run:

isNew = null
rankChange = null
firstSeenAt = null
hoursTrending = null

After subsequent runs, the Actor can determine whether a trend is new, how its rank changed, and how long it has been observed.

For example, if a term moves from rank 7 to rank 2:

rankChange = 5

If a term was not present in the previous run and appears in the current run:

isNew = true

For the most useful movement data, schedule the Actor hourly or daily depending on your use case.


Cross-country trend detection

When multiple countries are requested in the same run, the Actor checks which exact search terms are trending in multiple markets.

For example:

{
"country": "FR",
"term": "example trend",
"alsoTrendingIn": ["BE", "CH"],
"countryCount": 3
}

This allows you to filter for:

countryCount > 1

and identify topics that are spreading across borders instead of remaining specific to one market.


News articles

When includeNews is enabled, each trend can include up to three related news articles.

Each article may contain:

  • title
  • url
  • source
  • imageUrl
  • snippet

This makes it possible to combine trend detection with basic context about why a search is trending.


Reliability

Reliability is the point of this Actor, so here is exactly what it does:

  • Each country is isolated. One failure never aborts the others.

  • Three attempts with exponential backoff on network errors and 5xx responses. A 404 is not retried — an invalid country code will not become valid.

  • Output is validated. A feed that parses but contains no trends is treated as an anomaly and reported, not silently returned as an empty result.

  • Every run writes a RUN_SUMMARY to the key-value store: countries requested, succeeded, failed, and why. You can point a monitor at it and know when a country starts failing.


Performance

This Actor reads Google's public Trending Now RSS feed rather than loading Google's web interface.

That means:

  • No headless browser
  • No browser session
  • No proxies required
  • Independent requests per country
  • Parallel country processing
  • Fast execution

A full 56-country sweep typically completes in under a minute.


Pricing

Pay per event: $0.05 per country successfully processed.

A failed country is never charged.

Examples:

  • 4 countries once per day: about $6/month
  • 10 countries once per day: about $15/month
  • 56 countries once per day: about $84/month

The cost scales directly with the number of countries successfully processed.


Limits, stated plainly

  • Google's feed publishes up to 10 trends per country. This Actor cannot return more than Google publishes in this feed.

  • Traffic values are thresholds, not exact search volumes — that is how Google publishes them.

  • The feed covers Trending Now, not historical Google Trends search-volume data.

  • Historical movement is built by this Actor from your own successive runs. The first run has no movement data, and more frequent runs provide finer-grained movement detection.

  • Coverage is limited to the 56 countries supported by this Actor's Google Trending Now feed.


Data source

This Actor reads the public RSS feed published by Google for Trending Now.

It does not use Google's private APIs, does not require a browser session, and does not scrape the Google Trends front end.

Unofficial. This Actor is not affiliated with, endorsed by, or sponsored by Google LLC. "Google" and "Google Trends" are trademarks of Google LLC.

This Actor does not collect individual user data. It processes aggregate search trend information published by Google and links to publicly available news articles.

Found a bug or need a country added? Open an issue on the Actor page.