Google Trends Daily – Real-Time Trending Keyword Scraper
Pricing
$0.80 / 1,000 results
Google Trends Daily – Real-Time Trending Keyword Scraper
Google Trends Daily delivers real‑time trending searches directly from Google’s ‘Trending Now’ feed. Behind the scenes it drives Playwright headless Chromium, intercepts the internal i0OFE RPC, clean the payload, and ships structured metrics (traffic value, popularity score etc)
Pricing
$0.80 / 1,000 results
Rating
0.0
(0)
Developer

VMovies - Global
Actor stats
0
Bookmarked
6
Total users
4
Monthly active users
3 days ago
Last modified
Categories
Share
Google Trends Daily Trending Scraper
Turn Google’s hottest searches into instant insights. This premium Apify actor automates the official Google Trends “Trending Now” feed, parses the raw i0OFE RPC payload, and delivers clean, analytics-ready data in seconds.
What You Get
🔥 Live market pulse
Capture the exact trending searches your customers are typing today. No outdated CSVs, no broken unofficial APIs—this is the real feed the Google UI consumes.
📈 KPI-ready metrics
Every record ships with traffic volume, Google’s popularity score, related query ideas, category identifiers, and precise timestamps so you can drop the data straight into dashboards, alerts, or growth experiments.
🛡️ Built for scale
Powered by Playwright with Apify Proxy integration out of the box. The Docker image bundles Chromium and XVFB, so the actor is production-ready the second you add it to your account.
Input Options
| Field | Type | Default | Description |
|---|---|---|---|
geo | string | "US" | Two-letter Google Trends region code. Swap to any country or market you track. |
language | string | "en-US" | Interface locale for the Trends UI. |
timezone | integer | 0 | Informational UTC offset (minutes). |
date | string | — | Reserved for future historical coverage. Leave blank for the freshest feed. |
maxResults | integer | 0 | Cap the number of rows stored (0 = full feed). |
useProxy | boolean | true | Toggle Apify Proxy. Keep enabled for reliable production scraping; disable when testing locally without proxy credentials. |
Output Snapshot
Each dataset item is normalized and ready for BI tooling:
{"query": "lakers vs thunder","displayQuery": "lakers vs thunder","geo": "US","trafficValue": 200000,"score": 1000,"relatedQueries": ["lakers vs thunder", "okc vs lakers", "sga"],"categories": [17],"articleTokens": [4271349414, 4283335722, ...],"timestamp": "2025-11-12T23:00:00.000Z","date": "2025-11-12"}
How to Run
- Deploy – Click Add to console on Apify (or run
npx apify pushif you’re managing privately). - Configure – Provide your target
geo, adjustmaxResults, and keepuseProxyenabled for production. - Launch – Start a run in Apify Console or via API:
npx apify call <actor-id> --input '{"geo":"GB"}'. - Consume – Download the dataset as JSON, CSV, XLSX, or feed it directly into your automation stack.
Best Practices
- Leave
useProxyenabled when running on Apify’s cloud to avoid rate limits. - Monitor the run log—if Google adjusts the underlying payload structure, the actor will log parsing warnings so you can update fast.
- Need keyword-specific analytics or historical dates? Reach out—custom payload support can be added on demand.
Ready to convert trending searches into actionable intelligence? Launch the actor and start capturing the pulse of your market today. 🚀