Wikipedia:Redirect
![]() | This page documents an English Wikipedia editing guideline. Editors should generally follow it, though exceptions may apply. Substantive edits to this page should reflect consensus. When in doubt, discuss first on this guideline's talk page. |
- "WP:REDIRECT" redirects here. For general info and coordination guidelines for all Wikimedia projects, on creating redirects see Help:Redirect.
How to make a redirect (redirect command)
To redirect page A (the redirecting page) to a different page B (the target page), enter the following redirecting command at the top of the redirecting page.
#REDIRECT [[NAME OF PAGE B]]
For example, to redirect the Cambridge University page (redirecting page) to the University of Cambridge page (target page), edit the Cambridge University page and enter:
#REDIRECT [[University of Cambridge]]
You can also redirect to page sections within an article. See Meta:Help:Redirect#A redirect to an anchor:
#REDIRECT [[University of Cambridge#History]]
Redirects to anchors should be used sparingly as the user no longer sees the helpful "(redirected from... )" text at the top of the page. However, redirecting to a heading with the same name as the redirecting page seems rather safe, try for example "Argument from contingency". If the section name changes, the redirect will simply lead to the top of the target article. For redirects to a section heading, leave an editor’s note to remind others that the title is linked, so that if the title is altered, the redirect can be changed: for example:
==Evolutionary implications==<!-- This section is linked from [[Richard Dawkins]] and [[Daniel Dennett]] -->
A more resilient and proactive approach is to insert an {{Anchor}} inside the heading, with a copy-paste of the heading's current title; thus, even if the heading is renamed, its original anchor is preserved and your #links will still work. The above example becomes:
==Evolutionary implications {{Anchor|Evolutionary implications}}==
Undesirable redirects
Do not make double redirects (a redirect that points to another redirect); they do not work (to prevent endless looping, a redirect will not "pass thru" more than one entry; if someone is redirected to a redirect, the chain stops at the first redirect), they create slow, unpleasant experiences for the reader, and they make the navigational structure of the site confusing.
Double redirects are usually created after a move when old redirects are left unchanged and pointing toward an old name.
Another type of undesirable redirect is a self-redirect: an article that redirects to itself through a redirect.
Creating new redirects
You can create a new page in order to make a redirect.
Only the redirect line will be displayed when you save the page.
To go back and edit your redirect after it is working, add ?redirect=no to the end of the URL for your redirect:
http://en.wikipedia.org/wiki/Cambridge_University?redirect=no
If you wish to add a reason, select one of the tags from the Tag column below and add it one space after and on the same line as #REDIRECT [[Wherever]]. For example, on the redirect page University of cambridge,
#REDIRECT [[University of Cambridge]] {{R from other capitalisation}}
That will also add the redirect to the category listed in the Category column below. Note that there must be a space between the end of the redirect code and the template code for this to work properly.
Redirects take effect immediately after saving a page. You may need to clear your cache in order to see these changes.
Categories for redirect pages
- See Wikipedia:Categorizing redirects for situations where categorizing a redirect might be helpful.
Redirects should not normally contain categories that would fit on the target page because it can result in duplicate listings of the same page within a category. Relevant categories should be moved to the main page where the redirect is pointing. In some cases, however, adding categories to a redirect page allows legitimate alternative titles or names to be found in category lists. Redirect pages within categories will appear in italics.
What do we use redirects for?
- Compare the more complete template list in the guideline sub-page: Wikipedia:Template_messages/Redirect_pages and the notations in the corresponding category.
- Use of one of these redirects does not mean two or more can be added, if appropriate. Some redirects will have both alternative spellings, alternative capitalisations, and perhaps be a redirection to a list article entry or section. In the final analysis, all these templates do is establish a categorization of the redirect page, and like articles, more than one category can and frequently should apply.
Spellings, misspellings, tenses and capitalizations
Reason | Usage notes, and text that will be shown on Previewing the page when applied. |
Tag / Category to find articles so tagged | ||
---|---|---|---|---|
Abbreviations |
|
{{R from abbreviation}} | ||
Too short for own article List entry or Section |
Category:Redirects to list entries
When List is more sectionlike in organization, such as list of fictional characters in a fictional universe. |
{{R to list entry}} {{R to section}} | ||
Misspellings |
|
{{R from misspelling}} | ||
Other spellings, other punctuation |
|
{{R from alternative spelling}} | ||
Plurals |
Note that [[greenhouse gas]]es shows up as greenhouse gases, so it is not usually necessary to redirect regular plurals. However third-party websites started adding automatic links to Wikipedia from their topics (see, e.g., [1]). Many of them follow the opposite naming convention, i.e., topics are named in plural, and the link to Wikipedia may land into an empty page, if there is no redirect. |
{{R from plural}} | ||
Related words | {{R from related word}} | |||
Sub-topics or closely related topics that should be explained within the text |
|
{{R with possibilities}} Category:Redirects with possibilities | ||
People who are members of a group, organization, ensemble or team |
|
{{R from member}} Category:Redirects from members | ||
Other capitalisations, to ensure that "Go" to a mixed-capitalisation article title is case-insensitive |
Adding a redirect for mixed-capitalisation article titles (e.g., Isle of Wight) allows going to these articles to be case-insensitive. For example, without the redirect Isle of wight going to "Isle Of wight" or any capitalisation other than exactly 'Isle of Wight' would not find the article Isle of Wight. Why: Articles whose titles contain mixed-capitalisation words (not all initial caps, or not all lower case except the first word) are found only via an exact case match. (Articles, including redirects, whose titles are either all initial caps or only first word capitalised are found via "Go" using a case-insensitive match.) Note: Related redirects are needed only if the article title has two or more words and words following the first have different capitalisations. They are not needed, for example, for proper names which are all initial caps. Examples:
|
{{R from other capitalisation}} |
Alternative names
Reason | Usage notes, and text that will be shown on Previewing the page when applied. |
Tag / Category to find articles so tagged | ||
---|---|---|---|---|
Other names, pseudonyms, nicknames, and synonyms |
|
{{R from alternative name}} | ||
Other names with Historic significance, where subsumed into a modern entity or region. |
Note that in some cases, the entity can have articles under several names, each discussing the period of the entity's history when it had a particular name; see for example Byzantium, Istanbul and Constantinople. Depending upon the age and historic detail known about a principality, many of these might also be tagged with {{[[Template: R with possibilities| R with possibilities]]}} |
{{R from historic name}} | ||
Scientific names |
|
{{R from scientific name}} | ||
Scientific names |
|
{{R to scientific name}} | ||
Other languages |
|
{{R from alternative language}} | ||
Non-ASCII Characters |
|
{{R from ASCII}} | ||
Diacritical marks |
|
{{R from title without diacritics}} |
Miscellaneous and administrative redirects
Reason | Usage notes, and text that will be shown on Previewing the page when applied. |
Tag / Category to find articles so tagged | ||
---|---|---|---|---|
Facilitate disambiguation |
|
{{R to disambiguation page}} | ||
To track statements that date quickly | Template:R for as of
|
{{R for as of}} | ||
To redirect to decade article |
|
{{R to decade}} | ||
To redirect from a shortcut |
|
{{R from shortcut}} | ||
Oldstyle CamelCase links |
|
{{R from CamelCase}} | ||
links autogenerated from EXIF information |
|
{{R from EXIF}} | ||
From school microstub to merge location |
|
{{R from school}} |
- Avoiding broken links (see below)
- Minor but notable topics
Sub-topic or supra-topic redirects (redirect with possibilities) are often temporary, eventually being replaced by fully fledged articles on the sub-topic in question. Be conservative when creating sub-topic redirects — they can sometimes be counter-productive, because they disguise the absence of a proper article from editors. Sub-topic redirects should only be used where the main article has a section or item on the sub-topic. For example, denial of service has a section on distributed denial of service. Sub-topics should be boldfaced on their first appearance in the section, to indicate that they are in fact alternate titles or sub-titles.
In accordance with wikipedia:naming conventions (precision) it is best to have an article at a well-defined, unambiguous term, with redirects from looser colloquial terms, rather than vice versa.
Some editors prefer to avoid redirects and link directly to the target article, as it is reported that redirects lower search engine rankings.[1]
See also: Wikipedia:Template messages/Redirect pages which contains a somewhat longer list of available redirect templates
Renamings and merges
We try to avoid broken links because they annoy visitors. Therefore, if we change the layout of some section of Wikipedia, or we merge two duplicate articles, we always leave redirects in the old location to point to the new location. Search engines and visitors will probably have linked to that page at that url. If the page is deleted, potential new visitors from search engines will be greeted with an edit window. The same is true for anyone who previously bookmarked that page, and so on.
On a small scale, this applies to cases where we had duplicate articles on some subject, or lots of twisty little stubs on different aspects of the same overall subject. On a larger scale, we've had a few fairly major reorganisations:
- Moving away from CamelCase article names
- Moving away from having homepages in the article namespace (see User:Tim Starling/Redirects from : to User: for a partial list)
- Moving away from using subpages in the article namespace
When should we delete a redirect?
To delete a redirect without replacing it with a new article, list it on redirects for discussion. See 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 How do I change a redirect? for instructions on how to do 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 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.
Reasons for deleting
You might want to delete a redirect if one or more of the following conditions is met (but note also the exceptions listed below this list):
- 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", 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.
- The redirect constitutes self-promotion or spam. (Speedy deletion criterion G11 may apply.)
- The redirect makes no sense, such as redirecting "Apple" to "Orange". (Speedy deletion criterion G1 may apply.)
- 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, are an exception to this rule. (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.)
- 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.
Reasons for not deleting
However, avoid deleting such redirects if:
- They have a potentially useful page history, or an edit history that should be kept to comply with the licensing requirements for a merge (see 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 left alone in case there are any existing links on external pages pointing to them. See also Wikipedia: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.
- The redirect is to a closely related word form, such as a plural form to a singular form.
Neutrality of redirects
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:
- Articles that are created using non-neutral titles are routinely moved to a new neutral title, which leaves behind the old non-neutral title as a working redirect (e.g. Climategate → Climatic Research Unit email controversy).
- Articles created as POV forks may be deleted and replaced by a redirect pointing towards the article from which the fork originated (e.g. Barack Obama Muslim rumor → deleted and now redirected to Barack Obama religion conspiracy theories).
- 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 "Attorneygate" is used to redirect to the neutrally titled Dismissal of U.S. attorneys controversy. 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 would be 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?
We follow 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.
Normally, we try to make sure that all "inbound redirects" are mentioned in the first couple of paragraphs of the article. For example:
- James Tiptree, Jr. (August 24, 1915 – May 19, 1987) was the pen name of American science fiction author Alice Bradley Sheldon ...
- James Tiptree, Jr., redirect from Alice Sheldon
- Water (H2O, HOH) is the most abundant molecule ...
- Water (molecule), redirect from H2O
If there is an ambiguity associated with a redirect, one of the redirect disambiguation templates may be useful.
Do not cause a secondary redirect. They do not work like a primary redirect; same with tertiary redirects.
Self-links, duplicate links
Avoid self-links, including self-links through redirects ("loop links"). Also, avoid having two links that go to the same place. These can confuse readers, and cause them to unnecessarily load the same page twice.
Do not change links to redirects that are not broken
Some editors are tempted, upon finding links using a legitimate redirect target, to edit the page to remove the redirect and point the link directly at the target page. While there are a limited number of cases where this is beneficial, it is, in general, an unhelpful exercise.
In many cases where it might seem appropriate to make this change, such as those involving unprintworthy redirects, the better option is to edit the visible text rather than change where the link is pointing. If the linked term is printworthy and presents no other problems to the prose, there is no reason not to just link the term as is. There should almost never be a reason to replace [[redirect]] with [[target|redirect]]. This kind of change is almost never an improvement, and it can actually be detrimental.
Reasons not to change redirects include:
- Redirects can indicate possible future articles.
- Introducing unnecessary invisible text makes the article more difficult to read in page source form.
Furthermore, not only are Wikipedia editors asked not to worry about performance, changing redirects to direct links does not significantly improve performance anyway. See also Wikipedia:Tools/Navigation popups/About fixing redirects.
Exceptions:
- It is preferable to change redirected links in series templates, such as those found at the bottom of many articles (e.g. {{USPresidents}} on George W. Bush). In this case, when the template is placed on an article, and contains a direct link to that article (not 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.
- It may be appropriate to make this kind of change if the hint that appears when a user hovers over the link is misleading.
Redirecting non-articles
Template redirects
A template T2 can be redirected to another template T1. This creates an alias (T2 is an alias for T1). The alias name T2 can be used instead of the "real" template T1.
Aliases for templates can cause confusion and make migrations of template calls more complicated. For example, assume calls to T1 are to be changed ("migrated") to some new template TN1. To catch all calls, articles must be searched for {{T1}} and all aliases of T1 (T2 in this case).
Category redirects
Although it is possible to attempt to redirect categories by adding a line such as #REDIRECT [[:Category:Automotive technologies]] to a category, it is not generally recommended because of limitations in the mediawiki software. Categories "redirected" in this way do not prevent the addition of articles to the redirected category. Articles added to the "redirected" category do not show up as in the target category. Until these issues are addressed (in future versions of the software), #REDIRECT should not be added to category pages.
"Soft" redirects for categories can be created using {{Category redirect}}. A bot traverses categories redirected in this manner moving articles out of the redirected category into the target category, see Template talk:Category redirect.
Citations
See also
![](http://upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/30px-Commons-logo.svg.png)
- Wikipedia:WikiProject Redirect
- Wikipedia:Soft redirect
- Wikipedia:How to edit a page
- Wikipedia:How to rename (move) a page
- Wikipedia:Redirects for discussion
- Wikipedia:Redirects with possibilities
- User:Daniel Quinlan/redirects-project
- Wikipedia:List of interwiki redirects
- Wikipedia:Double redirects (maintenance list for items to be fixed; and instructions after moving a page)
- Wikipedia:Redirects to be made
- Wikipedia:Disambiguation
- Wikipedia:Hatnote