Soft 404 diagnosis and fixes
A soft 404 is a page that is effectively missing or empty but returns a 200 status, so it looks successful to crawlers while offering no real content. Search engines try to detect them, but you should not rely on that. Soft 404s waste crawl budget and can clutter the index with low-value URLs.
What a soft 404 is
A soft 404 happens when a URL that has no real content — a removed product, an empty search result, a broken template — nonetheless responds with 200 OK. The status says success, but the page is essentially 'not found'. Google explicitly flags soft 404s because they confuse crawling and indexing: the crawler cannot tell from the status that there is nothing worth indexing.
The fix is to make the status match reality.
How to detect and fix soft 404s
Detect them by looking for 200 responses on URLs whose content is missing, empty, or a generic 'not found' message. Common sources are custom error pages that forget to set a 404 status, empty filter or search-result pages, and out-of-stock or deleted items left to render a placeholder.
To fix: return a real 404 (missing, possibly temporary) or 410 (intentionally gone) for genuinely absent content; 301 to an equivalent page where one exists; or restore real content if the page should exist. Make sure your error template sends the correct status header, not a styled 200.
- Missing/empty content → return 404 or 410, not 200
- Equivalent exists → 301 to it instead of a soft 404
- Error templates must set the status header, not a styled 200
Operator checklist
Audit URLs returning 200 with thin, empty, or 'not found' content. Confirm your error pages send a 404 status. Map removed content to 404/410 or 301 as appropriate. Watch parameter and filter URLs that can generate empty 200 pages at scale.
How it appears in analytics and logs
A soft 404 is a mismatch between status and content: a 200 served for a page that is actually not found or empty. It misleads crawlers into treating non-content as indexable, wasting crawl budget and diluting index quality.
Diagnostic use case
Detect URLs that return 200 for missing or empty content, and fix them by serving a true 404/410 or restoring real content.
What WebmasterID can help detect
WebmasterID can surface the status codes crawlers receive, helping you spot URLs returning 200 where a 404/410 is correct, so soft 404s become visible rather than silently wasting crawl budget.
Common mistakes
- Serving a friendly 'not found' page with a 200 status.
- Leaving empty search or filter pages to return 200.
- Relying on search engines to guess that a 200 is really a 404.
Privacy and accuracy notes
Soft-404 detection looks at status codes and content presence, not personal data. WebmasterID reports these patterns for crawler traffic without exposing individual visitors.
Frequently asked questions
- Why are soft 404s a problem if the page still loads?
- Because the 200 status tells crawlers the URL is valid content. They may crawl and index empty or missing pages, wasting crawl budget and adding low-value URLs to the index. Returning a true 404/410 lets crawlers handle the URL correctly.
Related pages
- HTTP 404 Not Found: what it means for crawlers
404 Not Found means the server has no resource at that URL. It is the correct, healthy response for genuinely missing pages — crawlers expect some 404s. Problems arise when important pages 404 by accident, when removed pages should signal 410, or when 'not found' pages wrongly return 200.
- Crawl budget waste: causes and fixes
Crawl budget is the finite attention a search engine spends on your site. It is wasted when crawlers spend it on low-value URLs — endless faceted combinations, parameter variants, soft 404s, and redirect chains — instead of your important pages. Reducing that waste helps key content get crawled.
- Website observability
See where crawlers receive 200s on pages that should be 404s.
Sources and verification notes
- Google Search Central — Soft 404 errorsDocuments soft 404s and the recommendation to return correct status codes.
- MDN — 404 Not Found
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.