stringtranslate.com

Wikipedia:Redirects are costly

Because of the vagaries of any language, and the multitude of topics that don't have an actual page, there is a need for redirects. These are handy pages that allow readers and editors to quickly get to a page that they are trying to find. But there are some redirects that can be more of a burden than a boon to Wikipedia.

Server space and bandwidth are cheap

According to WP:RFD:

deleting redirects is […] cheap because recording the deletion takes up little storage space and uses very little bandwidth. There is no harm in deleting problematic redirects.

Editors wanting to keep or delete a redirect must weigh the trade-offs. It is obvious in many cases whether deletion or retention is the correct option, so we have to decide on the ones in the middle – the grey area that is discussed at WP:RFD.

Since server space and bandwidth are not arguments for deleting or retaining a redirect, we have to give other reasons.

Relevant factors

Redirects sometimes need to be updated as articles change

A redirect may be appropriate now only to become problematic later in the course of the growth of the encyclopedia. For example, if a new article is created that could be seen as a likely target of the redirect. Or whenever there is a change in the topic structure—when content is moved from one article into another, when one article is split into two, when an article is moved to or away from a primary title. In these cases, redirects could end up pointing to the wrong targets, so generally all incoming redirects need to be examined to see if any need retargeting. This is a laborious task if there are many of them, but also one that is not always performed.

Therefore, there should be as many redirects as are needed to guide readers to what they are looking for, but not more than that.

Redirects need looking after

Just like articles, redirects can see unhelpful edits: they can get vandalised, expanded into content forks, or retargeted to less suitable articles. Most redirects have few or no watchers at all, so such disruptive edits are likely to remain unnoticed for some time.

Incoming traffic is cheap

One valid reason for retaining an older redirect is that it is linked to from outside Wikipedia. This is particularly likely to happen if a redirect has been on Wikipedia for some time, as editors of other websites may have used either the original page name prior to a page move or have themselves used the redirect page name for other reasons. If the incoming traffic is large, it is always appropriate to keep it. ("Large" is a subjective term.) WP:RFD#KEEP lists incoming links as a good reason not to delete a redirect.

A redirect that has other wikipages linked to it is not necessarily a good reason for keeping it. Current internal wikilinks can be updated to point to the current title. However, updating the current versions of articles and then deleting the redirect will break all the prior versions, which can be inconvenient for people looking at prior versions, reading old discussions, etc.

Sending redirects to RFD is costly

The mere fact that a redirect is listed and discussed at the Wikipedia:Redirects for discussion page creates work for others. Reducing the maintenance burden that is placed on the shoulders of Wikipedians is important. There is a huge backlog of tasks that need attention and Wikipedia is forever growing. This means that there are evermore existing articles needing the attention of editors, and we have no inkling of whether there will be a large enough pool of editors in the future.

You can reduce this burden by:

Some unneeded redirects

There is no need to redirect from:

  • WP:UNHELPFUL
  • WP:PANDORA

This is but a short list, and there are many more reasons for deletion.

See also