Google Trending Searches Scraper

Scrape country-level Google trending search topics with traffic estimates, trend timing, and related news context.

Data fields

FieldTypeDescription
geotextGeo exported in the dataset view.
titletextTrend exported in the dataset view.
approxTraffictextApprox. traffic exported in the dataset view.
pubDatedatePublished exported in the dataset view.
linklinkTrend link exported in the dataset view.
pictureimagePicture exported in the dataset view.
pictureSourcetextPicture source exported in the dataset view.
newsItemsobjectRelated news exported in the dataset view.

Input preview

geosGeo codes
maxItemsPerGeoMaximum trends per geo
includeNewsItemsInclude related news items

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

Track country-level Google trending search topics, traffic estimates, timing, and related news context in a clean Apify dataset.

At a glance

  • Input: Google Trends geo codes, per-geo topic cap, and related-news mode.
  • Output: Trending search topics with traffic estimates, timing, related queries, related news, image URLs, and source geo.
  • Best for: News monitoring, SEO research, editorial planning, social trend tracking, and market-intelligence dashboards.
  • Pricing unit: A start event per run plus one result event for each saved trending-search topic.
  • Login required: No. The Actor reads public Google trending search data only.

What can it do?

Google Trending Searches Scraper collects current trending search topics for one or more countries.

It returns structured rows that are ready for dashboards, alerts, spreadsheets, content calendars, and market monitoring workflows.

Each result can include the trend phrase, approximate traffic, publication time, image metadata, source traceability, and related news context.

Use it when you need recurring visibility into what people are searching for right now.

Who is it for?

SEO teams

Monitor country-level trend demand and discover timely keyword opportunities.

Publishers and editors

Find story ideas while a topic is still gaining public attention.

Content marketers

Plan fast-response posts, newsletters, videos, or social media updates around real demand.

Market researchers

Track attention spikes by country and compare which themes appear in different markets.

Automation builders

Feed trend data into Slack alerts, BI tools, Airtable bases, or internal scoring workflows.

Why use this actor?

  • โšก Fast HTTP collection for lightweight trend monitoring.
  • ๐ŸŒ Multi-country input so one run can cover several markets.
  • ๐Ÿ“ฐ Optional related news cards for context around each search topic.
  • ๐Ÿ“Š Consistent dataset fields for export and automation.
  • ๐Ÿ” Designed for scheduled runs and recurring trend watchlists.

Example input

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

Example output

{
  "geo": "US",
  "title": "example trend",
  "approxTraffic": "2000+",
  "pubDate": "Tue, 16 Jun 2026 19:30:00 -0700",
  "link": "https://trends.google.com/trending/rss?geo=US",
  "picture": "https://encrypted-tbn0.gstatic.com/images?...",
  "pictureSource": "Example Source",
  "newsItems": [
    {
      "title": "Related story title",
      "snippet": "Short context about the trend",
      "url": "https://example.com/story",
      "picture": "https://example.com/image.jpg",
      "source": "Example Publisher"
    }
  ],
  "sourceUrl": "https://trends.google.com/trending/rss?geo=US",
  "scrapedAt": "2026-06-17T00:00:00.000Z"
}

How to run it

  1. Open the actor on Apify.
  2. Add one or more geo codes.
  3. Choose the maximum number of trends per geo.
  4. Decide whether to include related news context.
  5. Click Start.
  6. Export the dataset as JSON, CSV, Excel, XML, or RSS.

Tips for best results

  • Use common country codes such as US, GB, CA, AU, IN, DE, FR, BR, and JP.
  • Keep maxItemsPerGeo modest for scheduled monitoring runs.
  • Enable related news items when you need editorial context.
  • Disable related news items when you only need a compact keyword watchlist.
  • Schedule the actor daily or hourly depending on how quickly your workflow reacts to trends.

Scheduling ideas

Run the actor every morning for a daily editorial planning report.

Run it every few hours for newsroom alerts.

Run it before campaign planning meetings to identify sudden audience interest.

Run separate tasks by region if different teams own different markets.

Integrations

Slack alerts

Connect the dataset to a Slack automation and post the top trends for selected countries.

Google Sheets

Export results to Sheets for editorial review, keyword tagging, and content planning.

Airtable

Store trend rows in Airtable and add custom workflow fields such as priority, owner, or status.

BI dashboards

Use the Apify API to feed trend data into Looker Studio, Power BI, Tableau, or internal dashboards.

Content calendars

Turn trend titles and related news snippets into draft calendar ideas for writers or social teams.

API usage with 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);

API usage with Python

from apify_client import ApifyClient
import os

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,
})

items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~google-trending-searches-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"geos":["US","GB"],"maxItemsPerGeo":10,"includeNewsItems":true}'

MCP and AI agents

Use this actor through Apify MCP from Claude or other MCP-compatible clients.

MCP endpoint:

https://mcp.apify.com/?tools=fetch_cat/google-trending-searches-scraper

Claude Code MCP setup

Use the Apify MCP endpoint as an HTTP transport:

claude mcp add apify-google-trending-searches --transport http "https://mcp.apify.com/?tools=fetch_cat/google-trending-searches-scraper"

Then ask:

Run Google Trending Searches Scraper for US and GB with 10 trends per country and summarize the biggest topics.

Claude Desktop MCP setup

Open Claude Desktop โ†’ Settings โ†’ Developer โ†’ Edit Config and add an HTTP MCP server entry:

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

Restart Claude Desktop, then use a prompt such as:

Collect today's trending searches for CA, AU, and IN. Group them by country and suggest newsletter angles.

Cursor MCP setup

Open Cursor โ†’ Settings โ†’ MCP โ†’ Add new global MCP server and use the same HTTP endpoint:

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

After saving, ask Cursor to run the tool for the countries and trend limit you need.

VS Code MCP setup

In VS Code with MCP support enabled, add this server to your MCP configuration:

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

Then start the server from the MCP panel and ask Copilot or your MCP client to collect trends.

Example prompts for MCP

Use example prompts like these after connecting the MCP server:

  • "Use the Apify Google Trending Searches Scraper MCP tool to find trending searches in the US and suggest 5 blog post ideas."
  • "Run the MCP tool for GB and AU, then compare overlapping search themes."
  • "Collect trends for DE, FR, and IT with the MCP tool and create a short market brief."
  • "Use Google Trending Searches Scraper through MCP to send me the top 10 US trends with related news sources."

Data quality notes

Traffic values are approximate labels provided by the source.

Trend availability varies by country and time.

Some trend items may have images or related news while others may not.

The actor keeps missing optional fields as null or empty arrays rather than inventing data.

Limits

The actor caps maxItemsPerGeo at 100 to keep runs predictable.

Unsupported or temporarily unavailable geo codes may produce no rows.

Country-level availability can change over time.

For broad monitoring, start with a few geos and expand after confirming the dataset matches your workflow.

Legality and responsible use

This actor collects publicly available trend information.

Use the data responsibly and respect applicable laws, platform terms, and privacy requirements.

Do not use the actor to infer sensitive personal information about individuals.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.

Summary

Google Trending Searches Scraper helps teams spot what audiences are searching for now.

It is built for recurring trend monitoring, editorial planning, SEO workflows, and lightweight market intelligence.

Common questions

Questions and answers reused from the canonical actor README.

Why did a geo return no results?

Check that the geo code is supported and try a common code such as US, GB, CA, AU, or IN.

Why are some news fields empty?

Related news cards are optional. Some trend topics only include the trend title and traffic context.

Why is traffic a string like 2000+?

The source provides approximate traffic labels, not exact numeric counts.