Broken Link Checker

Practical guide: triaging what this checker finds

What this is

This tool probes outbound or listed URLs from a page or list and surfaces HTTP failures, timeouts, and obvious transport errors. It is ideal for periodic hygiene on blogs, resource pages, and directories—not a full-site enterprise crawl replacement. Treat the report as a prioritized punch list, not an automatic delete-everything script.

When to check for broken links

• After migrations, domain changes, or bulk slug updates that invalidate old paths.
• On evergreen resource hubs and “best of” posts that accumulate third-party citations over years.
• Before a major PR or paid campaign that will drive traffic to a curated link list.
• As a recurring item in your Search Console weekly routine when crawl errors spike.
• When UX surveys mention “dead ends” or support tickets cite missing partner pages.

When not to overreact

• Do not rip out every external 403 on a paywalled research source that still helps readers who have access.
• Avoid treating a single intermittent 5xx as permanent—retest before rewriting content.
• Do not “fix” soft 404s only with this tool; 200 pages that say “not found” need content or redirect work.
• Skip deleting educational internal links; update the target or add a 301 instead.
• Do not assume a bot-blocked partner is broken for real users—verify in a browser.

How to use this checker

Provide the starting URL or paste the links you care about, then run during off-peak windows for large batches. Export or note status codes: fix true 404s first, then 5xx that indicate instability. For third-party links that died, swap to an archive, a new authoritative source, or remove the anchor if nothing trustworthy remains. Assign owners and due dates so the list does not sit forever.

Worked example

A 2021 “vendor comparison” article lists twelve external product pages. The checker reports: three 404s, one timeout, two 301 chains, and one 200 that is a soft 404 (“product discontinued”). Triage: map the three 404s to successor product URLs with updated anchors; replace the soft 404 with a note plus link to the category; retest the timeout twice at different hours—if it persists, cite a secondary source; update the two 301 chains so anchors point to final destinations (cleaner for users and crawl budget). Internally, any site links still pointing at retired review URLs get 301s via the redirect generator. After edits, re-run the checker on the same URL list and file the before/after in your hygiene log (technical hygiene checklist).

How to read the results

Soft 404s (200 pages that behave like missing content) may not flag as broken here—pair with manual spot checks. Intermittent 5xx deserves retests before you rip links out. Some sites block automated fetchers; false negatives/positives can occur—verify in a browser or with curl when a major partner “looks broken.” Group by status code and by internal vs external so engineers and editors own the right queues.

Common mistakes

• Deleting educational internal links instead of updating targets.
• Ignoring broken anchors in PDFs, footers, or JS-rendered menus the tool never saw.
• Chasing every external 403 on gated sources that still serve legitimate readers.
• Forgetting to re-check after migrations when new 404 clusters appear.
• Leaving redirect chains in place because “the link still works.”
• Running one scan a year while the CMS auto-publishes broken related-post widgets.

QA checklist after a fix pass

1. Re-scan the same URL set; critical 404/5xx counts should drop.
2. Click a sample of updated anchors in a private browser session.
3. Confirm internal replacements use 301s where old paths must stay bookmarked.
4. Update sitemaps if retired URLs were listed—see sitemap include/exclude.
5. Note any bot-blocked partners with a manual “verified OK” comment so the next scan does not reopen the ticket.
6. Schedule the next check on the calendar; resource hubs deserve quarterly passes.

Related reading

SEO guide · Technical hygiene · Search Console checklist · XML sitemaps. Related tools: redirect generator, SEO audit, technical SEO tools.

Before / after: resource hub cleanup

Before: A “free tools and research” hub had 40 outbound citations. A single scan found eight hard 404s and five multi-hop redirects. Editors had been adding links for years without a retirement process.

After: Dead citations were replaced with current primary sources or removed with a short editorial note. Redirecting links were rewritten to final destinations. A quarterly calendar invite now runs this checker on the hub URL, and new posts must pass a link spot-check before publish. Support tickets about “outdated references” dropped the following quarter.

Triage order that saves time

Fix internal 404s first (you control them), then money-page externals that influence trust, then long-tail blog citations. Park bot-blocked partners in a “manual verify” column so automated noise does not drown real work. When a whole path prefix breaks after a migration, prefer bulk redirects over editing hundreds of posts by hand—then re-scan to confirm.