A redirect is a page with no other content than something of the form
#REDIRECT link in internal link style
If the link is to an existing page in the same project, going to the redirect (by means of a link, the URL, or the Go button) results in the new page, just like following the link, except that the browser shows the original URL, and the new page shows a redirection message below the title. (To get the canonical URL in your browser's address bar, click the article tab.)
For example, if somebody goes to: Help:Redirect, then they will end up at this page instead, and the top of the page will look like:
WikiCNS(Redirected from Help:Redirect)
If the link is to a non-existing page in the same project, or to a page in another project, one simply arrives at the redirect page.
As a simple way to avoid problems with infinite recursion, if the redirect target is another redirect page, the second redirect is not applied.
When a page called for inclusion is a redirect page, the redirect target is included instead, with the same parameters, without any redirect message. Again, a double redirect does not work.
Purposes of a redirect
- Finding a page
- Conveniently going to a page
- Conveniently linking indirectly to a page, without the need for a Piped link. For this purpose, making the stem (the common first part) of a collection of strongly related terms a redirect reduces the need for having many redirects. E.g. categor can be used for category, categories, categorical. Note that having the other redirects anyway is even better; also a piped link is in some respects even better than relying on a redirect, see Comparison with piped link.
- Allowing a link title independent of the final link target; one creates a page whose name is the desired link title, and which redirects to the desired target page.
Due to redirects, after renamings and merges, old URLs in links, bookmarks, search engines, etc., still lead to the appropriate page.
The move tool
When a page is renamed/moved with the Renaming (moving) a page function, a redirect is automatically created from the old to the new name, and also one for the corresponding talk page.
If the new page name is occupied by a redirect with only one edit in its history, it is replaced by the page being moved. If the redirect has more than one history entry, then it must either be deleted by an administrator or moved to another name. This move will leave behind a new redirect with no edit history, which can then be replaced by the desired page move. It might be desirable to delete the moved redirect.
Creating a redirect
If you're creating a new redirect, to create a new page, write
#REDIRECT [[pagename]] (
#redirect[[pagename]] will work too) at the top of the page, where pagename is the name of the target page. Here is an example. If you're replacing an existing page with a redirect, for example after merging a duplicate page, go to the page, edit it, and replace the existing text with
Extra text after the
#REDIRECT command and link, on the same line, can serve as explanatory text. It is only shown when viewing the redirect page itself.
Extra lines of text are automatically deleted on Save (not yet on Preview).
The page will not redirect if there is anything on the page before the redirect. Also, there must be no spaces between the # and the REDIRECT. Consider copying the
#REDIRECT [[pagename]] text into the edit summary so that people know that you have created a redirect.
After you create a redirect, you get sent to a page with the string "&redirects=no" in the URL. Thus the just created redirect page is shown, not the page to which it redirects. To see your redirect working, use your address bar to delete that part of the URL. Alternatively, create a link on another page to your redirect, and then follow that link.
When creating new redirects, bear in mind that creating too many redirects can clutter up the search results page, which can hinder users. Also, don't spend too much time creating redirects - often it's more important to spend time improving the quality of the target page. A piped link is another way to make a link to a page with a name which does not occur in the first page.
A code like %70 in a redirect disables it, although the link works from the redirect page.
Changing a redirect
Click on a link to the redirect page. Then look for the "
(redirected from source page)" link at the top of the page you've been redirected to. Click on the "source page" link. You will be taken to a page looking something like:
From project name ...
#REDIRECT [[''target page'' ]]
Then click Edit this page. You can then either change the target of the redirect or replace the redirect with a brand new page.
Another way to do the same thing: Go to the target page, and click "What links here". This will show you all the back-links from that page, including redirects. To change a redirect, click on it, and then click on Edit this page as above.
Deleting a redirect
A redirect to an anchor
An example of this:
This is not possible. You will still be redirected to [[definitions]] but you will not be sent to the #G anchor. (Note: if you view the redirecting article itself, where the redirect appears as a link (definitions#G), the link does work to redirect to the correct anchor.)
A redirect to a page in the image or category namespace
A redirect to an image page or to a category shows the editable text only. To get the full page after being redirected, use the link "Image", or "Category", respectively.
Specifying a very high value as threshold in the stub feature allows indication of links having a redirect as target: while other links to the main namespace are all marked as stub, they are not (however, links to other namespaces look the same, they are also not marked as stub). This can be useful for clean-up work involving bypassing redirects.
One may want to change the setting only temporarily, if one normally uses the stub feature in the regular way, and/or because section linking does not work on "stubs", unless external link style is used.