usdigitalmarketingindex.com SEO
Why can a page returning HTTP 200 be treated by Google as a soft 404?
Updated November 15, 2026
Because the status code and the content disagree. A 200 says the request succeeded and here is the page. If what comes back is a not-found message, an empty template, or a page with nothing in its main area, Google reads the content and concludes that the page is, in effect, missing. Search Console’s documentation describes the case: “The page request returns what we think is a soft 404 response”, meaning it shows a user-facing not-found message without a 404 status code, and Google recommends returning a real 404 for pages that are truly not found (Search Console’s page indexing report documentation). A 200 is a statement about transport. It does not guarantee that a page will be indexed.
Error messaging within HTTP 200
The plainest form is an error page served with a success code. Two responses for a product that no longer exists. Both are illustrations.
A correct response:
HTTP/1.1 404 Not Found
Content-Type: text/html; charset=utf-8
Page body: "Sorry, we can't find that page."
A soft 404:
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Page body: "Sorry, we can't find that page."
The visitor sees the same thing. A crawler sees a success code attached to an error message. Ways this comes about:
- An application catches the missing record and renders a friendly message through its normal page template.
- A removed page is redirected to the home page or to a generic listing. The redirect resolves to a 200, and the destination has nothing to do with what was requested.
- A custom error page is configured in a way that returns 200.
- A script-driven site shows a not-found view for an unknown route while the server has already answered 200.
Missing or empty main content
The second form has no error message at all. The page is real, and its main area is empty or nearly so.
| Page | What the main content holds |
|---|---|
| A category with no products | Header, filters, footer, and "0 results" |
| An internal search with no matches | "No results found" |
| A page whose content failed to load | The template, with the content area blank |
| A profile or listing that has been emptied | A heading and nothing under it |
| A placeholder published before its content | "Coming soon" |
A response pair for a category page shows the contrast. Both are illustrations.
Successful:
HTTP/1.1 200 OK
Main content: 24 products with names, prices, and links
Likely to be read as a soft 404:
HTTP/1.1 200 OK
Main content: "There are no products in this category."
The classification is Google’s judgment about the content. The documentation’s wording is “what we think is a soft 404”, and a page can be flagged that you consider valid.
URL Inspection evidence
Diagnose from what Google received.
- In the page indexing report, open the soft 404 list and export the URLs.
- Group them by template. A cluster in one template points to one cause.
- Run a live test in URL Inspection on a sample and view the rendered HTML and screenshot. Is the main content there? Rendering failures, blocked resources, and content that needs an action to appear all show up here as a page with a hole in it.
- Request the URL yourself and note the status code and the visible content.
- Compare with a similar page that is indexed.
For each URL, the question is the same: should this page exist?
Correct response design
Fix according to the answer.
| Situation | Correct response |
|---|---|
| The page does not exist and has no replacement | Return 404 or 410, with a helpful error page as the body |
| The page moved to a specific new URL | Permanent redirect to that URL |
| The page was removed and redirected to the home page | Replace with a 404, or redirect to the closest equivalent page |
| The page is valid and temporarily empty | Keep 200 if it will be filled soon and has other useful content; otherwise noindex until it has content |
| The page is valid and its content did not render | Fix the rendering; make the content available in the HTML |
| The page is valid and was misjudged | Add substantive main content that makes its purpose clear |
| A script-driven route that does not exist | Have the server return a 404 for unknown routes, or redirect to a URL that does |
A good error page helps the visitor and tells the truth to the crawler: a real 404 status, a clear message, the site’s navigation, and a search box.
Why it matters beyond tidiness: Google’s crawl budget guidance notes that “soft 404 pages will continue to be crawled, and waste your budget” (Google’s crawl budget guidance). A real 404 tells Google the content does not exist. A soft one leaves the URL in circulation.
Verify after the change.
- Request a nonexistent URL and confirm the status line reads 404.
- Run a live URL Inspection test on a corrected page.
- Use the validate fix option in the page indexing report, and watch the count over the following weeks.
Check the opposite error while you are there: real pages returning 404 or 500 with their full content visible. Visitors see nothing wrong, and the page cannot be indexed.
Single-page applications produce this problem in a particular way, because the server answers before the route is known. The implementation for that case is covered in the guide to how a single-page application should signal a real 404 for a nonexistent route.
The rule: the status code and the content must say the same thing. Missing pages say 404, and pages that say 200 have something on them.
Add your comment to this answer