Practical guide to broken links in 2026. Finding and fixing broken links at scale. Tools, redirects, and what 404s are okay.

Broken links: A Practical Guide for 2026

Introduction

Broken links are URLs that return a 4xx or 5xx status code instead of the expected content. On most sites, the majority of these resolve to 404 errors, signaling that a page either never existed, was moved without a redirect, or was deleted. Left unchecked, broken links frustrate users, waste crawl budget, and quietly erode the signals that search engines use to evaluate a site.

This guide is written for SEO practitioners, developers, and content teams who need to find and fix broken links at scale. We'll cover what 404 errors actually mean, how to choose the right redirect strategy, which tools surface link rot fastest, and which broken links you can safely ignore. Along the way, we'll reference the authoritative documentation from Google Search Central and MDN so you can verify any technical claim we make.

Why broken links matters in 2026

Crawlers have gotten better at tolerating occasional dead ends, but the underlying mechanics have not changed. Every broken link represents a failed promise to either a user or a search engine. When that promise fails often enough, the consequences show up in three places: user experience, crawl efficiency, and link equity flow.

First, users notice. Clicking a link that leads nowhere is one of the oldest signals of an unmaintained site, and it disproportionately affects the visitors who arrived through deep links from other domains. Second, search engine crawlers have a finite budget per site. Spending it on 404 responses is wasted effort that could have gone toward indexing your live pages. Third, inbound links that point to missing pages stop passing authority the moment the target goes away, unless you implement a redirect to a relevant destination.

The HTTP status codes documented at MDN describe 404 as "the server cannot find the requested resource," and 410 as "the intended resource is no longer available at the origin server and that this condition is likely to be permanent." That distinction matters because search engines treat the two slightly differently when deciding whether to keep crawling the URL.

Core principles

A few fundamentals apply no matter how large your site is:

Status code semantics are contracts. A 404 means "not found," a 410 means "gone, and not coming back," and a 301 means "moved permanently." Mixing these up sends confusing signals. Reference the Google Search Central documentation on redirects before choosing one.
Redirects are not free. Every redirect chain adds latency and dilutes a small amount of PageRank-like signal. A clean 301 from the old URL to the closest-matching new URL is always preferable to a chain of three or four hops.
404s are not inherently bad. A 404 on a page that genuinely doesn't exist, served with a helpful custom page, is normal and expected. Problems arise when high-value URLs return 404, or when the volume of 404s climbs sharply over time.
Internal and external broken links are different problems. Internal broken links are within your control. External broken links (other sites pointing at you) require either outreach, a redirect, or a custom 404 that suggests a relevant alternative.
Log files beat crawlers for scale. A crawl-based tool only sees what it requests. Server access logs show you every status code real users and bots actually received, including URLs you didn't know existed.

Common mistakes

Teams that handle broken links poorly usually fall into the same traps:

Redirecting everything to the homepage. A "sledgehammer" 301 from every removed page to / is treated as a soft 404 by search engines and provides no user value. Send users to the closest relevant URL instead.
Chaining redirects. Page A → Page B → Page C → Page D is fragile. If Page B is later removed, the whole chain collapses. Collapse multi-hop chains into a single redirect whenever possible.
Returning 200 for missing pages. Some CMS configurations send a 200 status code with a "not found" body to avoid hard errors. Search engines treat this as a real page and may index thin content. Confirm with your crawler that missing pages return a real 404 or 410.
Ignoring soft 404s. Soft 404s are pages that return a 200 status but display "not found" content. Crawlers flag these in reports, and they waste indexing slots.
Blocking 404 pages in robots.txt. If a crawler can't fetch the URL, it can't see the 404 and may keep requesting it indefinitely from other sources. Let crawlers reach your 404 pages.
Skipping log file analysis. Relying only on scheduled crawls misses URLs hit by external referrers, old sitemaps, or stale bookmarks. Logs are the ground truth.
"Fixing" 404s that should stay 404. URLs from spam referrers, hacked pages, or obvious typo-squats are fine to leave as 404. Redirecting them to real pages can be treated as a manipulative signal.
Forgetting parameter and case variants. /page, /Page, /page?ref=abc, and /page/ can each return different status codes depending on configuration. Audit them explicitly.
Treating 410 as interchangeable with 404. A 410 tells crawlers to de-index the URL faster. Use it for content you have intentionally and permanently removed. Use 404 when the absence might be temporary or accidental.
Not monitoring after migrations. Site migrations generate spikes in broken links for weeks afterward. Schedule recurring audits rather than one-time sweeps.

Tools

There is no single tool that handles every broken link scenario. A practical workflow combines crawl-based tools, log analysis, and a redirect manager.

