Do 404 Errors Hurt SEO? What Google Just Explained

You open Search Console, click into the Page indexing report, and there it is: a few hundred URLs sitting under "Not found (404)." Your stomach drops. Did something break? Is Google about to bury the whole site?

Probably not. On October 28, 2026, Google Search Central published Should we be scared of a 404 status code?, the latest episode of its sitcom-style series The Non-Canonical Cabinet. Google Search Developer Advocates Gary Illyes and Cherry Prommawin use it to take on the fear around 404 errors: whether they hurt healthy pages, whether you should redirect every dead URL to your homepage, and whether they eat your crawl budget.

Below, we break down what the episode covers and line each point up with Google's own documentation. By the end, you'll know which 404 errors to fix, which to redirect, and which to leave alone.

Do 404 errors hurt SEO? The short answer

No. A 404 error doesn't hurt your site's rankings or the indexing of your other pages. Google's Search Console Help page on 404 errors says plainly that 404s don't harm a site's indexing or ranking, and that many of them aren't worth fixing at all.

Here's what actually happens when Googlebot requests a URL that returns a 404:

• The URL isn't indexed. If it was indexed before, Google removes it from the index.
• Google crawls it less over time. Crawl frequency for that URL gradually decreases.
• Nothing happens to your other pages. A 404 only affects the URL that returns it.

That's the core message of the episode. 404 errors are a natural part of the web. Pages get deleted, products get discontinued, and people mistype URLs. A server that says "this doesn't exist" is simply doing its job.

What Google's video on 404 errors covers

The episode leans into comedy (a missing chicken haunts the set), but each segment answers a question site owners genuinely ask. Here's how it's structured, based on Google's official chapter markers:

For context, The Non-Canonical Cabinet launched in October 2026 to answer oddly specific technical SEO questions from the community. Earlier episodes covered what you can put in a URL and what belongs in a robots.txt file. Google has said the next episode will tackle redirects: 301, 302, 307 and 308.

Technical impact vs. business impact: when a 404 actually matters

The episode separates two questions most panicked site owners blur together. The technical question is whether a 404 hurts indexing. The business question is whether it costs you visitors or revenue. The first answer is almost always no. The second depends entirely on which URL broke.

Compare these three 404s:

1. A URL that never existed, like /prodcts/ typed by a visitor in a hurry. Nobody loses anything. Leave it.
2. An old promo page you deleted on purpose, with no traffic and no replacement. Returning a 404 is exactly right.
3. Your best-selling product page that vanished after a CMS migration, still linked from blog posts and old email campaigns. This one is costing you sales every day.

Search Console lists all three the same way. You shouldn't treat them the same. Before touching any 404, ask two things: did real people or real links rely on this URL, and does a genuine replacement exist?

This is why site migrations cause so much 404 damage. When URLs change during a website redesign and nobody maps redirects, pages that earned traffic for years suddenly lead nowhere. If you're weighing a platform change, read our comparison of WordPress vs. headless CMS for SEO before you start.

Should you redirect all 404 errors to your homepage?

No. Blanket homepage redirects are one of the most common "fixes" in SEO, and Google has been clear that they backfire.

Google's Search Console documentation tells site owners not to redirect 404s to the homepage, create fake content for them, or block them in robots.txt. All three make it harder for Google to understand your site's structure. Google calls the result soft 404s.

What is a soft 404?

A soft 404 is a URL that tells visitors the page doesn't exist but returns a 200 (success) status code, or that redirects them to an unrelated page instead of returning a 404. It confuses both audiences:

• Visitors who clicked a link to a specific article land on your homepage instead. They didn't ask for your homepage, so many simply leave.
• Google gets a mixed message. Instead of a clear "this page is gone," it sees a redirect that doesn't match what the old URL was about.

There's a crawl cost too. Google's crawl budget guide says soft 404 pages continue to be crawled and waste your budget. A clean 404, by contrast, is a strong signal not to crawl that URL again.

So redirect when a real equivalent exists. Otherwise, let the URL return a 404.

A 3-step framework for handling dead URLs

The episode frames dead URLs as a three-part decision: let them go with a 404 or 410, redirect them when it makes sense, and look at what else you can do. Here's how that maps onto Google's documented guidance.

Step 1: Decide whether the 404 is worth your time. Google's own advice is that many, perhaps most, 404 errors aren't worth fixing. Prioritize URLs you submitted in a sitemap, URLs that earned traffic or backlinks, and common misspellings of real pages.

Step 2: Redirect only to a true replacement. If the content moved or has a close equivalent, use a 301 redirect to that specific page. Frequent typos, such as /cancelling vs. /canceling, can be mapped to the correct page too.

Step 3: Let the rest go. If content is permanently deleted with no replacement, return a 404 or 410. Google currently treats the two the same. Search Console should stop reporting a deleted page's 404 after about a month.

Quick reference: which status code to use

What else can you do?

Fix the source. If a 404 comes from your own internal link or XML sitemap, update the link or remove the URL from the sitemap. A redirect patches the symptom; fixing the link removes the problem.

Online stores need this logic built into everyday operations, because products go out of stock and get discontinued constantly. Handling those URLs one at a time doesn't scale, which is why it belongs in your ecommerce SEO process.

Do 404 errors waste crawl budget?

No. This is the myth the episode sets out to bust, and Google's documentation backs it up.

