Google Trending Searches
Pricing
from $1.28 / 1,000 results
Google Trending Searches
Pricing
from $1.28 / 1,000 results
Rating
0.0
(0)
Developer
Ishaan Pare
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Google Trends Trending Searches and Top Terms
Get the searches trending right now on Google Trends for many countries in one run, at $1.50 per 1,000 results. Use it for news desks, content planning, market monitoring and AI agents that need to know what people are searching for today.
This Actor reads only Google's public Trending now feed and Google's public BigQuery dataset. It gives you what those sources contain, which is narrower than the Google Trends website. See What this Actor doesn't do before you buy.
What you get
- One row per trending search, for each country you list
- The search term, Google's approximate traffic label and the time the feed gives
- Related news headlines, snippets and links, and a picture link when the feed lists one
- A free status row for every country or keyword that couldn't be read or matched
- With your own Google Cloud key: the top 25 or rising 25 terms from Google's public BigQuery dataset, with rank, a 0 to 100 score, weekly history for those terms, and optional regional detail
Sample output
A trending search, in this format:
{"recordType": "result","source": "trending_rss","country": "US","countryName": "United States","term": "solar eclipse","matchedKeywords": [],"approxTraffic": "2000+","approxTrafficMin": 2000,"publishedAt": "2026-11-02T10:20:00.000Z","rank": null,"score": null,"percentGain": null,"week": null,"refreshDate": null,"regionName": null,"regionCode": null,"pictureUrl": "https://example.com/picture.jpg","pictureSource": "Example Daily","newsItems": [{"title": "Crowds gather for the eclipse","snippet": "A short summary of the story.","url": "https://example.com/story","source": "Example Daily","pictureUrl": "https://example.com/story.jpg"}],"sourceUrl": "https://trends.google.com/trending/rss?geo=US","keyword": null,"status": null,"reason": null,"fetchedAt": "2026-11-02T10:30:00.000Z"}
This example shows the format, and the values are made up.
How to use it
- Add country codes, one per line, such as US, GB or IN.
- Add keywords if you only want terms that contain certain words. Otherwise leave that list empty.
- Set Maximum results, then press Start.
Check the status rows after each run. If you only want data, filter on recordType equal to result.
Using BigQuery for top and rising terms
The trending searches source needs no key. The two BigQuery sources read the public Google Trends dataset through your own Google Cloud account:
- In Google Cloud, create a service account in a project of yours and give it the BigQuery Job User role.
- Create a JSON key for it, and paste the whole file into Google Cloud key.
- Set Source to Top terms or Rising terms, then press Start.
Apify stores that field encrypted, and the Actor doesn't write the key to the log or the dataset. The queries run in your project, so Google bills any BigQuery cost to you, separately from this Actor's price. Google's blog says the dataset is covered by BigQuery's free tier up to 1 TB of queries a month. Maximum data per query limits what a single query can read.
The Actor returns only recent data. If a table has nothing from the last 7 days, you get a free stale_data row instead of old results. Google's dataset covers the US and about 50 other countries.
What this Actor doesn't do
Google's robots.txt asks automated tools not to read the Trends explore pages, so this Actor doesn't read them or the private addresses behind them. That rules out what many Google Trends scrapers offer:
- No interest over time for a keyword you choose. Keywords here only filter terms Google already lists, so a keyword that isn't trending gets a no_match row, not a chart.
- No keyword comparison, related queries, related topics or interest by region for a keyword you choose.
- No category filter or custom date range.
If you need those, this isn't the right Actor. Google has a Trends API for them, but it's a limited alpha that needs your own access from Google, and this Actor doesn't use it.
Pricing
You pay only for what you get, and Apify platform usage is included.
| Event | Price |
|---|---|
| Each result delivered | $0.0015 ($1.50 per 1,000) |
| Each run started | Apify's default, about $0.00005 |
Status rows are free. A run with Maximum results left at 100 costs at most about $0.15.
On the free Apify plan, each run returns up to 100 results, and a status row tells you when you reach that limit. Any paid Apify plan removes it.
With BigQuery, each row is a result, so more weeks of history or regional detail cost more. Region detail can return a row for every term in every region of a country, so set Maximum results to what you're willing to pay for.
Status rows
The Actor always tells you what happened. Each of these is a free row with recordType set to status:
| Status | Meaning |
|---|---|
| no_input | No countries were given, so nothing was read |
| invalid_input | An entry wasn't a two-letter country code |
| blocked | Google refused the run, so it stopped and didn't try another way |
| robots_blocked | Google's robots.txt doesn't allow this feed, so it wasn't requested |
| robots_unavailable | robots.txt couldn't be checked, so no feed was read |
| not_found | Google has no feed for this country |
| failed | This country couldn't be read, and reason says why |
| no_results | The source was read, and it has nothing for this country |
| no_match | A keyword wasn't among the terms read |
| not_read | The run stopped before reaching this country |
| credentials_required | A BigQuery source was chosen with no key |
| credentials_invalid | The pasted key can't be used, and reason says why |
| credentials_rejected | Google didn't accept the key |
| stale_data | The BigQuery table has nothing from the last 7 days |
| query_too_large | A query would read more than Maximum data per query allows |
| query_failed | Google couldn't run the query, and reason says why |
| max_results | The run reached your Maximum results |
| free_limit | The run reached the free plan limit |
| spending_limit | The run reached your maximum cost |
A run that can't read anything still finishes normally with these rows, so check them rather than the run status alone.
Good to know
- Trending searches change through the day, and the feed decides how many it lists per country. Run the Actor on a schedule if you want a record over time, because the feed doesn't keep a history.
- Traffic is Google's rough label, not a count. approxTrafficMin is that label as a number.
- Countries are read one at a time, about a second apart, or slower if robots.txt asks.
- There's no proxy option. The Actor reads under its own name, and it stops if Google refuses it.
- BigQuery rows have a score only for weeks where the dataset gives one. Other weeks are left out.
- If you run out of budget or results partway, the rows already delivered are kept.
Using it with AI agents
The main inputs are lists, every field is optional, and the default source needs no credentials. An agent can cover many countries in one call and read status rows to see what went wrong.
Data and use
The trending searches source reads Google's public Trending now feed and robots.txt. The BigQuery sources read Google's public dataset with your key. The Actor uses no login to Google Trends and collects no personal data. Search terms can name people, so take care with how you use them. News headlines and pictures belong to their publishers, so check their terms before you republish them. You are responsible for how you use the data, including under Google's terms. Google asks anyone reusing this data to credit it, for example "Data source: Google Trends" with a link to trends.google.com. This Actor is not affiliated with or endorsed by Google.
Support
Open an issue on the Issues tab with your input and what you expected.