The web forgets.
A page that exists today can disappear tomorrow.
Domains expire.
Companies close.
Hosting accounts are deleted.
Software becomes obsolete.
Databases are lost.
Images disappear.
URLs change.
Third-party embeds stop working.
Accounts are suspended.
Files are overwritten.
A public website is not automatically a permanent archive.
Link rot
Link rot happens when links that once led to useful material stop reaching it.
This damages:
research
news archives
education
documentation
citations
community history
personal history
technical knowledge
The older a collection of links becomes, the more likely some destinations are to disappear or move.
Preserve more than a screenshot
A screenshot can preserve appearance.
It may not preserve the actual information system.
Depending on the property, useful preservation can include:
HTML
source documents
images
video
audio
database exports
original uploads
metadata
publication dates
URLs
redirect maps
software versions
configuration notes
citations
domain records
documentation
Public web archives
Web-archive services can preserve snapshots of publicly accessible pages.
They are enormously valuable for historical research.
They are not guaranteed backups of every website.
Some material may be missing because of:
crawl limitations
dynamic applications
authentication
blocked resources
large media
JavaScript behavior
robots policies
network failures
unsupported formats
pages the archive never discovered
If the property matters to you, do not assume somebody else’s crawler preserved it.
Preserve the URLs
A website’s URLs are part of its history.
When redesigning or moving a site, important old URLs can often be redirected toward their appropriate new locations.
Without a redirect plan, years of external links can suddenly point nowhere.
A migration can preserve both the new structure and the old roads leading into it.
Preserve the data behind the page
A rendered article might come from:
a database
an author record
categories
tags
media records
comments
revision history
related-content relationships
Preserving only the visible HTML may lose much of the original structure.
For important systems, preserve source data as well as output.
Preserve context
A file without context can become difficult to understand later.
Useful context can include:
where it came from
who created it
when it was published
which software used it
what domain served it
what version it belonged to
why it was retained
This is where preservation and provenance meet.
Software becomes archaeology too
Old websites can depend on:
obsolete PHP versions
abandoned CMS software
old database engines
browser plugins
Flash
Java applets
dead APIs
old image formats
third-party widgets
Preserving the files does not guarantee the old software can still run.
Documentation, screenshots, exports and static copies can therefore become important.
Domain history matters
A domain can change owners and purposes over time.
The fact that a domain hosts one subject today does not prove that it always did.
Historical research should consider dates, archived versions and ownership changes rather than assuming the current site represents the entire history of the address.
Migrations are historical events
When moving an important property:
make backups
export data
copy media
record the old structure
map important redirects
verify inbound links
document the migration
keep the old material long enough to confirm the move
A redesign should not automatically erase the history that made the property valuable.
Decide what deserves to survive
Not everything needs permanent preservation.
Temporary caches, generated files and obsolete duplicates may have little historical value.
The important question is deliberate:
If this disappears, will something useful or irreplaceable be lost?
If the answer is yes, create a preservation plan before the loss happens.
Preservation is part of ownership.
Put This Lesson to Work
Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.
Worked example
For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.
Your finished result
A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.
Check your understanding
- Can you explain the main idea without repeating a slogan?
- What evidence or example supports your explanation?
- Which decision will you make differently, and why?