Soft 404: when a successful response looks like a missing page
A soft 404 occurs when a URL may return a successful response but a search engine interprets its content as missing or erroneous. A typical example is a “page not found” screen served with HTTP 200. Soft 404 is a search-engine classification, not a separate HTTP status code.
Also known as: Soft 404 error
At a glance
- A soft 404 is a content-based classification, not an actual 404 response code.
- A functioning URL can still return empty or error-like content.
- The remedy is to serve the page’s real state correctly, not reach an arbitrary word count.
On this page

How it differs from a real 404
An actual HTTP 404 response tells the requester that the resource was not found. With a soft 404, the response and the apparent content can disagree: the server reports success while the page looks absent or broken. Google may interpret that as a missing page. HTTP status codes
This need not be intentional. A failed data request or a template problem can produce the same mismatch as a deliberately configured error screen.
Common situations to inspect
A discontinued product might show “not found” while returning 200. A JavaScript application might deliver its outer layout successfully but fail to load the information inside it.
For JavaScript SEO, examine the initial response, required resources and rendered content. Neither every missing page nor every JavaScript page is a soft 404. The actual result matters.
URL Inspection helps investigate what Google could access. Distinguish its stored information about the indexed version from a live test of the current page. Inspection documentation
It is not a word-count threshold
A short, complete answer can be useful. A long error page can still represent missing content. Adding three generic paragraphs about the company to an unavailable product does not restore that product’s information.
Check the expected answer, visible content and server response together. The Page indexing report identifies Google’s classification; it does not prescribe a universal minimum article length.
Example: three different product states
Imagine a ceramics shop with three mug URLs:
- One mug has been permanently removed and has no appropriate replacement.
- Another is temporarily unavailable for two weeks, but its description and restock information remain useful.
- A third has moved to a new URL that genuinely replaces the old product page.
These are different situations. The first may correctly return a missing-page status. The second can remain a useful product page. The third may need a permanent redirect. Serving the same empty 200 page for all three hides the distinction.
Fix the source of the mismatch
Check the HTTP response, visible content and failed resources. If a shared template causes the problem, rewriting one article will not address the underlying failure.
After a fix, compare a current live response with the date of Google’s stored observation. An older classification may remain until the page is processed again; repeatedly changing an already-correct response can create unnecessary work.
What a successful correction means
A working page should return useful content with the appropriate success response. A genuinely missing page should report that state. A moved page should redirect to the appropriate destination.
This verifies website behavior. Subsequent indexing is a separate process. The objective is an accurate response for each URL, not a report with no intentional 404s.