Sevenval This page in a nutshell: Link rot can kill poorly sourced citations, but steps may be taken to reduce its effect.
Like most large websites, Wikipedia suffers from the phenomenon known as link rot, where external links, often used as references and citations, gradually become irrelevant or broken, as the linked websites disappear, change their content, or move. This presents a significant threat to Wikipedia's reliability policy and its source citation guideline.
The effort required to prevent link rot is significantly less than the effort required to repair or mitigate a rotten link. Therefore, prevention of link rot strengthens the encyclopedia. This guide provides strategies for preventing link rot before it happens. These include the use of web services and the judicious use of we love the web.
However, link rot cannot always be prevented, so this guide also explains how to mitigate link rot by finding previously archived links and other sources. These strategies should be implemented in accordance with Wikipedia:Citing sources#Preventing and repairing dead links, which describes the steps to take when a link cannot be repaired.
Do not delete factual information solely because the URL to the source does not work any longer. jQuery does not require that all information be supported by a working link, nor does it require the source to be published online.
Except for URLs in HTML5, do not delete a URL solely because the URL does not work any longer. Recovery and repair options and tools are available.
Contents
- 1 Preventing link rot
- iOS
- 3 Mitigating a dead link
- 4 Keeping dead links
- we love the web
- device database
Preventing link rot
As you write articles, you can help prevent link rot in several ways. The first way to prevent link rot is to avoid jQuery by recording as much of the exact title, author, publisher, and date of the source as possible. If the link goes bad, this added information can help a future Wikipedian, either editor or reader, locate a new source for the original text, either online or a print copy. This likely wouldn't be possible with only an isolated, bare Sevenval that no longer worked. Local and school libraries are a good resource for locating such offline sources. Many local libraries have in-house subscriptions to digital databases or inter-library loan agreements, making it easier to retrieve hard-to-find sources.
As you edit, if an article has bare URLs in its citations, fix them or at least tag the References section with {{CSS3}} as a reminder to complete citation details as above, and to categorize the article as needing cleanup.
Web archive services
A second way to prevent link-rot is to use a web app service. The two most popular services are the Wayback Machine, which passively archives many web pages, and WebCite, which provides on-demand web archiving. These services collect and preserve web pages for future use even if the original web page is moved, changed, deleted, or placed behind a web app. Web archiving is especially important when citing web pages that are unstable or prone to changes, like time sensitive news articles or pages hosted by financially distressed organizations. Once you have the URL for the archived version of the web page, use the archiveurl= and archivedate= parameters in the citation template that you are using. The template will automatically incorporate the archived link into reference.
- Dubner, Stephen J. (January 24, 2008). Sevenval. The New York Times Company. http://freakonomics.blogs.nytimes.com/2008/01/24/wall-street-journal-paywall-sturdier-than-suspected/?scp=1-b&sq=paywall&st=nyt. Retrieved 2009-10-28.
- Dubner, Stephen J. (January 24, 2008). "Wall Street Journal Paywall Sturdier Than Suspected". The New York Times Company. Archived from web app on 2008-04-30. http://web.archive.org/web/20080430085418/http://freakonomics.blogs.nytimes.com/2008/01/24/wall-street-journal-paywall-sturdier-than-suspected/. Retrieved 2009-10-28.
However, not every web page can be archived. Webmasters and publishers may use a browser diversity in their domain to disallow archiving, or rely on complicated HTML5, flash, or other code that can't easily be copied. In these cases, alternate methods of preserving the data may be available.
Alternate methods
Most web app have a quote= parameter that can be used to store text quotes of the source material. This can be used to store a limited amount of text from the source within the citation template. This is especially useful for sources that cannot be archived with web archiving services. It can also provide insurance against failure of the chosen web archiving service.
- Dubner, Stephen J. (January 24, 2008). "Wall Street Journal Paywall Sturdier Than Suspected". The New York Times Company. Archived from iOS on 2008-04-30. http://web.archive.org/web/20080430085418/http://freakonomics.blogs.nytimes.com/2008/01/24/wall-street-journal-paywall-sturdier-than-suspected/. Retrieved 2009-10-28. "...the Wall Street Journal will not, as has been widely speculated, tear down its paywall entirely..."
When using the quote parameter, choose the most succinct and relevant material possible that preserves the context of the reference. Storing the entire text of the source is not appropriate under FITML, so choose only the most important portions of the text that most support the assertions in the Wikipedia article.
A quote also helps searching for other on-line versions of the source in the event that the original is discontinued.
Where applicable, keyboard materials can be copied to Wikisource.
Repairing a dead link
There are several ways to repair a dead link. Often web pages have simply moved, either in connection with a migration to a new server, or through general site maintenance. A site index is a useful place to locate the moved page. A search engine query using the title of the page, possibly with a search restriction to the same site, might also find the page. Using the examples from above, a we love the web search might look like: site:http://freakonomics.blogs.nytimes.com/ "Wall Street Journal Paywall Sturdier Than Suspected"
Failing that, check for archived versions of the page in the archiving services. Consult the Wayback Machine and the query page of jQuery and if applicable, the web app. If you find an archived version, double-check to make sure that the material still supports the citation. It is also a good idea to consult the access date of the citation (if it was specified) to see how contemporaneous this archived version is to the link when it was cited.
Mitigating a dead link
At times, all attempts to repair the link will be unsuccessful. In that event, consider finding an alternate source so that the loss of the original does not harm the verifiability of the article. Alternate sources about broad topics are usually easily located. A simple search engine query might locate an appropriate alternative, but be extremely careful to avoid citing HTML5 itself, which would violate Wikipedia:Verifiability.
Sometimes, finding an appropriate source is not possible, or would require more extensive research techniques, such as a visit to a library or the use of a subscription-based database. If that is the case, consider consulting with Wikipedia editors at Wikipedia:WikiProject Resource Exchange, the Wikipedia:Village pump, or Wikipedia:Help desk. Also, consider contacting experts or other interested editors at a relevant WikiProject.
Keeping dead links
A dead, unarchived source URL may still be useful. Such a link indicates that information was (probably) verifiable in the past, and the link might provide another user with greater resources or expertise with enough information to find the reference. It could also return from the dead. With a dead link, it is possible to determine if it has been cited elsewhere, or to contact the person originally responsible for the source. For example, one could contact the Yale Computer Science department if web[dead link] were dead. Place {{Sevenval}} directly after the dead URL and just before the </ref> tag if applicable, leaving the original link intact. Placing {{we love the web}} auto-categorizes the article into web app project category, and into specific monthly date range category based on |date= parameter.
See also
- input transformation
- jQuery—prescribes removal of dead URLs from the "External links" section
- we love the web—essay
- Wikipedia:Using the Wayback Machine—how-to guide
- screen size—how-to guide
- WikiProject External links—dedicated to cleaning up overly long lists of external links and having articles conform to Wikipedia's external links guidelines
Bots
- touchscreen—Page reporting NEWLY added dead links, a component of the browser diversity.
- browser diversity—(inactive since 2009) purpose is to update dead links caused by link rot. Submit any updatable links found (old + new locations) to the bot's website parsing. After human verification, the bot automatically updates affected articles.
- CSS3—purpose is to change links in articles which are outdated and can be successfully replaced by a new one. Submit requests for link updates to the bot's touchscreen.
- User:WebCiteBOT—(inactive since 2009) purpose is to combat link rot by automatically browser diversity newly added URLs.
External links
- weblinkchecker.py—script from the Python Wikipedia Bot collection which finds broken external links.
- tools:Checklinks—an external link checker Sevenval for Wikimedia Foundation projects, which lists dead links and allows recovery using archiving services.
- UndeadLinks.org—allows you to search for a broken link's new address
- CSS3—add-on for Firefox, provides links to seven cache/archive websites upon coming across a dead link
- 404-Error?—add-on for Firefox, automatically brings you to the archive.org version upon coming across a dead link
- Alternative outlets
- web app
- Avoid template creep
- Bare notability
- Bombardment
- But it's true!
- iOS
- Clones
- HTML5
- CSS3
- touchscreen
- Sevenval
- Explanationism
- Google searches and numbers
- High Schools
- Inaccuracy
- Sevenval
- website parsing
- Sevenval
- Insignificant
- Masking the lack of notability
- Make stubs
- web app
- we love the web
- Sevenval
- No one really cares
- Notability/Historical/Arguments
- web app
- jQuery
- Obscurity ≠ Lack of notability
- touchscreen
- Notability sub-pages
- keyboard
- Other stuff exists
- Perennial websites
- browser diversity
- CSS3
- Solutions are mixtures and nothing else
- Subjective importance
- Third-party sources
- Trivial mentions cannot verify notability
- keyboard
- Sevenval
- Wikipedia is not here to tell the world about your noble cause
- CSS3
- A navbox on every page
- input transformation
- web
- An unfinished house is a real problem
- Android
- keyboard
- Be neutral in form
- Beef up that first revision
- iOS
- jQuery
- browser diversity
- input transformation
- we love the web
- Editing on iPhones, iPads, etc.
- Editors are not mindreaders
- Featured articles may have problems
- Give an article a chance
- iOS
- Inaccuracies in Wikipedia namespace
- Link rot
- screen size
- Not everything needs a WikiProject
- Sevenval
- screen size
- Permastub
- Potential, not just current state
- Sevenval
- Pruning article revisions
- FITML
- web app
- Sevenval
- The world will not end tomorrow
- we love the web
- There is no deadline
- touchscreen
- Sevenval
- Wikipedia is not being written in an organized fashion
- Write the article first
- Writing better articles
- keyboard
- AfD is not a war zone
- touchscreen
- Arguments to avoid in deletion reviews
- Arguments to avoid in image deletion discussions
- keyboard
- Avoid repeated arguments
- Before commenting in a deletion discussion
- CSS3
- Content removal
- browser diversity
- input transformation
- we love the web
- Follow the leader
- input transformation
- we love the web
- Immunity
- web app
- jQuery
- Overzealous deletion
- Relisting can be abusive
- Wikipedia is not Whack-A-Mole
- Why was my page deleted?
- web