Google's guide to how HTTP status codes affect its crawlers states that 4xx status codes, except 429, have no effect on crawl rate. Its crawl budget guide goes further and recommends returning a 404 or 410 for permanently removed pages, because a 404 is a strong signal not to crawl that URL again.

Two caveats are worth knowing:

• Google doesn't forget URLs. It may still check a 404 URL occasionally, sometimes for a long time. That's normal and nothing you need to solve.
• Crawl budget is mostly a big-site concern. Google's guide targets sites with roughly a million or more pages, or 10,000+ pages that change daily. If your new pages get crawled the day you publish them, crawl budget isn't your bottleneck.

What does waste crawl budget? Soft 404s, long redirect chains, and large volumes of duplicate URLs. Those deserve your attention long before a pile of honest 404s does. On a large site, a technical SEO audit with server log analysis shows exactly where Googlebot is spending its time.

The real monsters: 5xx server errors and 429s

If 404s are harmless ghosts, server errors are the actual monsters. The episode points to 500 errors and 429 rate limits as the status codes that deserve real concern, and Google's documentation explains why.

When your server returns a 5xx error or a 429 (Too Many Requests), Google's crawlers read it as a sign the server is struggling, so they slow down. For 500 errors, Google lowers the crawl rate in proportion to how many URLs are failing. URLs that keep returning server errors are eventually dropped from the index. Once the server recovers, Google gradually increases crawling again.

Here's the difference side by side:

Network problems are just as serious. Google treats timeouts, connection resets and DNS errors much like 5xx errors, and indexed URLs it can't reach are removed within days.

So if you only have time to watch one thing, watch your server health in Search Console's Crawl Stats report, not the 404 list. A spike in server errors is an emergency. A spike in 404s usually isn't.

How to audit 404 errors in Search Console

Here's a practical routine for turning a scary 404 list into a short list of real fixes:

1. Open the Page indexing report and select "Not found (404)." Export the list.
2. Sort by importance, not volume. Flag URLs that appear in your XML sitemap, had organic traffic in analytics, or have backlinks pointing to them. Everything else is low priority.
3. Find where Google discovered each important URL. Use the URL Inspection tool and check the discovery information. If the URL came from your sitemap, update the sitemap.
4. Fix your own broken links first. Internal links pointing to dead URLs are entirely in your control and frustrate visitors on every click.
5. Redirect only what has a real replacement. Use a 301 to the closest equivalent page. Let everything else return a 404 or 410.
6. Confirm your 404 page returns a real 404 status. Check it with the URL Inspection tool or any HTTP header checker. A custom "page not found" design that returns 200 is a soft 404.
7. Make the 404 page useful. Add a search box and links to your main categories or most popular content, so visitors who hit a dead end can keep going.
8. Leave the rest alone. Google says 404s for deleted pages and URLs that never existed should drop out of the report after about a month.

For 404 checks inside a broader review, our franchise website audit checklist shows how 4xx errors, redirect chains and migration leftovers fit into a full site audit.

Frequently asked questions about 404 errors

Do 404 errors hurt SEO?

No. Google states that 404 errors don't harm a site's indexing or ranking. The URL returning the 404 drops out of the index, but your other pages aren't affected.

Is a 410 better than a 404 for SEO?

Not for Google right now. Google currently treats 410 (Gone) the same as 404 (Not Found). Use 410 if it fits your process for deliberate removals, but either one works.

Should I redirect 404 pages to my homepage?

No. Google advises against it, because homepage redirects for missing pages act as soft 404s. Redirect only to a specific, relevant replacement page.

What is a soft 404?

A soft 404 is a page that tells visitors the content doesn't exist but returns a 200 success code, or redirects to an unrelated page. Google flags these in Search Console, and they keep getting crawled.

Do 404 errors waste crawl budget?

No. According to Google, 4xx status codes other than 429 have no effect on crawl rate. Soft 404s and server errors are the real crawl problems.

How long does it take for a 404 to disappear from Search Console?

Google says 404s for deleted pages and never-existing URLs should drop out of the report after about a month. Google may still recheck the URL now and then, which is normal.

Should I block 404 URLs in robots.txt?

No. Google advises against it. Blocked URLs stay in the crawl queue longer, and Google can't see the 404 status if it isn't allowed to fetch the page.

Can too many 404 errors hurt my site?

Not on their own. The number of 404s isn't a ranking problem. What matters is why they exist: broken internal links frustrate visitors, and missing pages that should exist cost you traffic and sales.

Final thoughts: stop fearing the 404

The takeaway from Google's episode is refreshingly simple. A 404 is the web being honest. Let dead pages go, redirect only when a genuine replacement exists, never dump everything on your homepage, and save your worry for server errors.

The hard part is telling the harmless 404s from the expensive ones, especially on large or recently migrated sites. That's where a structured process pays off. It's also why status codes deserve a place in your overall SEO strategy, not just in a one-off cleanup.

KodRank's technical SEO services cover crawl and log-file analysis, redirect mapping and indexation cleanup. If you're about to relaunch, our website redesign services build redirect mapping in from day one. Not sure where your site stands? Request a free audit, and we'll show you which errors actually matter.

— Written by

Hidayatul Haq

Founder, KodRank · SEO Strategist

Hidayat is the founder and CEO of KodRank and a top-rated SEO strategist who has delivered 150+ projects across the globe— spanning technical audits, crawl-budget recovery, on-page optimization, and full-scale organic growth programs for founders, agencies, and in-house teams.