Google Trends Trending Now Scraper - Daily Trending Searches

For content teams, SEO analysts and newsrooms who want to know what people are searching for on Google right now. Returns the live "Trending now" list for any country - the trending search term, approximate search traffic, when it started, its picture and the news articles Google links to for it - read from Google's own official public Trending RSS feed. No login, no proxy, no browser. Turn on alert mode (onlyNewSinceLastRun) and run it on a schedule to be told only about trends you haven't seen yet.

Pay-per-result: $0.001 per trend — 1,000 trends = $1.

What this is (and is not)

This Actor reads exactly one thing: Google's "Trending now" feed, https://trends.google.com/trending/rss?geo=<country> - the same list Google publishes as an RSS feed. It is the current list of trending searches per country, with the volume bucket Google publishes for each.

It is not Google Trends Explore. It does not return interest-over-time curves, related queries or topics, regional breakdowns, or historical trends. Google's robots.txt disallows the Explore pages, so this Actor never requests them.

Quick start (1 minute)

1. Open the Input tab and list one or more two-letter country codes, e.g. US and GB.
2. Click Start. Export the dataset to CSV/Excel/JSON, or pull it through the API shown below.

{
  "countries": ["US", "GB"],
  "maxItems": 20,
  "includeNews": true
}

That prefilled example finishes in well under a minute and costs at most $0.02.

How it works

1. Checks trends.google.com/robots.txt for the exact feed path before reading anything, and skips (reporting why) if it were ever disallowed.
2. Requests one small RSS file per country - about one request every 3 seconds, with an honest User-Agent that identifies this Actor.
3. Parses each <item> into one flat row: search term, approximate traffic, start time, picture and news articles.
4. Reports honestly, per country, a feed Google did not serve (non-200 response, empty feed, or not an RSS document) and carries on with the other countries. A country with no feed costs you nothing.

Use cases

• Content and editorial planning: see what is surging in your market this hour, with the headlines Google associates with it, and decide what to publish next.
• SEO and keyword research: capture the day's trending searches per country, with the volume bucket (approxTrafficMin), and build a history by running on a schedule.
• Newsrooms and social teams: get an alert when a new term starts trending in a country, with source articles attached so you can see why.

Alert mode: get only new trends

Set onlyNewSinceLastRun: true and put the Actor on a schedule. Every run after the first delivers (and charges for) only trends it has not delivered before for that country. A trend is recognised by country + search term + the day it started, so a trend that stays on the list across runs is delivered once, and a term that trends again on a later day is new again.

1. Choose your countries:

{
  "countries": ["US", "GB", "DE"],
  "includeNews": true,
  "onlyNewSinceLastRun": true,
  "maxItems": 100
}

2. Click Schedule on the run page (or create one under Schedules in the Apify Console). Every 1-3 hours works well; the list changes through the day.
3. The first run is a baseline: it delivers every trend currently listed and remembers them. You are charged normally for that run.
4. Add a Webhook under the schedule's Integrations for ACTOR.RUN.SUCCEEDED, pointing at Apify's Slack/email integration (or a Zapier/Make step), so new trends reach you as they appear.

The run's status message says what happened, e.g. "First run for 3 countries: 30 trend(s) delivered and remembered; next runs return only new ones.", then "4 new trend(s) since last run across 3 countries (26 already seen).". A run with nothing new still succeeds with an empty dataset - that is the point of the mode. Each country keeps its own history. A trend that was cut off by maxItems or your spending limit is not remembered, so the next run still delivers it.

Get new trending search alerts in Discord, Telegram, Slack, Teams, Google Chat, your phone (ntfy/Pushover) or any app (webhook)

Want a Google Trends alert in Discord, Telegram or on your phone the moment a new search starts trending, instead of checking a dataset? Add one or more destinations in the Actor's Notifications (optional) section and each run sends the trends it delivered. It is a monitor that notifies you: it only reads Google's public "Trending now" RSS feed, and it never posts, logs in or contacts anyone.

