A soft 404 is a URL that technically returns a successful response but appears to search systems like an error, empty result, or missing page. The mismatch makes it harder to understand whether the URL contains real indexable content.
Quick Answer
If content is genuinely gone with no replacement, return a real 404 or 410. If there is a close successor, redirect to it. If the page should remain live, provide substantive content and a normal 200 response instead of an empty or error-like template.

Why HTTP 200 Can Still Be a Problem
A page can return 200 while displaying ‘not found’, an empty product shell, a zero-result screen or a generic template. Search systems may classify that experience as a soft 404 despite the success code.
The issue is not that 200 is bad; it is that the response code disagrees with the page’s purpose.
Choose the Correct Outcome
Use 404 or 410 when the resource is gone and there is no meaningful replacement. Use a permanent redirect only when another page genuinely replaces it.
Do not redirect every missing URL to the homepage. That creates irrelevant destinations and can itself be treated as an error-like result.
Check Templates at Scale
Soft 404 patterns often come from reusable CMS templates. Test several missing URLs, empty taxonomies and deleted content types so you fix the pattern rather than one page.

Soft 404 Diagnosis
- Check the HTTP response code.
- Read what a user actually sees.
- Look for empty or generic templates.
- Decide whether the URL should exist, redirect, or return an error.
- Retest representative URLs after the fix.
Examples of Soft 404 Patterns
An ecommerce site may keep a deleted product URL live with a 200 response and the message “This product is no longer available,” but provide no replacement, specifications, or useful alternatives. A directory may return 200 for every impossible location query while displaying an empty results template. A WordPress site may route mistyped slugs to a generic page that looks like an error but still returns success.
In each case, the problem is the mismatch between the server response and what the page represents. If there is no useful content at that URL, returning a real error code is clearer than preserving an empty shell.
When a Removed Page Should Redirect Instead
A redirect makes sense when the new destination genuinely replaces the old resource. If a discontinued product has a direct successor, or two duplicate articles were consolidated into one definitive guide, a permanent redirect can preserve a useful path for users.
Do not redirect solely to avoid a 404. Sending every removed URL to a category or homepage creates poor destinations. A correct 404 is often better than an irrelevant redirect because it accurately communicates that no equivalent resource exists.
Common Mistakes
Avoid stuffing a missing page with generic text just to preserve a 200 response. Also avoid sending every deleted page to the homepage regardless of topic.
Watch the Topic in Context
How Google Search Crawls Pages
Crawling retrieves both the status response and page content, which is why soft 404 diagnosis requires looking at both.
Watch on YouTube ↗ · Google Search Central