SiteRepair Site Audit. Run a full crawl at SiteRepair's site audit tool to get a categorized list of 4xx and 5xx URLs, including the referring pages that link to them. The audit groups errors by template, which makes it easier to fix hundreds of URLs at once.
SiteRepair SEO Checker. Use the SEO checker for a quick read on technical issues including redirect chains and orphaned pages, useful for spot checks between deeper audits.
Server access log analysis. Tools like the AWS-style log analyzers or self-hosted options parse your real traffic for every 4xx and 5xx response. This is the only way to surface broken links that no crawler knows about.
Screaming Frog SEO Spider. A desktop crawler that scales into the millions of URLs, integrates with Google Analytics and Search Console, and exports directly into redirect-mapper spreadsheets.
Google Search Console. The Pages report and URL Inspection tool show which URLs Google has actually indexed and which return errors. Export these lists before and after any redirect rollout.
Open-source crawlers (e.g., Sitebulb alternatives, wget-based scripts). Useful for very large sites where commercial crawlers get expensive. Combine with a redirect manager for bulk rules.
CDN-level rewrite rules. Most CDNs allow you to apply edge-level rewrite rules that 301, 404, or 410 any URL globally without touching application code — the fastest way to roll out redirects and harden old links across your entire site at once.

Actionable steps

Step 1: Run a comprehensive crawl to map every broken URL

Start by exporting every URL on your site from your CMS or analytics, then compare it against an automated crawl report. The free SiteRepair site audit flags broken links alongside other crawl-level issues in a single pass, so you can build your fix list in minutes instead of hours. Pay special attention to 404s, 500 errors, and soft 404s, because each behaves differently in how search engines treat them. Group the results by template or section so you can spot patterns rather than patching URLs one at a time.

Step 2: Decide whether to redirect, restore, or remove

Not every broken link deserves a redirect. If the destination page still has traffic or backlinks, set up a 301 redirect to the most relevant live page on your site. If the page is gone for good and nothing replaces it, returning a proper 404 or 410 is actually healthier than redirecting users to an unrelated page. The SEO checker can help you confirm that your chosen resolution matches current best practice for the specific URL pattern.

Step 3: Fix the source links, not just the destinations

Redirects solve the user-facing problem, but they leave the underlying broken links sitting in your content, navigation, and sitemaps. Search through your templates, blog posts, footer links, and XML sitemaps to update or remove the offending URLs at the source. This step matters because every internal broken link is a wasted crawl opportunity and a small loss of link equity flowing through your site.

Step 4: Check external links and reclaim lost backlinks

Head over to your backlink profile in a third-party tool and look for referring domains pointing at pages that now return 404s. Outreach to those sites asking them to update the link to a working URL can recover real link equity. For outbound links from your own site pointing at external 404s, swap them for an alternative resource or remove them entirely so you are not sending users to dead ends.

Step 5: Validate the fixes and set up ongoing monitoring

After deploying redirects and edits, re-run the free SiteRepair site audit to confirm the broken links count has dropped to zero. Schedule a recurring crawl, monthly at minimum and weekly for larger sites, so new broken links are caught before they accumulate. Pair this with alerts from your server logs so you hear about sudden spikes in 404s the same day they happen.

Frequently asked questions

How many broken links are too many for SEO? There is no single threshold Google publishes, but a small handful of broken links on a large site is normal and unlikely to cause ranking issues. The real risk comes from patterns, like dozens of broken links on key templates or broken internal links blocking important pages from being crawled. Treat any sudden jump in broken link count as a signal worth investigating rather than a one-off cleanup task.

Do 404 errors hurt my Google rankings directly? Google's own guidance is that a moderate number of 404s will not damage rankings, but widespread broken links can hurt user experience and crawl efficiency, which over time can affect visibility. The bigger concern is that broken links waste crawl budget, meaning Google may discover and index fewer of your working pages. Run the free SiteRepair audit to see how concentrated your broken links are and prioritize from there.

Should I use 301 redirects or just fix the links? A 301 redirect is the right call when the destination page has moved permanently and a clear replacement exists. If the page is gone for good and has no logical replacement, updating or removing the source link is better than redirecting to an unrelated page. Mixing the two strategies based on intent will keep your link graph clean and avoid the soft-cannibalization issues that come from mass redirecting everything.

How long does it take Google to recrawl and process my fixes? Once you submit an updated sitemap and the pages are reachable, Google typically recrawls within a few days, though large sites can take longer. You can speed things up by using the URL Inspection tool in Search Console on the fixed URLs and requesting indexing. After a week or two, re-run your audit to confirm the changes are reflected and to catch anything that was missed.

What's the fastest way to find broken links on a small site? For sites under a few hundred pages, the free SiteRepair site audit will return a complete broken link list in under a minute, grouped by URL and source page. That is usually faster and more reliable than manually clicking through every page or relying on browser extensions that only check the page currently open.

You can check this on your site with the Free Site Audit — it runs the relevant checks in under a minute.

Try it on your site

Run a full audit to find every broken link: Free Site Audit →

For a deeper look, also run the Redirect Checker.

These checks are part of the free SiteRepair site audit, which combines every tool on this page into one report.