Trend Signals: Google Trends Alternative (Wikipedia Views) avatar

Trend Signals: Google Trends Alternative (Wikipedia Views)

Pricing

Pay per event

Go to Apify Store
Trend Signals: Google Trends Alternative (Wikipedia Views)

Trend Signals: Google Trends Alternative (Wikipedia Views)

Reliable trend data without Google Trends blocks: daily Wikipedia pageviews for any keyword or article (official Wikimedia API), % change, spike detection and alerts, plus Google trending searches by country. $0.001 per keyword series, $0.0005 per trending item.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Kempt Horizon Data

Kempt Horizon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 hours ago

Last modified

Categories

Share

Trend Signals: A Reliable Google Trends Alternative (Wikipedia Pageviews + Trending Searches)

Google Trends scrapers break all the time: rate limits, 429 errors, CAPTCHAs and relative 0–100 numbers. Trend Signals gives you real daily interest numbers that don't get blocked: Wikipedia pageviews for any keyword or article (the official Wikimedia REST API, data back to 2015, 300+ languages), with % change, spike detection and spike alerts, plus Google's trending searches by country from the public trending RSS feed. Schedule it daily and get alerted when interest in your topic, brand, ticker or competitor jumps.

For AI agents (MCP / API) quick reference

  • Use when: you need a daily public-interest time series for a topic, company, person or product; you want to detect spikes in attention; or you want today's trending searches in a country.
  • Don't use for: exact Google search volumes or Google Trends 0–100 index values. Pageviews are a proxy for interest, not search counts.
  • Minimal input: {"keywords": ["nvidia"], "days": 30} or {"countries": ["US"], "maxTrendingPerCountry": 10}.
  • Output: items by type:
    • keyword-series: keyword, article, days[] (date, views, zScore, spike), totalViews, avgDailyViews, latestViews, changePercent7d, changePercentFirstToLast, spikeDays, latestIsSpike
    • trending-item: term, country, approxTraffic, startedAt, news[]
    • spike-alert: keyword, article, date, views, zScore, reason
  • Price: $0.001 per keyword series, $0.0005 per trending item, $0.005 per spike alert. No start fee. Pay per event only, limited permissions, so agentic payments (x402, Skyfire, Apify AGI token) work.
  • MCP: add https://mcp.apify.com?tools=kempt_horizon_yzk/trend-signals to your MCP client.

What can it do?

  • ✅ Daily pageviews for keywords (auto-matched to the best Wikipedia article) or exact article titles, in any Wikipedia language
  • ✅ Any date range from July 2015 to yesterday
  • ✅ % change over the last 7 days vs the 7 before, and first-to-last
  • ✅ Spike detection per day (z-score vs the previous 28 days plus a ratio-to-median check), with tunable thresholds
  • ✅ Spike alerts for the latest day; monitor mode alerts each spike once
  • ✅ Trending searches by country, with approximate search traffic and related news links, and an option for only new terms

Who uses it?

Marketers and content teams spotting rising topics, traders watching attention on tickers and crypto, PR teams tracking brand spikes, researchers and journalists, and AI agents that need a dependable trend signal.

How much does it cost?

EventPrice
Keyword series$0.001
Trending item$0.0005
Spike alert$0.005

A daily watch on 50 keywords plus 20 US trending terms costs about $0.06 a day.

Input example

{
"keywords": ["nvidia", "bitcoin", "ozempic"],
"articles": ["Taylor_Swift"],
"wikiLanguage": "en",
"days": 90,
"countries": ["US", "GB"],
"maxTrendingPerCountry": 10,
"alertOnSpikes": true,
"onlyNew": true,
"onlyNewTrending": true,
"stateKey": "daily-trend-watch"
}

Output example

[
{
"type": "keyword-series",
"keyword": "nvidia",
"article": "Nvidia",
"project": "en.wikipedia.org",
"articleUrl": "https://en.wikipedia.org/wiki/Nvidia",
"dateFrom": "2026-09-15",
"dateTo": "2026-10-14",
"days": [
{
"date": "2026-10-12",
"views": 4968,
"zScore": -0.7,
"spike": false
},
{
"date": "2026-10-13",
"views": 5153,
"zScore": -0.5,
"spike": false
},
{
"date": "2026-10-14",
"views": 5297,
"zScore": -0.3,
"spike": false
}
],
"totalViews": 166222,
"avgDailyViews": 5541,
"latestViews": 5297,
"changePercentFirstToLast": -20.5,
"changePercent7d": 5.2,
"spikeDays": [],
"latestIsSpike": false,
"scrapedAt": "2026-10-15T14:10:29.676Z"
},
{
"type": "trending-item",
"term": "nasdaq",
"country": "US",
"approxTraffic": "2000+",
"approxTrafficNumber": 2000,
"startedAt": "2026-10-15T13:50:00.000Z",
"news": [
{
"title": "Global tech sell-off deepens as enthusiasm for AI stocks wobbles",
"url": "https://www.cnn.com/2026/10/15/business/tech-selloff-nasdaq-ai-intl",
"source": "CNN"
}
],
"source": "Google Trends trending searches RSS",
"scrapedAt": "2026-10-15T14:10:29.998Z"
}
]

Data sources

  • Wikimedia REST API (pageviews, user agents only, all platforms). Wikimedia data is free to reuse; requests carry an identifying User-Agent as Wikimedia asks.
  • Google Trends trending searches RSS (trends.google.com/trending/rss, allowed by robots.txt). The Actor does not touch Google Trends Explore pages, which robots.txt disallows.

FAQ

Why Wikipedia pageviews? They are published officially every day, give absolute numbers, cover every language, and never block you. They track public interest closely.

Why is today missing? Wikimedia publishes each day's pageviews the next day.

Built and maintained by Kempt Horizon Data. Found a bug or need a field? Open an issue on the Actor's Issues tab and we usually reply within a day. Not affiliated with Google or the Wikimedia Foundation.