In brief
- A merge copies some or all of an article into another and then turns the original into a redirect.
- Neither is a deletion. The earlier versions stay in the page history, except after a close of delete and redirect.
- Since 24 March 2026, contested merges are nominated at Articles for Deletion. Uncontroversial merges can still be made by any editor without discussion.
- A bold redirect can be disputed on the talk page. A redirect decided at a deletion discussion needs a new discussion, usually backed by a draft built on coverage the first one did not see.
What does it mean when a Wikipedia page is redirected or merged?
It means the title no longer holds its own article. A redirect sends readers to another page, where a small "Redirected from" line appears under the title. A merge copies some or all of the content into the destination article first, then replaces the original with a redirect. For people known for a single event who are otherwise low-profile, the biographies of living persons policy prefers exactly this.
A redirect is not a deletion. Deletion removes every previous version from public view. When an article is redirected in the normal way, the history stays attached to the redirect, and anyone can read it.
How did the page become a redirect?
By one of several routes, and each is undone differently.
| Route | What happened | Old text still visible? |
|---|---|---|
| Bold merge | An editor judged the merge uncontroversial and carried it out without discussion, which the merging page permits. | Yes, in the history |
| Blank and redirect | An editor replaced a problematic article with a redirect to a suitable target, often called a BLAR. | Yes, in the history |
| AfD closed as merge or redirect | A deletion discussion agreed to fold the article into another or replace it with a redirect. | Yes, in the history |
| AfD closed as delete and redirect | The history was deleted and the title recreated as a redirect, usually because the content was harmful to keep, such as a copyright violation. | No. Only administrators can see it. |
| Page moved | The article was renamed and the old title left behind as a redirect. | The article is still there, under its new title |
How do you find out who redirected the page and why?
Go to the redirect page itself and read its history:
- Click the "Redirected from" link under the destination article's title. That opens the redirect page without following it; the address ends with redirect=no.
- Open "View history". The edit that replaced the article shows the editor's account and an edit summary. A merge after a discussion normally links to it.
- Check both talk pages. Merges, and AfD merges in particular, usually leave notices linking to the discussion.
- Search for a deletion discussion at Wikipedia:Articles for deletion/ followed by the title, with "(2nd nomination)" added for later rounds.
The question that matters most is whether there was a discussion. If there was, the redirect reflects a recorded consensus. If not, it reflects one editor's judgment, which the rules treat differently.
Before you edit anything yourself: every change, deletion discussion and declined draft stays in the page's public record, and reviewers read it. A free page health check tells you what that record already shows.
Request a page health checkCan you still see the old article?
Usually, yes. In the redirect's history, click the date of the last revision before the redirect, and the full article appears as it was, with its references, at a permanent link you can save. Keep the reference list: it shows what the article relied on and, by omission, what coverage it lacked.
After a close of delete and redirect, or where revisions were hidden through revision deletion, ordinary readers cannot open them. Our guide on finding a deleted Wikipedia page explains what can be requested.
Are merge proposals now decided at Articles for Deletion?
Yes, for contested ones. On 24 March 2026 a request for comment found consensus to absorb Proposed article mergers, the separate venue merge debates used to have, into Articles for Deletion, where discussions run for at least seven days. The closing statement added that bold merges remain permissible and that consensus to merge can still be reached by other means, such as a talk page.
So an AfD notice on your article may be a merge nomination rather than a deletion one, and the AfD instructions warn that a nomination to merge may finish as a redirect instead. Our guide to Articles for Deletion covers how those discussions run.
Can a redirect be turned back into an article?
Yes, and how depends on how the redirect arose.
After a bold redirect or merge
The deletion policy says that if a blank and redirect is disputed, consensus should be sought before the page is redirected again, preferably at a deletion discussion, with the talk page as an occasional alternative. A person connected to the subject should not restore the article themselves: the conflict of interest guideline strongly discourages connected editors from changing an affected article, and putting it back is that kind of change. The better move is a talk page post listing the independent coverage, for an uninvolved editor to weigh.
After a deletion discussion
Here the redirect rests on a recorded consensus, and the consensus policy says a change to a matter settled by discussion should normally be proposed by discussion. In practice:
- Write a draft built on independent coverage the discussion did not see. A draft can exist alongside a redirect of the same name.
- Raise it with the closer, or on the talk page of the article the redirect points to, linking the draft.
- If the close itself was wrong, or significant new information is being refused, use deletion review, which can allow recreation.
Restoring the old text over the redirect reopens a decided question without new evidence. It is likely to be reverted, and can start an edit war over the redirect itself.
When is a redirect the right outcome?
When the subject lacks enough coverage of its own, or readers understand it better inside a broader article. If the old article was a few paragraphs sourced to the subject's own website and announcements, a well-sourced section elsewhere may be the most accurate and stable coverage available. Editors can tag a redirect as having possibilities, signalling that it could become an article later.
A redirect does not protect the destination section, which is edited like any other. If it is wrong, the usual routes apply: correcting Wikipedia and Wikipedia edit requests. A redirect pointing somewhere misleading can be edited to point elsewhere, and requests to delete one go to Wikipedia:Redirects for discussion.
Why does the redirect's record matter for any comeback?
Because the people who review a new article read how the old one ended: the redirect's history, its edit summary, the merge notices and any archived AfD with its closing statement. Each failed attempt adds to it. A second AfD is titled as a second nomination, and repeated restorations against consensus can be reported as edit warring.
Raising a bold redirect on the talk page with two strong sources is a step anyone can take properly. Reversing a redirect from a deletion discussion is harder, because the case has to answer a recorded consensus and stand up as a draft at the same time. Our page repair service establishes which route produced the redirect and what the coverage now supports, then prepares the draft and the request where the evidence is there. We cannot promise a result. For a plain reading of your redirect's history, ask for a free page health check.
Wikipedia policies and pages referred to
- Wikipedia:Merging
- Wikipedia:Redirect
- Help:Redirect
- Wikipedia:Deletion policy
- Wikipedia:Articles for deletion
- Wikipedia:Requests for comment/Merging merge discussions with AfD
- Wikipedia:Proposed article mergers
- Help:Page history
- Wikipedia:Consensus
- Wikipedia:Drafts
- Wikipedia:Biographies of living persons
- Wikipedia:Conflict of interest
- Wikipedia:Redirects for discussion
- Wikipedia:Deletion review