← blog / Content strategy

Link Rot Audit: Your Blog's Dead Outbound Links

·updated ·18 min readseolink-rotcontent-maintenancefact-checkingpublishing
Abstract Magic Share brand graphic: a field of dots with a highlighted cluster in green and teal on a near-black grid, with the Magic Share name and the label "seo".

Every outbound link in your archive was checked exactly once — on the day it was published. That check has an expiry date: Pew Research Center found that 8% of webpages that existed in 2023 were already inaccessible when it re-checked them in October 2023, rising to roughly one in five for pages from 2021 and 38% for pages from 2013. A link rot audit is the scheduled re-resolution pass that catches those deaths, plus a written rule for what to do with each one — because the hardest cases don't return a 404 at all.

  • Citations decay on a schedule. Deep links, the kind blog posts cite, die fastest: one large study puts their median lifespan at 1.3 years.
  • Status codes miss the worst cases. A redirect to a homepage or a page whose content has drifted still returns 200.
  • Automate detection, not judgement. Run a scheduled checker, keep a commented ignore list, and give every verdict a predefined repair rule.

Those hard cases are where most audits fall apart, so let's start there.

Here are two citations resolved on 11 August 2026 and again on 12 October 2026, both of which any reasonable person would have called "verified" on the day they shipped.

The first: developer.twitter.com/en/docs/twitter-api returns a 307 redirect to https://docs.x.com, which forwards to the documentation's overview page. If your 2023 post cited a specific endpoint to back a sentence about rate limits, that sentence now points at a landing page. Every status-code checker on earth marks it green. The link works; the citation doesn't.

The second: in August, segment.com/blog/introducing-segment-personas/ returned a 301 to Twilio's error page, which answered with an honest HTTP 404. A checker catches that, but only if it follows the chain and evaluates the final status. A tool that stops at "301, fine, it moved" reports a clean archive. By October the error page itself redirected to Twilio's homepage, so the same dead post now ends in a 200 and looks as healthy as the first example.

Two links, one way of dying in plain sight, and neither has anything to do with how carefully you verified them at publish time. Publish-time verification answers was this real? It cannot answer is this still real? Those questions are asked years apart, and only one of them is on your calendar.

Google, incidentally, agrees about this pattern. Documenting soft 404 warnings that appeared after summer 2016 site migrations, Glenn Gabe noted that John Mueller "has always said that redirects to the homepage or non-relevant pages can be treated as soft 404s." If Google won't count a homepage redirect as a real destination, neither should your citation.

The decay curve you can plan against

Numbers make this schedulable rather than vibes-based. Pew sampled roughly 90,000 pages per year from Common Crawl for each year from 2013 to 2023 and checked them in October 2023. It counted a page as inaccessible only when it returned one of nine error codes that definitively indicate the page or host is gone. That deliberately conservative method produced the ladder above, plus one headline figure: 25% of the whole sample was inaccessible.

The split inside that 25% is what you can act on. Sixteen percentage points were pages deleted while their domain kept working; nine were root domains that vanished entirely. So most dead citations are page-level deaths on sites that are still alive and still ranking — the failure you cannot catch by scanning your archive and thinking "those companies all still exist." The company exists. The page doesn't.

Worse, the URLs a blog post cites are the ones that die fastest. A study of 27.3 million URLs sampled from the Wayback Machine and re-checked in 2023 found a median lifespan of 1.3 years for deep links against 8.8 years for root URLs, with 64.7% of the sample dead at the re-check. Over half of all deep links disappeared inside their first year. You don't cite stripe.com — you cite a changelog entry, a pricing page, a docs anchor. Every one of those is a deep link.

Source type matters as much as depth. A 20-year study of 2,886 web citations across 608 articles in four library and information science journals, published 14 January 2026, found .edu domains 93% accessible against .com at 42%, and static PDFs at 92% against database-driven content at 41%. Accessibility fell from 87% for citations under five years old to 38% for those over ten, and about 15% were unrecoverable by any method the authors tried. That's your prioritisation rule: the startup blog posts and vendor docs you lean on sit in the 42% bucket, standards documents and university PDFs in the 93% one.

