Help:Redirect

A redirect is a page created so that navigation to a given title takes the reader directly to a different page. A redirect is created using the syntax:

#REDIRECT [[Target]]

...where "target" is the name of the target page. It is also possible to add a section header to make a redirect to a specific section of the target page in the following manner:

#REDIRECT [[Target#Section header]]

The pound/number/hash sign (#) is also used to link to page anchors.

Syntax

A page is treated as a redirect page if its wikitext begins with #REDIRECT followed by a valid wikilink. A space is usually left before the link. (Note that some alternative capitalizations of "REDIRECT" are possible.)

Note that a redirect works as intended (takes the reader directly to the target page) only if the link is to an existing normal page (not a special page). In other cases soft redirects are often used – see below.

Examples:

• #REDIRECT [[The Pit]] (redirects to the The Pit article)
• #REDIRECT [[The Pit#Loot]] (redirects to the "Loot" section of the The Pit article)

Any text appearing after the redirect link is ignored in the display, but may be used to add categories, interwiki links, comments, etc.

Note that the redirect link must be explicit – it cannot contain magic words, templates, etc.

When redirecting to a category page, prefix the target pagename with a colon to prevent the redirect from showing up in the category. (Redirects from one category page to another should use soft redirects – see below.) Redirects to image pages also require the colon.

How it appears to the user

If the redirect target is an existing page on DDOwiki and a reader navigates to the redirect page – by wikilink, the search box, or a URL – the reader is taken directly to the target page. A small notice below the top title indicates that the user arrived via a redirect. For example, if you click Help:Group rights, you are redirected to the DDO wiki:Administration guideline article, and the top of the page looks like:

To go to the redirect page itself (to edit it, view its history, etc.), click the link in the "(Redirected from...)" notice.

If the redirect target is a non-existing page (redlink), or a special page, or a page in another project, then the redirect is not followed, and the reader sees the display of the redirect page (as illustrated below). If the target is a non-existent section of an existing page, then the redirect will take the reader to the top of the target page.

Chains of redirects are not followed. If title A redirects to B, and B is itself a redirect page, then a reader navigating to A will see the display of the redirect page B (as illustrated). See Double redirects.

A redirect page viewed directly, either in the situations described above, or when the URL used to access the page contains the query parameter &redirect=no, looks like this:

(See the actual Help:Group rights redirect page.)

Redirects to articles that begin with a lowercase title, for example the redirect from the page at 20 sided die to the article at d20, will display the target page with a capitalized first letter, even though the article displays the title with a lowercase title. This is because the true title of the target page is actually capitalized — it just appears lowercase because of the use of the magic word DISPLAYTITLE. (Usually, the template {{Lowercase title}} is used to implement the DISPLAYTITLE magic word for lowercase titles.)

Section redirects

When the redirect target is a section link, following a redirected link should lead to the section or other element identified by the link. Normally the redirected page includes the entire contents of the target page as if the section fragment wasn't specified, and uses JavaScript to jump to the section after the page is loaded. If JavaScript is disabled, this jump does not happen.

When a redirect page is viewed directly without following the target link, the link is shown as an ordinary section link, and works as usual without the use of JavaScript.

Purposes of a redirect

Redirects are usually created because readers may search for an article under different names (or editors may wish to link to it from different names). Examples are:

• Alternative names for the same thing
• Alternative spellings, capitalizations etc. (although it is not necessary to create redirects from different capitalizations just because readers may enter them in the search box - the Go button in the Monobook skin resolves this automatically)
• Common misspellings
• Plurals
• Subtopics that don't have their own article (in this case, you may redirect to a section of the target page)
• shortcuts to a page (such as CLLi  which points to Community Loot List items )
• Redirects that keep links to a page active after it has been renamed (even if internal links are updated—this still applies for links from outside and links in edit summaries)

Note that it is not necessary to create redirects from every title an editor may conceivably wish to link to a given page – piped links can be used as an alternative.

Creating and editing redirects

A redirect page can be created like any other page (see Creating a new page). Simply type in the wikitext #REDIRECT [[xxx]], replacing "xxx" with the title of the target page (optionally followed by a "#" sign and the section title).

Make sure that there is no text before the #REDIRECT keyword, or the redirect will not work. There is not usually any reason to place any text after the link either, although sometimes categories (or categorizing templates—see Categorizing redirects) or HTML comments (<!-- comment -->) are added.

Similarly, any existing page can be edited to turn it into a redirect.

To edit a page that is already a redirect (or to view its history, talk page, etc.), follow the redirect to the target page, then click on the link in the "(Redirected from ...)" notice at the top of the page. This takes you to the redirect page itself. (The URL for accessing a redirect page without following the redirect contains the query parameter redirect=no.)

Another way to get to a redirect page is to go to the target page, and click "What links here" (in the toolbox on the left of the page). This will show you all the backlinks to that page, including redirects. Clicking on a redirect in this list will take you to the redirect page, not the target.

The edit summary box can be left blank; the summary will then be automatically generated stating that the page has been redirected to the given target. (This applies for: a new redirect page; an existing article page turned into a redirect page; and a change to the target of an existing redirect.) The generated summary is overridden if the editor supplies their own summary.

Administrators can delete redirects in the same way as any other page. Deletion or other potentially controversial treatment of redirects can be proposed by any editor on the page's Talk: page. Please refer to DDOwiki's deletion policy for details and instructions.

Moving pages

When a page is moved (renamed), a redirect is automatically created from the old to the new name, and also one for the corresponding talk page (if that was moved as well). Administrators can choose to suppress creation of the redirect.

If the new page name is occupied by a redirect that has only one edit in its history and targeted to the old page name, it is replaced by the page being moved. If the redirect has more than one history entry, or has a different target page, then the move must be made by an administrator or pagemover.

Transclusion

When a page called for transclusion is a redirect page, the redirect target is included instead, with the same parameters, without any redirect message. Hence if Template:Hst is redirected to Template:Hat, then {{Hst|...}} will have the same effect as {{Hat|...}} As usual, double redirects are not followed.

Soft redirects

As an alternative to the normal "hard" redirects (which take the reader directly to the target page), it is possible to create "soft" redirects, which leave the reader on the redirect page, giving them the option of clicking the link to the target page. This is usually done in the following situation(s):

• For redirects between categories. (Hard redirects work for category pages, but soft ones are preferred because of the software's inability to recategorize pages from redirected categories.)

Soft redirects are created using the {{Redirect category}} template.