Do 404 Errors Hurt SEO? When to Fix, Redirect, or Just Ignore Them

Do 404 errors hurt your SEO? For the pages that still work, no. This is one of the most persistently misunderstood topics in technical SEO, so let's be precise about Google's actual position: 404 errors are a normal, expected part of the web, and a page returning 404 does not drag down the rankings of your other pages. Google's Search Central documentation and its search team have said this many times. Pages disappear, URLs change, people mistype links. Google expects a chunk of any site to 404 and does not penalise the site for it.

So the scary framing ("404s are killing your SEO, redirect them all now") is wrong, and acting on it causes real damage, as we'll see. But there's a more useful question hiding underneath: a 404 can still cost you something, not in rankings but in lost visitors and lost link value, and for those specific 404s you should do something. The skill isn't fixing every 404. It's knowing which handful actually matter and what the right response is for each.

Here's the decision tree we use.

First, the myth: do 404s lower my rankings?

No, and it's worth understanding why so you stop worrying about the count. Google indexes and ranks pages individually. A 404 at /old-page tells Google that URL is gone; Google eventually drops it from the index. That's the entire effect. It doesn't subtract from your domain, it doesn't lower /current-page, it doesn't count against you. A site with 2,000 URLs in Search Console's "Not found (404)" list and healthy content ranks exactly as well as it would with zero 404s.

What Google does dislike is lying about 404s, which is where the damage comes from, and it's almost always self-inflicted by over-eager "fixing".

The decision tree

For any 404, ask these in order.

Did the page have traffic, rankings, or backlinks? If yes, and there's a genuinely equivalent page, 301 redirect the old URL to that equivalent. This is the case that matters most. A retired product that has a natural replacement, an old blog post you rewrote at a new URL, a page other sites still link to: a 301 to the closest real equivalent preserves the link value and sends visitors somewhere useful instead of a dead end. Use a 301 (permanent), not a 302; the distinction matters and we cover it in 301 vs 302 redirects.

Is there no genuine equivalent? Then let it 404 (or 410, more on that below). This is the counterintuitive part. If a page is gone and nothing really replaces it, the honest answer is a 404. Do not redirect it to your homepage or a vaguely-related category just to avoid the error.

Is it a typo or a slightly-wrong inbound link? Redirect it. If another site linked to /produtcs (typo) or /blog/my-post/ when your URL is /blog/my-post, a 301 to the correct URL recovers a visitor and a link you'd otherwise lose to someone else's mistake. These are free wins.

Is the content permanently, deliberately gone? Consider a 410. See the section below.

Why "redirect everything to the homepage" backfires

This deserves its own warning because it's the single most common bad fix. When a page 404s and you don't have a real replacement, the tempting move is to 301 it to your homepage so the error "goes away". Google specifically treats this as a soft 404.

A soft 404 is when a URL returns a "success" or redirect response but the destination isn't a real equivalent of what was requested. Google detects mass redirects-to-homepage and, rather than crediting them, treats those URLs as soft 404s anyway, which is functionally the same as letting them 404, except now you've also created a confusing experience: a user clicking a link to a specific product lands on your homepage with no idea why, and bounces. You've spent effort to produce a worse outcome than doing nothing. Search Console flags these under "Soft 404" in the Pages report, and the fix Google wants is to either return a real 404/410 or redirect to a genuinely relevant page, not the homepage.

So the rule: redirect only to a real equivalent. No equivalent means let it 404.

The 410 nuance

There's a subtler status code worth knowing. 404 means "not found" (the page isn't here, maybe temporarily, maybe it'll come back). 410 means "gone" (this page is deliberately and permanently removed, don't expect it back).

In practice Google treats them almost identically and will drop both from the index. The small difference: Google tends to act on a 410 slightly faster, because 410 is an explicit "this is permanent" signal rather than the ambiguous "not found". If you've deliberately killed content and never want it back (a discontinued line, a spammy page you're purging, an expired campaign), returning 410 is a cleaner signal than 404. For most cases 404 is completely fine and you don't need to reach for 410; it's a nicety for content you're certain is permanently gone.

Finding your 404s

You can't triage what you can't see. Two sources.

Search Console. Go to Indexing > Pages and look at the "Not found (404)" and "Soft 404" rows. This is Google's view: the URLs it tried to crawl and got a 404 for, often because something (an old sitemap entry, an internal link, an external link) pointed there. Click in to see the list and, usefully, the "Referring page" so you know where the bad link lives.

Server logs and analytics. Your server access logs record every 404 with the requesting URL and often the referrer, which catches 404s from sources Google hasn't crawled yet, including broken internal links. If a real page on your site links to a URL that 404s, fix the link itself rather than redirecting; the redirect is for links you don't control.

Once you have the list, run the important URLs (the ones with traffic or links) through our redirect checker to confirm your fix works: a 404 you meant to redirect should now return a single 301 to the right place, and a 404 you meant to keep should still cleanly return 404. If your redirects turned into chains or loops while you were cleaning up, how to fix redirect chains and loops covers untangling them.

The short version: don't fear the 404 count, and don't bulk-redirect. Fix the few that had value, redirect the typo'd inbound links, use 410 for the deliberately-dead, and let the genuinely-gone pages 404 in peace.

Frequently Asked Questions

Do 404 errors hurt my site's SEO?

Not for your other pages. Google treats 404s as a normal part of the web and does not lower the rankings of your working pages because some URLs 404. The only "cost" of a 404 is on that specific dead URL: any traffic or backlinks it had are wasted unless you redirect it to a real equivalent. A high 404 count on its own is not a problem.

Should I redirect all my 404 pages to the homepage?

No. Redirecting unrelated 404s to your homepage creates soft 404s, which Google detects and treats as 404s anyway, while also dropping visitors somewhere confusing. Only 301 redirect a 404 when there's a genuinely equivalent page to send it to. If there's no real equivalent, let the URL return a clean 404.

What's the difference between a 404 and a 410?

404 means "not found" (possibly temporary), 410 means "gone" (deliberately and permanently removed). Google treats both similarly and removes them from the index, but acts on a 410 slightly faster because it's an explicit permanence signal. Use 410 for content you've intentionally deleted forever; 404 is fine for everything else.

How do I find the 404 errors on my site?

Use two sources. In Google Search Console, check Indexing > Pages for the "Not found (404)" and "Soft 404" rows, which show URLs Google tried to crawl and includes the referring page. And review your server access logs or analytics, which catch 404s from broken internal links and sources Google hasn't crawled yet. Together they give you the full list to triage.

A 404 page has good backlinks. What should I do?

Redirect it. Use a 301 (permanent) redirect to the most relevant equivalent page you have, so the link value and any visitors are passed to a live URL instead of hitting a dead end. Only redirect to a genuinely related page; if nothing on your site fits, it may be better to recreate suitable content at that URL than to redirect it somewhere irrelevant.