One piece of illustrative arithmetic, mine rather than a sourced statistic. A two-year-old blog with 60 posts averaging a dozen citations carries about 720 external links. Apply Pew's ~20% two-to-three-year rate and roughly 140 are already dead. Apply the finding that 13% of still-resolving links in the New York Times archive had drifted significantly and another 70 or so quietly point somewhere else. That's an order of magnitude, not a prediction — but it's enough to tell you the audit will find something.

One number to avoid is the one everyone reaches for: Ahrefs' finding that 66.5% of links to 2,062,173 sampled websites since January 2013 had rotted. Real study, wrong scope — it measures inbound backlinks pointing at those domains, not outbound citations inside posts. Use it to say the links you earned decay too, never as the decay rate of your own footnotes.

Four ways a citation dies, and only one of them 404s

Once you accept that "does it return 200?" is the wrong question, the audit needs a taxonomy — in ascending order of how hard each case is to detect.

Honest death: 404 or 410. The page is gone and says so. Google handles both the same way, dropping the URL from the index and reducing crawl frequency. Any checker catches this. Even Google lets its own URLs die this way: on 11 August and again on 12 October 2026, the old webmaster-blog URL for "Evaluating page experience" returned a hard 404, while the post itself lives happily on Search Central. Every pre-migration post that cited the webmaster blog now has a broken citation.

Redirect to an error page. The Segment case as it stood in August: catchable, but only by a tool that evaluates the destination.

Redirect to a homepage or section root. The docs.x.com case, and since October the Segment one too, invisible to status codes because the final response genuinely is a 200. Google's own definition of a soft 404 describes the same category of lie from the other direction: "The page request returns what we think is a soft 404 response. This means that it returns a user-friendly 'not found' message but not a 404 HTTP response code."

Content drift: still 200, no longer the same page. Klein et al. analysed 3.5 million science, technology and medicine articles from 1997–2012. They named this reference rot, meaning link rot plus content drift, and found one in five articles affected, rising to seven in ten among those containing web references. Drift compounds with age: across 553,693 New York Times articles and 2,283,445 external links, 4% of still-reachable links in 2019 articles had drifted, against 25% of those in 2009 articles.

Now the counter-example, because a rule that cries wolf gets switched off. nextjs.org/docs/basic-features/pages hasn't been a canonical path for years, yet it still lands on the equivalent current documentation — a true 1:1 redirect, a reorganisation handled well. So the rule isn't flag redirects. It's flag redirects whose destination isn't the same thing.

You can predict most of your failures before running anything, which is how the first pass stays finishable.

Acquired startups. Content gets folded into the parent's site and the long tail of blog posts rarely survives the merge. Note that segment.com/blog/ itself redirects cleanly to Twilio's blog while the individual post bounces through an error page to Twilio's homepage: page-level death on a living domain, the pattern behind Pew's 16%.

Rebrands. developer.twitter.com → docs.x.com. The docs still exist; your specific anchor no longer resolves to anything specific.

Platform migrations. Google's webmaster blog moving to Search Central. Any vendor moving off a hosted CMS onto their own docs framework does this to you.

Shorteners and campaign URLs. These fall off a cliff rather than decaying. Google announced on 18 July 2024 that goo.gl links would stop resolving. The post said "these URLs will no longer return a response after August 25th, 2025" and "all links served will return a 404 response." An August 2025 update spared links still in active use — but Google's framing of the rest was that "more than 99% of them had no activity in the last month." If an old post cites a goo.gl URL, the base rate says it's gone. Grep for shortener domains first; it's the highest-yield search you'll run all day.

Expired domains — the case that stopped being cosmetic. Infoblox research reported by Krebs on Security in December 2025 found visitors to parked domains directed to "illegal content, scams, scareware and anti-virus software subscriptions, or malware" over 90% of the time, against under 5% in 2014. The detail that should change your tooling: those redirects are driven by visitor profiling (geolocation, device fingerprinting, cookies), and visitors arriving over a VPN or from a non-residential address get the benign parking page. Your link checker runs from a datacenter IP, so it sees the safe version. Your readers don't.

Expired domains also get bought for their history. Google's spam policies name this expired domain abuse: "an expired domain name is purchased and repurposed primarily to manipulate search rankings by hosting content that provides little to no value to users." The canonical case is The Hairpin, which stopped publishing in January 2018 and let its domain lapse. In 2024 a Serbian DJ bought it and filled it with AI-generated SEO articles under replaced bylines; Wired reported that he chose it for its "great reputation and excellent backlinks." Every post that ever cited it now recommends a content farm.

