Google Trends Daily Searches — The Endpoint That Doesn't 429
Today's trending searches for 60+ countries, with the news stories driving each one. Uses Google's RSS feed, which does not rate-limit — so runs don't fail the way explore-API scrapers do.
Google Trends Daily Searches — The Endpoint That Doesn't 429 returns 7 documented output fields, including geo, term, approxTraffic, pubDate and newsTitle. Every field carries a declared type, a written description and an example value. 42 runs are recorded on Apify.
- 7
- Output fields
- 7
- Inputs
- 42
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| geo | stringnull | Geographic coordinates in 'lat,lon' form. | <geo> |
| term | stringnull | Term this row relates to. | <term> |
| approxTraffic | integernull | Approx Traffic as recorded for this row. | 0 |
| pubDate | stringnull | Pub Date as recorded for this row. | <pubDate> |
| newsTitle | stringnull | News Title as recorded for this row. | <newsTitle> |
| newsSource | stringnull | News Source as recorded for this row. | <newsSource> |
| trendUrl | stringnull | Trend Url as recorded for this row. | <trendUrl> |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"geo": "<geo>",
"term": "<term>",
"approxTraffic": 0,
"pubDate": "<pubDate>",
"newsTitle": "<newsTitle>",
"newsSource": "<newsSource>",
"trendUrl": "<trendUrl>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| geos | arrayoptional | Two-letter country codes to fetch trending searches for (e.g. US, GB, IN, DE, BR, JP). Google publishes feeds for 50+ countries; an unknown code fails immediately with the full supported list. |
| expandNews | booleanoptional | Off: one row per trend, with the top news story attached and a newsCount. On: one row per news story, trend fields repeated — better for CSV pivoting on articles. |
| termIncludes | arrayoptional | Keep only trends whose search term contains at least one of these words (case-insensitive). Leave empty for all trends. |
| termExcludes | arrayoptional | Drop trends whose search term contains any of these words (case-insensitive). Leave empty to drop nothing. |
| minTraffic | integeroptional | Drop trends with published traffic below this number (e.g. 50000 keeps only 50K+ trends). Trends where Google publishes no figure are always kept, so real trends are never silently hidden. |
| maxItems | integeroptional | Hard limit on results returned. This is strictly enforced — you will never be charged for more than this. |
| maxAgeHours | integeroptional | Leave empty for the full feed. Set to 24 to keep only trends that surfaced in the last day. Trends without a published date are kept. |
04 — run
Run Google Trends Daily Searches on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
7 of 7 fields described
- What does Google Trends Daily Searches — The Endpoint That Doesn't 429 return?
- It returns 7 documented output fields: geo, term, approxTraffic, pubDate, newsTitle, newsSource and trendUrl. Each field declares its type, a description of what it holds, and an example value.
- What input does Google Trends Daily Searches — The Endpoint That Doesn't 429 take?
- All 7 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does Google Trends Daily Searches — The Endpoint That Doesn't 429 need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Google Trends Daily Searches — The Endpoint That Doesn't 429?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.