Help:Redirects

Redirects are used to forward users from one page name to another. They can be useful if a particular article is referred to by multiple names, or has alternative punctuation, capitalization or spellings.

Types of redirects
Two types of redirections exist:


 * Hard redirection: Readers navigated to the redirect page are taken directly to the target page (usually other pages of the same wiki). Only hard redirection is described in this current article.


 * Soft redirection: Readers are left on the redirect page but given the option of clicking the link to the target page. Usually this is achieved via a template; see corresponding 1>m:Special:MyLanguage/Soft redirect|article on Meta.

Creating a redirect
You may start a new page with the name you want to direct from (see ). You can also use an existing page that you are making inactive as a page by going to that page and using the "edit" tab at the top. In either case, you will be inserting the following code at the very first text position of the Edit window for the page:


 * 1) REDIRECT pagename

where pagename is the name of the destination page. The word "redirect" is not case-sensitive, but there must be no space before the " " symbol. Any text before the code will disable the code and prevent a redirect. Any text or regular content code after the redirect code will be ignored (and should be deleted from an existing page). However, to put or keep the current page name listed in a Category, the usual tag for that category is entered or kept on a line after the redirect code entry.

Redirections can be simple page names or specified using a namespace. They can be suffixed with a section name if you have the corresponding anchor defined on the target page.

Examples of valid operational redirections:


 * #REDIRECTHelp:Magic_words
 * #redirect Help:Magic_words
 * #Redirect Manual:$wgConf
 * #REDIRECT MediaWiki/fr the translated page is imposed

Example of redirection not allowed (not operational):
 *  #REDIRECT  although  is operational.

You should 'preview' (using the button below the Edit window, or use Alt) to check that you have entered the correct destination page name.

When redirection is valid (and operational) you will see in the previewed text the name of the target you have provided, following a 'next line' icon ([https://www.mediawiki.org/w/resources/src/mediawiki.action/images/redirect-ltr.png image]) for example as follows: &#x021B3; Help:Magic words#URL encoded page names

This is what you must get.

When redirection is not valid, the previewed text looks like a numbered list item with the destination page in blue: (it will also be the contents of the redirection page if you save as it is):

1. REDIRECT pagename

If the pagename as you typed it is not a valid page, it will show in red. Until there is a valid destination page, you should not make the redirect.

JavaScript page redirect
In order to avoid JavaScript functionality from breaking, all JavaScript wikipages have a different redirect syntax from regular wikipages. This syntax allows for proper execution of the page by the browser's JavaScript engine, as well as being recognised by MediaWiki as a redirect. To create a redirecting JavaScript page, the format that must be used is as follows:

/* #REDIRECT */mw.loader.load("");

Where  is the target pagename.

Viewing a redirect
After making a redirect at a page, you can no longer get to that page by using its name or by any link using that name. However, near the top of the destination page, a notice that you have been forwarded appears, with the source pagename as an active link to it. Click this to get back to the redirected page, showing the large bent arrow symbol and the destination for the redirect.

By doing this, you can do all the things that any wiki page allows. You can go to the associated discussion page to discuss the redirect. You can view the history of the page, including a record of the redirect. You can edit the page if the redirect is wrong, and you can revert to an older version to remove the redirect.

Deleting a redirect
There's generally no need to delete redirects. They do not occupy a significant amount of database space. If a page name is vaguely meaningful, there's no harm, and some benefit, in having it as a redirect to the more relevant or current page.

If you do need to delete a redirect, e.g. if the page name is offensive, or you wish to discourage people from referring to a concept by that name, then you simply go to the redirect page as mentioned above, and follow the procedures at </>.

Double redirects
A double redirect is a page redirecting to a page which is itself a redirect, and it will not work. Instead, people will be presented with a view of the next redirect page. This is a deliberate restriction, partly to prevent infinite loops, and partly to keep things simple.

However, you could look out for double redirects and eliminate them by changing them to be 1-step redirects instead. You are most likely to need to do this after a significant 1>Special:MyLanguage/Help:Moving a page</>|page move. Use the "what links here" toolbox link to find double redirects to a particular page, or use <tvar|1>Special:DoubleRedirects</> to find them throughout the whole wiki.

There is an option, <tvar|1></>, to automatically fix double redirects with a 2>Special:MyLanguage/Manual:Job queue</>|job queue. However, it tends to aggravate page move vandalism, so it is disabled by default. The <tvar|1> __STATICREDIRECT__ </> 2>Special:MyLanguage/Help:Magic words#Behavior switches</>|magic word can be used to skip the double-redirect fix on a particular page.

A redirect to a page in the category namespace
To redirect to a category page and prevent the redirect appearing in this category, precede the word "Category" with a colon, otherwise the redirect page will also be categorized to the category itself:


 * 1) REDIRECT Category:Glossary

Suppressing a redirect
Users with the "<tvar|1> </>" 2>Special:MyLanguage/Manual:User rights</>|right may move a page without creating a redirect. By default this right is assigned to sysops and bots.