Google Trends Scraper (orbots) - Apify Actor
RemoteAbout Google Trends Scraper (orbots) - Apify Actor
An Apify Actor for collecting Google Trends data for trend analysis and monitoring. It returns trending searches and estimated volumes across countries and sub-regions, tracks trend duration, and can retrieve interest over time or by region for supplied keywords.
Key features
- 01Collects trends across 100+ countries and regions
- 02Includes estimated volume and trend duration
- 03Filters by Google topic category
- 04Retrieves keyword interest over time and by region
- 05Can return only previously unseen trends
Use cases
- 01Track trending searches by location
- 02Collect newly emerging trends on a schedule
- 03Analyze keyword interest over time
- 04Compare keyword interest across regions
MCP support
The Actor is available to AI agents through Apify's MCP server.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.apify.com/?tools=orbots/google-trends-scraperclaude mcp add --transport http orbotshq-google-trends-scraper https://mcp.apify.com/?tools=orbots/google-trends-scraper{"mcpServers":{"orbotshq-google-trends-scraper":{"type":"http","url":"https://mcp.apify.com/?tools=orbots/google-trends-scraper"}}}Open in Cursor{"servers":{"orbotshq-google-trends-scraper":{"type":"http","url":"https://mcp.apify.com/?tools=orbots/google-trends-scraper"}}}Open in VS Code{"mcpServers":{"orbotshq-google-trends-scraper":{"type":"http","url":"https://mcp.apify.com/?tools=orbots/google-trends-scraper"}}}{"mcpServers":{"orbotshq-google-trends-scraper":{"serverUrl":"https://mcp.apify.com/?tools=orbots/google-trends-scraper"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp.apify.com/?tools=orbots/google-trends-scraperAuth requiredTools
Details
From the project READMEGoogle 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
categoriesfilter 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: trueeach 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:
| field | meaning |
|---|---|
type | trending_now (or interest_over_time / interest_by_region in keywords mode) |
term | the trending query |
rank | position in the feed (1 = hottest) |
geo | country or sub-region code (e.g. US, US-CA, FR-75) |
search_volume / formatted_volume | Google's estimated volume, as a number (200000) and as the label shown in the UI (200K+) |
category / categories | Google's topic category for the term |
is_active | whether the trend is still running |
started_at / ended_at | trend window timestamps (ended_at is null while active) |
duration_minutes | how long the trend lasted, once it has ended |
trends_url | direct 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:
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.