Google Trends Scraper & API — Daily Trending Searches
Pricing
Pay per event
Google Trends Scraper & API — Daily Trending Searches
Google Trends scraper and API for daily trending searches across 50+ geos with news context. RSS-backed, no browser/proxy overhead, CSV/JSON-ready for SEO, content, and AI-agent workflows. Guide: https://konabayev.com/tools/google-trends-tracker/
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tugelbay Konabayev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Share
Pull daily trending Google searches across US, GB, DE, RU, KZ, JP, BR, IN and 50+ markets with related news context — in one Apify run. This is a lightweight Google Trends scraper and API alternative for daily trends: RSS-backed, high-success, no Playwright, no proxy gymnastics, and ready for CSV/JSON export, content, SEO, and AI-agent workflows.
For implementation notes, examples, and SEO/GEO trend-monitoring workflows, see the Google Trends Tracker guide on Konabayev.com.
What it does
For each country code in your geos input, the actor fetches the day's top trending search queries plus the news articles Google associates with each trend (title, URL, publication source, snippet, picture). Results are pushed as structured records ready for analytics dashboards, CRM enrichment, content-planning workflows, or AI-agent ingestion.
Why this actor vs alternatives
| Feature | Apify rivals (rental, $30/mo) | Google Trends API alternative |
|---|---|---|
| Pricing | rental subscription | pay-per-result, $0.001 per trend |
| Reliability profile | browser/runtime dependent | RSS endpoint, no JS render |
| Geos per run | 1 | unlimited list |
| News context | partial | full structured newsItems[] |
| AI agent / MCP-native | no (rental) | yes (PPE) |
| Setup latency | minutes (Playwright cold-start) | seconds (RSS fetch) |
Input
{"geos": ["US", "GB", "DE", "RU"],"language": "en-US","maxItems": 100,"includeNewsItems": true}
| Field | Type | Default | Notes |
|---|---|---|---|
geos | string[] | ["US"] | ISO country codes; pass several for cross-market scans |
language | string | en-US | BCP-47 locale tag |
maxItems | int | 25 | Hard cap across all geos (1–1000); raise for production |
includeNewsItems | bool | true | Attach related news per trend |
Ready-to-run presets
Use these as production starting points instead of a random demo input.
Daily US content brief
{"geos": ["US"],"language": "en-US","maxItems": 25,"includeNewsItems": true}
Multi-market SEO watch
{"geos": ["US", "GB", "DE", "IN"],"language": "en-US","maxItems": 80,"includeNewsItems": true}
RU/KZ trend pulse
{"geos": ["RU", "KZ"],"language": "ru-RU","maxItems": 40,"includeNewsItems": true}
Output
{"query": "champions league final","geo": "GB","language": "en-GB","approxTraffic": "500K+","pubDate": "Mon, 5 May 2026 14:30 GMT","newsItems": [{"title": "Champions League Final Live: Real Madrid vs Borussia Dortmund","snippet": "Goals, lineups and live commentary from Wembley...","url": "https://www.bbc.co.uk/sport/football/...","source": "BBC Sport","pictureUrl": "https://t1.gstatic.com/..."}],"newsItemCount": 5,"trendUrl": "https://trends.google.com/trends/explore?q=champions+league+final&geo=GB"}
Use cases
- Content marketing teams — daily trend digest for newsroom briefs, blog ideation, social posting calendars
- SEO agencies — pair with
tugelbay/keyword-rank-trackerto spot rising queries before they hit search-volume tools - Investor / market intel — track what consumers are searching across markets in real time
- AI agents — give your assistant a "what's hot today" tool via PPE-billable Apify integration
- Cross-border arbitrage — see what's trending in market A that hasn't yet hit market B
Programmatic usage
Python
from apify_client import ApifyClientclient = ApifyClient("YOUR_TOKEN")run = client.actor("tugelbay/google-trends-tracker").call(run_input={"geos": ["US", "GB", "JP"],"maxItems": 50,})for trend in client.dataset(run["defaultDatasetId"]).iterate_items():print(trend["query"], "—", trend["approxTraffic"])
JavaScript
import { ApifyClient } from "apify-client";const client = new ApifyClient({ token: "YOUR_TOKEN" });const { defaultDatasetId } = await client.actor("tugelbay/google-trends-tracker").call({geos: ["US", "GB"],maxItems: 50,});const { items } = await client.dataset(defaultDatasetId).listItems();console.log(items);
LangChain tool
from langchain_core.tools import toolfrom apify_client import ApifyClient@tooldef whats_trending_now(country: str = "US") -> list[dict]:"""Return today's top Google searches in {country}."""client = ApifyClient("YOUR_TOKEN")run = client.actor("tugelbay/google-trends-tracker").call(run_input={"geos": [country], "maxItems": 20,})return list(client.dataset(run["defaultDatasetId"]).iterate_items())
Pricing (PPE)
| Event | Price |
|---|---|
| Actor start | $0.005 |
| Daily-trend record | $0.001 |
| News-item child | $0.0005 (when includeNewsItems=true) |
The actor charges these PPE events explicitly: actor-start once per run, daily-trend once per returned trend record, and news-item for each attached related news item.
A typical 50-trend run with news: ~$0.005 + 50×$0.001 + 250×$0.0005 ≈ $0.18 per run.
Cost vs alternatives
- Pulling 100 trends/day × 30 days from rental rivals: $30/mo flat
- Pulling the same here: 30 × ~$0.30 = $9/mo (70% saving) and you only pay for runs you actually use
FAQ
Q: How fresh are the trends? A: Google's RSS feed is updated hourly; this actor returns whatever Google has staged for the requested geo at fetch time.
Q: Do I need an Apify proxy? A: No. RSS endpoint is public.
Q: Can I run this on a schedule? A: Yes — use Apify Schedules to run hourly/daily and pipe results into your dataset of choice.
Q: Why is my geo returning empty? A: Some smaller markets have sparse trending data. Try a major market (US, GB, DE, FR, JP) to verify the actor is functioning, then narrow to your target.
Q: How does it differ from keyword-rank-tracker?
A: This finds what's trending; keyword-rank-tracker measures where you rank on a known keyword. Use both together — trends → rank check → optimize.
Limitations
- Google's RSS feed exposes only the top ~20 daily trends per geo — not the full long-tail trending list (that requires the Web UI behind their bot wall).
- Locale string must match Google's accepted set (e.g.
en-US, noten_US). - News-item arrays vary in length; some trends have 0 news items.
Changelog
- 0.1.0 (2026-05-05): Initial release — multi-geo, news-item enrichment, PPE pricing.