This is a guest post written by Olivia Meehan, a 2022 Junior Fellow working with the Web Archiving Team. Her project was completed under the mentorship of Lauren Baker.
If you follow a link referenced in an article just to hit a dead-end, “page not found” error message – you have experienced link rot. “Link rot” and “reference rot” are terms used to describe the gradual loss of web resources.
According to a 2014 study from Harvard Law Review, “Link rot refers to the URL no longer serving up any content at all. Reference rot, an even larger phenomenon, happens when a link still works but the information referenced by the citation is no longer present, or has changed.” This study found that in 2014, 50% of URLs referenced in Supreme Court opinions from 1996 to 2013 had succumbed to reference rot. Over time, URLs change, content is deleted, businesses close, servers break down and, ultimately, information is lost.
Web archives exist to prevent this loss of information online. This summer, as a Junior Fellow with the Library of Congress Web Archiving Team, I have been investigating ways to identify content in the Library of Congress Web Archives that is no longer available on the live web. Identifying and communicating the status of URLs captured in a collection can not only demonstrate the value of web archives, it can also illustrate the impermanence of the internet more broadly.
The life cycle of a website, however, is unpredictable. Verifying the status of a site requires some level of manual investigation, which is time consuming and may be impractical when working with large collections. The Library of Congress, for example, has over 58,000 unique seed URLs in its collections.
Over the course of the summer, I was able to speak or correspond with web archivists from Columbia University and the Ivy Plus Libraries, the Bibliothèque nationale de France, the New York Art Resources Consortium (NYARC), and the Collaborative ART Archive (CARTA) about this issue. These conversations helped me identify some relevant concerns and challenges across web archiving organizations. For example: routinely checking the status of sites is not usually possible, so web archivists rely on information from subject experts or error messages from web crawlers (the software used to archive a website) to determine what sites to manually review. In some cases, offline websites might eventually go back online, so one manual review may not even be sufficient to definitively say a site is permanently defunct.
With those considerations in mind, the primary objectives of this project were to take a close look at some of the Library’s web archive collections; identify the status of sites captured in those collections; take note of what tools and information were needed to confirm the status of those URLs; and explore how the resulting data could be effectively communicated with Library staff and users.
The Library of Congress has 85 described web archive collections available online. For the purpose of this project, I chose to work primarily with the Papal Transition 2005 Web Archive. This collection contains 217 web archives related to the death of Pope John Paul II and the selection of Pope Benedict XVI in spring 2005. I picked this collection, in particular, because I felt that the size, age, and event-based context suggested that it would contain an informative variety of websites.
The official website of the Vatican as captured by a web crawler on April 7, 2005.
Using an HTTP Status Tool
When we access websites through a browser, the browser sends an HTTP request to a server hosting the website. An HTTP response code is a three-digit value that indicates the outcome of that request. A response code of 200, for example, means the request was successful and any code in the 400 and 500 range indicates an error. 300 codes indicate redirects and are not typically the final outcome of a request. It is also possible to receive an error message instead of a response code, which typically means the attempt to reach the remote web server was unsuccessful.
I used an online tool to generate a list of response codes for all 217 URLs. These response codes provide an informative high-level view of the collection, but they are not definitive indicators of an individual website’s status – in fact, they are frequently misleading.
For example, a 200 response just means that whatever website is hosted at the provided URL is online. URLs can change ownership, however, so the site that loads may not be the site that was originally there when the collection was created. Likewise, a 404 error means that there is a problem with the URL as entered – in many cases, the content originally hosted at that URL is still online, just at a different location.
So, as things stand, the best way to tell if a website is actually offline is to manually go to the URL and check.
Checking URLs manually
I used a browser to systematically check all 217 URLs in the collection and organized them into four categories:
- Available – The expected content loads without error.
- Content Relocated – The expected content is still online, just at a different web address.
- Content Missing – The website itself is still online, but the expected content cannot be found, even at a different web address.
- Website down – The entire website is inaccessible at any address.
If a site loaded as expected, I marked it as available. If I encountered any issues or error messages, I did additional research to see if the content was relocated or to find any articles, announcements, or definitive indications that the site is offline.
Once I confirmed the status of all the URLs, I was able to compile some useful statistics:
52% of the sites in the collection were still available; 7% of the sites were still available but at a different location; 21% were completely offline; and 20% were still online but were missing the specific page or content that was intended to be archived.
About 73% of URLs that originally returned a 200 response code were still available. 6% were available but missing the expected page and content, 3% were available at a different address, and 18% were completely offline.
While reproducing these steps with another collection would still require the manual review of URLs, there are some parts of the process that can be improved and automated. I wrote a Python script that reads a text file of URLs, sends an HTTP request to each URL, and then records the URL and the corresponding HTTP response code in a CSV file. This allows for all the URLs in a collection to be processed at once – the online tool I used originally could only accept up to 100 at a time.
Based on the results I have so far and conversations I’ve had with other web archivists, the lifecycle of websites is unpredictable to the extent that accurately tracking the status of a site inherently requires nuance, time, and attention – which is difficult to maintain at scale. This data is valuable, however, and is worth pursuing when possible. Using a sample selection of URLs from larger collections could make this more manageable than comprehensive reviews.
Of the content originally captured in the Papal Transition 2005 Collection, 41% is now offline. Without the archived pages, the information, perspectives, and experiences expressed on those websites would potentially be lost forever. They include blogs, personal websites, individually-maintained web portals, and annotated bibliographies. They frequently represent small voices and unique perspectives that may be overlooked or under-represented by large online publications with the resources to maintain legacy pages and articles.
The internet is impermanent in a way that is difficult to quantify. The constant creation of new information obscures what is routinely deleted, overwritten, and lost. While the scope of this project is small within the context of the wider internet, and even within the context of the Library’s Web Archive collections as a whole, I hope that it effectively demonstrates the value of web archives in preserving snapshots of the online world as it moves and changes at a record pace.