404 Errors and SEO: When They Hurt and How to Fix Them

404 errors and SEO get tangled up in a lot of myths. A 404 tells search engines a URL doesn't exist. Google drops that URL from its index, but 404s don't penalize the rest of your site. They only cost you something when a page that had traffic, backlinks or internal links breaks, or when a missing page wrongly returns 200 and becomes a "soft 404".

So the job isn't to get your 404 count down to zero. The job is to find the few 404s that matter and handle each one correctly.

What does a 404 error mean for Google?

A 404 (Not Found) is an HTTP status code. The server is saying "there is nothing at this address." Google takes that literally. In its words, Google "doesn't index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index".

Two more details from the same page matter for SEO:

• Google crawls a 404 URL less and less often over time, but it doesn't forget the URL right away.
• 4xx codes (except 429, "Too Many Requests") have no effect on crawl rate. A pile of 404s won't slow down how fast Googlebot crawls the rest of your site.

A 410 (Gone) works almost the same way. Google's crawl budget guide says to "return a 404 or 410 status code for permanently removed pages" and calls a 404 "a strong signal not to crawl that URL again." In practice, 404 vs 410 makes very little difference. Use whichever your platform makes easier.

Do 404 errors hurt SEO?

Not by themselves. Search Console's own help page says "404 responses are not necessarily a problem, if the page has been removed without any replacement". There's no sitewide ranking penalty for having 404s. Every site has them: deleted products, old campaign pages, URLs people mistyped, links from scraper sites to pages that never existed.

The SEO impact is page-level, and it depends on what the broken URL had:

1. Rankings and traffic. If an indexed page that ranked starts returning 404, it falls out of the index. All the clicks it earned go with it. This is the most common real cost.
2. Backlinks. External links pointing to a 404 point at nothing. When a page moves, a 301 redirect is how you keep those links working. Google's site move guide says redirects let it "transfer all signals to the new URLs, including recrawling and reassigning links on other sites that point to your old URLs".
3. Internal links. Links from your own menus, articles and product pages to a 404 send visitors and crawlers into a dead end, and they waste the link equity you meant to pass. See our internal linking guide for how link structure guides crawling.
4. User experience and conversions. A visitor who clicks "Buy" or "Pricing" and gets an error page usually leaves. That's lost revenue whatever Google thinks.

A 404 on a URL nobody links to, nobody visits and Google never indexed costs you nothing. A 404 on last year's best-selling product page with 40 referring domains is a real loss.

What is a soft 404, and why is it worse?

A soft 404 is a page that looks like an error to users or Google but returns a 200 (OK) status code. Examples: an empty category page, a "product not found" template served with 200, or a missing URL quietly redirected to the homepage. Google has to guess, and Search Console flags it as a soft 404.

Google describes a soft 404 as a page that tells the user the page doesn't exist "and also a 200 (success) status code." Soft 404s are worse than real 404s for two reasons. First, you've lost control: Google decides on its own whether the page counts as an error, and it can get thin but valid pages wrong too. Second, crawl efficiency suffers. Google's crawl budget guide warns that "soft 404 pages will continue to be crawled, and waste your budget". A real 404 lets Googlebot back off, but a soft 404 keeps getting crawled. The fix is simple: return a real 404 or 410 for pages that don't exist, and add real content to pages that do exist but look empty.

Why does redirecting every 404 to the homepage cause soft 404s?

Many plugins and agencies "fix" 404s by sending every missing URL to the homepage with a redirect. Google advises against it: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error". A redirect only helps when the target really replaces the old page.

Soft 404s on JavaScript sites

Single-page apps often can't send a 404 status from the server for a route that doesn't exist, so every missing route returns 200. Google's JavaScript SEO basics gives two fixes: use a JavaScript redirect to a URL where the server responds with 404 (for example /not-found), or add <meta name="robots" content="noindex"> to error views with JavaScript.

Which 404 errors should you fix first?

Fix the 404s on URLs that still have value first: pages with backlinks, past traffic or internal links pointing to them. Leave 404s on junk URLs alone. A 404 is the correct answer for a page that never existed or was removed on purpose with no replacement.

