Ever stared at a blank screen where an article used to be? It happens. One minute you're reading about a minor band or a local politician, and the next, it's gone. For new editors, this can feel chaotic, like the rules change every hour. But they don't. Wikipedia runs on a strict set of deletion processes that balance community consensus with efficiency. Understanding how these mechanisms work is the difference between getting your edits wiped out and building a lasting contribution to the world's largest encyclopedia.
The core tension in Wikipedia's governance model is simple: we want accurate, verifiable information, but we also want to avoid cluttering the project with junk. To solve this, the community developed three main pathways for removing or consolidating content: Articles for Deletion (AfD), Speedy Deletion, and Mergers. Each serves a distinct purpose, and knowing which one applies to your situation saves you weeks of back-and-forth debates.
Articles for Deletion: The Community Courtroom
Articles for Deletion is a formal process where the Wikipedia community votes on whether an article should be kept, deleted, merged, or redirected. This is the most common route for articles that have existed for a while but are struggling to meet notability standards. If you think an article is worth saving, this is your primary battleground.
The process isn't a popularity contest. When someone tags an article with an AfD nomination, it goes into a queue for review. Editors discuss the article's merits over a period of seven days. They look at specific criteria, primarily notability. Does the subject have significant coverage in reliable, independent sources? If the only mentions are from the subject's own website or social media, the argument for deletion becomes strong.
You might wonder why it takes a week. It’s designed to give the community time to react. A quick vote might favor those who are online at that moment, but a week allows for a broader consensus. During this time, you can add references, improve the structure, or argue for a redirect instead of full deletion. Many articles survive AfD because editors realize the subject is notable but the writing was poor. Fixing the prose often saves the entry.
Speedy Deletion: When There’s No Debate
Not everything needs a week-long discussion. Sometimes, an article is so obviously unsuitable for inclusion that debating it wastes everyone's time. This is where Speedy Deletion comes in. It is a mechanism for removing articles that clearly fail to meet basic inclusion criteria without a community vote.
Think of Speedy Deletion as the trash bin. It handles obvious cases like spam, vandalism, or pages created by bots. The criteria are codified in a list known as CSD (Criteria for Speedy Deletion). If an article falls under one of these categories, any editor can tag it for removal. Usually, an administrator deletes it within 48 hours if no one objects.
Common reasons for speedy deletion include:
- Spam: Articles that exist solely to promote a business or product without neutral context.
- Vandalism: Pages filled with nonsense text or offensive content.
- Duplicate Content: An exact copy of another existing article.
- Non-Notable: Subjects with zero coverage in reliable external sources after a reasonable search effort.
If you see a page tagged for speedy deletion, check the reason. If you believe it’s wrong, you can remove the tag and explain why in the talk page. But proceed with caution. Repeatedly tagging obvious spam for speedy deletion is encouraged; fighting over borderline cases here usually leads to an AfD nomination instead.
Mergers: Combining Related Topics
Sometimes, two articles cover the same ground. Maybe there’s a separate page for "History of X" and "X," and the history section in the main article is redundant. Or perhaps two different names refer to the same entity. In these cases, neither article should necessarily be deleted. Instead, they should be combined. This is the realm of Mergers, which are processes for combining two or more Wikipedia articles into a single, more comprehensive entry.
Mergers are less dramatic than deletions but equally important for organization. They prevent fragmentation, where readers have to jump between multiple pages to get a complete picture. The goal is to create a single, cohesive narrative. When proposing a merger, you need to suggest which article will remain as the primary title and how the content from the other(s) will be integrated.
Unlike AfD, mergers don't always require a formal vote if both parties agree. If the editors of both articles consent to the merge, it can happen quickly. However, if there’s disagreement-say, one editor wants to keep their article standalone-a formal proposal is made, and the community decides. The result is usually a cleaner, more readable experience for users.
Comparing the Three Processes
To help you decide which path to take when reviewing or creating content, here’s a breakdown of how these processes differ in practice. The right choice depends on the state of the article and the level of community agreement.
| Process | Primary Use Case | Timeframe | Decision Maker | Risk Level for Editor |
|---|---|---|---|---|
| AfD | Debatable notability or quality issues | 7 days | Community Consensus | Medium (requires defense) |
| Speedy Deletion | Obvious spam, vandalism, or duplicates | 48 hours | Administrator | Low (if criteria met) |
| Mergers | Overlapping topics or redundant sections | Variable (days to weeks) | Editorial Agreement/Consensus | Low (constructive) |
Notice the shift in decision-making power. Speedy Deletion relies on administrative authority to maintain order. AfD relies on collective judgment to handle nuance. Mergers rely on editorial cooperation to improve structure. Using the wrong tool for the job is a common mistake. Tagging a nuanced biography for speedy deletion because you personally dislike the subject will likely lead to a revert. Nominating a blatant ad for AfD is slow and inefficient when it could be speedily deleted.
Strategies for Surviving Deletion Nominations
If you’re an editor facing an AfD nomination, panic is your enemy. The first step is to read the nomination carefully. What specific criterion is the nominator citing? Is it lack of notability? Poor writing? Duplicate content?
If it’s notability, go find sources. Not just any sources, but reliable ones. News outlets, academic journals, and established books count. Avoid blogs, forums, and self-published works unless they are widely recognized authorities in their field. Add these references directly to the article body, not just the talk page. The article must stand on its own feet.
If it’s a quality issue, clean up the prose. Remove jargon, fix grammar, and ensure the tone is neutral. A well-written article is harder to delete, even if the subject is niche. If it’s a duplicate, propose a merger or a redirect. Show the community that you’re willing to collaborate rather than fight for a separate page.
Engage in the talk page discussion politely. Argue facts, not feelings. Point to specific guidelines. If you can get other editors to support your position, the consensus shifts. Remember, the goal isn’t to win an argument; it’s to demonstrate that the article meets the project’s standards.
The Role of Administrators and Bots
While the community drives most decisions, administrators play a crucial role in enforcement. They have the tools to delete pages, protect them from edit wars, and manage user accounts. However, admins aren’t judges. They follow the consensus reached by the community. If an AfD vote results in a clear majority for deletion, the admin executes the deletion. If the vote is split, they might close the discussion as a tie, leaving the article in place.
Bots also play a part, especially in maintenance. Automated scripts can identify orphaned images, broken links, and potential duplicates. These bots often flag issues before humans do, triggering the deletion or merger processes. For example, a bot might notice that two articles have identical infoboxes and suggest a merger. This automation keeps the encyclopedia tidy at scale, something impossible for human volunteers alone.
Frequently Asked Questions
What happens if I lose an AfD vote?
The article is typically deleted by an administrator. However, you can recreate it later if you have better sources or improved content. Deleting an article doesn't ban the topic forever; it just means the current version didn't meet the standard at that time.
Can I nominate my own article for deletion?
Yes, and it's often seen as a positive sign of good faith. If you know your article has issues, nominating it yourself shows you care about quality. Just make sure to provide a clear reason for the nomination.
How long does a merger take to complete?
If both editors agree, it can take just a few days. If there's a dispute, it may take several weeks as the community discusses the best way to combine the content. Complex mergers involving many subtopics can take longer.
What is the difference between a redirect and a deletion?
A redirect sends readers from one title to another related article. Deletion removes the page entirely. Redirects are useful for alternate names or spellings, while deletion is for content that shouldn't exist separately.
Do all languages use the same deletion processes?
No. While English Wikipedia uses AfD and Speedy Deletion, other language versions may have different systems. For example, German Wikipedia has a different approach to consensus-building. Always check the local guidelines if you're editing a non-English version.
Understanding these processes turns Wikipedia from a mysterious black box into a manageable platform. Whether you're trying to save an article, clean up spam, or organize related topics, knowing the right tool for the job makes all the difference. Start small, read the guidelines, and engage with the community. That’s how you contribute meaningfully to the world’s free encyclopedia.
