Cross-Platform Trends
Pricing
$5.00 / 1,000 topics
See what's trending on Google right now and whether the same topic is also spiking on Wikipedia, Bluesky and YouTube, with real view and post counts.
Pricing
$5.00 / 1,000 topics
Rating
0.0
(0)
Developer
Stephen Sievertsen
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
Two-letter country codes, e.g. US, GB, DE, BR, or ALL for ~60 countries (a full scan: with Minimum platforms set to 1 that's hundreds of trends per run). Used for Google trends, the matching Wikipedia language edition and the YouTube chart.
[ "US"]Which platforms to check. Pick any mix, e.g. only Bluesky + Wikipedia. All are free; YouTube also needs your API key below. Polymarket doesn't count as a platform: it adds the betting odds and dollars bet to topics that have a big prediction market.
[ "google", "wikipedia", "bluesky", "youtube", "polymarket"]Only save topics trending on all of these, e.g. Google, to get Google trends confirmed elsewhere. Leave empty for no requirement.
[]Your own free YouTube Data API v3 key, from Google Cloud Console. Adds matching videos from each country's 'most popular' chart. Uses 1 unit of the 10,000 free daily units per country per run. Without a key, YouTube is skipped.
Only save topics mentioning at least one of these, e.g. a brand, team or person ('Nike', 'Taylor Swift'). The topic, headline, Wikipedia article and matched video titles are searched. Leave empty for all topics.
Also save topics trending on Bluesky or spiking on Wikipedia that aren't in your countries' Google lists (country 'GLOBAL'). These are also checked against the Google lists of all major English-speaking countries. Always on when Google isn't a source.
Only save topics trending on at least this many platforms. 2 (the default) keeps confirmed, cross-platform trends only. Set to 1 to get every trend from every platform (many more rows, each charged). Lowered automatically if you pick fewer sources.
Save only topics not seen in earlier runs. Good for scheduled alerts.
Stop after this many topics (highest platform count first). Leave empty for all.
Name of the storage that remembers topics between runs. Use a different name for each schedule that should track separately.