Wikipedia Bot Approvals Group: How to Apply for Approval in 2026

Ever tried to fix a thousand typos on Wikipedia and ended up getting blocked? If so, you’ve likely hit the wall that separates casual editors from power users. The Bot Approvals Group is the committee of experienced Wikipedians responsible for reviewing, approving, and managing bots on English Wikipedia. Getting your script approved by this group is the only way to run automated edits without risking a ban.

It’s not just about speed; it’s about safety. A bot can edit faster than any human, but if it makes a mistake, it can damage thousands of articles in seconds. That’s why the process is strict. This guide breaks down exactly how to navigate the BAP application process, what they look for in a proposal, and how to avoid the most common pitfalls that cause rejections.

Why You Need BAP Approval

On English Wikipedia, any user can create an account and start editing. However, once you want to use software to make changes automatically, the rules change. Without approval, your edits might be seen as vandalism or spam. The Bot status grants your account special permissions that allow high-volume editing while keeping track of your actions in a separate log.

The main reason for this gatekeeping is community trust. When a bot makes a change, readers see a small robot icon next to the editor's name. This tells them the change was automated. If the bot isn’t approved, there’s no such indicator, which can confuse readers and irritate other editors who have to manually revert every single change you make. By getting approved, you signal that your tool has been vetted by experts who understand the risks of automated editing.

Preparation: Before You Write Your Proposal

Don’t rush into writing your application. The BAP rejects many proposals simply because the applicant didn’t do their homework. Here is what you need to prepare before you even open the request page:

• Define your task clearly: What exactly will the bot do? Will it add categories? Fix grammar? Move pages? Be specific. "Cleaning up articles" is too vague. "Adding the {{Infobox film}} template to movie articles released in 1995" is specific.
• Choose your programming language: Most bots are written in Python using the Pywikipediabot framework, though JavaScript and other languages are acceptable if justified.
• Create a test account: You need a dedicated account for the bot. Don’t apply using your personal account unless you plan to keep using it for manual editing alongside the bot (which is discouraged).
• Review existing bots: Check the list of active bots to ensure you aren’t duplicating work. If another bot already does what you want, ask them if they can expand their scope instead of creating a new one.

Step-by-Step Application Process

Once you’re ready, follow these steps to submit your request to the Bot Approvals Group.

1. Navigate to the BAP Request Page: Go to the "Requests for approval" section on the BAP talk page. This is where all applications live.
2. Start a new thread: Click "New topic." Give your post a clear title like "Request for approval: [Bot Name] - [Brief Description]."
3. Fill out the standard template: Use the pre-filled template provided. It asks for:
   • Bot name: The username of the bot account.
   • Operator: Your personal username.
   • Task description: A detailed explanation of what the bot will do.
   • Method: How it works (e.g., "Uses Pywikipediabot to scan category X").
   • Frequency: How often it will run (daily, weekly, on-demand).
   • Code availability: Link to the source code repository (GitHub is preferred).
4. Attach examples: Show at least three example edits the bot would make. Use diff links if possible. This helps reviewers see the impact immediately.
5. Submit and wait: Once posted, the clock starts. There is no fixed deadline, but most reviews take 3-7 days. Be patient.

What the Reviewers Look For

The BAP members are volunteers with deep experience in Wikipedia policies. They don’t just check if your code runs; they assess the risk. Here are the key criteria they evaluate:

One critical aspect is Rate Limiting. If your bot tries to edit 100 pages per minute, it might overload the server or trigger anti-spam filters. Set a conservative limit, like 10-20 edits per minute, and explain how you control the speed in your proposal.

Common Reasons for Rejection

Even well-intentioned bots get rejected. Knowing why can save you weeks of waiting. Here are the top reasons:

• Duplication: Another bot already handles this task. Always check first.
• Lack of Consensus: You applied without discussing the idea on the relevant WikiProject talk page. Editors feel bypassed.
• Poor Documentation: The code is messy, or the proposal lacks clear examples. Reviewers hate guessing.
• Risk of Error: The task involves subjective judgment (like categorizing art) rather than objective facts. Bots should handle mechanical tasks, not editorial opinions.
• Inactive Operator: If your personal account hasn’t edited in months, reviewers worry you won’t monitor the bot after approval.

After Approval: Maintaining Your Bot Status

Getting approved is just the beginning. The BAP monitors active bots regularly. If your bot goes silent for more than six months, it may be suspended. To stay in good standing:

1. Log your activity: Keep a public log of what your bot did each day.
2. Respond to feedback: If an editor reports an error, fix it quickly and explain the correction.
3. Update your proposal: If you change the bot’s behavior significantly, file a new request or update the original one.
4. Stay active: Run the bot periodically, even if only for a few hours, to show it’s still under maintenance.

Remember, the goal isn’t just to automate work-it’s to improve Wikipedia reliably. Treat the BAP process as a partnership, not a hurdle. When you show respect for the community’s standards, approval becomes much smoother.