← All articles

Broken Link Monitoring: Setting It Up Right

John Liddy ·

Close-up of HTML and JavaScript code on a computer screen in Visual Studio Code.

Broken link monitoring is one of those things every site owner assumes is handled until a customer emails to say the "Buy Now" button goes nowhere. Links break quietly: a vendor renames a page, a partner site redesigns, an internal page gets deleted during a content cleanup, and nothing alerts you because the server still returns a page, just not the right one. Monitoring for broken links isn't about running a one-time scan before launch. It's about building a recurring check that separates real breakage from noise, catches both internal and outbound failures, and gives you evidence you can act on instead of a long list you ignore.

What Counts as a Broken Link

A broken link isn't only a 404. It includes soft 404s where a page returns a 200 status but shows an error message or empty content, redirect loops that never resolve, links to pages blocked by robots.txt, and outbound links to domains that have expired or changed ownership entirely. Each of these behaves differently in a scan, so a tool that only checks for 404 status codes will miss a meaningful share of real breakage.

Internal links matter most because they affect navigation and crawl paths directly. If your product pages link to a category page that no longer exists, visitors stall and search engines waste crawl budget following dead paths. Outbound links matter for a different reason: they signal site quality to visitors and, less directly, to search engines evaluating your page's trustworthiness. A page full of dead citations or expired partner links looks neglected even if the content itself is fine.

The practical move is to treat internal and external links as separate checks with separate urgency. An internal 404 on a page that gets traffic is urgent. An outbound link to a blog post that moved is lower priority but still worth a monthly cleanup pass.

How Often to Scan and Why Frequency Matters

A quarterly scan catches the obvious rot but misses the links that break right after a vendor update or a CMS migration. Weekly scans catch problems closer to when they happen, which matters most for high-traffic pages like pricing, contact, and top product pages. For a small site with modest traffic, monthly scanning of the whole site paired with weekly spot-checks on key pages is usually enough.

The frequency decision should follow traffic, not convenience. A page that drives five percent of your conversions deserves more frequent checking than an archived blog post from three years ago. If you don't have per-page traffic data handy, Search Console's performance report gives you a rough sense of which URLs actually get clicks, and that should guide where you point monitoring effort first.

It's also worth scanning right after any site change: a plugin update, a theme switch, a bulk content edit, or a migration. These events are where most new broken links originate, and catching them within days rather than weeks keeps the damage contained to a short window instead of months of silent decay.

Turning Scan Results Into Action

A list of broken links is only useful if someone reads it and fixes things. The common failure mode is treating the scan as the deliverable rather than the fix. Set a rule: anything found on a page with meaningful traffic gets fixed within a week; everything else goes into a monthly batch cleanup. Without this split, teams either ignore the list entirely or burn hours fixing links nobody will ever click.

When you find a broken internal link, the fix is usually a redirect to the closest living equivalent page, not just a silent removal of the link. Removing it without redirecting loses whatever value that old URL had built up. When you find a broken outbound link, decide whether the citation still matters; if it does, look for an archived version or a replacement source rather than just deleting the reference.

Keep a simple log of what broke, when, and why, even if it's just a spreadsheet. Patterns show up over time: if the same category of page keeps breaking after every content update, that's a process problem, not a link problem, and it's worth fixing the workflow rather than repeatedly patching symptoms.

Keep reading

More on this topic: Run a free health scan · See monitoring plans

We use Google Analytics to understand how visitors find Site Clinic. No cookies fire until you choose. Privacy policy.