Welcome to the Pageviews Analysis feedback forum

This is the forum to provide feature requests, bug reports, and general feedback for the Pageviews Analysis suite of tools.

Some key notes when making a post:

Click here to start a new discussion

Hello. Thanks to those who developed this tool, it's extremely useful.

I'm wondering, would it be possible to add a "Past year" option re: date range? As in, the last 365 days? The current "Last year" option instead does the whole year prior to the current year (e.g., all of 2025 if the current year is 2026). A last 365 days option would be really helpful for my use, especially for links. Even if only added/accessible in the URL params, that would be really helpful still.

Another thing—there seem to be some issues on mobile, for instance difficulty/impossibility of selecting a date range. I hope it's possible for that to be fixed at some point.

Thank you! – AlyInWikiWonderland (talk) 23:56, 7 March 2026 (UTC)Reply

I too would like to see more of these buttons. At least change the default view of 20 days to 90 days. Aloysius Jr (talk) 11:21, 12 March 2026 (UTC)Reply
This isn't hard to do so I will try to look into it. Thanks for the feedback, MusikAnimal (WMF) (talk) 22:57, 12 March 2026 (UTC)Reply
Actually, as it turns out, I think it may already work via URL params—"latest-365" for the "range" param. No UI option, but still viable and handy. – AlyInWikiWonderland (talk) 04:07, 13 March 2026 (UTC)Reply
Yes! :) I should have mentioned that. See also the URL structure documentation, accessible via the "Help" menu for each tool in the suite.
You could add a link on your userpage to show the last year's worth of data, for example, with something like:
[https://pageviews.toolforge.org/?project=en.wikipedia.org&pages={{FULLPAGENAMEE}}&range=latest-365 Past year's pageviews for this page]
The UI options are of course easy to add, too. With the widget we're using now, there's exactly just enough room to add a "Past year" option, so I'll do it :)
The default of 20 days was from the original demo app by the Data Engineering team. I don't know why it was chosen or why I kept it that way, to be honest… How about changing it to the past 30 days? A small data sample I think is best for demonstration purposes when first loading the page. 30 days would presumably still look decent enough on smaller devices but give the more meaningful metric of roughly one month's worth of data. MusikAnimal (WMF) (talk) 04:23, 13 March 2026 (UTC)Reply
The default is now 30! Thank you. Aloysius Jr (talk) 12:15, 17 March 2026 (UTC)Reply
That's great, thank you! – AlyInWikiWonderland (talk) 00:20, 18 March 2026 (UTC)Reply
  • Please provide a link to the results that are breaking for you.
  • Please explain what is broken.
    • Ultimately, the search returns no results at all: Totals: 0 pages, 0 pageviews, 0 daily average. This is for a PagePile with 9,471 pages in it. As the search progresses, there are a lot of orange "Error querying Pageviews API - Unknown" errors
  • Please say what browser you're using
  • What operating system and version are you using?

I have noticed this behaviour over the past few days - there are a lot of orange "Error querying Pageviews API - Unknown" as a search continues, and I only get Massviews statistics for a small subset of a large PagePile. Today the subset is zero. Thanks for your help! Cheers, SunloungerFrog (talk) 12:40, 12 March 2026 (UTC)Reply

Most of the "Error querying Pageviews API" errors are due to phab:T219857. It used to work perfectly but hasn't in quite some time. It's annoying, but one workaround is to just keep refreshing until eventually it will process all pages. I see in this case that doesn't work either, though. I have been meaning to add some retry logic in the tool to get around this, but I don't know for certain if that'd actually fix it or not, and it's also a considerable amount of work. I'll comment on phab:T219857 and see what can be done. Apologies for the inconvenience! MusikAnimal (WMF) (talk) 22:57, 12 March 2026 (UTC)Reply
@MusikAnimal (WMF), thanks for the response. That makes sense, annoying as it is. I've subscribed to the ticket. Thank you in advance for anything you are able to do to get Massviews working again, even if it means it runs slower. Cheers, SunloungerFrog (talk) 00:31, 13 March 2026 (UTC)Reply
Just to follow up - I tried some Massviews against some Pagepiles again this morning. The first one, a batch of ~600, worked fine. The second, a batch of ~1,900, worked fine for about the first 1,000 pages, then the orange "Error querying Pageviews API - Unknown" errors started appearing. I then waited for a bit and ran the first batch again, and got the orange errors immediately, ultimately returning no results, so I suspect my browser/IP address combo (or however "client" is defined) got blocked. It is annoying that https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/documentation/access-policy.html#rate-limits is so vague - clearly there are some explicit rate limits, because otherwise how does the block get triggered, and it would be nice to know those up front. Cheers, SunloungerFrog (talk) 06:42, 13 March 2026 (UTC)Reply
@MusikAnimal (WMF):. Above you only mention Pagepiles with a lot of pages. But recently Massviews Analysis for Categories only returns an error message like "An unknown error occurred when querying Category:Brazilian female single skaters" for all categories, the category in the example just contains three articles. The Massviews Analysis worked fine earlier this week for categories with several hundred articles, but since this morning the only result I get is the mentioned error message. Larske (talk) 15:04, 13 March 2026 (UTC)Reply
That's exactly what I also get. Every time, for each Category, the same error today Pschemmo (talk) 15:13, 13 March 2026 (UTC)Reply
It's all the same issue. They changed the API limits, apparently. I'll make it a priority to get a fix in. Thanks for your patience, MusikAnimal (WMF) (talk) 06:05, 14 March 2026 (UTC)Reply
Hey, thank you, I'm also getting the same error. I find this tool really useful on what cleaning to prioritise, and i'm sure many other editors do too, Tpbradbury (talk) 14:37, 16 March 2026 (UTC)Reply
The category search tool is so awesome for casual research, hope it is back up soon. Thanks for the work that you put in! OaklandJohn (talk) 16:56, 16 March 2026 (UTC)Reply
From phab:T219857, it transpires that mw:Wikimedia APIs/Rate limits has just gone into effect. I am slightly heartened to see that Requests from Toolforge or WMCS using a User-Agent as the user identity should allow a very high rate of requests, so maybe it is a matter of making Pageviews et al. authenticated against a Wikimedia user account rather than anonymous as it is at the moment? I would certainly not be fussed at having to authenticate. Cheers, SunloungerFrog (talk) 16:20, 16 March 2026 (UTC)Reply
I've long wanted to move some pageview processing to server-side (for phab:T157830 specifically), but in most cases this does more harm than good because it will overwhelm the server. I think our best bet is to refine the clientside logic to not go too fast. After I've got that working, I may look into server-side solutions. MusikAnimal (WMF) (talk) 18:45, 16 March 2026 (UTC)Reply
@SunloungerFrog I'm not sure that means it needs authenticate against a Wikipedia user account, I read it as it just that it has to be on WMCS and comply with the Foundation:Policy:Wikimedia Foundation User-Agent Policy. -- Ahecht (TALK
PAGE) 19:34, 16 March 2026 (UTC)Reply
For now, everything should be working properly. Using mass-querying tools like Massviews is significantly slower than it used to be, but it should in fact finish eventually. I've added retry logic in as well.
No, it doesn't need to authenticate against a Wikimedia user account, but doing so will make it much faster. So that's the next step. I hope to have that implemented within a week or two. Until then, we'll have to settle with the slowness.
Thanks for your patience, all! MusikAnimal (WMF) (talk) 00:22, 17 March 2026 (UTC)Reply
Thanks very much @MusikAnimal (WMF). Massiews is certainly slower (!) but that's much better than failing completely. I will just make a cup of tea while it chugs along. Cheers, SunloungerFrog (talk) 06:07, 17 March 2026 (UTC)Reply

