Answer First
Definition: Link rot is the decay of published URLs: a link that once resolved starts returning an error — usually a 404 — because the destination page behind it moved, was deleted, or was replaced. The published link never changes; the page it points to does — RFC 9110 defines 404 as the origin server finding no current representation for the target resource.
Why: Because link rot is a system-wide operational problem, not bad luck. Studies keep measuring it across legal, scientific, and government archives, and it recurs wherever URLs are published without a stable layer between link and destination. When a link dies, teams absorb it as a support ticket, a broken campaign, or an unverifiable citation — and usually fix only that one link.
Example: A marketing email published in March links to https://acme.example/spring-launch. In June, a site migration replaces that page and deletes the old URL. The email is still live and now returns 404 — and nobody knows until customers ask. A managed entry — a forwarding record on a branded subdomain your team controls — would let you point the published URL at the new destination without touching the email, the ad, or the archived campaign — and it would log the change.
Key Facts
- Measured, not anecdotal. A 2014 Harvard Law Review Forum study by Lessig, Zittrain, and Albert found that more than half of URLs cited in U.S. Supreme Court opinions, and more than 70% of URLs in three major law reviews, suffered reference rot.
- Scientific literature rots too. A 2014 PLOS ONE analysis of more than a million references found one in five science, technology, and medicine (STM) articles suffers reference rot — seven in ten among those that cite web resources.
- A 404 is a defined protocol event. It is the server’s way of saying no current representation of the resource exists at that URL.
- The usual causes are ordinary lifecycle events: redesigns, CMS migrations that change slugs, campaign landing pages taken down after a run, and domains that change or expire.
- The structural fix is a stable entry layer: a forwarding entry on a subdomain you control lets the destination change while the published URL stays the same, and makes link health visible.
Expert Explanation
How link rot happens
Every URL is a promise: at this address, you will find this content. The web keeps that promise only while the destination holds up its end. Link rot sets in through routine events: a redesign swaps the URL structure, a CMS migration changes slugs, a campaign ends and its landing page is removed, content is archived or taken down, or a domain is sold, expires, or is rebranded. None are failures of intent — they are normal publishing operations. The failure is structural: the published link has no layer between it and the destination, so any downstream change breaks every upstream link.
Why it’s an operational problem
Each broken link surfaces as a ticket: “the link in the email is dead,” “the ad goes nowhere.” The cost compounds because broken links are invisible until someone clicks — no alert fires when a destination disappears. Campaign and analytics value leaks too: when a tracked destination changes, the historical picture of what that link did is harder to reconstruct. And archives suffer quietly: documentation, compliance records, and campaign reports lose the evidence trail that made them verifiable. Link health belongs in operations, not in the support queue.
How managed entries change the failure mode
A managed entry is a forwarding record on a branded subdomain you control — for example, go.yourbrand.com/spring-launch — that points to a destination page. Because the entry sits between the published URL and the page, updating the entry updates every link ever published against it. The published URL never changes; what changes is the entry, and the change is recorded.
That property reshapes the problem. A redesign no longer threatens every campaign, email, and citation you have shipped: update the destination once, and the archived links keep working. When a landing page changes after an ad is approved, the fix is an entry update, not a re-approval cycle — the scenario our ad-destination change guide walks through. Entry status tells you whether a published link still resolves; access statistics and logs show what hits each link; and every change is traceable — the evidence trail compliance auditors ask to see. Choosing between a 301 and a 302 is a deliberate decision, as our 301 vs 302 comparison explains.
Entries are managed through a Console and an OpenAPI surface, so updating a destination, checking status, and reviewing logs are operations a team can do — and automate. The point is not the redirect — a well-understood HTTP mechanism — but that the entry becomes the single, stable, visible place where link health is controlled.
Where entries honestly stop helping
A managed entry is a management and visibility layer, not a magic proxy. It stops helping at three boundaries:
- No replacement destination. If the destination host is gone — site shut down, page deleted, no replacement — an entry has nothing to forward to. It can point at a new location if one exists; it cannot conjure one.
- The entry layer itself can expire. The entry lives on a subdomain, and the subdomain lives on a domain. If the domain is not renewed or the subdomain is dropped, every entry on it disappears with it. The layer is only as durable as the domain you control and keep renewed.
- No SEO or uptime guarantee. A forwarding entry manages where a URL goes and makes its health observable; it does not promise search ranking benefits or guaranteed availability of the destination.
Decision Framework
Use a managed entry when:
- You publish campaign or ad URLs that must outlive their landing pages.
- Your team runs frequent redesigns, CMS migrations, or rebrands that change URLs.
- You need stable links for email, print, QR codes, or documentation you cannot update after publication.
- You want to see which published links still resolve, and what is being accessed.
- Compliance or audit processes require knowing what changed and when.
Do not expect an entry to help when:
- The destination is gone and no replacement page exists — there is nothing to forward to.
- The subdomain or domain is not renewed — the entry layer disappears with it.
- You are seeking an SEO ranking or uptime guarantee — entries do not make those promises.
In practice, decide by lifecycle risk: if a URL points at content that can move, and anything permanent points at that URL — an ad, an email, a printed QR code, a citation — the entry is cheap insurance. Checking entry status and access statistics beats discovering a dead link in a support ticket. After an acquisition, the same discipline applies at scale: consolidating subdomain entries is a standard step in the acquisition playbook. And before you rewrite ads to chase conversion problems, check the campaign entry first — a mismatched destination produces the same symptoms as a bad ad.
Key Takeaways
- Link rot is a measurable, system-wide problem across legal, scientific, and government archives — not a run of bad luck.
- Every broken link comes from an ordinary lifecycle event: redesign, migration, campaign cleanup, or domain change. The structural cause is publishing URLs with no layer between link and destination.
- A managed entry on a branded subdomain decouples the published URL from the destination: update the destination once, keep published links alive, and see status, statistics, logs, and a trace of every change.
- Entries have honest limits: they need a live destination to point to, a domain that stays renewed, and they make no uptime or SEO promises.
- Treat link health as an operational function — visible, logged, reviewable — rather than a stream of one-off tickets.
FAQ
Q: What exactly counts as link rot?
A: Link rot is when a published URL stops resolving to the content it promised — typically returning a 404 — because the destination page moved, was deleted, or was replaced. The published link itself never changed; the world behind it did. A mistyped URL is not link rot; a correct URL whose destination vanished is.
Q: How do I know whether my published links are rotting?
A: Only by checking. Link rot is invisible until someone clicks, which is why it surfaces as support tickets. With managed entries, the entry’s status tells you whether each published link still resolves, and access statistics and logs show what is being hit — so you can detect decay instead of waiting for complaints.
Q: Does a managed entry fix a link to a website that no longer exists?
A: No. If the destination host is gone and no replacement content exists, an entry has nothing to forward to. Entries absorb destination changes — a page that moved, a new URL for the same content — but they cannot create a destination that does not exist.
Q: Is a managed entry the same thing as a redirect?
A: Not quite. A redirect is the HTTP mechanism (301, 302, and other 3xx statuses) that tells a client where the content went. A managed entry is the record that uses that mechanism and adds management around it: a stable URL on your own subdomain, a configurable redirect type, status visibility, access statistics, logs, and traceable change history.
Sources
- Lessig, Zittrain & Albert, Perma: Scoping and Addressing the Problem of Link and Reference Rot in Legal Citations, Harvard Law Review Forum, 2014 — harvardlawreview.org
- Klein, Van de Sompel, et al., Scholarly Context Not Found: One in Five Articles Suffers from Reference Rot, PLOS ONE, 2014 — journals.plos.org
- RFC 9110, HTTP Semantics (404 status code) — rfc-editor.org
- MDN Web Docs, Redirections in HTTP — developer.mozilla.org