Channel	Fill in	What you get
Discord	discordWebhookUrl	One card per trend, 10 per message
Telegram	telegramBotToken + telegramChatId	Up to 10 trends per message, one line each
Slack	slackWebhookUrl	Block Kit message, up to 10 trends per message
Mattermost, Rocket.Chat	slackCompatibleWebhookUrl	Slack-style incoming webhook: a Markdown list (these apps do not render Slack Block Kit)
Microsoft Teams	teamsWebhookUrl	Adaptive Card from a Teams Workflows webhook, up to 10 trends per card
Google Chat	googleChatWebhookUrl	Card in a space, up to 10 trends per message
ntfy (phone push, no account)	ntfyTopic (optional ntfyServer, ntfyToken)	A push per trend, up to 10, then one "...and N more"
Pushover (phone push)	pushoverUserKey + pushoverAppToken	A push per trend, up to 10, then one "...and N more"
Any app: Zapier, Make, n8n, Pipedream, IFTTT, Home Assistant	webhookUrl	One JSON POST per run with every delivered row

Fill in as many as you like; each channel works on its own and a failing one never stops the others.

Setup, channel by channel

• Discord (1 minute): Server Settings → Integrations → Webhooks → New Webhook → pick the channel → Copy Webhook URL.
• Telegram (2 minutes): chat with @BotFather, send /newbot, paste the token into telegramBotToken. Add the bot to the chat or channel (administrator for a channel; for a chat with yourself press Start on the bot). telegramChatId is a numeric id (123456789, or -1001234567890 for a group or channel) or a public @channelusername.
• Slack: at api.slack.com/apps create an app (From scratch) → Incoming Webhooks → switch it on → Add New Webhook to Workspace → pick the channel → copy the https://hooks.slack.com/services/... URL.
• Mattermost or Rocket.Chat: create an incoming webhook in the app and paste its public https:// URL into slackCompatibleWebhookUrl. It must be reachable from the internet: localhost, private IP addresses and .local / .internal names are rejected.
• Microsoft Teams: in the channel open ... → Workflows → Post to a channel when a webhook request is received → finish the wizard and copy the URL (a host ending in .logic.azure.com or .powerplatform.com). The old "Office 365 connector" webhooks are retired and not supported.
• Google Chat: in the space open Apps & integrations → Webhooks → Add webhook, name it and copy the https://chat.googleapis.com/v1/spaces/... URL (needs a Google Workspace account that allows webhooks).
• ntfy (free, no account): install the ntfy app (or open ntfy.sh), subscribe to a topic with a long random name, and put the same name in ntfyTopic. Anyone who knows the topic can read it, so make it unguessable. Own server or a protected topic: set ntfyServer (public https:// address) and ntfyToken.
• Pushover: copy your user key from pushover.net into pushoverUserKey, create an application at pushover.net/apps/build and put its API token in pushoverAppToken. Pushover itself is a separate paid app after its trial: check their pricing.
• Any app (webhook): paste the catch-hook URL from Zapier, Make, n8n, Pipedream, IFTTT or Home Assistant into webhookUrl. It must be a public https:// address.

The recipe: a trending-search alert in five steps

1. Choose your countries (and leave includeNews on if you want the top story in each message).
2. Turn on onlyNewSinceLastRun.
3. Add your destination(s) from the table above.
4. Run it once. The first run is the baseline and sends the trends currently listed (up to maxNotifications).
5. Create a Schedule (every 1-3 hours works well; the list changes through the day). From then on you only hear about trends it has not delivered before.

{
  "countries": [
    "US",
    "GB"
  ],
  "includeNews": true,
  "onlyNewSinceLastRun": true,
  "maxItems": 100,
  "discordWebhookUrl": "https://discord.com/api/webhooks/<id>/<token>",
  "ntfyTopic": "your-long-random-topic-name",
  "maxNotifications": 25
}

The generic webhook (webhookUrl)

Each run sends one POST per 100 delivered rows (so usually one) with this body, followed by whatever your tool does with it:

{
  "source": "apify",
  "actor": "google-trends-trending-now",
  "runId": "HG7ML7M8z78YcAPEB",
  "count": 2,
  "total": 2,
  "part": 1,
  "parts": 1,
  "items": [
    {
      "...": "the full dataset rows"
    }
  ]
}

count is the number of rows in this POST, total the number delivered in the run, and part / parts number the POSTs when a run delivers more than 100 rows. maxNotifications does not cap the webhook: your tool gets every delivered row. Your endpoint should answer with a 2xx status; redirects are not followed and a failure is reported in the run status, never retried in a loop.

What each message contains

Each trend is announced as New trend: <search term> (<country>) with the traffic bucket Google publishes (for example 500+), the time it started, the top news story Google attached to it (headline and outlet), the number of news articles, and Google's picture where the channel can show one. A trend has no page of its own in the data, so the link opens that top news article. With includeNews off there is no link and no story, only the trend itself. Discord gets a card per trend, Telegram one line per trend, Slack Block Kit sections, Teams an Adaptive Card, Google Chat a card, and ntfy/Pushover a push. Link previews are off, and titles are escaped so a title can never inject formatting or mentions.

What to expect

• Only delivered trends are sent. A run that finds nothing new sends nothing, so there is no "no new trends" spam. Rows the run could not deliver (for example because your spending limit was reached) are not sent.
• Without onlyNewSinceLastRun, every delivered row is sent, so a scheduled plain run would repeat the same trends: use alert mode for alerts (the message then says "New trend"; a plain run says "Trend").
• maxNotifications (default 25, max 100) caps how many trends go to chat and phone channels per run (the webhook is not capped). The rest are still in the dataset and the status message says so. ntfy and Pushover send at most 10 individual pushes, then one "...and N more" summary.
• Cost: notifications are free. You pay only the usual price for delivered trends, exactly as without alerts. There is no extra charge for any channel.
• Failures never fail the run. A deleted webhook or an unreachable service leaves the run successful and the dataset complete, and the status message says what happened, for example Notified: Discord 12, Slack 12, ntfy 10 (+summary). Teams failed (HTTP 404) - check the webhook URL. The logs show the channel name and HTTP status only, never a URL or token.
• Your URLs, tokens and ntfy topic are stored as secret inputs. Anyone holding a webhook URL can post to that channel, so treat it like a password.
• It is a monitor that notifies you. It never posts, logs in to anything or contacts anyone. The messages go only to the destinations you set up.
• Nothing changes by default. With no destination set, a run behaves exactly as before and the dataset rows are identical.

Input

{
  "countries": ["US"],
  "maxItems": 100,
  "includeNews": true,
  "onlyNewSinceLastRun": false,
  "stateStoreName": "google-trends-trending-now-seen"
}

Field	Type	Default	Description
countries	string[]	["US"]	Two-letter ISO 3166 country codes, e.g. US, GB, DE, IN. One feed per country, up to 50 per run. A country Google publishes no feed for is reported and skipped.
maxItems	integer	100	1-5,000. Hard cap on trends delivered across the whole run - your cost cap.
includeNews	boolean	true	Attach the news articles Google lists for each trend as a newsItems array. When false, newsItems is null. The price is the same either way.
onlyNewSinceLastRun	boolean	false	Alert mode - see above.
stateStoreName	string	google-trends-trending-now-seen	Name of the store that remembers what alert mode has already delivered. Change it only to isolate several Actor tasks or reset a watch.
discordWebhookUrl	string (secret)	(none)	Discord webhook URL. Must look like https://discord.com/api/webhooks/<id>/<token>. Empty means no Discord messages. See the alerts section above.
telegramBotToken	string (secret)	(none)	Telegram bot token from @BotFather. Needs telegramChatId.
telegramChatId	string	(none)	Telegram chat to post to: a numeric chat id or @channelusername. The bot must be added to that chat or channel. Needs telegramBotToken.
slackWebhookUrl	string (secret)	(none)	Slack incoming webhook, https://hooks.slack.com/services/....
slackCompatibleWebhookUrl	string (secret)	(none)	Mattermost / Rocket.Chat incoming webhook (public https:// URL; Markdown list, no Block Kit).
teamsWebhookUrl	string (secret)	(none)	Microsoft Teams Workflows webhook (host ending .logic.azure.com or .powerplatform.com).
googleChatWebhookUrl	string (secret)	(none)	Google Chat space webhook, https://chat.googleapis.com/v1/spaces/....
ntfyTopic	string (secret)	(none)	ntfy topic name; setting it turns ntfy phone pushes on. Pick a long, unguessable name.
ntfyServer	string	https://ntfy.sh	ntfy server. Only change it for your own public https:// ntfy server.
ntfyToken	string (secret)	(none)	Optional ntfy access token for a self-hosted server or protected topic. Needs ntfyTopic.
pushoverUserKey	string (secret)	(none)	Pushover user key. Needs pushoverAppToken.
pushoverAppToken	string (secret)	(none)	Pushover application API token. Needs pushoverUserKey.
webhookUrl	string (secret)	(none)	Generic JSON webhook (Zapier, Make, n8n, Pipedream, IFTTT, Home Assistant): every delivered row, 100 per POST. Public https:// only.
maxNotifications	integer	25	1–100. Most trends sent to chat and phone channels per run (the webhook is not capped). Extra trends are still in the dataset. Only used when a destination is set.

Output fields

Category	Fields
Identity	id, geo
Trend	title, approxTraffic, approxTrafficMin, pubDate
Media	pictureUrl, pictureSource
News	newsItems (array of title, url, source, picture)
Provenance	feedUrl

title is the trending search term. approxTraffic is the volume bucket exactly as Google publishes it (for example "500+"), and approxTrafficMin is that number as an integer - a lower bound, not an exact search count. pubDate is when the trend started, converted to UTC. Missing values are returned as null; nothing is invented.

Example output

A real row from the US "Trending now" feed (captured 2026-10-03):

{
  "id": "US-5dcd1495871c",
  "geo": "US",
  "title": "apple tv",
  "approxTraffic": "500+",
  "approxTrafficMin": 500,
  "pubDate": "2026-10-03T08:10:00.000Z",
  "pictureUrl": "https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcRRCylSSADVtJXRBmVHlK6xnd4BzGyDLCHGHcnTOiljNS_WkzqFG2qnaGUaTzU",
  "pictureSource": "The Economist",
  "newsItems": [
    {
      "title": "What to watch this week",
      "url": "https://www.economist.com/culture/2026/10/02/what-to-watch-this-week",
      "source": "The Economist",
      "picture": "https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcRRCylSSADVtJXRBmVHlK6xnd4BzGyDLCHGHcnTOiljNS_WkzqFG2qnaGUaTzU"
    },
    {
      "title": "What To Watch This Weekend: New Shows And Movies To Stream On Netflix, Hulu, Prime Video, Apple TV And More",
      "url": "https://www.forbes.com/sites/erikkain/2026/10/02/what-to-watch-this-weekend-new-shows-and-movies-to-stream-on-netflix-hulu-prime-video-apple-tv-and-more/",
      "source": "Forbes",
      "picture": "https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcS1PnTGGyNzKUGUeVAJTDjcTJdL9akdlRWxox2VULYcgiJ0lK7X5thHDecG_J8"
    }
  ],
  "feedUrl": "https://trends.google.com/trending/rss?geo=US"
}

(The real row lists a third news article; it is trimmed here for length.)

Use it as an API

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("lukehunter/google-trends-trending-now").call(
    run_input={
        "countries": ["US", "GB"],
        "maxItems": 50,
    }
)

for trend in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(trend["geo"], trend["title"], trend["approxTraffic"])

Pricing

Pay per delivered trend.

$0.001 per trend — 1,000 trends = $1.

Trends delivered	Cost
20	$0.02
1,000	$1.00
10,000	$10.00

There is no charge for starting a run, and no charge for a country whose feed is skipped, fails or is empty. maxItems gives you a hard upper bound on cost, and your run's maximum-cost setting is honoured: the Actor never delivers a trend your spending limit cannot pay for.

Notifications to Discord, Telegram, Slack, Teams, Google Chat, ntfy, Pushover and webhooks are free: you pay only for delivered trends, never for messages sent.

Limitations

• Trending now only. This is the current list from Google's Trending RSS feed - not Google Trends Explore, not interest over time, not related queries, and not a history. To build a history, run the Actor on a schedule.
• Small lists. Each country's feed currently holds about 10 trends (the four captured feeds each held exactly 10), so a run over one country returns about 10 rows. maxItems is a ceiling, not a promise of that many.
• Traffic is a bucket. approxTraffic is the rounded-down figure Google publishes ("200+", "50000+"), not an exact search count.
• Country codes. Pass two-letter country codes. A code for which Google publishes no feed is reported in the run status and costs nothing. Sub-country regions are not supported.
• Some fields are sometimes empty. A trend can have no picture, or no news articles; those fields come back as null or [].
• No login, no workarounds. If Google ever blocks a request or rate-limits it, this Actor reports that for the country and stops there; it does not rotate identities or evade blocks.
• This is an independent tool, not affiliated with, endorsed by, or connected to Google. You are responsible for using the collected data in accordance with Google's terms and applicable law.

Use it from your code, Make, Zapier or n8n

Built for automated pipelines: small runs, stable field names, one row per item, and you pay only for rows actually delivered.

One API call that runs the Actor and returns the data (replace $APIFY_TOKEN with your token from Apify Console → Settings → Integrations):

curl -s -X POST "https://api.apify.com/v2/acts/lukehunter~google-trends-trending-now/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"countries": ["US", "GB"], "maxItems": 20}'

JavaScript (npm i apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('lukehunter~google-trends-trending-now').call({
  "countries": [
    "US",
    "GB"
  ],
  "maxItems": 20
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python (pip install apify-client):

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('lukehunter~google-trends-trending-now').call(run_input={"countries": ["US", "GB"], "maxItems": 20})
items = client.dataset(run['defaultDatasetId']).list_items().items

Schedules, webhooks and no-code tools: save your input as a Task, add a Schedule (e.g. hourly or daily), and attach a webhook or one of the Integrations tab's connectors (Make, Zapier, n8n, Google Sheets, Slack) to push each run's results into your own system.

Only new items each run: set "onlyNewSinceLastRun": true on a scheduled Task and every run after the first delivers, and charges for, only items it hasn't delivered before for that same input. That makes it a ready-made change feed.

Reliability: an automated test runs this Actor's parser against the live site every day, and failures are fixed fast.

Feedback: an honest rating on the Store page, good or bad, helps others decide if this Actor fits their needs. Missing a field or found a problem? Open an issue on the Actor page.

FAQ

Is this the same as Google Trends Explore data?

No. It reads only the public "Trending now" RSS feed. Explore data (interest over time, related queries) is not included.

How often does the list change?

Through the day. Run it on a schedule with onlyNewSinceLastRun: true to capture each new trend once.

Why is approxTrafficMin a round number?

Google publishes a volume bucket such as "1000+", not an exact count. approxTrafficMin is that number as an integer.

Why do I get fewer rows than maxItems?

Each country's feed holds only about 10 trends. Add more countries to get more rows.

Which countries work?

Any two-letter country code for which Google publishes a Trending now feed. The US, GB, DE and IN feeds were verified when this Actor was built; if a code has no feed, the run status says so for that country and the others still run.

Do you collect personal data?

No. Rows contain only the trending search term, traffic bucket, timestamps, and the pictures and news article links Google publishes in the feed.

Can I get Google Trends alerts in Discord, Telegram, Slack or on my phone?

Yes. Set discordWebhookUrl, telegramBotToken + telegramChatId, slackWebhookUrl, teamsWebhookUrl or googleChatWebhookUrl, or use ntfyTopic (free, no account) or pushoverUserKey + pushoverAppToken for phone pushes. Mattermost and Rocket.Chat work through slackCompatibleWebhookUrl. With onlyNewSinceLastRun on and a schedule, each run sends only the trends it has not delivered before for each country. Setup steps for each are in the alerts section above. Notifications cost nothing extra.

Can I get Google Trends alerts by email?

Not natively. There are two routes. (1) Set webhookUrl to a Zapier, Make or n8n catch hook and add an email or Gmail step: the webhook delivers every row as JSON, so the email can list the trends. (2) Apify's own run integrations and run notifications can email you when a run finishes, but they only send a link to the run or dataset, not the trends themselves. For instant alerts without building anything, Telegram, ntfy or Pushover reach your phone directly.

Can I get Google Trends alerts in WhatsApp?

Not natively, and we do not use unofficial WhatsApp APIs, which risk getting your number banned. The official route is the WhatsApp Business Platform (Cloud API) with its own business account, message templates and pricing: point webhookUrl at a Zapier, Make or n8n flow that calls it. For free phone alerts use Telegram or ntfy instead.

More from this publisher

• Vinted Scraper & New Listing Alerts: Vinted search results with prices, brands, sizes and favourites, across any Vinted country, with a new-listing alert mode.
• Apple App Store Reviews Scraper: Apple App Store reviews for any iOS app, across countries, with rating, version and date.