Menu

Findmetry guide / Indexing

Soft 404 in Google Search Console: What It Means and How to Measure the Risk

In simple terms

A soft 404 means a URL told Google it loaded successfully, but the page Google saw looked missing, empty or broken. If it is an old page you meant to remove, correct the response. If it is a page customers need, find out why Google could not see its useful content. The label alone cannot tell you what it cost.

Verified HTTP response01 / 404
HTTP/2 404
content-type: text/plain

404 Not Found
Actual response from http-stat.us/404, checked 26 September 2026. The status code is the key distinction: a soft 404 can display a similar message while returning HTTP 200.

Published · Updated

Should I worry?

Usually fine

The URL represents content intentionally retired with no replacement. Its exclusion is expected; make sure the server returns a real 404 or 410.

Investigate

The page is meant to exist, but you have not compared Google's crawled render with the live response or established when the label appeared.

Likely problem

Current product, service or category pages have missing main content, error text with HTTP 200, or a shared rendering failure. Fix the observed defect.

What the status proves, and what it does not

Google classified this URL as a soft 404. Its documentation describes a page that returns HTTP 200 while indicating that it does not exist; sometimes its main content is absent or empty. Google excludes such pages from Search. The report does not identify the cause or quantify lost sales. Google's crawling-error guidance

A browser opening the page now does not establish what Google received at its last crawl. Use URL Inspection to compare the stored view with a live test and note their dates. A live test does not guarantee indexing. Google's URL Inspection help

Findmetry diagnostic framework

Follow the page's intended state

  1. Should this exact page still exist?

    If no and there is no relevant replacement, return HTTP 404 or 410. Keep a useful custom error page for visitors while preserving the error status.

  2. Did it move?

    If a clear equivalent exists, redirect the old URL to that page. Check the final destination. An unrelated homepage is not a substitute for the missing page.

  3. Should it be a live, useful page?

    Record its final HTTP status, visible main content and error text. Compare source HTML, rendered HTML and Google URL Inspection. If a 200 response contains a missing-page message, fix the mismatch.

  4. Is the failure shared?

    Group affected URLs by template, content source and deployment date. Test representative pages and the requests that load their main content, including intermittent failures.

  5. What changed commercially?

    Only after confirming the affected page group, compare its organic search visits and business outcomes with a suitable baseline. Do not treat a count of excluded URLs as a count of lost customers.

Three cases, three different decisions

Illustrative / expected exclusion

Retired product without a replacement

An old product URL should not be indexed. If it says “no longer available” but returns 200, serve a real 404 or 410. This corrects the signal; it does not recreate demand for that product.

Illustrative / technical defect

Current product with an empty content panel

A product URL returns 200, but a failed database or content request leaves the main product details blank when Google renders the page. Restore the content and retest. Google's documentation names missing resources and database failures as possible causes. This is a diagnostic example, not a verified Findmetry customer finding. Google's examples

Illustrative / unresolved

Browser looks fine; Search Console says soft 404

The current page appears complete, but Google last crawled it before a repair. Compare crawl date and stored render, then monitor the next crawl. A transient error or different rendering remains possible until evidence distinguishes them.

How much money can a soft 404 cost?

There is no defensible universal dollar figure per soft 404. A 2004 study found soft 404 substitutions among the dead links in its sample, but measured web decay, not business loss. Read the original study.

A published 2026 migration case reported an approximately 90% decline in organic traffic alongside soft 404s and other indexing and migration issues. The case does not isolate the effect of soft 404s or provide verified revenue lost to that one problem. Its percentage is not a forecast for another website.

Make a site-specific estimate instead

  1. Identify pages that should exist and were actually affected; keep retired URLs out of the estimate.
  2. Use Search Console to record those pages' search clicks before and after the issue, with dates. Compare a matched period and similar unaffected pages where possible.
  3. Use your analytics or order system to examine conversions and recorded value from the affected landing pages, noting attribution and tracking gaps.
  4. Present a range under explicit assumptions about how much of the observed difference is related to the fault. Call it a scenario, not observed lost revenue or a guaranteed recovery.

Without a relevant baseline and conversion data, a monetary forecast would be invented.

What changes for AI search?

Google says a page must be indexed and eligible for a Search snippet to appear as a supporting link in AI Overviews or AI Mode. An excluded page does not meet that eligibility condition while excluded. This does not establish how many AI citations or visits it would have received. Google's AI features guidance

Bing Webmaster Tools' AI Performance preview reports citations on supported Bing and Copilot experiences; its aggregated figures do not measure the revenue value of an individual missing page. A Google soft 404 report is not proof of the same outcome in Bing, ChatGPT Search or other systems. Inspect those surfaces separately. Microsoft's reporting explanation

Technical deep dive

A soft 404 is Google's classification, not an HTTP status. Inspect the response after redirects, the body delivered with it, and the rendered main content. A client-side route can display a “not found” view while the server continues to return 200. Google documents ways to return meaningful status codes or prevent error views being indexed in single-page applications. Google's JavaScript SEO guidance

Test representative URLs from each template. Compare the last indexed crawl with the live test; check content API failures, blocked or missing resources, server-side includes and intermittent empty responses. Fix the cause before requesting a recrawl. Google notes that correcting the response depends on whether content is gone, moved or still exists. Google's repair paths

What not to do

  • Do not redirect every missing page to the homepage.
  • Do not add filler text merely to make an empty page look longer.
  • Do not quote another site's traffic loss as your own expected revenue loss.
  • Do not assume that a successful live browser visit disproves Google's earlier observation.
  • Do not repeatedly request indexing without fixing a confirmed problem.

Technical checklist

  1. Export soft 404 URLs and identify which should still exist.
  2. Check response status, redirects and main content for representative URLs.
  3. Compare Search Console's crawled view with a live test and record dates.
  4. Test shared templates, content requests and error routes.
  5. Return 404/410 for gone pages, redirect moved pages to relevant replacements, and restore existing pages.
  6. Retest the response and monitor indexing plus affected page performance over subsequent crawls.

Sources and update date

Published and checked 26 September 2026. Primary technical references: Google on soft 404s, Google on JavaScript and HTTP status, Google on AI features, and Microsoft on AI citation reporting. Contextual historical references: the 2004 web-decay study and a 2026 reported migration case. Neither establishes a general financial loss per soft 404.

Need to know which case applies?

Findmetry can examine your public pages and show the observed problem, scope and next action.

Request a diagnostic →