Google Trends Scraper (orbots) - Apify Actor

io.github.orbotshqPublished by GitHub account orbotshqv0.1.20Updated Oct 24, 2026

Google Trends trending searches, volume estimates & trend duration. Not affiliated with Google LLC.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant pull Google Trends trending searches, search volumes and keyword interest data via the orbots scraper Actor.

What you can do
  • Retrieve trending searches for 100+ countries and sub-regions, with estimated search volume, rank and topic category
  • Filter trends by Google category and by active versus ended status, including how long each trend has run
  • Fetch interest over time and interest by region for keywords you supply
  • Return only trends not seen before per country and window, for scheduled runs
  • Get structured rows with term, geo, volume, timestamps, duration and a link to the term's Trends page
When to use it
Useful when you want an assistant to answer questions about what is trending in a market or region, compare keyword interest across geographies, or feed recurring trend reports without building your own scraping pipeline.
Requirements
A remote MCP endpoint at mcp.apify.com with OAuth authentication; an Apify API token sent in the Authorization header. The Actor runs on Apify and is billed pay-per-event in USD.
Before you install
The Apify token is a secret credential sent in the Authorization header. Runs are billed per event in USD, with a start fee plus a per-result fee, though runs returning zero rows are not charged. It is an independent tool, not affiliated with Google, and reads publicly available Google Trends data that may be throttled or incomplete.

Installation

In SourceWeft

  1. Open Google Trends Scraper (orbots) - Apify Actor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.orbotshq%2Fgoogle-trends-scraper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "google-trends-scraper-orbots-apify-actor": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=orbots/google-trends-scraper"
    }
  }
}

README

Google Trends Scraper - Trending Now, Search Volume & Trend Duration

Reliable Google Trends data on the Apify platform, billed pay-per-event in USD. Built and maintained by orbots.

Not affiliated with, endorsed by, or sponsored by Google LLC. "Google" and "Google Trends" are trademarks of Google LLC. This is an independent tool that reads publicly available Google Trends data; it is not an official Google product.

▶️ Run it on Apify: https://apify.com/orbots/google-trends-scraper


What it does

  • Trending searches for 100+ countries and sub-regions (e.g. US-CA, FR-75), with estimated search volume.
  • Active trends vs. ended, plus trend duration: how long each trend has been running.
  • Topic categories on every term (Google's own 19 categories), with an optional categories filter to keep only one vertical.
  • Interest over time and interest by region for keywords you provide.
  • Up to ~370 terms per run in large markets. No item cap.
  • A run that collects nothing is not charged at all.

Why this one

  • Reliability first. The official Google Trends source is flaky; this Actor is built to degrade gracefully. When part of a request is throttled, it returns the regions that responded and reports the ones that didn't, instead of failing the whole run.
  • Honest pricing. A small start fee plus a per-result fee that scales down with volume. A run that returns zero rows costs nothing.
  • Built for schedules. With onlyNew: true each run returns only the trends you have not received before, per country and window, so a daily schedule stops paying for the same list twice.
  • Agent-ready. Exposed to AI agents through Apify's MCP server; see the MCP page.

Output (shape)

Each row is one trend (trending mode) or one interest data point (keywords mode). Typical fields in trending mode:

fieldmeaning
typetrending_now (or interest_over_time / interest_by_region in keywords mode)
termthe trending query
rankposition in the feed (1 = hottest)
geocountry or sub-region code (e.g. US, US-CA, FR-75)
search_volume / formatted_volumeGoogle's estimated volume, as a number (200000) and as the label shown in the UI (200K+)
category / categoriesGoogle's topic category for the term
is_activewhether the trend is still running
started_at / ended_attrend window timestamps (ended_at is null while active)
duration_minuteshow long the trend lasted, once it has ended
trends_urldirect link to the term's Google Trends explore page

Quick start

Run from the Actor page, or call it via the Apify API and get the rows back in one request:

bash
curl -X POST "https://api.apify.com/v2/acts/orbots~google-trends-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \  -H "Content-Type: application/json" \  -d '{ "mode": "trending", "trendingGeos": ["US", "GB", "BR"], "trendingHours": 24 }'

Add "onlyNew": true for schedules, or "categories": ["Sports"] to keep one vertical. Full input options and examples are on the Actor page.

Support

Issues and feature requests: open an issue in this repository, or use the Issues tab on the Apify Actor page.


orbots builds small, reliable data Actors on Apify. Data is read from publicly available sources; see each Actor's page for details and terms.

Source: README.md at commit 2e69ffa

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.20LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Apify integrations