Google Trending Searches Scraper

Export current Google trending searches by country, including traffic estimates, publication times, images and optional related news. Google Trending Searches Scraper returns one dataset row per topic for editorial planning, keyword discovery and country comparisons—not historical interest-over-time charts or arbitrary keyword searches.

Quick start

1. Choose country codes such as US, GB or IN.
2. Set a small per-country limit and choose whether to include news.
3. Start the Actor, then open its dataset to export JSON, CSV or Excel.

{
  "geos": ["US", "GB"],
  "maxItemsPerGeo": 10,
  "includeNewsItems": true
}

This requests up to 10 available topics per country. A limit is a ceiling, not a promise that Google supplies that many topics. The Actor preserves the source order. It does not sort by traffic or calculate growth.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Google Trending Searches Data Studio Export
• Google Trending Searches Country Comparison
• Google Trending Searches US Daily Editorial

What you get

One row per available trending-search topic in a requested country, with its title, country feed and collection time. Source traffic labels, publication text, links and images may be null. Optional nested news objects provide article context when available rather than full article bodies or related search queries.

Who is it for?

• News editors reviewing current country topics and linked coverage before assigning stories.
• SEO and content researchers discovering timely phrases without treating traffic labels as keyword-volume measurements.
• Regional analysts grouping source-linked topic snapshots by country in their own reports.
• Data and automation teams passing bounded topic rows into their own briefs or notification workflows.

How you can use the data

• Prepare a US and UK editorial shortlist. Use the existing two-country input with a small per-country cap and news enabled. Keep geo, title, sourceUrl and available news URLs together before opening the coverage for editorial review.
• Review India as a separate current snapshot. Request country IN with a modest cap. Keep publication text and collection time distinct: this is what the feed currently exposes rather than a complete calendar-day record.
• Inspect the evidence behind a topic. Keep traffic labels as text rather than converting them into exact search counts. Review available nested news titles and URLs for context, without treating them as related search-query suggestions or sentiment analysis.
• Build a simpler downstream report. Disable news when only topic rows are needed, or retain JSON to preserve nested items. Group your exported rows by country and add any comparison or alert logic yourself. The Actor neither calculates growth nor remembers previously seen topics.

Input settings

All three settings are optional. Detailed validation and availability guidance is in the input form.

Setting	JSON key	Omitted-input default
Country codes	geos	["US"]
Maximum topics per country	maxItemsPerGeo	20
Include related news	includeNewsItems	true

The form's starting example uses US and GB with a limit of 10 per country. API calls that omit settings use the defaults above. No login or Google API key is required.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each saved row contains a country and trend title. Other source fields can be null. newsItems is omitted when disabled and can be an empty array when enabled.

Illustrative shape only—not an observed trend:

{
  "geo": "US",
  "title": "Example topic",
  "approxTraffic": "2000+",
  "pubDate": null,
  "link": null,
  "picture": null,
  "pictureSource": null,
  "newsItems": [],
  "sourceUrl": "https://trends.google.com/trending/rss?geo=US",
  "scrapedAt": "2026-10-24T12:00:00.000Z"
}

Field	Meaning
geo	Normalized country code for this row.
title	Trending search phrase.
approxTraffic	Source traffic label, such as 2000+. Not an exact numeric count.
pubDate	Source publication date text, when supplied.
link	Source-provided trend link, when supplied.
picture, pictureSource	Available image URL and credit.
newsItems	Optional array of news objects with title, snippet, url, picture and source. Individual values can be null.
sourceUrl	Country feed used for the row.
scrapedAt	UTC collection timestamp.

Related news is not a list of related search queries. Article bodies, sentiment, growth percentages, category filters and historical charts are not included.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges one start event when collection begins after input validation and one result event for each saved trending-search topic. Nested news items are part of the topic row rather than separate results.

See the live Pricing tab for current rates and applicable discounts.

Tips for best results

• Choose a few countries and a small per-country cap first. Supported inputs allow one to one hundred normalized countries and one to one hundred topics per country.
• Keep source traffic labels as supplied. They are estimates rather than exact numeric keyword volumes.
• Check country outcomes before comparing markets. One country can fail while other countries supply usable rows.
• Use JSON when related news matters. Nested items can be empty even when enabled, and the field is omitted when disabled.
• Read source and collection dates separately. Feed freshness and current availability do not establish a complete day's trends.

Limits and caveats

Country availability, feed freshness and topic counts depend on Google. Raising a cap does not extend the available feed. Source order is retained without traffic sorting or calculated growth. Current country snapshots are not full calendar-day archives or historical interest-over-time charts, and arbitrary keyword search is not supported.

Optional traffic labels, dates, links and image fields can be null. Related news can be empty and contains no full article bodies. It is not a list of related searches. Sentiment, growth percentages, category filters and historical charts are not included.

An isolated country failure can leave useful rows from other countries. Check platform status and RUN_SUMMARY for outcomes and unfinished countries. The current implementation can fail if all countries return no usable topics, so an empty dataset is not a complete market report.

Country comparisons, editorial briefs and notifications require your own downstream analysis or integration. The Actor does not send alerts or remember seen topics. No Google login or API key is required, and FetchCat is not affiliated with Google.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~google-trending-searches-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "geos": [
    "US",
    "GB"
  ],
  "maxItemsPerGeo": 10,
  "includeNewsItems": true
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-trending-searches-scraper').call({
  "geos": [
    "US",
    "GB"
  ],
  "maxItemsPerGeo": 10,
  "includeNewsItems": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/google-trending-searches-scraper').call(run_input={'geos': ['US', 'GB'], 'maxItemsPerGeo': 10, 'includeNewsItems': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Google Trending Searches Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Google Trending Searches Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/google-trending-searches-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Google Trending Searches Scraper by Fetch Cat, or give it the identifier fetch_cat/google-trending-searches-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Google Trending Searches Scraper to collect up to 5 current topics each for the US and Great Britain with related news enabled. Keep countries, traffic labels and news source links for an editorial review.”
• “Collect up to 5 current trending-search topics for India with related news off. Show source feed URLs and collection times without describing the export as a complete day's archive.”
• “Retrieve up to 3 current topics each for the US and Great Britain with related news enabled. Group the returned rows by country and flag failed or unfinished markets without calculating growth or exact search volumes.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I get today's Google trending searches for India or the UK?

Use geos: ["IN"] for India or geos: ["GB"] for the UK. Results are the current available country snapshot, not a complete calendar-day archive. Availability can change.

Is this a Google Trends API alternative for keyword history?

It provides an Apify API for current country-level trending searches. It does not accept arbitrary keywords or return historical interest-over-time charts.

Can I export Google trending searches to CSV or Excel?

Yes. Open the run's dataset and choose the export format, or use the API to retrieve JSON. Nested newsItems are easiest to preserve in JSON. Disable them for a simpler report.

Why are news or traffic values missing?

Google does not supply every optional value for every topic. Missing values remain null, and news can be empty. Turning off includeNewsItems omits that field entirely.

Related Actors

• Google News Scraper — Collect news results for a broader news-research workflow.
• Google Autocomplete Scraper — Discover query suggestions rather than current trending topics.
• Google Trends Scraper — Collect current country-level Trending Now topics, traffic labels and available related news, without historical keyword-interest data.
• Google Images Scraper — Find images for a separate visual-research workflow.
• Google Scholar Profiles Scraper — Collect scholarly profile data for research-oriented projects.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