GlossarySearch Console States

Soft 404

A soft 404 is a page that returns HTTP 200 but that Google judges to be an error or empty page. Google treats it as a real 404: the URL is excluded from the index and reported in Search Console.

Updated Sep 3, 2026

A soft 404 is a contradiction between the protocol layer and the content layer: the server answers 200 OK — "this page exists" in HTTP status code terms — while the content Google sees is an error message, an empty template, or nothing worth indexing. Google resolves the contradiction in favor of the content: the URL is classified as a soft 404, treated exactly like a real 404, and excluded from the index.

Search Console reports the state under Indexing → Pages → "Soft 404" in the "Why pages aren't indexed" table. The classification is Google's judgment call, not a server signal, which is why it catches setups that look healthy in every log: single-page applications that render an error screen while the server returns 200 for every route, category and site-search pages with zero results, and "product no longer available" templates served with a success status.

Soft 404s cost more than the affected URL. Because the URLs return 200, Googlebot keeps rescheduling them for recrawl, and Google's crawl-budget documentation lists soft error pages among the URL classes that waste crawl budget — fetches spent on pages that will never be indexed instead of pages that would be.

Quick facts

Reported in
Google Search Console → Indexing → Pages → "Soft 404"
HTTP status returned
200 OK — the mismatch with error-page content defines the state
Google's treatment
Same as a real 404: the URL is excluded from the index
Common causes
Empty listing pages, JS error screens served with 200, "not found" text, thin doorway pages
Fixes
Real 404/410, substantive content, or a 301 to a relevant replacement
Crawl impact
Wastes crawl budget — soft error pages stay in the recrawl rotation

Why does Google classify a page as a soft 404?

Google flags a soft 404 when the fetched, rendered page looks like an error or empty page despite its 200 status. The classifier reads the rendered content, so the trigger is what the page shows, not what the server intends.

The common triggers:

  • Empty listing pages — category, tag, or site-search pages with zero results
  • JavaScript error screens — an SPA route fails during rendering and shows "something went wrong" while the server returns 200
  • "Not found" text with a 200 status — custom error pages that never set a 404 code
  • Thin doorway pages — near-empty templates with no substantive content

Confirm what Google saw with the URL Inspection tool: its rendered HTML and screenshot show the page as Googlebot processed it.

How do you fix a soft 404?

Match the fix to what the URL deserves: an honest error code if the page is gone, real content if it should exist, or a redirect if a replacement exists. After deploying, use Validate Fix in the Search Console report to trigger rechecking.

  1. 1Page is gone — return a real 404 (not found) or 410 (gone). Error codes on dead URLs are correct behavior, not a problem to suppress, and they stop the recrawl cycle.
  2. 2Page should exist — add substantive content: populate the empty listing, fix the JavaScript error so the route renders, replace the placeholder text.
  3. 3Page has a replacement301 redirect to the closest relevant page. Redirecting every dead URL to the homepage does not work: Google treats redirects to an irrelevant page as soft 404s too.

Do soft 404s waste crawl budget?

Yes. A URL returning 200 stays in Googlebot's recrawl rotation, so every soft 404 keeps consuming fetches that produce nothing — Google's crawl-budget guidance names soft error pages as a crawl-budget drain. On a site with a few hundred URLs the waste is negligible; on a site with tens of thousands of empty category and search pages, it delays crawling of pages that would actually be indexed.

Returning a real 404 or 410 ends the cycle: Google drops confirmed-dead URLs out of frequent recrawling and spends the reclaimed fetches on live pages.

Once a soft 404 is fixed, the page still needs a recrawl — IndexBolt gets Google to refetch the corrected URL within hours instead of waiting weeks for a natural revisit.

Frequently Asked Questions

Is a soft 404 a penalty?+

No. It is a per-URL classification, not a site-wide action. The cost is that the affected URL cannot rank and its recrawls waste crawl budget; other pages are unaffected.

Why is my real content page flagged as a soft 404?+

Google's rendered view of the page looks empty or error-like — usually a JavaScript failure during rendering, or main content that never reaches the HTML Googlebot receives. Inspect the rendered HTML in the URL Inspection tool, restore the missing content, then validate the fix.

Should I redirect soft 404 pages to my homepage?+

No. Google treats redirects to an irrelevant page — including the homepage — as soft 404s, so the state persists. Redirect only when a closely relevant replacement exists; otherwise serve a real 404 or 410.

Ready to get your URLs indexed?

Start with 100 free credits. No credit card required.