Open a folder of links you saved two years ago and start clicking. A surprising share will be dead — 404s, parked domains, "this page has moved," or worse, a redirect to something you never intended to share. This is link rot, and it isn't bad luck. It's a predictable decay curve that every collection of links rides down over time. If you save, share, or publish links for a living, link rot is quietly eroding your work right now. This guide explains why it happens, how to defend a collection against it, and a non-obvious risk that can take a whole archive down at once.
The short version: links die because the destinations they point to are out of your control, and short links add a second, sharper failure mode — if the shortener disappears, every link through it breaks simultaneously. The defense is to control what you can (where the link physically points), archive what you can't afford to lose, and audit on a schedule instead of discovering rot the hard way.
Why links rot — the mechanics
A link is a pointer to something on someone else's server. You don't own the destination, so anything that happens to it breaks your link:
- Content moves or is deleted. Sites restructure, articles get unpublished, products are discontinued. The URL you saved no longer resolves to anything.
- Domains expire or change hands. A site shuts down, the domain lapses, and a new owner (often a spam or parking page) takes it over. Your link now points somewhere actively unhelpful.
- URLs change without redirects. A site migrates platforms and doesn't set up redirects, so every old path 404s.
- Paywalls and logins appear. The page still exists but is now gated, so the link "works" but the content is unreachable.
The decay is gradual and compounding: a small percentage of links break every year, and it accumulates. A collection you never maintain trends, slowly but surely, toward mostly-dead.
The short-link trap nobody warns you about
Short links feel like the fix — clean, trackable, brandable. But they introduce a failure mode worse than ordinary link rot, and it's the single most under-appreciated risk in link management.
A short link is an extra hop. Instead of pointing at the destination, it points at the shortener's server, which then redirects. That means your link now depends on two things staying alive: the destination and the shortener. And here's the dangerous part: if the shortening service shuts down, changes ownership, or sunsets a free tier, every single link you ever made through it breaks at once — not one at a time, but the entire archive, simultaneously, often with no warning and no way to recover the original destinations.
This has happened repeatedly when popular shorteners closed. People who'd put thousands of short links into printed materials, social posts, and saved collections found them all dead in a single day. The lesson isn't "never use short links" — they're genuinely useful for tracking and clean presentation. It's:
- Never put a critical, hard-to-recreate destination behind a shortener you don't control, especially in anything permanent like print or a published archive.
- Prefer a shortener that lets you change the destination of an existing short link, so a dead target can be repointed instead of lost.
- Use a custom domain for your short links where it matters, so even if you switch providers you keep control of the link itself.
- Keep the original long URLs stored alongside the short ones, so you can rebuild if a service vanishes.
A self-controlled link platform mitigates exactly this risk, because the redirect layer stays under your management — which is the deeper reason organizing links well, covered in the link management guide, is about control as much as tidiness.
A defense system that actually holds up
You can't stop the web from changing, but you can make your collection resilient. Three layers:
- Triage by importance. Not every link deserves protection. Separate the handful you genuinely can't afford to lose — key references, sources you cite, links in published work — from the disposable majority. Spend your effort on the former.
- Archive what matters. For critical links, save an archived snapshot (a web-archive capture, a saved PDF/HTML, or a copy of the key content) so the information survives even when the live URL dies. The archive is your insurance; the live link is convenience.
- Audit on a schedule. Run a periodic link check across your collection to catch rot before it bites — quarterly is reasonable for most people. Finding a dead link during a calm audit is fine; finding it because a reader emailed you is not.
The principle: control the things you can (where links point, what you've archived, when you check), and accept that the live web will keep moving under you.
A worked example: a creator's link-in-bio
A creator routes 30 important links — shop, portfolio, key posts — through a free shortener for clean stats. It works for a year. Then the shortener sunsets its free plan and disables old links. All 30 break at once. Followers hit dead ends; sales links 404; there's no list of the original destinations because they only ever lived inside the shortener.
The resilient version of the same setup: the creator uses short links on a custom domain they control, keeps a master list of every short link paired with its long destination, and archives the few truly critical pages. When a provider issue hits, they repoint the custom-domain links to a new backend in an afternoon, and nothing is permanently lost — because the link layer and the destination list were both under their control, not the vendor's.
Common mistakes and why people make them
- Trusting that a saved link is permanent. It feels permanent because it worked when you saved it. People mistake "works now" for "works forever."
- Routing everything through one free shortener. It's convenient and the bulk-failure risk is invisible until the day it happens.
- Never keeping the original long URL. The short link feels like the "real" one, so people discard the destination — and lose the only way to rebuild.
- Auditing reactively. Most people only find dead links when something visibly breaks, by which point the damage is public.
FAQ
What is link rot?
Link rot is the gradual decay of links over time as the pages they point to move, get deleted, or change owners. Because you don't control the destinations, a steady percentage of links break each year, and it compounds — an unmaintained collection trends toward mostly dead links.
Are short links more likely to break than regular links?
They add a second failure point. A short link depends on both the destination and the shortening service staying alive, and if the service shuts down, every link you made through it can break at once. They're useful for tracking and presentation, but don't put critical, hard-to-recreate destinations behind a shortener you don't control.
How do I protect important links from dying?
Triage your links by importance, archive the few you can't afford to lose (a web-archive snapshot or saved copy), keep original long URLs alongside any short links, and run a periodic link check to catch rot early. Using a shortener on a custom domain you control adds another layer of safety.
Can I recover a dead link?
Sometimes. A web-archive service may have a saved snapshot of the old page, and if you kept the original long URL you can often find where the content moved. If a critical link only ever existed as a short link with no record of its destination, recovery may be impossible — which is why keeping the long URLs matters.
How often should I check my links for breakage?
For most people, a quarterly audit catches rot before it causes real problems. If you publish or share links professionally, check critical links more often. The goal is to find dead links during a calm review rather than because a reader or customer hit one first.
Next step
Treat your links as something that decays, because they do. Audit your most-used links this week, archive the handful you truly can't afford to lose, keep the long URLs for anything you've shortened, and never put a critical destination behind a shortener you don't control. The trick: a short link isn't a copy of a destination — it's a dependency on a second service, and the day that service disappears, you'll wish you'd kept the original.
