Blog

Link rot and how to prevent it on the links you cannot recall

Printed links, email footers and bios break slowly and silently. A repair plan that takes an afternoon, plus the trade a shortener actually makes.

By Wasim Idrishi · Updated · 4 min read

The links that rot are never the ones on your website. Those get clicked, and someone complains. The ones that rot are the ones nobody in your company ever clicks: the URL in the email signature, the address on the back of the business card, the link in the Instagram bio that was set up in 2023 and has been correct ever since, right up until it was not.

404. The server is there, the page is not. Almost always a site redesign that changed every path and skipped the redirects.

410. The server is telling you the page is gone deliberately. Rarer and more honest; search engines drop a 410 faster than a 404.

Soft 404. The server answers 200 and shows "page not found" or the homepage. Nothing automated flags it. This is the one that survives every audit.

Chain growth. The link still works, through three redirects that accumulated over five years. It is alive until somebody tidies the middle hop, and then it dies without warning.

What a shortener actually changes

It moves the repair from a place you do not control to a place you do.

A QR code on a laminated table tent encodes gc.mw/menu. The menu itself moves host, path and domain over three years, and you edit one row each time. The printed card never becomes wrong. That is the entire argument for putting short links on anything that gets printed, and it is a strong one.

What it does not do is make the destination immortal. If the destination 404s and you do nothing, the short link faithfully forwards people to a 404. The rot moved; it did not go away.

An afternoon that prevents most of it

  1. List the links you cannot recall

    Printed material still in circulation, email signatures, social bios, QR codes on packaging, PDFs you have sent to customers, the link in your voicemail greeting. Twenty rows is a normal list. This is the whole inventory that matters.

  2. Run each one through a checker

    Look at the final URL and the status, not only the verdict. A 200 that lands on a homepage instead of the page you meant is a soft 404 and needs the same repair as a hard one.

  3. Replace the direct URLs with short links you own

    For anything not yet printed. From then on the repair is a row edit rather than a reprint.

  4. Fix the survivors at the source

    If your own site moved a page, add the redirect on your own server at the old path. That repairs every copy of the old URL in the world, including the ones in other people's articles.

  5. Put a reminder in the calendar

    Twice a year, and once immediately after any website redesign. The redesign is when most links die in a single afternoon.

The redirect code matters more than people think

A 301 says permanent, and browsers believe it: Chrome, Safari and Firefox cache it and stop asking. That is fine for a page that genuinely moved and terrible for a link you might need to repair, because the repair never reaches the people who already have the old answer cached.

Short links default to 302 for exactly this reason. It costs one round trip per click and it keeps the link repairable for its whole life. Save 301 for the one case it is designed for: a URL on your own site that has moved for good and whose search signals should follow it.

The thing that decays fastest

Query strings. A link with UTM tags, a session id, or a ?ref= parameter picked up from wherever it was copied survives structurally but stops meaning anything: the campaign it named ended, the referrer it credited is gone, and the tags outlive the reason for them.

When you build a link that will exist for years, strip it back to the bare URL, then add the tags on the short link where you can edit them later. The printed thing stays constant; the metadata behind it stays current.

Questions people ask

Does using a shortener make link rot better or worse?

Both, and the direction depends on one thing: whether you can leave. A shortener moves the repair job to a row you control, which is a large win for anything printed. It also adds a dependency, and when Google retired goo.gl every link created through it died at once. Only commit printed material to a service that lets you export every link with its destination and move the whole set to your own domain.

What is a soft 404 and why does it matter more than a real one?

A server that answers HTTP 200 and shows a page saying the content is missing. Automated checkers see a successful response, so the link looks alive in every report until a person opens it. They are the reason a checker's verdict should be read alongside the final URL, not instead of it.

Should I use 301 or 302 on links I want to keep working?

302 on anything you might repair. A 301 is cached by browsers indefinitely, so once the link is out in the world you cannot re-point it for anyone who already followed it. Use 301 only for a move that is genuinely permanent, such as a retired page on your own site pointing at its replacement.

How often should I check?

Twice a year for anything printed or in an email footer, and once when a website is redesigned — that is when most of the damage happens in one go. Checking every link you have ever made is busywork; the ones you cannot recall are the ones that pay for the effort.

What about links in things I have already printed?

If they are short links you own, nothing is lost: change the destination and every printed copy follows. If they are direct URLs to a page that moved, the only repair is a redirect on your own web server at the old path — which is worth doing even years later, because the old URL is probably in other people's pages too.

Sources

  1. RFC 9110 §15.5.11 — 410 Gone — checked 5 September 2026
  2. Google Search Central: redirects and Google Search — checked 5 September 2026

Try it with your own link

Paste a long link and get a 10-character gc.mw link with a QR code. No account needed for 30 days; free forever with one.