Running the pass without drowning in false positives

The mechanics are cheap. The reason people abandon link audits isn't cost — it's noise.

If your blog lives in a git repo, lychee is the natural fit: a Rust link checker that reads Markdown, HTML, text, globs, remote URLs or stdin. Start with inventory rather than judgement — --dump will "dump all the links extracted from inputs that would be checked" without checking anything, which tells you how many outbound citations you're carrying. Then tune: --accept sets which codes pass (default 100..=103,200..=299), --exclude and .lycheeignore hold your regexes, --cache with --max-cache-age (default one day) keeps repeat runs cheap, and --host-concurrency (default 10) plus --host-request-interval (default 50ms) stops you hammering a small site. What it doesn't do: nothing in its docs claims soft-404 detection, so the homepage-redirect case stays yours to adjudicate.

Make it a schedule, not a chore you remember. lychee-action runs on cron (its README shows on: schedule: - cron: "00 18 * * *"), and the documented pattern pipes the Markdown report into peter-evans/create-issue-from-file@v5 when steps.lychee.outputs.exit_code != 0, given issues: write permission. A dead citation then arrives as a GitHub issue with the report attached. If you already handle publishing a blog post by pull request, a citation repair ships through the same gate as a new article: branch, preview, merge.

If your blog is hosted or CMS-based, Screaming Frog's SEO Spider does the equivalent. Crawl the site, open the Response Codes tab, filter to "Client Error (4XX)", then use the Inlinks pane to see which of your posts links to each dead URL, anchor text included. The documented bulk path is Bulk Export > Response Codes > Client Error (4XX) Inlinks. Timeouts and DNS failures won't show up in that filter: the Spider reports them as status 0, with labels such as DNS Lookup Failed and Connection Timeout, so review those rows too. Plan around two things: the free version crawls up to 500 URLs (a licence is £199/year), and it classes external broken links as low-priority warnings — sensible for most audits, exactly backwards for this one.

Simpler setups work. One indie blogger's entire audit is a single linkchecker invocation with --check-extern and --ignore-url patterns for image paths, geo-redirecting corporate domains, consent pages and login-gated services. The last documented run, in March 2024: 376 links across 378 URLs, one error, fixed from a Wayback snapshot. That's the shape of a maintained archive, and it's what makes the job feel finishable. If you'd rather buy soft-error detection than build it, Dr. Link Check advertises a soft-error check for servers that answer with a 200 OK code while the page content shows something is wrong, plus scheduled runs and a check against blacklists of malicious hosts.

Now the noise. Automated checks mislead in both directions. Terence Eden, who gave up on an automated checker and now checks his old posts' links by hand, is blunt about why he distrusts status codes: "Lots of the dead sites have been taken over by scammers, spammers, and AI grifters. They return an HTTP OK and then serve up advertising." And in the other direction, plenty of live URLs simply refuse to talk to robots: on 11 August 2026, a tweet URL that exists returned HTTP 402 Payment Required to an automated fetch, and a plain 200 to a re-check on 12 October. That's one client on one day rather than a claim about any platform — but paywalls, consent walls and bot management routinely answer non-browser agents with 402, 403 or 429.

So the target is never zero errors. Automate detection and inventory, keep a human on adjudication, and treat the ignore list as a maintained artefact: every entry should carry a comment saying which URL it covers and why. Otherwise, in eighteen months, it's just a list of things you've agreed not to look at.

A rule for every verdict

The audit only pays off if each result has a predetermined action; otherwise the report becomes a backlog. Start from the best-documented policy in existence, Wikipedia's. Its first principle is the one most people get wrong: "In general, do not delete cited information solely because the URL to the source does not work any longer." The claim and the link are separate things.

Wikipedia's repair order runs: find the content at its new location, check web archives, find an alternative source so the loss doesn't harm verifiability, then request a URL move. Dead links get a dated {{dead link}} tag, because "marking dead links signals to editors and to link rot bots that this link needs to be replaced with an archived link or a more current source verifying the same information."

That approach scales: by October 2018, more than 9 million broken Wikipedia links had been repaired by pointing them at Wayback snapshots, across 22 language editions. Your archive is not Wikipedia, but the pattern transfers.

Here's the table version, adapted for a blog. It's a proposal rather than a standard — commit it beside your ignore list, and a scary-looking report turns into ten minutes of work.

