404 page SEO impact guide showing when 404 errors harm rankings versus when they are harmless
Technical SEO

404 Pages and SEO — What's the Real Impact?

Sunny Pal Singh · · 6 min read

404 errors are frequently overstated as an SEO problem. Google's John Mueller has confirmed that 404 pages themselves don't harm a site's overall rankings — Google expects pages to disappear. The actual SEO impact comes from two specific scenarios: internal links pointing to 404 pages (which waste crawl budget and create a poor user experience), and 404s on URLs that previously had backlinks (which silently delete link equity from your site). This guide explains when 404s matter, when they don't, and how to find and fix the ones that do.

Key Takeaways

  • A 404 response on a URL that never had backlinks or internal links causes no SEO harm — Google discovers it, notes it as gone, and stops crawling it
  • A 404 on a URL that has backlinks from other sites permanently loses that link equity — a 301 redirect to the most relevant current page recovers it
  • Internal links to 404 pages waste crawl budget (Google spends crawl quota on pages that return nothing) and create broken user journeys — fix with internal link updates or redirects
  • GSC's Coverage report "Not found (404)" section shows which 404 URLs Google has encountered and how many pages link to them — sort by "Linked from" count to prioritise
  • Soft 404s (pages returning 200 status but containing thin or empty content) are worse than hard 404s — Google may index them as low-quality content rather than treating them as gone

When 404s Actually Harm SEO

Not every 404 is a problem. The three scenarios below are the ones that genuinely hurt — the rest you can ignore.

Scenario 1 — 404 With External Backlinks

If a page is deleted but external sites still link to it, all the link equity from those backlinks is lost. The URL returns 404, the linking sites' PageRank flows nowhere. This is the most impactful 404 scenario — a popular page that earned dozens of inbound links can represent a significant ranking signal that has simply been switched off.

Fix: implement a 301 redirect from the old URL to the most topically relevant live page. The redirect passes link equity (approximately — Google says redirects can lose a small fraction) to the destination. Even a redirect to the homepage is better than a clean 404, because it recovers at least some of the equity. A redirect to a highly relevant replacement page recovers most of it.

Scenario 2 — Internal Links to 404 Pages

Google follows internal links when crawling. If 50 internal links across your site point to a deleted page, Google spends crawl quota on 50 requests that return nothing useful. On large sites with tens of thousands of pages, limited crawl budgets mean this kind of waste can meaningfully reduce how many live pages get crawled each day — and therefore how quickly new or updated content gets indexed.

Beyond crawl budget, broken internal links create poor user experiences. A visitor clicking a navigation link or related-post recommendation and landing on a 404 is a broken journey that rarely converts.

Fix: update or remove the internal links. Run the Link Checker on your domain to surface every internal link returning a 4xx status, the source page for each one, and the broken destination URL — then update the links to point to the correct live page.

Scenario 3 — Soft 404s

A soft 404 is a page that returns HTTP 200 (success) but contains almost no real content. Common examples: "Product not found", empty category pages when all items are out of stock, dynamically generated pages with no data, or pages that exist in a template but have never been populated.

These are worse than real 404s because Google wastes index capacity on thin content that may show up in search results as low-quality pages. Google's algorithms may eventually detect them as soft 404s and de-index them, but the process is slower and less clean than a real 404 response.

Fix: return a real 404 or 410 HTTP status code so Google knows to treat the URL as gone, or add substantial, meaningful content to the page so it earns its 200 status.

When 404s Don't Matter

Google's official guidance is clear: 404s on pages that were never important are handled automatically. Google discovers the 404, removes the URL from its index, and stops crawling it. This is normal website operation — pages get deleted, URLs change, content expires. Google has been handling this since its earliest days.

404s that don't require any action:

  • Old pages that never ranked, never had backlinks, and were removed intentionally
  • Typo URLs and URL variants that were never linked to
  • Staging or test URLs that accidentally got indexed
  • Expired promotions and seasonal pages with no backlink value
  • URLs that appear in GSC's 404 report but show zero "Linked from" pages

The test: check whether the 404 URL has external backlinks (use a backlink checker like Ahrefs or Moz) and check whether the URL appears in GSC's "Linked from" data. If neither condition is true — ignore it. Chasing every 404 in GSC is one of the most common time-wasting SEO activities. Prioritise by link count, not by sheer number of 404 entries.

Finding 404s That Matter

Method 1 — GSC Coverage Report

Google Search Console → Index → Pages → "Not found (404)". The list shows every 404 URL Google has encountered in recent crawls. For each URL, click through to see "Linked from" — which pages point to this broken URL, and how many. Sort by link count to prioritise which 404s are actually affecting your crawl budget or internal linking. This is the most direct signal Google provides about which 404s it considers significant.

