404 Errors and SEO — What They Cost and How to Fix Them

Not all 404 errors are created equal. A page that was created, got zero inbound links, and was then deleted is effectively a non-event — one wasted crawl, no equity loss, nothing to worry about. A page that accumulated backlinks over years, drove traffic, and then quietly returned 404 after a site migration is a serious ranking problem. The severity of a 404 depends entirely on what was pointing to it.

Understanding which 404s actually matter — and which action to take for each — is the skill. This guide covers the SEO mechanics of 404 errors, the decision framework for fixing them, and the tools that surface them before they compound.

The SEO Cost of 404 Errors

Crawl budget waste. Googlebot crawls links it finds. If internal pages link to 404 URLs, Googlebot spends crawl quota visiting dead ends. For large sites, this adds up — thousands of broken internal links can meaningfully reduce how often Google crawls your live pages. Crawl budget is not infinite, and every wasted request on a dead URL is a request that didn't go toward discovering or refreshing your content.

Link equity loss. External backlinks pointing to a 404 page pass zero equity. The link exists in the referring domain's HTML, but the destination is gone — the equity evaporates. If you've deleted a page that had valuable backlinks from high-authority sites, those links are no longer helping your rankings. This is often the most damaging consequence of a 404, particularly after site migrations where URLs change without redirects being set up.

User experience signals. Users clicking a link that leads to a 404 bounce immediately. High bounce rate from organic search results is a negative engagement signal. If the 404 appears in search results — it can, briefly, if Google cached the URL before the page was removed — the bad experience affects perceived site quality. Repeat 404 experiences across a site erode user trust and increase pogo-sticking back to search results.

GSC Coverage report. 404s on pages in your XML sitemap appear as "Submitted URL not found" errors in Google Search Console — a direct flag that your sitemap is pointing Google to dead pages. Having a sizeable number of these tells Google your sitemap is unreliable and may cause it to deprioritise sitemap-submitted URLs.

Which 404s Actually Matter

The Three Fixes

1. 301 redirect. Use this for any 404 that previously had traffic, backlinks, or is listed in your sitemap. A 301 redirect tells both users and search engines that the page has permanently moved to a new URL, and transfers approximately 90–99% of the link equity from the old URL to the new destination. Redirect to the most topically relevant live page on your site.

One important nuance: don't redirect everything to the homepage as a catch-all. Google may treat mass homepage redirects as "soft 404s" — it detects that the destination is generic and not a true equivalent for the requested URL, and discounts or ignores the redirect entirely. Redirect to a page that genuinely serves the same user intent as the deleted page.

2. Restore the page. If the content was useful and you deleted it by mistake, restore it. The original URL keeps all its backlinks, search history, and internal links intact — no redirect equity loss, no broken chain. This is always the cleanest fix when the content itself still has value and the deletion was unintentional.

3. Leave as 404 (or upgrade to 410). For pages that never accumulated traffic, backlinks, or internal links, the correct action is often nothing. A 410 (Gone) status code is a stronger signal than 404 — it explicitly tells Googlebot the resource is permanently gone and will never return, which speeds up deindexing. Useful when you've bulk-deleted pages (old product variants, expired event pages, duplicate content) and want Google to clear them from its index quickly rather than recrawling them repeatedly.

Finding 404 Errors on Your Site

Google Search Console → Coverage. The Coverage report shows "Submitted URL not found" errors for pages in your sitemap, and "Not found (404)" for discovered URLs Google has attempted to crawl. Your most important 404s are in these two lists — prioritise them by how recently they had impressions or clicks in the Performance report.

ByteWaveNetwork Link Checker. Crawls your entire site from the homepage, following every internal link. Reports all broken internal links — 404s and other error codes — with the source page for each. That "source page" column is critical: it tells you not just which URLs are broken, but which of your live pages contain the broken links. This gives you the complete fix list: update the link on the source page and either redirect or restore the destination.

ByteWaveNetwork Sitemap Validator. Checks every URL listed in your sitemap and flags 404 responses. A sitemap is a direct signal to Googlebot about which pages to crawl — having 404s in it sends the wrong signal and wastes the crawl budget allocated to sitemap-submitted URLs. Run this after any content deletion or site restructure to confirm the sitemap is still clean.

301 Redirect Best Practices

Redirect to the most topically relevant live page — not the homepage. If you deleted a blog post about email deliverability, redirect to your email marketing category page or a related post, not to the root domain.

Avoid redirect chains. A chain where A redirects to B and B redirects to C wastes crawl budget at each hop and dilutes the equity transfer. Redirect directly to the final destination (A → C). Use the Redirect Tracer to audit existing redirect chains and identify any that have grown beyond two hops.

Update internal links to point directly to the destination URL after setting up a redirect. Internal links through redirects slow down crawling and create unnecessary hops. Once the redirect is in place, find every internal page linking to the old URL and update the href to the final destination directly.

Batch your redirects in your web server config or CMS rather than managing them individually. A well-structured .htaccess file, Nginx rewrite block, or CMS redirect manager is far more maintainable than one-off page-level redirects.

Bulk 404 Cleanup

When a site migration or CMS change has produced dozens or hundreds of 404 errors, a systematic approach saves time:

Step 1. Export the full list of 404 URLs from GSC or the Link Checker. You want two columns: the broken URL and the page that links to it (source page).

Step 2. Sort by inbound link count. Tools like Ahrefs or Majestic can show you which broken URLs have the most referring domains — prioritise those first, since they represent the most equity loss.

Step 3. For each high-equity 404, find the most topically relevant live page and set up a 301 redirect. Group similar URLs (e.g., old product SKUs that map to a new category) into pattern-based redirect rules rather than listing each one individually.

Step 4. Remove 404 URLs from your sitemap immediately. Don't wait until the redirects are in place — a sitemap pointing to broken URLs is worse than a smaller, accurate sitemap.

Step 5. For internal broken links: update the href on the source page to point directly to the redirect destination, bypassing the redirect chain entirely. The Link Checker's source page column makes this step mechanical — work through each source page once.

Affiliate disclosure: Some links on this page may be affiliate links. We only mention tools we've personally used and have an honest opinion about. Affiliate revenue helps keep ByteWaveNetwork's tools free and maintained. We are not paid by any of the tools compared in this article for favorable coverage.