Wikipedia Trending rank_change climbers via get_top_trends

Wikipedia Trending rank_change on Trends MCP is get_top_trends with type Wikipedia Trending, sort rank_change, and a window such as 1d. From the August 26, 2026 pull, the board stamped 2026-08-26T14:01:28 UTC. The 1d window used baseline 2026-08-25T02:01:58 UTC and returned count 28. The largest climb was a File: SVG traffic-sign page at rank 66, prev_rank 174, rank_change 108. Donald Trump sat at rank 55, prev_rank 117, rank_change 62. The 30d window still returned count 23. Same-stamp Google Trends 30d returned count 0. Free tier access is 100 requests per month.

What Wikipedia rank_change data shows right now

From the Trends MCP scan of August 26, 2026, Wikipedia Trending sort rank_change stamped 2026-08-26T14:01:28 UTC and filled 28 climber rows on window 1d, 28 on 3d, 29 on 7d, 26 on 14d, and 23 on 30d, so a default sort rank pull at limit 25 never lists these mover fields.

Shared as_of 2026-08-26T14:01:28 UTC:

Wikipedia Trending 1d climbers (first 12 of 28):

Default sort rank on the same stamp filled 200 article titles (50+50+50+50, offset 200 empty). Rank 1 was Dolly Parton. Rank 3 was Deaths in 2026 (1d rank_change 2). Rank 4 was Shelley Fabares (1d rank_change 2). Dolly Parton was not a 1d climber; the title already sat at rank 1.

How to call sort rank_change on Wikipedia Trending

Wikipedia climbers are the same get_top_trends tool as the live rank board, with sort set to rank_change and window set to 1d, 3d, 7d, 14d, or 30d, and each window is a separate request billed per feed type and page.

{"mode": "get_top_trends", "type": "Wikipedia Trending", "sort": "rank_change", "window": "1d", "limit": 50}
{"mode": "get_top_trends", "type": "Wikipedia Trending", "limit": 50, "offset": 0}

The first call returns objects. The second returns [rank, title] arrays. Default sort is rank. Default window for rank_change is 30d. On this stamp the 1d baseline was 2026-08-25T02:01:58 UTC, about 36 hours before the 14:01 scan, not a rolling 24 hours. The Google Trends rank_change API page uses the same fields on a different type. Live Wikipedia ranks without mover fields are on the Wikipedia Trending API page. Offset and limit are documented on get_top_trends pagination.

wikipedia get_growth is a different tool. It wants an article title, not a live-board type. 7D on wikipedia often returns collapsed_range because points are monthly through 2026-07-01.

Window counts from 1d through 30d

Wikipedia Trending kept returning climbers on every window through 30d, while same-stamp Google Trends 30d returned count 0 and a note that everything held or fell, so a client that copies a Google 30d empty result onto Wikipedia will skip 23 real mover rows.

ChatGPT appeared on four Wikipedia windows: 1d +27 to rank 22, 3d +2, 7d +33 from prev_rank 55, 30d +27 from prev_rank 49. Donald Trump appeared on 1d (+62), 3d (+46), 7d (+78), 14d (+56), and 30d (+86 to rank 55 from 141). Toxic (2026 film) led 7d at +157 from prev_rank 171 to rank 14, then only +9 on 14d from prev_rank 23.

JSON-LD at rank 103, Microdata (HTML) at rank 105, and RDFa at rank 108 climbed together: 1d +19, +23, +22; 30d +83, +84, +85 from prev_ranks 186, 189, 193. Those three markup articles moved as a cluster, not as unrelated news pages.

Same-stamp climber counts on other feeds

The 1d window used one baseline timestamp across Wikipedia Trending, Google Trends, TikTok Trending Searches, and YouTube Trending, and the climber counts on this stamp still diverged from 30 down to 2, so window support does not mean window fill is equal.

Same 1d baseline 2026-08-25T02:01:58 UTC, as_of 2026-08-26T14:01:28 UTC:

Google Trends 1d also listed a second jake lang object at rank 41, prev_rank 44, rank_change 3. Duplicate keyword objects on the same rank showed up on the earlier Google rank_change page as well. YouTube Trending 1d returned only Heaven Baby and Jarahn - Lamasaga (rank 10, prev 13, +3). TikTok Trending Searches 1d filled 15 rows at limit 25, so that board was short of the limit rather than truncated by it.

App Store Top Free on the same stamp listed ChatGPT at rank 1. Wikipedia Trending listed ChatGPT at rank 22 with 1d rank_change 27. Those are different objects: an iOS chart versus a Wikipedia article.

What get_growth returns on climber titles

get_growth does not read rank_change rows, so the follow-up is a keyword lookup, and on this stamp ChatGPT held a high google search index while Shelley Fabares sat at Wikipedia rank 4 and Google Trends rank 8 with google search 0.0.

Shared google search recent_date 2026-08-22 unless noted:

ChatGPT wikipedia 7D returned collapsed_range. ChatGPT wikipedia 30D sat at 47.5 / 6,574 views on 2026-07-01, up 41.79% from 33.5 / 4,632. List of S&P 500 companies wikipedia returned no_data despite Wikipedia Trending rank 45 and 1d rank_change 55. A live rank is not a guarantee that get_growth has a series.

Where Wikipedia climber rows go wrong

rank_change on Wikipedia Trending includes File: pages, markup-spec articles, and current-events lists next to film titles, so the largest 1d climb on this stamp was not a news story, and a client that takes row 1 as the day's story will misread the board.

The 1d leader was File:Traffic Sign GR - KOK 2009 - R-54.svg at +108. The 30d leader was File:WNBA logo.svg at +105. File:WhatsApp.svg sat at rank 56 with 7d rank_change 29. JSON-LD, RDFa, and Microdata (HTML) climbed as a group into ranks 103-108. Deaths in 2026 at rank 3 only moved +2 on 1d. Dolly Parton at rank 1 did not appear on the 1d climber list.

wikipedia get_growth 7D often collapses. Exact titles such as Toxic (2026 film), Shelley Fabares, JSON-LD, and List of S&P 500 companies returned no_data on wikipedia even while sitting on the live board. Quote the live rank plus whatever get_growth actually returned. Free covers 100 requests per month. Starter is $19 for 1,000. Check current pricing before locking a production budget.