A response that search engines interpret as a missing or empty page despite the server returning a different status, often 200 OK.
A soft 404 is a search engine’s assessment that a response behaves like a missing or empty page even though the server has not returned an appropriate not-found status. A common case is an error message delivered with 200 OK. The code says the request s\ucceeded, while the content tells a different story.
This can arise from a broken page template, missing content or a problem loading the material the page is supposed to show. The right repair depends on whether the page should exist. Restoring its genuine content is different from correctly retiring a URL. Adding a few generic sentences just to change an automated classification may leave the customer’s problem unresolved.
A soft 404 report is therefore a diagnostic clue, not simply another label for every short page. Inspect what the crawler received and compare it with the intended page. A compact but useful page and a blank shell are different cases, even if both contain relatively few words.
Takeaway: Check whether the page delivers the thing its URL and links promise. Fix missing content or return an appropriate missing-page response instead of disguising the error with a success code.
Example
A product template displays “product unavailable” for a deleted item but still returns 200. There is no description, no purchasing option and no useful remaining product information. The team must decide whether to restore the item, offer a genuinely relevant replacement, or return a proper missing-page response. Merely changing the message’s wording does not settle that decision.
What to check
Use URL Inspection and the site’s actual response to compare the indexed or tested content with what visitors should receive. If rendering fails, investigate the failed content or resources before assuming the product page itself should be removed.
For more detail, see Google HTTP status guidance.