Use this table to decide what to do with each broken URL:

To rank a list of broken URLs, score each one on three signals: referring domains, organic clicks in the last 12–16 months, and number of internal links pointing to it. A URL with any of the three goes on the fix list. A URL with none of them can stay a 404. Our guide on how to prioritize SEO fixes shows how to weigh this against the rest of your backlog.

How do you find 404 errors that matter?

Combine three data sources, because each one sees something the others miss.

1. Google Search Console. Go to Indexing → Pages and open the reasons "Not found (404)" and "Soft 404". The 404 list includes URLs Google found anywhere, including old links from other sites, so expect noise. Search Console help says Google "discovered this URL without any explicit request or sitemap" for many of them. For the meaning of every other reason in that report, see Google Search Console errors explained.

2. A site crawler. Crawl your site and filter for internal links whose target returns 4xx. These are the broken links you control directly, and they're always worth fixing at the source.

3. Your sitemap and analytics. Any 404 URL that appears in your XML sitemap is a contradiction you're sending Google, so remove it. XML sitemap errors covers this. In analytics, filter page views by your 404 page title to see which broken URLs real visitors actually land on, and where they came from.

To check a single URL's status code yourself, ask for the headers only:

curl -I https://example.com/old-page
# HTTP/2 404  → real 404
# HTTP/2 200  → check the content: a "not found" message here is a soft 404
# HTTP/2 301  → follow the Location header and check the final URL

A free SEORecheck audit crawls your pages in a real browser and lists broken internal links, 4xx and soft-404 pages, and redirects that land on errors, with the exact URLs affected.

How do you fix 404 errors without creating new problems?

Work through the list in this order:

1. Restore pages deleted by mistake. Check with whoever manages content before redirecting anything.
2. Redirect moved or replaced pages with a 301, one to one, to the most relevant equivalent. Point straight at the final URL to avoid redirect chains. Google advises keeping redirects "for as long as possible, generally at least 1 year".
3. Fix internal links at the source. Update navigation, body links and canonical tags so they point to live 200 URLs, not to redirects.
4. Convert soft 404s to real 404s in your CMS or server config, and make sure your custom error template returns status 404.
5. Remove dead URLs from sitemaps.
6. Validate in Search Console with the URL Inspection tool and "Validate fix" on the affected reason.

Build a helpful custom 404 page

Your 404 page should return a 404 status and help visitors carry on: a short message, site search, links to main categories or popular pages, and a contact option. It should not auto-redirect, and it should not be a generic white server error.

Common mistakes

• Redirecting all 404s to the homepage (soft 404s, confused users).
• Using a 302 for permanent moves.
• Blocking 404 URLs in robots.txt. Google then can't see the 404 and may keep the URL indexed longer.
• Panicking over a jump in 404s after removing old pages on purpose. If the pages had no value, that's expected.
• Letting a redesign or CMS change break hundreds of URLs at once. Add status-code checks to your SEO regression testing before every release.

How long does it take Google to process fixes?

There's no fixed timeline. Google recrawls URLs on its own schedule, and 404 URLs get crawled less often over time, so a redirect added to an old 404 may take weeks to be picked up. Restored or redirected high-value pages are usually recrawled sooner, especially if they're in your sitemap and linked internally. Use URL Inspection to request indexing for the most important ones, then compare clicks for those URLs in the Performance report a few weeks later.

To check that the fixes held, crawl again after 30–60 days and compare the broken-URL lists. The SEORecheck sample comparison report shows this kind of fixed / unresolved / new breakdown.

Key takeaways

• 404s don't penalize your whole site. Google simply drops those URLs from the index, and 4xx codes (except 429) don't change crawl rate.
• The SEO cost is page-level: lost rankings, wasted backlinks and broken internal links on URLs that had value.
• Soft 404s (error content with a 200 status) waste crawl budget. Return a real 404 or 410 instead.
• Use a 301 only when a relevant replacement exists. Never send all 404s to the homepage.
• Prioritize by backlinks, past traffic and internal links, and leave worthless URLs as 404s.
• Fix internal links at the source, clean your sitemap, and recheck after 30–60 days.