Imagine spending hours writing a detailed entry on a local musician, only to find a week later that someone else wrote a similar page with a slightly different title. Now you face a choice: keep both, combine them, or send one to the digital trash. This is the daily reality for thousands of Wikipedia is a free, web-based, collaborative encyclopedia project that allows anyone to edit articles. Wikipedia relies on community consensus to maintain quality, which means decisions about content aren't made by a single administrator but through a structured process. Whether you are a new editor or a veteran contributor, knowing when to merge, redirect, or delete is crucial for maintaining the encyclopedia's integrity.
Without a clear strategy, the platform risks becoming cluttered with duplicates, dead links, and irrelevant information. The goal isn't just to remove content but to organize knowledge efficiently. This guide breaks down the specific scenarios where each action applies, offering a practical framework to help you make the right call without triggering unnecessary edit wars.
Understanding the Three Core Actions
Before making a move, you need to understand what each action actually does to the data structure of the site. These aren't just buttons; they represent different philosophies of information management.
Deletion is the most drastic measure. It removes an article from the main namespace entirely. This isn't just hiding the page; it prevents the title from being reused for a new article unless the deletion is overturned. Article for Deletion is a process on Wikipedia where editors discuss whether an article should be deleted. AfD is the standard venue for debating controversial deletions. When a page is deleted, the content usually moves to a deleted archive, accessible only to administrators, unless it was a clear case of vandalism.
Redirects are traffic signs. Instead of deleting a page, you turn it into a signpost that automatically sends readers to a different, more appropriate page. For example, if someone searches for "Tomato Plant," a redirect sends them to the main "Tomato" article. This preserves the link history and ensures that users don't hit a dead end. Redirects are essential for handling common misspellings, alternative names, or narrower topics that belong under a broader umbrella.
Merges combine the content of two or more articles into a single, comprehensive entry. This is the preferred solution when two articles cover the same subject but are fragmented. Merging preserves the history of both pages in the edit log, ensuring that contributors get credit for their work. It is more labor-intensive than deleting but maintains more information for the reader.
When to Delete: The Notability Threshold
Deletion is often the most contentious action because it feels like censorship to the author. However, Notability is a policy on Wikipedia that determines whether a topic deserves its own article. WP:N sets the bar high. If a topic lacks significant coverage in reliable, independent sources, it generally does not belong as a standalone article.
Consider a local business that has only been mentioned in its own press releases. While the business exists, it fails the notability test because there is no independent verification of its significance. In this case, deletion is the correct path. Keeping such articles clutters the search results and dilutes the quality of the encyclopedia.
There are also cases where deletion is immediate and non-negotiable. These are known as Speedy Deletion criteria. If an article is pure vandalism, blatant advertising, or contains copyrighted material that has been pasted from another site without permission, it can be removed instantly. You don't need a debate for a page that is clearly a spam link or a personal attack.
However, if you are unsure, do not delete immediately. Tag the page for discussion. This allows other editors to weigh in. Sometimes, a topic seems non-notable at first glance, but a quick search reveals a major news story you missed. Deleting prematurely can lead to accusations of bias and damage your reputation as a contributor.
When to Redirect: The Navigation Strategy
Redirects are the glue that holds the site's navigation together. They are particularly useful for handling synonyms and common variations. If you have an article titled "Electric Vehicle," you might want to create redirects for "EV" or "Battery Electric Vehicle." This ensures that no matter how a user phrases their search, they land on the right information.
Redirects are also the solution for disambiguation. If a term has multiple meanings, you don't delete the pages; you create a disambiguation page that lists the options. For instance, "Apple" could refer to the fruit or the technology company. A redirect from "Apple (fruit)" to the specific article helps clarity.
One common mistake is creating a redirect to a section within a page. While some editors do this, it is often discouraged because it breaks the flow of the article. Instead, use the redirect to point to the main page and let the reader find the section via the Table of Contents. This keeps the internal linking structure clean and predictable.
Redirects also preserve link juice. If an external website links to an old page title, a redirect ensures that link still works. Without it, you would create a broken link, which is bad for the reader and bad for the site's overall health. Think of a redirect as a courtesy to the user who might have bookmarked an old URL.
When to Merge: Combining Fragmented Knowledge
Merging is the most constructive action. It happens when two articles are essentially about the same thing but have been split unnecessarily. For example, you might find one article on "World War II Aircraft" and another on "WWII Planes." These are identical topics with slightly different titles. Merging them creates a single, stronger article with all the history combined.
The decision to merge often requires careful editing. You cannot simply copy-paste one page into another. You need to remove duplicate information, smooth out the transitions, and ensure the citations are consistent. This requires a good understanding of the subject matter. If you merge two articles on complex medical topics, you need to ensure that the medical information remains accurate and doesn't get muddled in the process.
Merges are also appropriate when a sub-topic is too small to stand alone but too detailed to be just a sentence. If you have an article about a minor character in a popular TV show, but the character appears in multiple episodes, it might be better to merge that character's history into the main episode guide or the main show article, depending on the depth of the content.
There is a specific tool called the "Merge" tool on the edit page. Using this tool automatically adds a tag to the talk pages of both articles, notifying other editors of your intent. This is a best practice because it prevents you from overwriting someone else's work. It signals that you are proposing a change, not forcing it.
The Decision Framework: A Step-by-Step Guide
To make the right choice, follow this logical flow. It helps you avoid emotional reactions and stick to policy.
- Check for Sources: Does the article have reliable, independent citations? If no, it likely fails notability. Move to deletion.
- Check for Duplicates: Is there another article covering the exact same topic? If yes, move to merge or redirect.
- Assess Content Quality: Is the content well-written and neutral? If it is poorly written but notable, consider improving it first. If it is spam, delete it.
- Consider User Intent: If a user searches for this term, where do they want to go? If they want a specific page, keep it or redirect. If they want nothing, delete it.
- Consult the Talk Page: Before making big changes, check the talk page. Has this been discussed before? If yes, follow the consensus. If no, start a discussion.
This framework ensures you are making decisions based on evidence and community standards rather than personal preference. It also protects you from edit wars. If you follow the policy, other editors are less likely to revert your changes.
Remember that Consensus is the process by which Wikipedia editors agree on the content and direction of articles. Community Consensus is the ultimate authority. Even if you are right about the policy, if the community disagrees, you may need to step back. The goal is a functional encyclopedia, not a victory in an argument.
Community Etiquette and Conflict Resolution
Wikipedia is a social platform as much as it is an informational one. How you propose a deletion or merge matters as much as the action itself. If you delete a page without explanation, you will likely be reverted and possibly blocked. Always leave a note on the talk page explaining your reasoning.
Use the standard templates available. There is a specific template for nominating a page for deletion. There is also a template for proposing a merge. Using these templates makes your intent clear to other editors. It signals that you are following the rules.
If you encounter resistance, don't escalate. If someone disagrees with your deletion nomination, engage in a discussion. Provide links to the policies that support your view. If you cannot reach an agreement, you can request a third-party opinion. There are experienced editors who specialize in resolving disputes. They can look at the situation objectively and help you find a solution.
Be careful with Deletionism is a viewpoint on Wikipedia that favors deleting articles that do not meet strict notability criteria. Deletionist Viewpoint can sometimes lead to removing valid content. On the other hand, Inclusionism is a viewpoint on Wikipedia that favors keeping articles even if they have minor flaws. Inclusionist Viewpoint can lead to clutter. The middle ground is usually the best approach. Keep what is notable, merge what is redundant, and delete what is useless.
Comparison of Actions
| Action | Best Use Case | Impact on History | Community Effort |
|---|---|---|---|
| Delete | Non-notable, Vandalism, Spam | Content archived, title freed | Low (if speedy), High (if AfD) |
| Redirect | Aliases, Misspellings, Disambiguation | History preserved, redirects to target | Low |
| Merge | Duplicates, Overlapping Topics | History combined, content unified | High (requires editing) |
Choosing the right action saves time in the long run. Deleting a page that should have been merged wastes the work of the original author. Redirecting a page that should have been deleted keeps spam alive. Taking the time to assess the situation correctly ensures that the encyclopedia remains a reliable resource for everyone.
Can I delete a page I wrote myself?
Yes, you can delete your own page, but it is often better to tag it for deletion. This allows other editors to review it. If you delete it yourself, you might lose the ability to restore it later if you change your mind.
What happens if I merge two articles incorrectly?
If a merge is done incorrectly, other editors can revert it. The history of both pages is preserved in the edit log, so the content can be separated again if necessary. Always use the merge tool to track the process.
How long does an Article for Deletion discussion last?
A standard AfD discussion usually lasts for seven days. This gives the community enough time to gather sources and debate the notability of the topic before a final decision is made.
Should I delete a redirect that points to a deleted page?
Yes, if the target page is deleted, the redirect becomes broken. It should be deleted or redirected to a relevant alternative page. Broken redirects confuse users and waste server resources.
Is it okay to merge articles without permission?
It is best to propose the merge on the talk page first. While you don't technically need permission, ignoring the discussion can lead to edit wars. Collaboration ensures the merged article is high quality.