hi :) The tool is looking for page in the en wiki. Is it possible to use another wiki language ? Thanks :) Haymillefolium (talk) 00:00, 25 March 2026 (UTC)Reply

I got my response : we can set the language in the page pile. It found a lot of page in another language (the pile was en and the page where fr) don't get why Haymillefolium (talk) 00:03, 25 March 2026 (UTC)Reply

No data for April 17th and 18th, 2026.--Sinsyuan (talk) 08:21, 19 April 2026 (UTC)Reply

and 19th Sinsyuan (talk) 04:00, 20 April 2026 (UTC)Reply
@MusikAnimal (WMF) Ping. Dušan Kreheľ (talk) 10:56, 20 April 2026 (UTC)Reply
and 20th Vitti (talk) 11:17, 20 April 2026 (UTC)Reply
A bug was already filed at phab:T423818. I have pinged the Data Engineering team internally to ensure they're aware of it. Best, MusikAnimal (WMF) (talk) 20:56, 20 April 2026 (UTC)Reply

In the page view table comparing multiple pages, e.g. [1], one would not expect the daily averages of the pages to sum exactly to the daily average of the total due to rounding, but there is a much larger discrepancy.

The daily average for each page is round(num_views / num_days), but the total average appears to be round(total_views / (num_days-2)).

This happens with Firefox, Chromium and GNOME Web. Kanguole (talk) 10:21, 19 April 2026 (UTC)Reply

@Kanguole: The data from last 2 days are missed (none uploaded now), so this days are ignored – because "minus 2". Dušan Kreheľ (talk) 17:47, 19 April 2026 (UTC)Reply

With the way the data is currently displayed one usually can't make sense of the data and often not see much of the chart at all. The value changes a lot from day to day so the lines wobble up and down a lot and in addition there are spikes that make the chart tiny and indiscernible. I think it would be rare to see any other notable site which visualizes similar data in this way, at least none as large Wikimedia where Pageviews Analysis is the main way to get and display pageviews data afaik.

Could you please add a moving average like in those images? Python code is attached, don't know how the data is displayed but it should be relatively quick nowadays to add a moving average to the chart. This would make the pageviews tool much more useful (it would then also work for timespans/articles that include spikes which are common). It's a great tool, thanks for developing it. @MusikAnimal (WMF): pls take a look. Thanks, Prototyperspective (talk) 17:41, 23 April 2026 (UTC)Reply

I'll try to look into this at the Hackathon next week. There is the old task, phab:T147515, that you can follow. Best, MusikAnimal (WMF) (talk) 17:22, 24 April 2026 (UTC)Reply
Nice to hear, thanks. It's good that at least an issue has been created about just this key problem of the pageviews charts describing it succinctly but at the same it's disturbing that it has remained open for so long with no activity and nobody participating anyhow at that issue (on the other hand I was aware of the issue but never searched for it in phabricator and it's not particularly quick and simple to find issues there currently). Prototyperspective (talk) 21:59, 24 April 2026 (UTC)Reply