Method 2 — Link Checker Crawl

Run the Link Checker on your domain. It performs a BFS crawl of every internal link and surfaces every destination returning a 4xx status — showing the source page, destination URL, and status code for each broken link. This surfaces the internal link issues that GSC doesn't directly show you (GSC reports 404 URLs but doesn't group them by which internal pages link to them the way a crawler does).

The Link Checker also distinguishes between broken links (404), blocked links (403), and redirect chains — so you get a complete picture of your internal link health in a single crawl.

Method 3 — Server Log Analysis

Parse your server logs for 404 responses. This is more work but catches 404s that Google doesn't crawl — for example, URLs only linked from external pages that Googlebot visits infrequently. It also surfaces 404s from real users who may have bookmarks, direct links, or referrals to pages that no longer exist. Log data gives you the full picture, not just what Googlebot has recently visited.

Fixing 404s

Once you've identified the 404s worth fixing, there are four options depending on the situation.

Option 1 — 301 Redirect. When the content has genuinely moved or has an equivalent replacement. The redirect passes link equity to the destination page. Best for: deleted pages with external backlinks, URL restructures (e.g. changing from /blog/post-name to /articles/post-name), domain migrations. Implement the redirect at the server or CDN level rather than in JavaScript — server-side 301s are processed before the browser renders anything, and are the form Google follows reliably.

Option 2 — Restore the Page. When the page was deleted by accident or still has demonstrable search demand. Check GSC for search impressions on the URL — if it was receiving clicks before it was deleted, restoring it (or redirecting to updated content) may recover that traffic. A high-impression URL that 404s is a straightforward quick win.

Option 3 — Update Internal Links. When the 404 is an internal link problem rather than a backlink problem. Find every page linking to the broken URL (the Link Checker surfaces these as "Found on" source pages) and update the link to point to the correct live destination. This fixes crawl budget waste without necessarily needing a redirect.

Option 4 — Do Nothing. When the 404 URL has no external backlinks, no internal links, and no ranking history. The only action needed is to monitor via GSC to confirm Google eventually stops crawling it. Most 404s in a healthy site fall into this category.

The 410 Status for Permanent Deletions

A 410 (Gone) status is the HTTP response code that tells Google the resource has been permanently deleted and will not return. Google de-indexes 410 URLs faster than 404 URLs — the signal is unambiguous. A 404 can theoretically mean "temporarily unavailable"; a 410 means "gone for good".

Use 410 when:

  • You are intentionally deleting content and don't want a redirect
  • You have thin or low-quality pages you want removed from Google's index promptly
  • You are cleaning up canonical URL variants you no longer want indexed

Most CMS platforms return 404 by default for deleted content — returning a 410 requires custom configuration. For WordPress, a plugin or custom code in your theme's functions.php can map specific URL patterns to 410. For custom servers, set the response status code explicitly in your route handler. The difference in de-indexing speed is real but modest — 410 is worth using for deliberate content removal, but don't spend significant engineering time implementing it for routine page deletions.

Custom 404 Page Best Practice

Even when a 404 is SEO-irrelevant, a good custom 404 page keeps the user engaged rather than sending them away. The requirements are straightforward but frequently overlooked.

Return HTTP 404 status — not 200. A page that looks like a 404 error page but returns a 200 status code is a soft 404. Google may index it as a low-quality page. Always verify your custom 404 page is actually serving a 404 response header.

Include site navigation. A user who lands on a 404 via a broken link or old bookmark should be able to reach your live content without using the browser back button. Navigation links, a search box, and links to your most visited sections all help.

Keep it on-brand with a clear message. Explain that the page doesn't exist, offer alternatives, and avoid making the user feel like something went wrong on their end. A clear, helpful 404 page converts some of those visitors into engaged users rather than bounces.

Find Every Broken Link on Your Site

Free, no signup. The Link Checker crawls your entire site and surfaces every internal link returning a 4xx status — showing the source page, destination URL, and status code so you know exactly which broken links to fix first.

Try the Link Checker Free →
SP

Sunny Pal Singh

Fellow · Technical Director — AI Infrastructure, Cloud Orchestration & Network Automation

Sunny is a Fellow and Technical Director specialising in AI infrastructure, cloud orchestration, and network automation. With hands-on depth across AWS, Azure, GCP, Red Hat OpenStack, and OpenShift, he leads high-performing teams of architects and engineers building transformative solutions at scale. He built ByteWaveNetwork to bring the same engineering rigour to everyday web tooling.

· ByteWaveNetwork

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.

Choose design