From DrumCorpsWiki
Jump to navigation Jump to search
For general info on creating redirects see Help:Redirect.

How to make a redirect

To redirect a page (1) to a different page (2), enter the following on the top of page 1.


For example, to redirect the Cambridge University page to the University of Cambridge page, edit the Cambridge University page and enter:

#REDIRECT [[University of Cambridge]]

Don't make double redirects (a redirect that points to another redirect); they don't work, create slow, unpleasant experiences for the reader, waste server resources, and make the navigational structure of the site confusing.

Double redirects are usually created after a move when old redirects are left unchanged and pointing towards an old name.

Another type of undesirable redirect is a self-redirect: an article that redirects to itself through a redirect.

Please note that you can redirect only to articles, not sections in them; although the syntax allows them, they don't work:

#REDIRECT [[University of Cambridge#History]]

Everything after the redirect line will be blanked when you save the page. Any text on the same line as the redirect will stay, but will not be visible unless someone edits the page.

To go back and edit your redirect after it's working, add ?redirect=no to the end of the URL for your redirect:


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.

More examples are included below:

What do we use redirects for?

Compare the more complete template list and the corresponding category.
Reason Usage notes, and text that will be shown Tag /
Category to find articles so tagged
Abbreviations Template:R from abbreviation Template:Tl

Category:Redirects from abbreviation

Misspellings Template:R from misspelling Template:Tl

Category:Redirects from misspellings

Other spellings, other punctuation Template:R from alternate spelling Template:Tl

Category:Redirects from alternate spellings

Other capitalisations, to ensure that "Go" to a mixed-capitalisation article title is case-insensitive Template:R from other capitalisation

Adding a redirect for mixed-capitalisation article titles (e.g., Isle of Wight) allows "Go" to these articles to be case-insensitive. For example, without the redirect Isle of wight a "Go" for "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 via "Go" only by 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: "Go" 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.

In accordance with DrumCorpsWiki:naming conventions (precision) it's 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[citation needed] that redirects lower search engine rankings.

Renamings and merges

We try to avoid broken links because they annoy visitors. Therefore, if we change the layout of some section of DrumCorpsWiki, 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.

When should we delete a redirect?

To delete a redirect without replacing it with a new article, list it on redirects for deletion. See deletion policy for details on how to nominate pages for deletion.

This isn't necessary if you just want to replace a redirect with an article, or change where it points. 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 DrumCorpsWiki:Requested moves to request help from an admin in doing that.

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:

Don't cause a secondary redirect. They don't 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.

Don't fix links to redirects that aren't broken

Some editors are tempted, upon finding links using a legitimate redirect target, to edit the page to "fix" the link so that it points "straight" at the "correct" page. Unless the link displays incorrectly — for instance, if the link is to a misspelling, or other unprintworthy redirects, or if the hint that appears when you hover over the link is misleading — there is no need to edit the link. The link may be deliberate, may consolidate related information in one place, or may indicate possible future articles.

Most especially, there should never be a need to replace [[redirect]] with [[direct|redirect]].

Some editors are under the mistaken impression that fixing such links improves the capacity of the DrumCorpsWiki servers. Because editing a page is seemingly thousands of times more expensive for the servers than following a redirect, the opposite is true if anything.

One area where it is preferable to fix redirected links is in series templates, such as those found at the bottom of many articles. In this case, where the template is placed on an article, and contains a direct link to that article (not a redirect), that link will display in bold (and not as a link), making it easier to navigate through a series of articles using the template.

See also

The original source of this article is from Wikipedia, used under the terms of the Wikipedia:GFDL. See this article's Talk page for details.