Google Trends Scraper — Pay Per Result

Reliable Google Trends data without the flaky runs people hit on the default Store scrapers. Two modes:

1. Trending searches — public RSS, multi-geo, cheap HTTP
2. Keyword interest — interest over time, related queries, optional regions

Store search keywords: Google Trends scraper · Google Trends API · trending searches · interest over time · related queries

---

Why this Actor

Pain on popular Trends scrapers	What we do
~70% success / silent empties	Retries + backoff; empty / no-data rows are not charged
Unclear pricing	Flat pay-per-result PPE
One geo at a time	Batch many country codes in one run
Browser-heavy cost	HTTP-only (no Playwright)

Public data only. No Google account. No ToS-evasion playbook.

---

Modes

Trending (mode: "trending")

Fetches Google Trending RSS for each geo.

Field	Description
recordType	trending
geo	Country code
title	Trending query
traffic / trafficValue	Approx traffic label + parsed int
url	Trends link when present
publishedAt	RSS pubDate
newsTitles	Related news headlines (up to 5)

Interest (mode: "interest")

Uses Google Trends explore + widget APIs (same public endpoints the web UI uses).

recordType	When
interest_over_time	Always (per keyword × time point)
related_query	If includeRelatedQueries (top + rising)
interest_by_region	If includeInterestByRegion

Keywords are compared in batches of up to 5 so values share one 0–100 scale.

---

Example input

{
  "mode": "trending",
  "geos": ["US", "GB", "DE"],
  "maxItemsPerGeo": 20
}

{
  "mode": "interest",
  "keywords": ["apify", "scrapy", "playwright"],
  "geos": ["US"],
  "timeRange": "today 12-m",
  "includeRelatedQueries": true,
  "includeInterestByRegion": false
}

---

Pricing

Pay-per-event: charged for each successful dataset row.

• Empty geos / missing widgets / hasData: false points → not charged
• Trending RSS is lightweight — best cost/reliability ratio
• Interest mode uses more requests; raise requestDelayMs or enable Apify Proxy if you see 429s

Exact $/1k is on the Store pricing tab (set to cover platform cost with margin).

---

Limitations (honest)

• Google rate-limits interest APIs; large keyword × geo matrices need throttling
• Traffic values on RSS are approximate buckets (500+), not exact volumes
• Interest values are relative 0–100 (Google’s normalization), not absolute search volume
• Sub-region resolution depends on the parent geo
• Public endpoints only — no private Google Ads / Keyword Planner data

---

Output tips

• Filter dataset by recordType
• Schedule trending mode hourly/daily for monitoring
• For competitor brand tracking, put 2–5 brands in one keywords array

Issues / feature requests: use the Actor Issues tab.