Google Trending Searches Scraper API - Trending Now avatar

Google Trending Searches Scraper API - Trending Now

Pricing

from $0.50 / 1,000 trending terms

Go to Apify Store
Google Trending Searches Scraper API - Trending Now

Google Trending Searches Scraper API - Trending Now

What is trending on Google right now, by country: every trending search from the last 4 to 168 hours with approximate search volume, growth, when it started, its category, and the latest news headlines with links. Put it on an hourly schedule and pay only for new trends. Failures are free.

Pricing

from $0.50 / 1,000 trending terms

Rating

0.0

(0)

Developer

Blackcube

Blackcube

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 hours ago

Last modified

Share

Google Trends Suite  •  2 Actors, one codebase, one keyword-report billed once
Google Trends Scraper
Interest, Regions, Related & Trending
Google Trending Searches Scraper API
➤ You are here

More from this account: YouTube Transcript Suite · Website Contact & Email Suite · Career Site & ATS Jobs Suite · Google News Suite · Keyword Research Suite · Shopify Store Intelligence Suite · eBay Data Suite · Amazon Reviews Suite · Reddit · Meta Ad Library · Vinted · Trustpilot Review Intelligence Suite · App Store & Google Play Reviews Suite · Telegram Channel Intelligence Suite · Business Reviews Suite · Amazon Product Data Suite · Google Sheets Suite · TikTok Suite · Snapchat Suite · LinkedIn Public Data Suite · Instagram Suite · Contact Validation Suite

The Google Trends suite — 7 Actors, one engine

What is trending on Google right now, by country — every trending search with approximate volume, growth, start time, category and the latest news headlines.

A run that finds nothing costs nothing. There is no run-start fee, error and coverage rows are free, and on a schedule a re-run bills only what is new.

⭐ Why this one

This is Trending Now, structured. For each country you get the currently trending searches from the last 4 to 168 hours: the term, its approximate search volume, its growth, when it started and whether it is still active, its category, the related queries Google groups with it, and the latest news headlines with links and sources.

It is built for a schedule. Put it on an hourly cron with delta billing on, and you pay only for trends that are new since the last run — a quiet hour costs almost nothing. If a country's live feed is briefly unavailable, it falls back to a lighter feed and says so in the coverage row rather than returning nothing.

🎯 Use cases

  • Feed a newsroom with the trends breaking in each market this hour.
  • Catch a spike early and publish while a topic is still climbing.
  • Track trends by category — sports, politics, entertainment — per country.
  • Power a "trending now" widget from a clean, scheduled feed.

🚀 Recipes

The default two-country pull with news.

{
"mode": "trending",
"trendingGeos": [
"US",
"GB"
],
"trendingHours": 24
}

Hourly alerts, only what is new

On a schedule, billed only for new trends.

{
"mode": "trending",
"trendingGeos": [
"US"
],
"trendingHours": 4,
"onlyNewSinceLastRun": true,
"stateName": "hourly"
}

The widest window, for analysis.

{
"mode": "trending",
"trendingGeos": [
"DE"
],
"trendingHours": 168
}

📥 Input

FieldWhat it does
trendingGeosThe countries to pull trending searches for, one per line.
trendingHoursHow far back to reach: the last 4, 24, 48 or 168 hours.
includeTrendingNewsAttach the latest news headlines, links and sources to each trend.
onlyNewSinceLastRun / stateNameFor a schedule: return and bill only trends that are new since the last run.
maxTrendingTerms / maxCostUsdHard ceilings on rows and on spend.

No proxy settings. Unblocking is handled and priced in — you never configure infrastructure.

📤 Output

RowWhat it is
trending-termThe billed row. One trending search: the term, approximate volume, growth, when it started and whether it is still active, its category, related queries, and the latest news with links and sources.
coverageFree. Per country: how many terms were found, how many were new, and which feed served them.
errorFree. Anything that could not be read, with a stable reason.

Every run also ends with a free summary row: counts, the estimated spend, and why it stopped. Export any run to CSV, Excel, JSON, XML or HTML from the Storage tab or the API — the dataset ships with ready-made views (Trending Now).

One trending-term row is a complete picture of a single trend:

  • The term and its approximate search volume bucket.
  • Growth — how fast it is climbing.
  • When it started, and whether it is still active or has already faded.
  • Category — Sports, Politics, Entertainment, and the rest.
  • Related queries Google groups with the trend.
  • News — the latest headlines with their links, sources and timestamps, so you can act on the trend, not just count it.

A few things about the data itself — the kind of detail most scrapers leave you to discover on your own bill:

  • The numbers are relative, on a 0–100 scale. A value is interest against the peak of the same series, not a count of searches. It only means something next to another value on the same scale — which is exactly why this returns approximate volume buckets alongside the trend, so you get an absolute signal too.
  • The most recent bucket is partial. The latest point of any live series is still being collected and will move; it is flagged isPartial so you can drop or discount it rather than mistake it for a drop in interest.
  • City-level data is sparse. Google reports city interest for only a handful of places for most keywords.
  • Related topics are sparse. The related topics section was empty in every session we measured. It is off by default here, and when it is empty the report says so rather than inventing rows — you are never billed for a section Google did not return.

💰 Pricing

Pay per trending term. Failures are free and there is no run-start fee.

EventFREEBRONZESILVERGOLDPLATINUMDIAMOND
keyword report$10.00$8.30$6.30$5.00$4.70$4.30
trending term$1.00$0.83$0.63$0.50$0.47$0.43

