How this tool works
Request thirty or sixty complete UTC calendar dates ending yesterday, using the legacy per-article endpoint’s inclusive date boundaries. The selected access and agent filters remain part of the result. Returned points retain their actual date spacing; missing dates are not filled with invented zeros. The table shows daily values and the chart joins returned points for visual comparison without predicting future traffic.
Returned-view total = sum of returned daily counts; average = total / number of returned datesA worked example
The demonstration has three returned daily counts: 100, 200 and 300. Their total is 600 and their mean over those returned dates is 200. It is explicitly partial within a thirty-day requested window. Last-versus-first change is 200%, which compares two endpoints rather than measuring a fitted trend.
Good to know
Pageviews under a stated request filter are not unique readers, edit counts, article quality or a forecast. All-agents can include automated traffic. Data publication can lag, and redirects or renamed articles can have separate historical series. A missing or partial response does not establish zero demand.
Reference: Official Wikimedia API documentation (opens in a new tab) ↗
A pageview count is not a count of unique people
One reader can generate several requests, and the agent filter changes which classes of requests are included. All-agents and user-classified traffic therefore answer different questions. The chosen filter is reported with the daily table rather than being hidden behind a generic popularity number.
The Wikipedia internal link grapher counts a bounded set of outgoing links, not attention. It cannot establish readership from the number or placement of graph nodes. Likewise, a pageview spike does not by itself establish article accuracy, importance or the reason people arrived.
Use complete UTC dates and retain missing-data information
The request ends yesterday so the current incomplete UTC day does not masquerade as a full day’s traffic. The legacy endpoint includes both date boundaries, making a thirty-date window start twenty-nine days before its final date. Requesting an extra endpoint would produce an off-by-one comparison.
If a date is absent from the response, the tool does not invent a zero. The displayed mean uses returned days and the result is marked partial. Endpoint percentage change also depends strongly on the chosen first day; it is not a fitted trend or a forecast. The Wikipedia category explorer supplies a separate organizational view that should not be confused with a time series of attention.
A few questions, answered
Are pageviews unique readers?
No. They are request counts under the selected access and agent filters.
Are missing days filled as zero?
No. Missing records remain missing and the response is marked partial.