What the pass sees What it usually means The rule
200, same page Healthy Leave it; cache the result
301/308 → equivalent page Reorganisation (the Next.js case) Rewrite the URL to the final destination; no prose change
301/307 → homepage or docs root Page deleted, redirect papering over it Treat as dead: find the new page, else a snapshot, else re-source the claim
301 → error page Content retired in a migration Same as above — your checker must evaluate the final status
404 / 410 Honest death Snapshot if the claim still needs the citation; otherwise replace the source
402 / 403 / 429 / consent wall Probably alive, bot-blocked Verify by hand once, then add to the ignore list with a comment
200 but content unrelated Drift, repurposing, or a resold domain Highest risk: re-read your own sentence, because the claim may now be wrong
DNS failure or parked page Domain expired or resold Never re-link the live URL; snapshot or remove
No snapshot anywhere Unrecoverable Rewrite the sentence so the claim stands alone, or cut it

Two of those rows lean on archives, and that step has an API so it needn't stay manual. A request to the Wayback availability endpoint, such as http://archive.org/wayback/available?url=example.com&timestamp=20060101, returns the closest snapshot's URL, timestamp and status. If the URL is not archived or currently not accessible, it returns {"archived_snapshots":{}}. That empty object is your triage signal, but retry it before you trust it, because a temporarily unreachable archive produces the same answer. A confirmed empty result means the citation is unrecoverable and the work moves back into the prose. Note the limits, though. The Internet Archive was knocked offline by a DDoS attack on 9 October 2024, and archive.org was still only provisionally available in read-only mode on 21 October. Several archive.org pages were returning server errors again when we re-checked this post on 12 October 2026. Combined with that ~15% of citations nothing could recover, archives are an excellent fallback and a poor strategy.

The cheapest repair is the one you set up before the link dies — and almost nobody does. Klein's analysis found that around 65% of URI references had no archive snapshot within 30 days of their citing article's publication, and around 75% had none within 14 days. The snapshot you want later usually doesn't exist, because nobody took it at the time.

Three habits fix that. First, save each cited page as you publish: Save Page Now at web.archive.org "save[s] a specific page one time" — it does not add the URL to future crawls, and there's a documented 3–10 hour lag before the capture appears. Second, record what the link resolved to: the final URL, the destination title, and the one sentence you're relying on. Since no small-blog tool reliably detects "still 200, no longer the same page", evidence stored at publish time is the only thing a later drift check can compare against.

Third, Robust Links is the standards-flavoured version: data-originalurl, data-versionurl and data-versiondate attributes on the anchor, so a reader can choose the live page or the snapshot as it stood the day you cited it.

This is where automated drafting earns its place instead of adding to the pile. The useful output of publish-time checking isn't a green tick — it's the record of what every link resolved to and when. Magic Share's agent checks every cited link before it hands over a draft, and it attaches a link verification report to every draft: read that report as the day-zero baseline your day-700 drift check will diff against, and archive its URLs while they're warm. If you're auditing fresh drafts rather than an old archive, the companion piece is our 20-minute fact-checking checklist for AI drafts — same discipline, opposite end of the timeline.

Keep the dates honest afterwards. Google's guidance is direct: "Don't specify future dates, or the date of the action described on the page. The dates must describe the publication or update date of the page", and visible dates must stay consistent with structured ones — where dateModified means the date and time the article was most recently modified. Repairing two links is not a republication; a genuine rewrite is.

Cadence, and what "done" looks like

Pick the interval from the decay data rather than from enthusiasm. Pew's newest pages lost roughly 8% within their first year, so an annual pass can leave about a twelfth of your recent citations wrong for up to twelve months, while a daily full crawl mostly re-checks links that were fine yesterday. Monthly across the whole archive is cheap once responses are cached, and quarterly is defensible. Every build should also re-check the newest post's links plus any URL that has failed before. Prioritise by risk with the evidence you already have: deep links before root URLs, .com before institutional domains, shorteners before anything, vendor docs and startup blogs before standards bodies.

Be clear about the payoff, because a technical reader will ask. Outbound links are not a ranking factor. Search Engine Journal's verdict is that their presence on its own is not a ranking factor, and it quotes Mueller in 2016 that "external links to other sites... isn't specifically a ranking factor. But it can bring value to your content and, in turn, can be relevant for us in search," and Danny Sullivan in 2019: "I'd think of linking as just part of proper attribution." So don't sell this as a traffic lever. Sell it as accuracy, reader trust, and not handing readers a parked domain.

