← Back to blog
Technical SEO

Soft 404 Errors: What They Are, Soft 404 vs 404, and How to Fix Them

The page says "not found" — or nothing at all — while the server says "all good". Google believes the page, not the status code. Here's how to tell which of three cases you have and fix each one.

By Rajhussain Kanani7 min read

The short answer

A soft 404 is a page that tells visitors “not found” — or shows nothing useful at all — while the server returns 200 OK, the code for “this page is fine”. Google’s crawling guide defines it as a URL that returns a page saying the page doesn’t exist along with a 200 status, and adds that an empty page or a page with no main content can count too. Google keeps these pages out of Search and lists them as Soft 404 in the Page indexing report. The fix depends on the page: if it’s really gone, return a real 404 or 410; if it moved, redirect it; if it should exist, make sure Google can see its content.

Soft 404 vs. 404: what’s the difference?

404 (“hard” 404)Soft 404
Status code the server sends404 (or 410)200
What the visitor seesA “not found” pageA “not found”, empty or broken-looking page
How Google knowsFrom the status codeBy judging the content
Is it a problem?No, if the page is gone on purposeYes — the status code says the opposite of the page

A 404 is honest: the page doesn’t exist and the server says so. Google’s documentation describes 4xx responses as telling its systems the content doesn’t exist, and says all 4xx codes except 429 are treated the same — so 404 and 410 both remove a URL from the index, and neither affects crawl rate. A soft 404 is a page whose status code and content disagree, which is what Google calls a bad experience.

What causes soft 404s

  • Error pages served with 200. A CMS or framework renders a friendly “Sorry, we couldn’t find that” template but never sets the status code. Single-page apps are the classic case: the server answers 200 for every route and the “not found” view is drawn in the browser.
  • Empty pages. Google names an empty internal search results page as an example. Empty category pages, a product listing with no products, or a tag archive with no posts look the same.
  • Pages that didn’t render for Googlebot. If critical JavaScript, CSS or API calls are blocked, slow or failing, Google can see an empty shell or an error message that visitors never see.
  • Redirecting removed pages to an unrelated page. Google’s site-move guide warns against sending many old URLs to one irrelevant destination such as the homepage — it can confuse users and might be treated as a soft 404.
  • Very thin pages. A page with a heading and almost nothing else can be judged as having no main content.

How to fix it: three cases

1

The page is gone for good

Return 404 or 410. A custom, helpful not-found page is fine — it just has to be sent with the 404 status. Fix: Don’t redirect it to the homepage “to keep the link equity”; that’s the soft 404 pattern.

2

The page moved or has a clear replacement

Return a 301 to the new URL — the page that actually replaces it, not the nearest category or the homepage. Google’s guide says a redirect is right when content has moved or has a clear replacement on your site.

3

The page should exist and be indexed

Run URL Inspection → Test live URL → View tested page and check the screenshot, the rendered HTML and the status code. Google’s list of reasons a real page gets flagged: it didn’t load properly for Googlebot, it was missing critical resources, or it showed a prominent error message while rendering. Fix: Unblock the resources, fix the failing API call or the error state, and make sure the main content is in the page — then validate the fix.

Empty search, category and listing pages

These are soft 404s by design: there’s nothing on them. Either return a 404 when a filter or search has no results, or add noindex to empty result pages so they stay out of the index. If they shouldn’t be crawled at all, stop linking to them. A category that’s only temporarily empty is better shown with related products or articles than as a blank page.

Single-page apps (React, Vue, Next.js client routes)

Google’s JavaScript SEO guide gives two techniques for client-rendered error views, and you can use one or both: redirect with JavaScript to a URL the server answers with a 404, or add a <meta name="robots" content="noindex"> tag to the error view. Server rendering avoids the problem entirely, because the server can send the right status code with the page.

// Single-page app: the server answers 200 for every route, so tell Google
// about missing content one of these two ways (from Google's JavaScript SEO guide).

// 1. Redirect to a URL your server answers with a real 404
if (!product) {
  window.location.href = "/not-found";
}

// 2. Or add a noindex robots meta tag to the error view
if (!product) {
  const meta = document.createElement("meta");
  meta.name = "robots";
  meta.content = "noindex";
  document.head.appendChild(meta);
}

The Custom 404 Page Checker requests a random URL that can’t exist on your site and tells you whether the server answers with a real 404 or quietly returns 200 — the soft 404 setup. No signup.

Test your site’s 404 handling

Checks from a terminal

# A URL that can't exist on your site should return 404 (or 410), not 200
curl -s -o /dev/null -w "%{http_code}\n" "https://example.com/this-page-does-not-exist-$RANDOM"

# The status of a URL Search Console flagged, following any redirects
curl -sIL "https://example.com/products/blue-widget" | grep -iE "^http|^location"

# How much text the server sends for it (a near-empty page is a soft 404 suspect)
curl -sL "https://example.com/products/blue-widget" | sed 's/<[^>]*>//g' | wc -w

On this site, a made-up URL such as /blog/this-does-not-exist returns 404, and old tool URLs that have a real replacement — /tools/broken-links, for example — return a 308 to that replacement. That’s the split Google asks for: 404 for what’s gone, a permanent redirect for what moved. The custom 404 page guide covers what a good not-found page should contain.

After you fix it

Click Validate fix on the Soft 404 row once every affected URL is handled. Google says validation typically takes up to about two weeks. URLs you changed to a real 404 will move to the Not found (404) row — that’s the intended result, not a new problem. URLs you redirected will show up as Page with redirect, which is also expected.

If several reasons appear in your report at once, the overview of every “Why pages aren’t indexed” reason helps you decide what to fix first.

The free site scan finds your site’s pages, checks a sample for thin content, unreachable URLs, noindex tags and other problems, and estimates how many pages across the site share each one.

Scan your whole site, free

Sources

Frequently asked questions

What is a soft 404 error?

A page that tells visitors it doesn't exist, or shows no main content, while the server returns a 200 OK status. Google detects these from the page content, keeps them out of Search, and lists them as Soft 404 in Search Console's Page indexing report.

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

A 404 is the server correctly saying the page doesn't exist. A soft 404 returns 200, the code for a working page, while the content looks missing or empty. A real 404 for a deleted page is fine; a soft 404 is a mismatch between the status code and the page.

Do soft 404 errors hurt SEO?

The affected URLs are excluded from Search, so if a page you want ranked is flagged, it can't rank until you fix it. For pages that are genuinely gone, the fix is simply to return a real 404 or 410.

Should I redirect soft 404 pages to the homepage?

No. Google's site-move guidance warns that redirecting many old URLs to one irrelevant page such as the homepage can confuse users and might be treated as a soft 404. Redirect to a real replacement, or return 404 or 410.

Is a 410 better than a 404?

Google's documentation treats all 4xx codes except 429 the same way: the URL is removed from the index if it was indexed. Use 410 if you want to signal the removal is permanent, but either works for Google Search.

Check your own site with the Custom 404 Page Checker.

Open Custom 404 Page Checker

Want every check at once?

The free Full Audit runs 33 checks on any URL, most of them in seconds. Add your email afterwards and we send a detailed one-page report; the full-site report covers up to 1,000 pages.

More from the blog

We use cookies to analyze site usage and improve your experience. You can decline non-essential cookies. Privacy Policy