Past year option?

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)

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)

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)

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)

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)

The default is now 30! Thank you. Aloysius Jr (talk) 12:15, 17 March 2026 (UTC)

That's great, thank you! – AlyInWikiWonderland (talk) 00:20, 18 March 2026 (UTC)

Massviews not returning any results

• Please provide a link to the results that are breaking for you.
  • https://pageviews.wmcloud.org/massviews/?platform=all-access&agent=user&source=pagepile&start=2026-02-19&end=2026-03-11&target=111105&sort=views&direction=1&view=list&target=111105
• 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
  • Edge 145
• What operating system and version are you using?
  • MacOS Tahoe 26.3.1

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)

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)

@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)

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)

@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)

That's exactly what I also get. Every time, for each Category, the same error today Pschemmo (talk) 15:13, 13 March 2026 (UTC)

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)

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)

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)

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)

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)

@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)

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)

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)

Redirect views not shown on pageviews analysis even when "Include redirects" is ticked

The issue occurs both on Windows and Android at least when using chrome. To pick an obvious example, the "Redirect Views" page for Stephanorhinus kirchbergensis shows that it got 1,446 views from 15 February to the 16 of March, of which 809 were non-redirect views. , when checking the pageviews analysis for the same article and time period, it only shows the 809 number including when the "Include redirects" box is ticked Hemiauchenia (talk) 21:01, 17 March 2026 (UTC)

Ah, yes. I'm not sure what to do about this one… we could potentially be firing off a lot of requests. I'll get it fixed, but you'll have to okay with waiting a bit longer to get results than you did in the past. Thanks for letting me know, MusikAnimal (WMF) (talk) 21:40, 17 March 2026 (UTC)

Missing data for some days

Hi, i discovered that there is no data for the following dates:

https://wikimedia.org/api/rest_v1/metrics/pageviews/top/it.wikipedia/all-access/2015/06/29

https://wikimedia.org/api/rest_v1/metrics/pageviews/top/it.wikipedia/all-access/2024/03/31

is this a bug of pageview API, or is the data actually missing? Sette-quattro (talk) 13:22, 23 March 2026 (UTC)

can we use Massviews with another language

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)

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)