The adjacent case for touching old posts at all is HubSpot's report that historical optimisation raised monthly organic search views of the old posts it optimised by an average of 106%. That's a vendor self-report, though, and the intervention was a full refresh rather than link repair.

One question is worth flagging rather than answering: as answer engines increasingly summarise archives, does a dead citation make a page less likely to be cited? I found no evidence either way. What is evidenced is that verification pressure is rising at both ends of the pipeline — an April 2026 study of commercial LLMs and deep-research agents found 3–13% of citation URLs hallucinated and 5–18% non-resolving. If you're working on getting cited by ChatGPT and AI Overviews, a citation trail that still resolves is table stakes.

"Done" isn't zero broken links forever. It's a maintained ignore list, a written rule per verdict, a scheduled job that files its own issue, and a first pass that ends like that indie blog's did: 376 links, one error, one snapshot substitution.

FAQ

How often should I run a link rot audit on my blog? Monthly across the whole archive if your checker caches results, quarterly at minimum, and on every build for the newest post plus any URL that has failed before.

Do broken outbound links hurt my SEO rankings? Not directly: Search Engine Journal concludes that outbound links on their own are not a ranking factor. The real costs are accuracy and reader trust, since a dead citation can now lead to a parked domain serving scams.

What's the difference between link rot and content drift? Link rot is a URL that no longer resolves; content drift is a URL that still resolves but no longer says what you cited it for. Together they're called reference rot, and drift is the more dangerous half because status codes can't see it.

Should I replace dead links with Wayback Machine snapshots or delete them? Follow Wikipedia's principle and don't delete cited information solely because the URL stopped working. Try the new location, then a snapshot, then an alternative source, and cut the claim only when all three fail.

Why does my link checker report errors for pages that clearly work? Paywalls, consent walls, login gates and bot management often answer non-browser clients with 402, 403 or 429. Verify each by hand once, then add it to .lycheeignore or --exclude with a comment explaining why.

An archive is a garden, not a monument

Publish-time verification is the floor. It proves a citation was real on the day it shipped, which matters — but a link checked once is a link checked once, and the median deep link only lives about 1.3 years. A scheduled re-resolution pass plus a written rule per verdict turns that decay from an ambient embarrassment into a small recurring task with a defined end.

For a pre-publish pass that covers both link and claim accuracy, this audit of Google's October 2026 AI content guidelines turns the rater attributes into twelve yes/no checks.

Set the cron job this week. Grep for shortener domains first, run lychee --dump to see how many citations you're carrying, and commit the decision table so future-you doesn't have to re-litigate what a homepage redirect means.

And if the bigger problem is that new posts arrive faster than you can verify them, that's the part Magic Share handles. The agent researches, drafts, and checks every cited URL before handing a draft over, then waits for your approval: nothing publishes until you press publish, and on a git-backed site the publish step is a pull request you merge. The free plan includes three posts, enough to point it at your own site and read a real verification report before you commit to anything.

More on Content strategy →

by email

Get new posts in your inbox

A short digest when new posts go up. Confirm once, unsubscribe from any email.

We use your address only for this digest. Privacy

Keep reading

  1. ·15 min read

    Google AI Content Guidelines (Oct 2026): Audit a Post

    Google AI content guidelines now define main content and four rater attributes. How to audit an AI-drafted post for effort, originality and accuracy.

    seogoogle-searchai-contentfact-checkinghelpful-content

  2. ·12 min read

    Do You Have to Disclose AI-Written Content? (2026)

    Do you have to disclose AI-written content? Google doesn't require it and advises against an AI byline. Here's what to credit instead in 2026.

    ai-contentseogoogle-searchpublishingcontent-strategy

  3. ·16 min read

    Update Old Blog Posts vs Write New Ones: A Small-Blog Rule

    Update old blog posts vs write new ones? On a 30-post blog, the split is a rule, not a ratio: refresh what lost half its impressions, publish into gaps.

    content-strategyseocontent-refreshsmall-blogpublishing

Want posts like this for your site?

Magic Share researches, writes and fact-checks posts like this for any site — point it at your URL and review your first draft today.

Plant your first post