Broken Links Are Killing Your SEO — Here's How to Find Them

A broken link is a small thing on its own — one dead URL, one 404 page. But most sites don't have one broken link. They have dozens, sometimes hundreds, hiding in old blog posts, footer menus, resource pages, and comment sections. Left alone, they chip away at rankings, waste crawl budget, and quietly convince visitors your site isn't maintained.

Here's how to actually find them — not just the theory, but the specific methods that work.

Why Broken Links Matter More Than You'd Think

Search engines treat broken links as a signal of poor site quality. If Googlebot repeatedly hits 404s while crawling your site, it can:

• Waste crawl budget on dead ends instead of your actual content
• Lower the perceived trustworthiness of pages linking to those dead URLs
• Break the flow of internal link equity between your pages

On the user side, a broken link is a dropped conversation. Someone clicked expecting an answer and got a "Page Not Found" instead. Depending on where that link sits — a product page, a checkout step, a resource in your top navigation — that's a lost sale or a lost reader who won't come back.

Internal vs. External Broken Links

Not all broken links are equal, and you should treat them differently:

• Internal broken links point to pages within your own site that have been deleted, renamed, or moved without a redirect. These are fully within your control to fix.
• External broken links point to other websites that have since taken down the page, restructured their URLs, or gone offline entirely. You can't fix the destination, but you can update or remove the link.

Manual Methods to Spot Broken Links

1. Check Google Search Console First

Before running any third-party tool, look at what Google already knows:

1. Open Google Search Console and go to Pages under the Indexing section
2. Look for entries marked "Not found (404)"
3. Cross-reference these against your sitemap to see if any of them should actually exist

This shows you exactly what Google is stumbling on when it crawls your site — which is often more urgent to fix than links only a human visitor might click.

2. Use Ctrl+F on Key Pages

For smaller sites, manually clicking through navigation menus, footers, and your most-linked blog posts is tedious but effective. Pay particular attention to:

• Footer and header navigation (these appear site-wide, so one broken link multiplies across every page)
• Resource or "further reading" sections in older blog posts
• Comparison tables or "best of" list posts that link out to many external sites
• Old landing pages from past campaigns that may reference discontinued products

Faster, More Reliable Ways to Scan Your Whole Site

Manual checking works for a handful of pages, but it doesn't scale. For anything beyond a small site, you need something that crawls every link automatically.

3. Run a Full Site Crawl

Tools like Screaming Frog SEO Spider (free up to 500 URLs) crawl your entire site and flag every link returning a 4xx or 5xx status code. The workflow looks like this:

1. Enter your root domain and start the crawl
2. Once complete, filter the results by Response Codes
3. Sort by status code to separate 404s (not found) from 301/302 redirects and 500-series server errors
4. Export the list with the source page column included, so you know exactly where each broken link lives

4. Check Redirect Chains, Not Just Dead Links

A link doesn't have to return a 404 to be a problem. Redirect chains — where a URL redirects to another URL, which redirects again — slow down page load, waste crawl budget, and sometimes eventually terminate in a dead end anyway.

This is where a dedicated redirect checker is genuinely useful: paste in any URL and see the full chain of redirects it goes through, including the final status code. If you spot a chain of three or four hops before landing on a working page, that's worth cleaning up into a single direct redirect — both for SEO and for page speed.

5. Test External Links Separately

Because external broken links depend on other sites' uptime and structure, they need periodic rechecking even after you've fixed them once. A site you linked to a year ago might have restructured its URLs since. Build this into a recurring habit rather than a one-time fix.

Common Mistakes When Auditing for Broken Links

• Only checking the homepage and main nav. Most broken links live deep in old blog content, not your primary navigation.
• Ignoring redirect chains. A working redirect isn't the same as an efficient one — chains still cost you crawl budget and load time.
• Fixing links without checking why they broke. If a page was deleted and never redirected, that's a process problem, not just a one-off link problem. Make 301 redirects part of your standard workflow whenever you retire a URL.
• Not checking images and downloadable files. Broken links aren't limited to anchor text — missing images, dead PDF links, and broken embedded videos count too.
• Running the audit once and forgetting about it. Link rot is ongoing. Sites you linked to externally will eventually restructure or disappear, so schedule rechecks quarterly at minimum.

Fixing What You Find

Once you have your list of broken links, prioritize fixes in this order:

1. High-traffic pages first. A broken link on a page ranking well and getting real visits does more damage than one buried in a post nobody reads.
2. Internal links before external. You have full control over internal fixes — either update the link or set up a proper 301 redirect to the correct page.
3. Replace or remove dead external links. If the original source is gone, look for an archived version via the Wayback Machine, find an equivalent resource, or simply remove the link if it's no longer necessary.

For any link you're unsure about — especially ones inherited from old content or written by a previous contributor — it's worth confirming exactly where it leads and whether it passes through any suspicious redirects before you republish it.

Run your site's links through AXOX Hub's free redirect checker to trace every hop, catch redirect chains, and confirm your fixes actually resolve to a working page.