A redirect is a page that automatically sends readers to another page, usually an article or section of an article. For example, if you type "UK" in the search box or click on the wikilink UK, you will be taken to the article United Kingdom with a note at the top of the page (or on mobile, in a black message bar at the bottom): "(Redirected from UKUK)". This is because the page UKUK contains wikitext that defines it as a redirect page and indicates the target article. It is also possible to redirect to a specific section of the target page.
Redirect pages can contain other content below the redirect, such as redirect category templates, and category links (which provide a way to list article sections in categories).
Closely related words (for example, Symbiont redirects to Symbiosis).
Adjectives or adverbs point to noun forms (e.g., Treasonous redirects to Treason)
Less specific forms of names, for which the article subject is still the primary topic. For example, Einstein redirects to Albert Einstein, whereas Albert is a disambiguation page rather than a redirect, since no Albert is regarded as the primary topic for that name.
Abbreviations and initialisms (for example, ADHD redirects to Attention deficit hyperactivity disorder). But often an abbreviation will have multiple meanings, none of which is a primary topic—in that case a disambiguation page should be created rather than a redirect.
Punctuation issues—some titles containing dashes should have redirects using hyphens, and vice versa. The proper title depends on official spelling (in the case of a name, such as Olivia Newton-John), or established Wikipedia policy and naming conventions (such as Spanish–American War).
Likely misspellings (for example, Condoleeza Rice redirects to Condoleezza Rice). Note: this criterion typically does not apply to redirects from typos in the template namespace; consensus is that such typos, unless they are very common, should remain as red links until they are fixed.
Likely alternative capitalisations (for example, Natural Selection redirects to Natural selection). This is not necessary for user searches made via Wikipedia's search engine, but may aid linking from other articles and external sites, as well as direct URL entry.
To retain edit history for attributing copied or merged content per Wikipedia:Copying within Wikipedia for copyright licensing requirements.
To retain nontrivial edit history.
Subtopics or other topics that are described or listed within a wider article. (Such redirects are often targeted to a particular section of the article.)
Redirects to disambiguation pages that do not contain "(disambiguation)" in the title (for example, Durham (disambiguation) redirects to Durham). These help maintenance by allowing deliberate links to disambiguation pages to be distinguished from links that need to be disambiguated. See WP:INTDAB for a fuller explanation.
Note that redirects to other Wikimedia wikis, other websites, special pages, or direct file links (Media: namespace) do not work. These should be avoided or replaced with a {{soft redirect}} template. Soft redirects are also used in category space (using the {{category redirect}} template). Redirects from list titles to categories (e.g. a redirect from [[List of things]] to [[Category:Things]]) are highly discouraged.
To create a basic redirect using the source editor, type #REDIRECT [[target page name here]] as the only text on the page. The capitalization of the word REDIRECT doesn't matter. For instance, if you were redirecting from "UKUK" to "United Kingdom", this would be the entire body of the "UK" pageUK:
#REDIRECT[[United Kingdom]]
If desiring to categorize the redirect, you may add redirect category templates (rcats) (optionally with the shell template) with each rcat on a separate line. For example:
{{Redirect category shell|{{R to section}}{{printworthy}}}}
Sometimes an existing redirect should really be handled by a full article, per Category:Redirects with possibilities. For example, the name of a notable musician (who does not yet have an article) may instead be a redirect to an existing article about a band of which the musician is a member. In this case, you can edit the redirect to make it into an article. Also, if an existing redirect points to the wrong page, you can edit the redirect to point to a different page.
If you want to edit a redirect page you must use a special technique in order to get to the redirect page itself. This is because when you try to go straight to the redirect page and edit it, the redirect page will automatically redirect you to its target page (because this is what a redirect page is meant to do). Below is an example of why you might need to go to a redirect page itself (to do a small edit) and how to actually get there.
#REDIRECT[[Secretary-General of the United Nations]]
to
#REDIRECT[[Trygve Lie]]
When adding or changing a redirect, always verify the links that already point there. For instance, if another person named Trygve Lie becomes very well known, it would make sense to make Trygve Lie a redirect to his page (after renaming the existing Trygve Lie page). Such a change cannot be made without changing all the preexisting links to Trygve Lie; these links can be found by clicking on What links here in the left-hand menu. Also, when changing the target of a redirect verify that its talk page is not also a redirect and if it is, either retarget it to the current target's talk page, replace the redirect with {{talk page of redirect}} or if you turned the redirect into an article, remove it entirely unless WP:TALKCENT applies. If the redirect is connected to a Wikidata item (in which case it is a member of Category:Redirects connected to a Wikidata item), also verify that it makes sense to keep it connected to that item.
Most redirects are untargeted, i.e. they lead simply to a page, not to any specific section of the page. This is usually done when there is more than one possible name under which an article might be sought (for example, Cellphone redirects to the article Mobile phone). For deciding which should be the actual title of the article, see WP:Article titles.
It is also possible to create a targeted redirect, i.e. a redirect to a particular point on the target page—either a section header or an anchor. For example, the page Malia Obama contains the code #REDIRECT[[Family of Barack Obama#Malia and Sasha Obama]], which redirects to the Malia and Sasha Obama section in the article Family of Barack Obama. Therefore, entering Malia Obama will bring the searcher straight to the content that deals with "Malia and Sasha Obama".
Consider that when the target page is displayed, it is likely that the top of the page will not be shown, so the user may not see the helpful "(redirected from...)" text unless they know to scroll back to the top. This is less likely to cause confusion if the redirect is to a heading with the same name as the redirect.
It is usually appropriate to give a redirect-to-target article its own short description, otherwise search operations and wp:annotated links will display the description in place for the whole article. The {{short description}} line must immediately follow the #Redirect line.
A retarget in a redirect can either mean changing the page or changing the section that a redirect goes to. The term is used in redirects for discussion as an alternative to deleting it if the redirect can instead serve a purpose in targeting a different place in Wikipedia. The related term refine is used in RfD to mean retargeting a redirect to a specific section of its target page.
The text given in the link on a targeted redirect page must exactly match the target section heading or anchor text, including capitalization and punctuation.
For example, the Horsecart article may redirect to the Horse-drawn carts subsection of the Cart article by writing the destination as [[Cart#Horse-drawn carts]]. However, if (for example) someone in the future renames the Horse-drawn carts subsection to Carts drawn by horses or Horse-powered carts or anything else, the Horsecart redirect would break and instead go to the beginning of the Cart article.
To prevent this, it is recommended to use the {{subst:anchor}} template to create an explicit target anchor in the page. Anchors for section headings are ideally placed directly before the name of the heading, after the opening equals signs:
Now the Horsecart article may redirect to [[Cart#Horsecart]], and the redirect will not break if the Horse-drawn carts subsection is later renamed.
The {{subst:Anchor}} should be substituted in such cases because otherwise, when the section is edited via its own "[edit]" link, the anchor markup and alternative section title(s) will appear as undesirable clutter at the beginning of revision history entries, among other accessibility and technical issues.
The anchor text will not be visible on the page, but it will serve as a permanent marker of that place on the page. Editors should generally not remove or alter such anchors without checking all incoming links and redirects. If several logically independent aspects of a topic are discussed under a single section header and should be linked to, it is sometimes useful to define separate anchors for them, if the current amount of information doesn't justify a division into multiple sections already. This makes it easier to rearrange contents on a page as it develops since those anchors can be moved with their corresponding contents without a need to fix up incoming links.
Be careful with anchor capitalization, as redirects are case-sensitive in standards-compliant browsers.
Anchors may also be used to create a redirect to a point on the page other than a section heading. For example, in the Google Search article, the text {{Anchor|calculator}} is placed at the point where Google Calculator is discussed. The Google Calculator page can then be redirected to Google Search#calculator.
Alternatively, a hidden comment can be put in the target text, to inform other editors that a section title is linked, so that if the title is altered, the redirect can be changed. For example:
In the above example, where Horsecart redirects to [[Cart#Horse-drawn carts]], someone who is about to rename the Horse-drawn cart subsection could then also change the destination of the Horsecart redirect, preventing it from breaking. However, this is not ideal since it puts the workload on the editor seeking to change the section title.
When a section title is known to be the target of incoming links, the Wikipedia Manual of Style suggests creating a redundant anchor with the same name as the section title, so that such links will continue to work even if someone renames the section without creating an anchor with the old name. Technically, the redundant section and anchor names result in invalid HTML. However, when a document contains multiple tags with the same id value, browsers are required to return the first one, so in practice, this is not a problem.
↑While spaces and underscores are interchangeable in the current implementation of the MediaWiki software, it is generally good practice and aids maintenance to use exactly the same spelling in links as is used in the corresponding targets also for these characters. In the absence of a match, the reader will simply be taken to the top of the target page.
↑"Syntax of anchor names". HTML 4.01 Specification - W3C Recommendation. W3C. 24 December 1999. Retrieved June 3, 2022.
The software will not follow chains of more than one redirect—this is called a double redirect. A redirect should not be left pointing to another redirect page.
Double redirects often arise after a page is moved (renamed)—after moving a page, check whether there are any redirects to the old title (using the link on the move result page, or using "What links here"), and change them to redirect straight to the new title. Double redirects are usually fixed by a few specialised bots in a few hours; however, an editor should not leave behind any self-created double redirects.
You can link to a redirect page just as you can link to an article page by placing the redirect page name within a set of double brackets, such as:
[[Redirect page name]]
replacing Redirect page name with the name of the redirect page to link.
To link to a redirect page without following the underlying redirect, use: {{No redirect|Redirect page name}} replacing Redirect page name with the name of the redirect page to link. Clicking on a no-redirect link will send the reader to the redirect page rather than the final redirect destination.
Most redirect pages are not placed in article categories. There are three types of redirect categorization that are helpful and useful:
Maintenance categories are in use for particular types of redirects, such as Category:Redirects from initialisms, in which a redirect page may be sorted using the {{R from initialism}} template. One major use of these categories is to determine which redirects are fit for inclusion in a printed subset of Wikipedia. See WP:Template messages/Redirect pages for functional and alphabetical lists of these templates. A brief functional list of redirect category (rcat) templates is also found in the {{R template index}} navbar.
Sometimes a redirect is placed in an article category because the form of the redirected title is more appropriate to the context of that category, e.g. Honey Lantree used to redirect to the band article The Honeycombs, but the redirect was placed in Category:1943 births and other categories which related to Lantree as an individual. (Redirects appear in italics in category listings.)
Discussion pages. If a discussion/talk page exists for a redirect, please ensure (1) that the talk page's WikiProject banners are tagged with the "class=Redirect" parameter and (2) that the talk page is tagged at the TOP with the {{Talk page of redirect}} template. If the discussion page is a redirect, then it may be tagged with appropriate redirect categorization templates (rcats).
Redirects from moves
When a page is renamed/moved, a redirect that is titled with the replaced page name is created and is automatically tagged with the {{R from move}} template. This sorts the redirect into Category:Redirects from moves.
To delete a redirect without replacing it with a new article, list it on redirects for discussion. See the WP:Deletion policy for details on how to nominate pages for deletion.
Listing is not necessary if you just want to replace a redirect with an article, or change where it points (see these instructions for help doing this). If you want to swap a redirect and an article, but are not able to move the article to the location of the redirect, please use Wikipedia:Requested moves to request help from an admin in doing that.
The major reasons why deletion of redirects is harmful are:
a redirect may contain non-trivial edit history;
if a redirect is reasonably old (or is the result of moving a page that has been there for quite some time), then it is possible that its deletion will break incoming links (such as links coming from older revisions of Wikipedia pages, from edit summaries, from other Wikimedia projects or from elsewhere on the internet, do not show up in "What links here").
Therefore consider the deletion only of either harmful redirects or of recent ones.
You might want to delete a redirect if one or more of the following conditions is met:
The redirect page makes it unreasonably difficult for users to locate similarly named articles via the search engine. For example, if the user searches for "New Articles", and is redirected to a disambiguation page for "Articles" (itself a redirect to "Article"), it would take much longer to get to the newly added articles on Wikipedia.
The redirect might cause confusion. For example, if "Adam B. Smith" was redirected to "Andrew B. Smith", because Andrew was accidentally called Adam in one source, this could cause confusion with the article on Adam Smith, so the redirect should be deleted.
The redirect is offensive or abusive, such as redirecting "Joe Bloggs is a Loser" to "Joe Bloggs" (unless "Joe Bloggs is a Loser" is legitimately discussed in the article), or "Joe Bloggs" to "Loser". (Speedy deletion criterion G10 and G3 may apply.) See also§Neutrality of redirects.
It is a cross-namespace redirect out of article space, such as one pointing into the User or Wikipedia namespace. The major exception to this rule are the pseudo-namespace shortcut redirects, which technically are in the main article space. Some long-standing cross-namespace redirects are also kept because of their long-standing history and potential usefulness. "MOS:" redirects, for example, were an exception to this rule until they became their own namespace in 2024. (Note also the existence of namespace aliases such as WP:. Speedy deletion criterion R2 may apply if the target namespace is something other than Category:, Template:, Wikipedia:, Help:, or Portal:.)
If the redirect is broken, meaning it redirects to an article that does not exist, it can be immediately deleted under speedy deletion criterion G8. You should check that there is not an alternative place it could be appropriately redirected to first and that it has not become broken through vandalism.
If the redirect is a novel or very obscure synonym for an article name that is not mentioned in the target, it is unlikely to be useful. In particular, redirects in a language other than English to a page whose subject is unrelated to that language (or a culture that speaks that language) should generally not be created. (Implausible typos or misnomers are candidates for speedy deletion criterion R3, if recently created.) The message template {{subst:not mentioned}} may be useful.
If the target article needs to be moved to the redirect title, but the redirect has been edited before and has a history of its own, then the title needs to be freed up to make way for the move. If the move is uncontroversial, tag the redirect for G6 speedy deletion, or alternatively (with the suppressredirect user right; available to page movers and admins), perform a round-robin move. If not, take the article to Requested moves.
If the redirect could plausibly be expanded into an article, and the target article contains virtually no information on the subject.
If the redirect ends in "(disambiguation)" but does not target a disambiguation page or a page performing a disambiguation-like function (such as a set index of articles). Speedy deletion criterion G14 may apply.
They have a potentially useful page history, or an edit history that should be kept to comply with the licensing requirements for a copy or merge (see Wikipedia:Copying within Wikipedia and Wikipedia:Merge and delete). On the other hand, if the redirect was created by renaming a page with that name, and the page history just mentions the renaming, and for one of the reasons above you want to delete the page, copy the page history to the Talk page of the article it redirects to. The act of renaming is useful page history, and even more so if there has been discussion on the page name.
They would aid accidental linking and make the creation of duplicate articles less likely, whether by redirecting a plural to a singular, by redirecting a frequent misspelling to a correct spelling, by redirecting a misnomer to a correct term, by redirecting to a synonym, etc. In other words, redirects with no incoming links are not candidates for deletion on those grounds because they are of benefit to the browsing user. Some extra vigilance by editors will be required to minimize the occurrence of those frequent misspellings in article text because the linkified misspellings will not appear as broken links; consider tagging the redirect with the {{R from misspelling}} template to assist editors in monitoring these misspellings.
They aid searches on certain terms. For example, users who might see the "Keystone State" mentioned somewhere but do not know what that refers to will be able to find out at the Pennsylvania (target) article.
Deleting redirects runs the risk of breaking incoming or internal links. For example, redirects resulting from page moves should not normally be deleted without good reason. Links that have existed for a significant length of time, including CamelCase links (e.g. WolVes) and old subpage links, should be retained in case there are any existing links on external pages pointing to them. Please tag these with {{R from old history}}. See alsoWikipedia:Link rot §Link rot on non-Wikimedia sites.
Someone finds them useful. Hint: If someone says they find a redirect useful, they probably do. You might not find it useful—this is not because the other person is being untruthful, but because you browse Wikipedia in different ways. Evidence of usage can be gauged by using the wikishark or pageviews tool on the redirect to see the number of views it gets.
Just as article titles using non-neutral language are permitted in some circumstances, so are such redirects. Because redirects are less visible to readers, more latitude is allowed in their names, therefore perceived lack of neutrality in redirect names is not a sufficient reason for their deletion. In most cases, non-neutral but verifiable redirects should point to neutrally titled articles about the subject of the term. Non-neutral redirects may be tagged with {{R from non-neutral name}}.
Non-neutral redirects are commonly created for three reasons:
The subject matter of articles may be represented by some sources outside Wikipedia in non-neutral terms. Such terms are generally avoided in Wikipedia article titles, per the words to avoid guidelines and the general neutral point of view policy. For instance the non-neutral expression "AttorneygateAttorneygate" is used to redirect to the neutrally titled 2006 dismissal of U.S. attorneys. The article in question has never used that title, but the redirect was created to provide an alternative means of reaching it because a number of press reports use the term.
The exceptions to this rule are redirects that are not established terms and are unlikely to be useful, and therefore may be nominated for deletion, perhaps under deletion reason #3. However, if a redirect represents an established term that is used in multiple mainstream reliable sources, it should be kept even if non-neutral, as it will facilitate searches on such terms. Please keep in mind that RfD is not the place to resolve most editorial disputes.
What needs to be done on pages that are targets of redirects?
Wikipedia follows the "principle of least astonishment"; after following a redirect, the reader's first question is likely to be: "Hang on... I wanted to read about this. Why has the link taken me to that?" Make it clear to the reader that they have arrived in the right place.
Most (but not all) "inbound redirects" other than misspellings or other obvious close variants of the article title should be mentioned in the first couple of paragraphs of the article or section to which the redirect goes. It will often be appropriate to put the redirected term in bold at its first occurrence in the target. For example:
Alice Bradley Sheldon (August 24, 1915 – May 19, 1987) was an American science fiction and fantasy author better known as James Tiptree Jr. ...
If other similarly titled pages exist, a hatnote may be placed at the top of the target article or targeted section that will direct readers to the other meanings or to a relevant disambiguation page. This is usually done using one of the redirect disambiguation templates(examples).
Removing all content in a problematic article and replacing it with a redirect is common practice, known as blanking and redirecting. If other editors disagree with this blanking, its contents can be recovered from page history, as the article has not been deleted. If editors cannot agree, the content issues should be discussed at the relevant talk page, and other methods of dispute resolution should be used, such as restoring the article and nominating the article for redirection at Articles for deletion.
The article creator or significant contributors may be notified using {{uw-blar}}, if desired. To make it easier for other editors to find the history of the blanked article, a short notice may be added on the redirect's talk page using {{Blank and redirect notice}}.
Note that certain forms of blanking are not allowed.
Illegitimate blanking of valid content without reason is considered vandalism. Other forms of blank-and-redirect, although not vandalism, are still undesirable. If you want to rename the article to a different title, you should instead move the page with the Move option. If you want to keep some content from the blanked article and add it to another article, you should follow the instructions at Wikipedia:Merging §How to merge. Both processes will create proper links to the edit history, which is required by the Wikipedia license to preserve attribution of content to its authors.
Do not "fix" links to redirects that are not broken
There is usually nothing wrong with linking to redirects to articles. Some editors are tempted, upon finding a link to a redirect page, to bypass the redirect and point the link directly at the target page. However, changing to a piped link is beneficial only in a few cases. Piping links solely to avoid redirects is generally a time-wasting exercise that can actually be detrimental. It is almost never helpful to replace [[redirect]] with [[target|redirect]].
That is, editors should not change, for instance, [[Franklin Roosevelt]] to [[Franklin D. Roosevelt]] or [[Franklin D. Roosevelt|Franklin Roosevelt]]just to "fix a redirect". However, it is acceptable to change it to [[Franklin D. Roosevelt]] if it is preferred that "Franklin D. Roosevelt" actually appear in the visible text. Editors should also not change redirects with possibilities like [[Journal of the Franklin Institute]] to [[Franklin Institute#Journal of the Franklin Institute|Journal of the Franklin Institute]], so that readers arrive at the more pertinent article in the eventuality that it is created.
Introducing unnecessary wikitext makes the article more difficult to read in page source form.
Non-piped links make better use of the "what links here" tool, making it easier to track how articles are linked and helping with large-scale changes to links.
Shortcuts or redirects to embedded anchors or sections of articles or of Wikipedia's advice pages should never be bypassed, as the anchors or section headings on the page may change over time. Updating one redirect is far more efficient than updating dozens of piped links. (The Rdcheck tool is extremely useful in such cases for finding which redirects need to be changed after an article is updated.)
Intentional links to disambiguation pages always use the title with "(disambiguation)", even if that is a redirect.
If editors persistently use a redirect instead of an article title, it may be that the article needs to be moved rather than the redirect changed. As such the systematic "fixing of redirects" may eradicate useful information that can be used to help decide on the "best" article title.
It is an {{R from former name}}, and in its context of use, this was the contemporary name. For example, when discussing contemporary news coverage of World War II, using the name a publication had then makes better sense than using its modern name.
It is usually preferable not to use redirected links in navigational templates, such as those found at the bottom of many articles (e.g., {{US presidents}} at the end of George Washington). When a template is placed on an article and contains a direct link to the same article (rather than a redirect), the direct link will display in bold (and not as a link), making it easier to navigate through a series of articles using the template. There are exceptions to this exception: where a redirect represents a distinct sub-topic within a larger article and is not merely a variant name, it is preferable to leave the redirect in the template.
It may be appropriate to make this kind of change if the hint or tooltip that appears when a user hovers over the link is misleading (see Principle of least astonishment).
Spelling errors and other mistakes should be corrected. Don't link to a misspelled redirect. This does not necessarily mean that the misspelled redirect should be deleted (see {{R from misspelling}}).
Radio and TV station call letters, since call letters given up by one station can be used later by a different station.
In other namespaces, particularly the template and portal namespaces in which subpages are common, any link or transclusion to a former page title that has become a redirect following a page move or merge should be updated to the new title for naming consistency.
Links on the Main Page, to avoid stealthy vandalism by retargeting high-traffic redirects. Main Page links that point to an article section should utilise a section link.
Avoid linking to titles that redirect straight back to the page on which the link is found. This situation may arise if a redirect is created from a red link on the page, or if the title was once a separate page but was merged.
However, linking to a title that redirects to a section or anchor within the article (redirects with {{R to section}} or {{R to anchor}}) is acceptable, as it facilitates navigation, in particular on long articles that cannot be viewed all at once on an average-sized computer screen. In addition to readability benefits, when such redirects are marked with {{R with possibilities}}, they have the potential to become independent articles in the future. However, consider using section links instead, when such redirects do not already exist.
A template can be redirected to another template in the same way, e.g., by entering the following markup at the top of a template T2:
#REDIRECT[[Template:T1]]
This allows the template name T2 to be used instead of the actual template name T1. All the parameters of T1 will be respected by T2.
A redirect categorisation (rcat) template such as {{R from move}} may be added to T2 (on the third line below the #REDIRECT line) as follows:
#REDIRECT[[Template:T1]]{{Redirect category shell|{{R from move}}}}
While template shortcut/alias redirects are common, they may infrequently cause confusion and make updating template calls more complicated. For example, if calls to T1 are to be changed to some new template NT1, articles must be searched for {{T1}} and a separate search must also be made for each of its aliases (including T2 in this example). Moreover, changes to syntax, corrections, scans and other processes (for example tag dating) must take into account all applicable redirects.
Redirects in other namespaces may be protected for technical reasons or are protected under existing guidelines. For example, a template redirect (shorthand) used thousands of times qualifies it as a highly visible template eligible for template protection.
Do not create inter-category redirects by adding #REDIRECT [[Target page]] to a category page. Unlike when renaming articles, categories cannot be redirected using "hard" redirects. Articles added to a redirected category will not show up in the target category. And since redirected categories do not become "red links", editors will not be aware when they add an article to a redirected category.
Instead, a form of "soft redirect" may be used in limited circumstances. You can create a category redirect by adding {{Category redirect|target}} to the category page. Bots patrol these categories and move articles to the "target" of the redirect.
If you need to add a redirect category to a {{Category redirect}}, use the template's second parameter. For example: {{Category redirect| Years of the 19th century in Ceylon |{{R from category navigation}}{{R from template-generated category}}}}
Category redirects are costly. While placing a page in a category redirect is not a big problem, it is a problem. There are plenty of helpful uses of category redirects, but category redirects are not as cheap as regular redirects. Links to article redirects are not broken: i.e. click on the link and you are automatically redirected to its target. However, links to category redirects are broken and need to be fixed, except when resolved by a template (i.e. the template generates categories using a pattern, and some of the resulting category names are intentionally resolved by the use of {{Resolve category redirect}} within the template, as in the Ceylon example above). Placing a page into a category redirect makes it show up in the category redirect–not its target–until a bot comes along and fixes the link.
Module redirects
It is possible to redirect a module, however it uses a different syntax. To redirect Module:A to Module:B, add the line returnrequire[[Module:B]] to Module:A. For Cross-namespace redirects from module space like redirecting Module:Example to Template:Example, change the content model to wikitext and use the regular syntax #REDIRECT[[Template:Example]] on the module page.
When a page is moved, a redirect is automatically left behind. Some groups of users (those who possess a suppressredirectright) have the ability to prevent the redirect being created, by unchecking the box labelled "Leave a redirect behind." Currently these groups are administrators, bots, page movers, and global rollbackers. In some circumstances, a page should be moved, but a redirect from its current name is inappropriate, such as reverting page-move vandalism. Suppressing the redirect can avoid an extra action (page removal) and save time in these cases.
However, in general, the redirect will be a useful entry in the history, and it is best to leave it behind, unless there is a good reason to suppress the redirect, such as vandalism, userfyingrecently created malplaced items or freeing a title to be occupied immediately by another page (e.g., moving term to accurate term and term (disambiguation) to term). Redirects leave a trail to help readers find the old article, in case a new article is created at its previous location, and to prevent linkrot. Therefore, we usually neither suppress nor delete redirects. As Brooke Vibbersaid, "Not breaking links helps everyone, especially us first and foremost". She also said that the removal of (file) redirects is "extremely user-hostile and makes the project less useful".
Some types of pages (such as user JSON pages) do not support redirects, as a result, if such a page is moved by any user, page mover or not, a redirect will not be left behind.
Technical notes
A Wikipedia redirect is not the same as an HTTP redirect—it does not generate an HTTP 302 (or other 30x) response. Instead, a page with almost the same content as the target of the redirect is generated by the MediaWiki software, differing in that a small-text note appears below the title of the page, identifying the name of the redirect used to get there (and linking to it in such a way that it can be accessed without the redirect, e.g. so it can be changed). When a user clicks on a redirect such as housecat, the page URL initially will be https://en.wikipedia.org/wiki/Housecat, but the URL shown by the browser will change to https://en.wikipedia.org/wiki/Cat after the page loads.
On one hand, this allows links like housecat#Characteristics to work as expected, but it also requires redirects to anchors to be implemented as a piece of JavaScript that jumps to an appropriate section after the page has loaded. For example, second-stage boot loader, which is rendered as the URL https://en.wikipedia.org/wiki/Second-stage_boot_loader, is a page defined as a #REDIRECT to Booting#SECOND-STAGE. "SECOND-STAGE", in this case, is a manually defined {{anchor}} (using the markup "=== {{subst:anchor|SECOND-STAGE}} Second-stage boot loader ===") that will persist even if the section is renamed. However, whether a redirect points to a manually defined anchor, or an anchor defined implicitly via a section name, the behavior will be the same: the page will automatically be scrolled down to the pointed-to anchor only after the page finishes loading (at which point the URL bar will also change to reflect the redirected-to URL, including "#anchor" portion, rather than the redirected-from URL).
Notes
↑An RfC closed in 2021 found that [m]ost users believe that AfD should be used to settle controversial or contested cases of blanking and redirecting.
