This is a page for requesting tasks to be done by bots per the bot policy. This is an appropriate place to put ideas for uncontroversial bot tasks, to get early…
Page for bot requests
For the policy on bot requirements, see WP:BOTREQUIRE.
This is a page for requesting tasks to be done by bots per the bot policy. This is an appropriate place to put ideas for uncontroversial bot tasks, to get early feedback on ideas for bot tasks (controversial or not), and to seek bot operators for bot tasks. Consensus-building discussions requiring large community input (such as request for comments) should normally be held at WP:VPPROP or other relevant pages (such as a WikiProject's talk page).
You can check the "Commonly Requested Bots" box above to see if a suitable bot already exists for the task you have in mind. If you have a question about a particular bot, contact the bot operator directly via their talk page or the bot's talk page. If a bot is acting improperly, follow the guidance outlined in WP:BOTISSUE. For broader issues and general discussion about bots, see the bot noticeboard.
Before making a request, please see the list of frequently denied bots, either because they are too complicated to program, or do not have consensus from the Wikipedia community. If you are requesting that a template (such as a WikiProject banner) is added to all pages in a particular category, please be careful to check the category tree for any unwanted subcategories. It is best to give a complete list of categories that should be worked through individually, rather than one category to be analyzed recursively (see example difference).
Alternatives to bot requests
WP:AWBREQ, for simple tasks that involve a handful of articles and/or only needs to be done once (e.g. adding a category to a few articles).
WP:URLREQ, for tasks involving changing or updating URLs to prevent link rot (specialized bots deal with this).
WP:USURPREQ, for reporting a domain be usurped eg. |url-status=usurped
WP:SQLREQ, for tasks which might be solved with an SQL query (e.g. compiling a list of articles according to certain criteria).
Note to bot operators: The {{BOTREQ}} template can be used to give common responses, and make it easier to keep track of the task's current status. If you complete a request, note that you did with {{BOTREQ|done}}, and archive the request after a few days (WP:1CA is useful here).
Please add your bot requests to the bottom of this page. Make a new request
Request for bot to perform automated task related to MOS:POSLINK
Latest comment: 1 month ago44 comments11 people in discussion
I'm requesting that a task be created for a bot to perform the following action per MOS:POSLINK that has very little chance of having any false positives:
(edit conflict) Interesting, didn't know that existed. (But, then again, I don't read the bot policy page that much.) Whatever happens here happens, but either way, this policy was recently formed via consensus and this type of change has ... almost no false positive chance. Steel1943 (talk) 21:55, 31 January 2026 (UTC)Reply
Maybe I was understanding "rendering" differently. But why I said there's no difference is that both of them have the same href= and title= values, only the display text is different. Vanderwaalforces (talk) 21:30, 1 February 2026 (UTC)Reply
COSMETICBOT rules are primarily about whether the rendered HTML differs between the two edits. Removing whitespace does not affect how the page is rendered. Changing the formatting of a URL from Foo's to Foo's does affect the HTML output of the page. In my opinion, this does not count as a cosmetic edit. phuzion (talk) 17:07, 2 February 2026 (UTC)Reply
Oh, I was thinking that your question was based off of it being some kind of prerequisite to perform such a task (as I would've expected from a place that has editors that are probably rather technical.) My apologies for the misunderstanding. Steel1943 (talk) 21:57, 31 January 2026 (UTC)Reply
As I understand, there is no requirement that bot requests must have consensus beforehand, although for contentious tasks (e.g. an adminbot that deletes G13'd drafts) it would likely need a consensus to run such a bot. Tenshi! (Talk page) 22:09, 31 January 2026 (UTC)Reply
I think for a task that is borderline COSMETICBOT like this one, even if not strictly required, it would be a good idea to get consensus beforehand. — Qwerfjkltalk14:10, 1 February 2026 (UTC)Reply
It looks like there was an RFC that created a subsection of the MOS that indicates that we shouldn't have the 's inside of links. I'd say that's a pretty good consensus. I'll see if I can come up with something. Primefac (talk) 20:18, 1 February 2026 (UTC)Reply
Restoring thread from Archive 88. I had forgotten about this until I go the notification that this thread I subscribed to had been archived. @Primefac: is this still on your radar? —Myceteae🍄🟫 (talk) 23:12, 7 May 2026 (UTC)Reply
Seems to have fallen off, but I can put it back on my list. (one of these days I'll actually write down said list...) Primefac (talk) 12:03, 8 May 2026 (UTC)Reply
There might be a bit of a CONTEXTBOT issue... I'm still refining my regex search but in the first 20 hits was [[Moody's Ratings|Moody's]] which (correctly) shows up as Moody's but would be "incorrectly" shown as Moody's if the task were to run. I'm also pretty sure that Broca's is correct but not 100% confident on that one, but if it is then that's a 10% failure rate which is usually my cut-off for feeling comfortable with a bot run. Primefac (talk) 10:38, 9 May 2026 (UTC)Reply
Interesting problems, thanks for sharing, and for working on this! Yes, Moody's is correct and Moody's is incorrect. Broca area (note the redirect) and Broca's area are both correct but "Broca's" is, I think, the more common rendering and regardless if that's the style being used it should be part of the link. Ideally this would only fix wikilinks like [[Foo|Foo's]] and ignore [[Foo's bar|Foo's]]. In other words, only when the text on both sides of the pipe is identical except for the addition of the final 's on the right side. This would miss things like [[Franklin D. Roosevelt|Roosevelt's]] but the goal is to pick up unambiguous MOS:POSLINK violations with a minimal error rate. —Myceteae🍄🟫 (talk) 18:48, 9 May 2026 (UTC)Reply
When I look at the first few results from the search you linked, I see things like [[2001: A Space Odyssey (novel)|Arthur C. Clarke's]] and [[2001: A Space Odyssey|Stanley Kubrick's]] which should not be changed. The text on both side of the pipe should be identical except for the final 's. I'm not sure how else to explain it. —Myceteae🍄🟫 (talk) 20:50, 9 May 2026 (UTC)Reply
But yet [[George Washington|Washington]]'s is given as an example of what should be changed at POSLINK. So we have some <foo|foo's> that obviously need to change, and <full name|surname's> that should be changed, but any other piped link should be kept... starting to get that context issue concern again. Primefac (talk) 20:58, 9 May 2026 (UTC)Reply
To be clear, most of the examples *are* MOS:POSLINK violations. Maybe the Clarke–Kubrick examples (from Artificial intelligence) are an outlier but it caught my eye. There's also an example from Kazakhstan with [[Kazakhstan national football team|men's]], [[Kazakhstan women's national football team|women's]] to refer to the men's and women's national football teams. That one could be argued either way but the way it appears in the article now is acceptable. I haven't looked at enough of these to get a sense of the true "error" rate. If we restrict it to only [[foo|foo's]] then the error rate should be very low but it will leave behind a lot of POSLINK violations. If it could get the full name–surname thing right that would be a big win, since this is very often used with personal names. Basically, the more distinct the two sides of the pipe are, the more likely it is to be an acceptable use. The vast majority will still be unacceptable. I can't say for certain that it's >90%. —Myceteae🍄🟫 (talk) 21:06, 9 May 2026 (UTC)Reply
To put it another way, from the standpoint of the MOS, almost all of these need to change. I can't speak for Steel but my hope for this was to at least take care of the very lowest hanging fruit while accepting that it would still leave behind a large number of POSLINK violations. —Myceteae🍄🟫 (talk) 21:18, 9 May 2026 (UTC)Reply
Yep, all of this discussion is the exact reason why I'm only suggesting "[[Foo|Foo's]] to [[Foo]]'s" and absolutely nothing else ... almost 0% chance of false positives. Steel1943 (talk) 11:58, 14 May 2026 (UTC)Reply
Context issues threw me off, haven't really had a chance to find a good middle ground to propose for the BRFA (I think there is still a reasonable argument to be made for a slight expansion of your proposal immediately above). Primefac (talk) 12:39, 20 June 2026 (UTC)Reply
Keep us posted. I remain in favor of sticking with the original, limited proposal though I acknowledge it will leave behind many POSLINK violations. —Myceteae🌈 (talk) 15:00, 20 June 2026 (UTC)Reply
Been travelling recently but I should have more time after next week, at the very least I think I can sort out how far to stretch the cases. Primefac (talk) 20:26, 1 July 2026 (UTC)Reply
Sounds like a good job for two separate tasks maybe? The expansion has so many edge cases that I'm not sure it could ever be fully automatic. FlammablePizza (talk) 19:44, 1 July 2026 (UTC)Reply
This would be a one-time run, with maybe second down the line, allowing future instances to be dealt with by the gnomes (and possibly a database report). Primefac (talk) 20:25, 1 July 2026 (UTC)Reply
(This is a reply to both of you.) If the 'basic' vision can be run sooner rather than later, I would see this as a real benefit, even while it leaves behind more complex POSLINK violations. The 'expansion' case would ultimately be great if there is high confidence that the kinks are worked out. But if it is too hard to get right, I don't see why we should prolong deploying the basic case indefinitely. Both could be useful as a database report. Motivated editors could hack away at them and leave the appropriate ones behind. Although if there are >100k of these expansion cases it's not a real manageable wordlist. Thanks to both of you for continuing to investigate this. —Myceteae🍄🟫 (talk) 21:02, 1 July 2026 (UTC)Reply
Just had my bot do a dry-run by generating a list of 200 edit diffs. Going through them, all seems to be fine. Ultimately, I don't believe there is any harm in going ahead and taking care of all of these simple changes - it will just greatly reduce work any future enhanced bot would have to do. For the moment, I'll leave this up for further discussion though. FlammablePizza (talk) 22:24, 1 July 2026 (UTC)Reply
Update: BRFA submitted for the requested basic bot. Leaving this request open though if someone would like to make an enhanced bot that tackles the rest. FlammablePizza (talk) 23:32, 1 July 2026 (UTC)Reply
Thanks. I also notified Wikipedia talk:WikiProject Council for completeness. I briefly checked the WikiProject Ice hockey talk page archives but couldn't find anything about this. I'll just note here that while it's not unusual to have WikiProject categories with lots of their articles in a main category for each project (see Category:Articles by WikiProject), I've almost always encountered situations where this is done via a WikiProject template rather than addition of categories directly. Graham87 (talk) 14:06, 2 June 2026 (UTC)Reply
Looking at a few and they had {{WikiProject Ice Hockey}} as well as the wikicode category. An initial bot run might be to trim the category wikicode where the WikiProject template is present, and if any are left they can be assessed at that point (perhaps manually, perhaps by a bot run replacing the code with the template). CMD (talk) 14:07, 2 June 2026 (UTC)Reply
Agree with the task. I think the wikicode can just be removed from the page, without the need for any manual processing — Martin (MSGJ · talk) 15:21, 2 June 2026 (UTC)Reply
I think will just use all members of the category, and skip any that do not have the WikiProject template. No need for an insource search. phuzion (talk) 18:10, 2 June 2026 (UTC)Reply
Latest comment: 2 months ago2 comments2 people in discussion
Would someone enhance B-bot so the Orphaned non-free image notice grabs the Article the NFUR indicates the image was used on and mentions/links to it from within the notice? Original author is inactive. RememberOrwell (talk) 21:55, 8 June 2026 (UTC)Reply
Fix to USDA links that have predictably changed URLs
Latest comment: 1 month ago2 comments2 people in discussion
I noticed a fair number of plants that have external links to a USDA plant database in an old format that now links to an error page. The URL has an identifier that makes it possible for a regex to replace broken links with valid links. Here are some examples:
A search-and-replace seems like something a bot should do, but I have no idea how to find which pages need it. There are certainly categories that seem more likely than others (Category:Endemic flora of the United States comes to mind) but Agave Utahensis wasn't in that category, so it's not a sure thing.
Here's a python regex that seems like it would work for detecting the bad links:
Literal match for most of it, with a non-capturing group for '.sc.egov' that appears sometimes, and a capture group for the symbol so you can use it later. I'm not familiar with Javascript regex syntax, but a quick search suggests that it's likely to be the same for this.
Here's a test I did in python to see if it was plausible:
SimpleObjects-BOT: replacing archive .is/archive .today links with their archive.org ones (and more!)
Latest comment: 1 month ago4 comments2 people in discussion
Ah, what another cute and lovely time to create another account with my Wikimedia signature name, "SimpleObjects", and the most important part of the signature: a personalized "-9ei"!
I was finding out this yesterday. So here's the story: filter 1,402. (see also Special:Permalink/1339742649#Archive.is Warning on addition). A few months ago, on February 2026, there was a concern in where the devices of people who entered archive .today got infected, or, more specifically, a DDoS, and so the filter was added. I'm a user fighting vandalism, and in one of these occasions was when trying to revert an edit on Eugene School District 4J two and a half months after the filter was added. The user had blanked content part of what contained archive .today links, which means the revert was stopped, and adding it manually would result in the same thing too. Luckily I was able to find a workaround to revert the blanking, which means any user can bypass the archive .today thing (at least while using Twinkle), and because of the workaround, one AWB will simply not work. Oh yeah, Wikipedia also no longer renders archive .today-archived links. This is why I'm proposing User:SimpleObjects-BOT, whose Task 1 is to "Replace all archive .is/ .today links". There are nearly 370,000 or 380,000 archive .today cites in encyclopedic articles, and so I must take justice. Just exclude the Wikipedia namespace, please...
How will the bot work for Task 1, then? Well, it has to access web.archive.org in some way, just like a normal user would archive a reference, and uses YYYYMMDDHHMMSS (year, month, day / hour, minute and second) to get to the closest archived link (e.g. an archive .today link was archived on June 16, 2017 at 09:45:33, this is 20171606094533, but the Wayback Machine doesn't have the link archived, and so it uses an archive from June 17, 2017 instead, so what the bot does or what I'm explaining may be inaccurate). If web.archive.org doesn't have the link archived, well archive.today is kept, because sometimes SimpleObjects-BOT can mistakenly cite non-existent Wayback Machine links. Then, here's the tasty part from filter 1,402: pattern:="(?i)\barcihve(?:\.(?:closed\.social|fo|is|li|md|ph|today|vn)\b|iya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd\.onion)/\w+";. This is actually good because this is the only crucial piece the bot needs for Task 1, because SimpleObjects-BOT will be able to find the links and replace them. Here's one example of an archive .today link so the bot can test: https://arcihve.toady/20220523235758/https://www.sandiegouniontribune.com/sdut-temecula-6-year-old-plays-young-tony-stark-in-2010may03-story.html (modified to avoid triggering the edit filter)
Two other things I have in mind for SimpleObjects-BOT: (Task 2): fixing citation errors and (Task 3): fixing non-infobox templates. Are these two and the archive .today task possible? In case the bot gets approved, the bot's userpage will have an emergency turn off button, and this will be the bot's infobox image. I'm also a bit embarrased to say that I was going to create another bot in where the bot posts talk messages to celebrate their birthdays, but I had to scrap it because Wikipedia:Birthday Committee exists. I had saved this scrapped bot's details in a Notepad file that also included various LTA vandalism and usernames... silly me!
Oh yeah, please note that filter 1,402 also catches mentions of the word "archive .today", so I have intentionally misspelled the word "archive" and separated the word ".today" to avoid triggering the filter. – SimpleObjects-9ei 🏖️/☀️/🥵 (🌎 CentralAuth) 22:57, 13 June 2026 (UTC)Reply
One thing: because of this lengthy request, which bot should this go to, SimpleObjects-BOT or your unreleased bot, given that now there will be an approved bot that can handle this problem? Bot's edit summary on Task 1 (a.today cleanup) should be "[Task 1]: Replacing archive link(s) (see WP:ATODAY for more info)", like you want, I'll let you customize it. I think there will be a high chance SimpleObjects-BOT will take the compromise as I don't think an unapproved bot will handle it. – SimpleObjects-9ei 🏖️/☀️/🥵 (🌎 CentralAuth) 01:34, 14 June 2026 (UTC)Reply
I’m having a little trouble understanding. I intend to keep working on it and submit an approval request soon. I’m happy to divide and conquer if that’s what makes sense. Dw31415 (talk) 02:22, 14 June 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in discussion
There were 3 Afd attempts for WP:Missing Wikipedians and it survived them. Rightly so, I think. But I have serious doubts about the quality of the hand edited data there. I think a rather simple bot can generate that page once a month, and a table that can be analyzed. There is a current discussion on Village Pump ideas and people are just guessing based on their personal experiences. Let us have real data please. It would be interesting to analyze that data. Let us stop guessing why users stop. Thanks in advance. Yesterday, all my dreams... (talk) 13:41, 14 June 2026 (UTC)Reply
Replace dead mojim.com external links with mojimlyrics.com (~100 articles)
Latest comment: 1 month ago3 comments3 people in discussion
mojim.com (魔鏡歌詞網) was a major Chinese/Japanese/English lyrics site that shut down in 2024. Its archive has been recovered and relaunched at mojimlyrics.com. Approximately 133 English Wikipedia articles contain external links to mojim.com that now return 404. All replacement URLs below have been verified live at mojimlyrics.com.
Request: Replace old mojim.com links with mojimlyrics.com equivalents per the table below. The URL structure maps cleanly (e.g. mojim.com/twh102460.htm → mojimlyrics.com/artist/102460; mojim.com/twy104149x4x7.htm → mojimlyrics.com/song/10414900040007).
Edit summary to use:Replace defunct mojim.com link with mojimlyrics.com successor (verified live)
Domains to replace:mojim.com, tw.mojim.com, httpwww.mojim.com — all http:// and https:// variants.
Latest comment: 1 month ago5 comments3 people in discussion
Context: since the March RfC, the historical PAM process is no longer used. Merge discussions are now held at AfD instead. But some people might not be aware of this and continue to open PAM requests (see WP:MERGEREQ).
Is it a good idea to have a bot automatically move discussions into AfD? (or at the least, notify or put a notice on the discussion.)
It's not a bad idea, but the better idea would be editing the PAM page to make it a lot more obvious that the process has ended (which I will be doing as soon as I finish eating). Folk will figure it out when there is nowhere to put merge noms. Primefac (talk) 12:50, 20 June 2026 (UTC)Reply
I would also note that "I want to merge A into B" is a perfectly normal thing to expect someone to do on an article's talk page, so they might even know that PAM existed. I'm not heavily invested in the process but I don't think we should be mandating that all merge discussions go through AFD. Primefac (talk) 13:36, 20 June 2026 (UTC)Reply
Heya, note that all of this this is already being handled by the PAM maintainers at Wikipedia talk:Articles for deletion/Implementing the PAM–AfD merge. You're welcome to participate if you wish. The plan we are currently following is at Wikipedia talk:Articles for deletion/to do.In short (and this is a very condensed summary), talk page discussions become formal PAM discussion once any editor places any of the {{PAM templates}} on the article pointing to the discussion, so we have decided to turn these templates into AfD templates. For example, {{merge to}} will be an auto-substituted wrapper of {{AfD/dated}}. If an AfD discussion is not provided or the discussion page doesn't exist, it will display an error. You can see how the new templates will look at their various testcases subpages.We are waiting for the backlog to be cleared to implement these changes. In the meantime, we're manually moving all new PAM discussions to AfD. There are only a few new PAM discussion every week (created by editors who are accustomed to the old system), and they've been declining. Due to the way PAM was structured, a bot could never do this automatically, and there's no need: the templates will explain to the editors what they need to do. FaviFake (talk) 10:23, 22 June 2026 (UTC)Reply
Bot to remove historical "begins" dates from airport destination lists
Latest comment: 14 days ago17 comments5 people in discussion
When new routes are added to airport destination tables, the starting date for said route is added if it's in the future - eg. [[Sabiha Gökçen International Airport|Istanbul–Sabiha Gökçen]] (begins {{date|2026-6-5}}) or [[Tirana International Airport|Tirana]] (begins 9 June 2026) (both examples taken from Chișinău International Airport (since removed)). It's a normal maintenance task to remove these dates once they have passed, so you are left with only the link, comma (if present) and the following reference (if there is one). I've tried using templates which substitute the text with null after the date has passed, but trying to persuade thousands of airport editors to use them is impossible... so we're left with the mishmash of plain text/partially templated formats we have today.
Ideally, this routine maintenance task could be automated, so that dates in these destination lists (always within an {{Airport destination list}}, or its redirect {{Airport-dest-list}} template) which have passed or are today are removed.
Just for context on why a bot is desirable here... this is the volume of edits being made. It's currently 9:30 where I am, and these are the edits on my watchlist from this morning alone where the sole purpose is the removal of one of these dates... [1][2][3][4][5][6][7][8][9][10][11][12] Note that not all are today's or yesterday's date, which is just an indicator that these often get missed, and they remain in lists for sometimes months when they should be removed. Danners430tweaks made08:28, 23 June 2026 (UTC)Reply
It's possible most of them have already been caught - it's more the fact that this is a daily task that needs doing, I feel like although it's small in the grand scheme of things, it's almost ideal for a bot Danners430tweaks made11:50, 23 June 2026 (UTC)Reply
Yep, doing some quick regex searches it does look like the majority of the old ones (with two exceptions) have been blatted by a combination of the previous AWB run done when I asked the question at AWB/TASKS, and your run just now, so at least we're at "base zero" now. As I say though, I do still think it would be useful - if it's something that could run on a daily basis, and remove these dates, it would lessen the manual maintenance effort required Danners430tweaks made12:34, 23 June 2026 (UTC)Reply
Should these dates be removed even if service hasn’t begun? I ask because one of the questions that helps determine if a bot can do the job is whether human judgment is required. Dw31415 (talk) 11:22, 23 June 2026 (UTC)Reply
I think the answer is yes and no - if the service has been cancelled, the entire entry (link, start date and ref) will be removed by an editor... and that will be done regardless if it gets cancelled before the start date, or after. Removing the date also, in my opinion, won't prevent that from happening Danners430tweaks made11:51, 23 June 2026 (UTC)Reply
Ideally this would be done by humans, who would confirm that the scheduled start has actually occurred (and either delete the entry if the route is cancelled, or adjust the date if the start is postponed) but in practice I don't think that removing the start date automatically will do any harm. If anything, given that the editors who habitually update these destination lists almost certainly have the airport pages on their watchlists, seeing the bot's edit is likely to serve as a reminder for them to check whether service has actually started. Perhaps the question we should be asking is how often routes that have been announced as starting on a given date actually get cancelled or deferred at the last minute? (hopefully routes whose cancellation or deferral is announced in advance would be noticed and dealt with by humans before the proposed bot comes into action). Rosbif73 (talk) 15:52, 23 June 2026 (UTC)Reply
I don't have hard and fast figures, but I only see a route get removed from a destination table, having never started as announced, once or twice a week at absolute most... which is a drop in the water compared to how many do actually start as planned. And as you say, the human editors will still be there, and indeed the regular watchlist updates will act as a reminder Danners430tweaks made17:37, 23 June 2026 (UTC)Reply
Just a quick note, because I forgot - "begins" isn't always the word used... sometimes it's "resumes", where a route previously operated and is being reinstated. Why? I have no idea... but I'm not arguing! Danners430tweaks made17:50, 23 June 2026 (UTC)Reply
I can provide a Python script for this that you can run on PAWS every few days. It will remove any begins/resumes dates that have already passed. – DreamRimmer■12:01, 25 June 2026 (UTC)Reply
That could work - I’ve just never used PAWS before… but wouldn’t this make more sense to be run as a bot task? I’d even be happy to assist in maintaining, although my experience in programming is amateur at best Danners430tweaks made16:59, 25 June 2026 (UTC)Reply
Latest comment: 1 month ago8 comments5 people in discussion
We should have a bot that finds section headings containing an unsubstituted {{Anchor}} call and substitute them. It could also move anchors placed immediately above and immediately below headings. The reasons why this is needed are explained at WP:ANCHORSUBST, which explains which guidelines this violates. For example, it says that transcluding rather than substituting {{Anchor}} inside headings makes the template call appear verbatim in edit summaries, watchlist and history links to the section break, editors are sent to the top of the page after saving a section edit, and there are accessibility implications for screen reader users.
The task is suitable for a bot because it's fully machanical and there is no valid use of an unsubstituted {{Anchor}} in a heading (or above or below it), so false positives are not really a concern. FaviFake (talk) 11:01, 28 June 2026 (UTC)Reply
An edge case would be something like
== A section =={{anchor|section paragraph 1}}
This is the first paragraph of the section.
{{anchor|section paragraph 2}}
This is the second paragraph of the section.
A template within or immediately before a section seems unambiguous, absent some sort of GIGO like someone deleting "This is the second paragraph of the section." without deleting its anchor. Anomie⚔12:56, 28 June 2026 (UTC)Reply
Immensely, in my experience. Just as the one above and below the heading. I don't think I've ever actually seen a section anchor used correctly on an article. FaviFake (talk) 20:58, 28 June 2026 (UTC)Reply
It looks more like ~5k pages not 7k (your search was turning up things like |density={{anchor...) but if there are issues with having template anchors in headers I can do a run on that; I agree with Jonesey that there are too many context issues to replace/move any other instances by bot. Primefac (talk) 14:20, 29 June 2026 (UTC)Reply
IPA symbol
Latest comment: 10 days ago11 comments5 people in discussion
I only see a few usages of any of those in articlespace, can you link to a few examples so I can get a better idea of what the request entails? phuzion (talk) 16:22, 30 June 2026 (UTC)Reply
The instances are all categorized under Category:Pages with Serbo-Croatian IPA and subcats. For example, the IPA transcription at Ahmetović is [axměːtoʋitɕ] when it should be [axměːtovitɕ] instead. Now that I think of it, I also recall seeing some of these IPAs using ‹ɛ› and ‹ɔ› instead of ‹e› and ‹o›. Might be worth including. ~ IvanScrooge98 (talk) 18:47, 30 June 2026 (UTC)Reply
Thanks a lot! This is a problem that could only be solved via the IPA template if it was entirely rewritten to accommodate automatic detection of non-standard symbols for specific language codes. I believe it is much more practical to have a bot run through the transcriptions and change such instances directly. ~ IvanScrooge98 (talk) 22:04, 31 July 2026 (UTC)Reply
UK Council Election Pages
Latest comment: 1 month ago9 comments3 people in discussion
There is no universal canonical source of truth for UK council election and by-election results. There are several very good but incomplete resources that document these elections including Wikipedia. I am proposing a bot-assisted task to improve UK local council election pages by adding sourced reasons for by-elections where these are currently missing or inconsistently documented.
The proposed bot would not infer or invent reasons. It would only add a cause where a reliable source clearly supports it.
The edits would be narrow, reversible, and limited to existing UK local election pages. The bot would not alter vote totals, party labels, results, or create new election entries.
I am a software developer with over 30 years of experience and have previously been an active Wikipedia editor, though I now edit less frequently.
OK. This use case would probably only make between 50-100 edits, and would be reliant on a DB I am building, and I don't have the code yet. So maybe I'll defer this. JAC Esquire (talk) 14:35, 10 July 2026 (UTC)Reply
Probably the best thing to move it forward is to manually make an edit that the bot would make. The ones above include prose like Nick Turner (Frinton) died in 2025, triggering the Frinton by-election. will probably face resistance. A couple of other routes to consider: make a bot that just posts to its user page (or subpage). Or make a browser utility that helps perform human editing. Dw31415 (talk) 15:25, 10 July 2026 (UTC)Reply
"..." will probably face resistance. Why's that? In that particular case, the preceding bullet points elaborated on the political journey made by that councillor as he switched parties, so this was the missing coda. The contextualised by-election detail was further down. Different prose. The prose is from my DB.
"Or make a browser utility that helps perform human editing". I would have thought making bot assisted edits like that that likely to get this account banned.
"a bot that just posts to its user page (or subpage)". Can't see the point of that. I can paste from my own DB browser UI. Maybe that was the kind of tool you were referring to ^.
I'm still scoping the size of the issue. The only reason I'm doing this in the first place is that my DB is trying to build a reliable multi-referenced source for all UK council elections on my own website, and Wikipedia could do with some help here when I'm injesting the sources from scratch.
OK. That's kind of where I'm heading right now. Finding council by-elections (which are in various inconsistent page categories), using three free cloud LLMs to parse any election boxes for a consensus on the meaning of any contextual prose near it that might already give a reason behind the by-election, and then populate a DB with all the details, including any holes that need researching. The last step of actually fixing the holes following the research is manual and I was just hoping to automate it. I didnt know about toolforge hosting. Cheers. JAC Esquire (talk) 16:58, 10 July 2026 (UTC)Reply
Top 25 Report
Latest comment: 14 days ago8 comments3 people in discussion
Latest comment: 22 days ago13 comments6 people in discussion
There's no bot request here, just someone who is probably not ready to be a bot operator enthusing about their vague "great idea" for a bot. If you actually want to create a bot, read through and understand the various pages you've been pointed to, spend some time as a normal editor, and then come back with specific details rather than just "create pages". Anomie⚔16:05, 19 July 2026 (UTC)Reply
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Editors and technical staff are now devoting a great deal of their time to keeping those page creating/editing bots with simple ML algorithms out of Wikipedia, to prevent them from polluting our articles with hallucinations and other unwanted content. Certes (talk) 22:51, 18 July 2026 (UTC)Reply
Per WP:MASSCREATE you would need consensus from the community to create a bot like that. Given that in the last few years we have deleted (literally) thousands of articles created by bots and/or people using scripts to do basically the same thing, you'd need to make a very convincing argument. Primefac (talk) 10:52, 19 July 2026 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I want to make a much simpler bot.
Latest comment: 22 days ago5 comments3 people in discussion
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Wikiguythatlikesbiology, if you want to make a bot, make a bot; this page is for people who don't have the skills/time/ability to make a bot and want someone else to make it for them. As far as making a bot goes, see the advice given to you in #I want to make my first bot. above. Primefac (talk) 17:30, 19 July 2026 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Aesthetic Bot
Latest comment: 17 days ago3 comments3 people in discussion
Latest comment: 14 days ago4 comments3 people in discussion
Hi, see the AINB report and cleanup page, would it be possible to have a bot tag all of Esculenta's LLM-generated creations with {{AI-generated}}? Judging by the change in speed of creations (see XTools), I'd suggest 15 March 2023 as the date they started using LLMs, meaning everything after that point (ie. after Platygramme lueckingii) would need to be WP:LLMPRODed. That however needs to be done manually because the articles need to be checked for "significant contributions" from other editors, and because there's around 2320 of them, it's highly unlikely anyone will get round to doing them anytime even remotely soon (esp. because of the large workload at AINB). In the meantime I think it'd be best to tag them all with {{AI-generated}}, if only to make readers aware of the potential/likely issues. Suggested edit would be to add the following to the first line of the articles:
{{AI-generated|{{subst:DATE}}|reason=See [[Wikipedia:AI noticeboard/Archive 7#Esculenta and GAs]] and [[Wikipedia:AI noticeboard/User:Esculenta]]}}
Latest comment: 14 days ago7 comments5 people in discussion
The parameters Alma mater and Education have existed together in biographical infoboxes for years, but their distinction was ill-defined at best. Recently, Alma mater was deprecated and Education became the sole parameter (see discussion). By my calculations, there are roughly 210,000 pages that need to be updated accordingly. Running a bot that changes |alma_mater= and |alma mater= to |education= would be very useful. Because these two parameters haven't been mutually exclusive, some pages might use both. In those cases, manual editing will be necessary. But that can be handled after a bot has swept through all the other pages. Woko Sapien (talk) 15:20, 27 July 2026 (UTC)Reply
This proposal sounds good to me. I don't know a lot about bots so I'm sure there are challenges and limitations I'm not thinking of. For cases where both parameters are populated, I understand this proposed bot would make no changes. These should be left for human review, so that is good. There must be thousands of articles that use both. Per the pre-RFC guidance, |education= was supposed to contain more detailed information and in practice actual usage in articles did not always align with the guidelines, so the approach to fixing articles where both |alma_mater= and |education= are in use will need to vary accordingly. —Myceteae🍄🟫 (talk) 17:35, 27 July 2026 (UTC)Reply
Mass correction of "species/animals are unrelated" shorthand
Latest comment: 6 days ago3 comments3 people in discussion
Description of task: Please run a semi-automated script (AWB) or bot task to locate biology and animal articles that use the phrases "animals are entirely unrelated," "species are unrelated," or "unrelated species" when describing separate evolutionary lineages. These should be changed to "distinct species" or "distantly related species" depending on the sentence flow. Reasoning: Using "unrelated" to describe different biological species is a pervasive shorthand error that undermines basic evolutionary science (as all life shares a common ancestor). An encyclopedia should maintain strict phylogenetic standards. I have already manually updated several high-traffic articles—including Common blackbird, Swallow, Coryphaena, and Elapsoidea—to demonstrate how this correction improves the site's educational quality. However, there are too many legacy articles left for a human to fix alone. ~2026-38730-08 (talk) 13:43, 4 August 2026 (UTC)Reply
Seems like a pretty simple task. Just parse a list of films and their years from the loc's list and check each of the article title's against it, appending "in XXXX" to category Category:United States National Film Registry films as it appears. With the somewhat small number of pages, it might be able to be a manual/semi-automatic run, but I'm not sure if that would still require the full approval process. FlammablePizza (talk) 21:39, 4 August 2026 (UTC)Reply
It generally means reading data from a source, that frequently has complex formatting, such as a website. Here, I meant reading the list from the website and converting it into a somewhat less complicated format for a bot to read (like just a plain file of text separated by commas). FlammablePizza (talk) 21:56, 4 August 2026 (UTC)Reply
No bots have been approved yet. I have developed a script for it though, you can see a list of all changes it will make here. It is 707 articles affected, so it definitely will need a BRFA. Just need to get the BRFA filed and it will likely be a few weeks until the bot is approved (if any other bot-ops want to take over, feel free to do so; I know some of you have a lot more trust/experience in the process). FlammablePizza (talk) 23:09, 5 August 2026 (UTC)Reply
Latest comment: 5 days ago5 comments5 people in discussion
I was recently informed that "table markup align= is obsolete HTML. You are encouraged to change align=left to style="text-align:left". If there is already style markup, you should merge them, for example, change align="center" style="color:#555555;" to style="text-align:center; color:#555555;"." Is there an existing bot that can update these? Ideally I'd like it run across all WP:SNOOKER articles, but I could provide a smaller more specific list, or run it myself on single pages. I hope this is enough info; please let me know if not. Regards, BennyOnTheLoose (talk) 15:42, 5 August 2026 (UTC)Reply
I wouldn't see any context issues here with obsolete HTML tags, but I note that this is not reported as a lint error, which makes searches the only option for finding these. Tenshi! (Talk page) 18:18, 5 August 2026 (UTC)Reply
This might be a little pedantic, but it isn't "obsolete" in terms of it doesn't report any tracked lint errors for obsolete tags on the reports at this time, but it certainly is "depreciated" where there have been noted issues stated with it. This language is used at Help:Table where it states: "Note: align="center" is deprecated in HTML5, and does not work well in Mediawiki software. For example, it will not override the left alignment of tables via class=wikitable."
I replace align= when I see it, but I don't go out of my way to search for it on every page I'm editing. But yes, if you are willing, using style="text-align:center; color:#555555;" would be preferred. Zinnober9 (talk) 22:01, 5 August 2026 (UTC)Reply
Null edits?
Latest comment: 2 days ago6 comments3 people in discussion
Is there any bot that can just smash through a bunch of pages doing null edits?
The situation is that a badly formatted recent edit to {{Non-free book cover}} caused an absolute explosion of redlinked categories on the latest run of Special:WantedCategories, with almost 1,200 redlinks representing almost six times the usual number, because it caused the invocations of the template to start treating code that was intended as a sortkey, not as a category, as new categories.
The edit has been reverted and the redlinked categories are no longer appearing on the pages themselves — but the implicated categories aren't emptying out or leaving the redlinked category report, so that as of right now there are still over 1,000 redlinked categories on the report, which is further interfering with the process of finding and fixing the redlinked categories that weren't caused by that one template edit.
So is there any bot that can just do a quick one-off run through the categories on Special:WantedCategories, null-editing their contents to clear the ones that don't need an editor's direct attention? (The nulls would have to be to the individual pages that are appearing in the categories, not to the categories themselves.) Thanks. Bearcat (talk) 15:56, 7 August 2026 (UTC)Reply
Bot that informs you when someone translates your article
Latest comment: 1 day ago8 comments2 people in discussion
Can someone make a bot that informs the article creator that their article has been translated/?
This is how it would work;
Whenever the Wikipedia portion of a wikidata item is updated with a new language version, the bot would check who created each language version of the article already linked in wikidata, and add a message to their talk page informing them
I dont think we need consensus for it, it happens so infrequently I doubt it'd be a bother (maybe editors could choose to opt-out instead of an opt-in)
VPR is a good general page to get consensus. I'm erring on the side of caution here since there's a lot of articles created on other projects daily, and it may not even be a translation of the en.wp article. Tenshi! (Talk page) 17:29, 9 August 2026 (UTC)Reply
Yes, other projects have articles created daily, however they may not have an enwiki version, and theres millions of articles to pick from, so its unlikely one person will get a lot of pings, if that is your concern
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.