Scrape Google Trends Trending Now — Top Searches by Country
Pricing
from $2.00 / 1,000 results
Scrape Google Trends Trending Now — Top Searches by Country
Google Trends Trending Now for any country: trending keywords with approximate search traffic, publish time and picture. Keyword filters and new-trend monitor.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Lorenzo Talamucci
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Share
Scrape Google Trends Trending Now for any country and export the trending searches to CSV, Excel or JSON: keyword, approximate search traffic (like 2000+ and 2000), publish time and picture link. Filter by keyword or minimum traffic, and schedule it to receive only the trends you have not seen yet.
The Actor reads Google's public Trending Now RSS feed for the country you choose and turns it into flat, spreadsheet-ready rows. It is small, fast and cheap by design: one feed, one clean table, ready for dashboards, newsroom alerts or content planning.
How to get Google trending searches by country
- Open the Input tab and paste one of the examples below (JSON view).
- Click Start: a run takes a few seconds.
- Download the dataset from Storage → Dataset as CSV, Excel or JSON, or read it through the API.
Current trending searches in the United States:
{"geo": "US", "maxResults": 100}
Italy, only new trends since the last run (for a schedule):
{"geo": "IT", "onlyNew": true, "monitorName": "italy-trending-daily"}
United Kingdom, football-related trends with at least 1,000 searches:
{"geo": "GB", "keywordContains": "football", "minTraffic": 1000, "maxResults": 20}
Input fields
| Field | What it does |
|---|---|
geo | Two-letter country code in capitals, e.g. US, IT, GB (default US) |
maxResults | Maximum rows, 1–1,000 (default 100); the feed usually has fewer entries |
keywordContains | Keep only trends whose keyword contains this text (case-insensitive) |
minTraffic | Minimum approximate traffic, e.g. 1000 |
onlyNew | Return only trends that are new or changed since the previous run |
monitorName | Named store that remembers trends between runs (default google-trends-monitor) |
proxyConfiguration | Optional Apify proxy; not needed for the tested feeds |
What trend data you get
| Field | Meaning |
|---|---|
keyword | The trending search |
geo | Country code |
publishedAt | When Google published the trend (RFC 2822 date) |
traffic | Google's approximate traffic label, e.g. 2000+ |
approxTraffic | The same label as a number, e.g. 2000 |
sourceUrl | The RSS feed the row came from |
pictureUrl | Picture link from the feed, when present |
id | Stable ID (same keyword, country and publish time = same ID) |
type, collectedAt | Row type (trending) and collection time |
Real record from a run on 28 September 2026:
{"type": "trending","keyword": "national coffee day 2026","geo": "US","publishedAt": "Mon, 28 Sep 2026 11:40:00 -0700","traffic": "2000+","approxTraffic": 2000,"sourceUrl": "https://trends.google.com/trending/rss?geo=US","pictureUrl": "https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcT41rvzqnDr-C72eisGHClWVvUb7R3dHlwyqCqhZg_MzBnNOWGFMws1GXt9crA","id": "ca45fde2dd84fe31a16080b52b9279ea684eeecb66a4f944552b4a15bfb2623d","collectedAt": "2026-09-28T19:32:40.714Z"}
How to monitor new Google trends every hour
Set "onlyNew": true and your own monitorName. The first run returns the whole current feed; later runs return only trends that were not there before, or whose traffic label changed. Trends already delivered and unchanged are skipped and not charged.
- Save the input as a Task.
- In Schedules, run it every hour (
0 * * * *) or every morning (0 7 * * *) in your timezone. - Connect the dataset to Slack, email, Google Sheets or a webhook in Integrations to get the new trends where you work.
Use one monitor name per country and filter set, and do not run two jobs on the same monitor at once.
Use cases
- Newsrooms and editors: spot breaking topics in your country and write while interest is rising.
- SEO and content teams: find timely keywords for articles, social posts and landing pages.
- Marketing and social media: react to trending moments with relevant campaigns.
- Dashboards and BI: log daily trends per country into a sheet or database and build your own history.
- AI agents and LLM workflows: feed current topics into summaries, briefs or newsletters.
Pricing
| Event | Price |
|---|---|
| Run start (1 GB memory) | $0.05 |
| Trends in the dataset | $2 per 1,000 rows ($0.002 each) |
A single country feed usually has a few dozen rows or fewer, so a typical run costs about $0.05–$0.10. The start fee scales with memory above 1 GB. With onlyNew, repeated trends are not charged.
Data source and limits
- Source: Google's public Trending Now RSS feed (
https://trends.google.com/trending/rss?geo=<country>). No login, no API key, no captcha solving. - This is the current snapshot only. It does not provide interest over time, comparisons, related queries or topics, regional breakdowns, or historical archives. Schedule the monitor if you want to build a history.
- The feed length is controlled by Google: our tests returned 10 entries per country.
maxResultsis a ceiling, not a promise. - Traffic is Google's approximate label, not an exact search count.
- Some countries may return an empty feed; the run still succeeds and explains it in the
OUTPUTrecord. - Google's terms apply to how you reuse the content; public access is not an unrestricted redistribution licence.
FAQ
Which countries are supported? Any two-letter country code for which Google publishes a Trending Now feed. We tested US, GB and IT; if a country has no feed, the run ends with 0 rows and an explanation.
Is this the same as Google Trends interest over time? No. This Actor returns what is trending right now, not keyword charts.
How often does the list change? Google refreshes Trending Now throughout the day; hourly or daily schedules both work.
Why did I get zero rows? Your keywordContains or minTraffic filter removed everything, or the monitor had already delivered those trends. Both are normal, successful runs.
Do I need a proxy? Not for the feeds we tested. Proxy usage adds Apify fees.
Changelog
- 1.0 — 29 Sep 2026: first public release.