Prices are per 1,000. Your tier is your Apify plan. On the Gold plan, 1,000 trending terms cost $0.50. A trending term with no data costs $0.00, and on a schedule an unchanged feed re-bills nothing.

⏰ Run it on a schedule

Trending Now is built for a schedule. Set an hourly cron, turn on only new since the last run, and each hour you get the trends that appeared since the last pull and nothing else — a quiet hour costs almost nothing.

Cron: 0 * * * * (every hour).

❓ FAQ

Google does not publish an official public API for this data. This Actor is the practical equivalent: give it countries and it returns clean, structured rows you can pull from the Apify API or export to a file — no account on Google's side, no infrastructure to run.

Every run's dataset exports to CSV, Excel, JSON, XML or HTML from the Storage tab, or through the Apify API. Each trending term is one row.

Google Trends values are relative, not absolute. Each series is scaled 0–100 against its own peak over the window you asked for, so the same keyword reads differently over "past 7 days" than over "past 12 months", and today's live window differs from yesterday's. The numbers are an index of relative interest, not a count of searches — so a value only means something next to another value on the same scale.

Can I compare more than five keywords?

Google's shared-scale comparison holds at most five keywords at once.

Trending Now moves continuously — new trends appear and old ones fade through the day. A short window (4 hours) shows what is breaking now; a longer one (up to 7 days) shows what has trended over the period. On an hourly schedule you catch each new trend as it appears.

What time zone are the timestamps in?

Every timestamp — when a trend started, when it ended, and each news item — is a UTC ISO timestamp, so results line up across countries without any conversion on your side.

Can I get absolute search volume numbers?

Trending Now includes an approximate volume bucket per trend (for example 20,000+), which is the closest thing Google publishes to an absolute number.

Do I need a proxy or a Google account?

No. Everything is handled for you and priced into the per-trending term fee. There is no proxy field to configure and no login anywhere.

🛟 Support

Something not working, or a signal you want added? Open an issue on the Issues tab — it is read and answered. If this saved you time, a rating on the listing helps more than you would think.

Unofficial and not affiliated with, endorsed by or sponsored by Google. It reads only publicly available Google Trends data.

Looking for the full toolkit? → Google Trends Scraper

Use it from n8n, MCP, the API or a schedule

Built to be called by a workflow, not only from the Store form. The Actor is vonsensey/google-trending-searches; every snippet below sends {}, which runs the defaults shown on the form — replace it with your own input.

n8n

Install the Apify community node (@apify/n8n-nodes-apify under Settings → Community Nodes, or search "Apify" on n8n Cloud). Add Apify → Run Actor with Actor vonsensey/google-trending-searches and your input JSON, then Apify → Get Dataset Items on the run's defaultDatasetId and pipe the rows anywhere. For scheduled runs, the On new Apify Event trigger fires when a run of this Actor finishes.

MCP (Claude, Cursor, VS Code, any MCP client)

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=vonsensey/google-trending-searches",
"headers": {
"Authorization": "Bearer <YOUR_APIFY_TOKEN>"
}
}
}
}

Your agent then calls vonsensey/google-trending-searches as a tool with the same input the form takes and reads the dataset back.

REST API (one call, rows in the response)

curl -X POST "https://api.apify.com/v2/acts/vonsensey~google-trending-searches/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" -d '{}'

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("vonsensey/google-trending-searches").call(run_input={})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('vonsensey/google-trending-searches').call({});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Make, Zapier, LangChain, CrewAI

The Apify app in Make and Zapier has a Run an Actor module: pick vonsensey/google-trending-searches. In LangChain and CrewAI the Apify tool wrappers take the same Actor id. A daily schedule needs nothing but the Console: Schedules → Create → this Actor → cron, and the dataset fills on its own.

Run it without configuring anythingScrape Google trending searches by country, a ready-made example you can start as-is or copy.

Use cases

  • Every Trends signal in one report. Interest over time, interest by region and city, and related and rising queries for a keyword — bundled into one row, not four datasets to join.
  • Compare up to five keywords on one scale. Google Trends is relative; measured together, the numbers are actually comparable instead of five incomparable charts.
  • Catch what is trending now, by country. Trending Now with approximate volume, growth, category and news — on an hourly schedule, billed only for new trends.
  • Failures are free. A keyword with no data is a free row that says so, never an invented zero and never a charge; there is no run-start fee.

Run it on a schedule

A one-off pull answers a question; a schedule answers it every day without you. Open Schedules in the Apify Console, point a cron at this Actor, and the dataset keeps filling on its own — no server, no cron box, no babysitting. Everything here is built to be re-run: you are billed per keyword-report delivered, and the FAQ below says exactly what a scheduled run that finds nothing new costs.

FAQ

Google does not publish an official public API for this data. This suite is the practical equivalent: pass keywords or countries and get clean, structured rows you can pull from the Apify API or export to a file, with no Google account and no infrastructure to run.

Google Trends values are relative, scaled 0-100 against the peak of each series over the window you asked for. The same keyword reads differently over "past 7 days" than over "past 12 months", and the latest bucket is always partial because it is still being collected. The numbers are an index of relative interest, not a count of searches.

Every run's dataset exports to CSV, Excel, JSON, XML or HTML from the Storage tab or the Apify API. Turn on the flat-rows option and every timeline point, region and related query becomes its own line, ready for a spreadsheet.

Do I need a proxy or a Google account?

No. Unblocking is handled and priced into the per-report fee. There is no proxy field to configure anywhere in the suite and no login on Google's side.


Something wrong, or a field you need that is missing? Open an issue on the Issues tab — it is read and it gets fixed. If this saved you time, a rating on the Store page helps the next person find it.