Soft 404 Errors: What They Are and How to Fix Them
A soft 404 is a page that looks like a not-found page to users but returns a normal success response. Google flags it and it will not be indexed as a real page. This guide explains the definition, the two fixes Google gives, how to confirm what Google sees, and how to tell soft 404s from real 404s.
- Definition
- Two official fixes
- Soft vs real 404
- WordPress causes
HTTP 200 OK Page says: "Not found" => soft 404
A soft 404 is a page showing a user-friendly not-found message while returning a success status code instead of 404. Google’s fixes: return a true 404 for pages that really are not found, or, if the page is valid, add more content so it is not treated as a soft 404. Run a live URL Inspection test and use View tested page to see how Google renders it.
What a soft 404 is
A page that shows a user-friendly not-found message but returns a normal success response instead of an HTTP 404 code. Google’s systems flag such pages as soft 404s in the Page indexing report. Google’s HTTP guidance adds that a success response with content suggesting an error, such as an empty page or an error message, triggers the soft 404 label.
Soft 404 vs real 404
| Type | Status code | What Google does |
|---|---|---|
| Real 404 | 404 | Removes a previously indexed URL; newly met 404s are not processed; crawling slows over time |
| Soft 404 | 200 (success) | Flags the page as soft 404 in the report |
For a deeper look at real 404s, see fix 404 errors.
Google’s two fixes
Return a true 404
Make the server send a 404 response code for pages that are actually not found.
Add more content
If the page should exist, add content so Google does not treat it as a soft 404.
Google also says a 404 is not necessarily a problem when a page was removed with no replacement, and that a 301 redirect fits a page that moved. It generally recommends fixing only 404s you link to yourself or list in a sitemap.
Confirm what Google sees
Run a live test in the URL Inspection tool and click View tested page to see a screenshot of how Google renders the page. This shows whether the content looks empty or like an error.
How Google treats real 404s and 410s
- Google ignores any content from URLs returning a 4xx status.
- All 4xx codes except 429 are treated the same way: the content does not exist. 410 is listed in that group, with no separate handling described.
- A previously indexed URL returning 404 is removed from the index. Newly encountered 404 pages are not processed, and crawling gradually decreases.
- The Page indexing report shows only URLs that returned 404s in the past month.
Fix a soft 404 step by step
Open each URL
Is it empty, an error, or thin?
Should it exist?
Gone, moved or valid.
Apply the right fix
404, 301 or real content.
Run a live test
Check the status code and render.
Which fix to choose
| Situation | Fix (mix of Google and my own advice) |
|---|---|
| Deleted page, no replacement | Return a real 404 (or 410) |
| Page moved | 301 redirect to the new URL. See 301 vs 302 |
| Valid but thin page | Add useful content |
| Empty category or search result | Return 404 or noindex if there is nothing to show (my own advice) |
| Redirect to unrelated page | Avoid; use a relevant target or a 404 (my own advice) |
Notes for WordPress sites
- Themes with custom 404 pages sometimes send 200 (my own note). Check the response code with a header checker.
- Empty archives or tags with no posts can be flagged.
- Thin pages such as placeholder or tag pages may need content or noindex. See noindex tag.
- Caching or security plugins can rewrite status codes.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| Custom 404 page flagged | Returns 200 | Send a real 404 |
| Valid page flagged | Too little content | Add substance |
| Still flagged after fix | Not yet rechecked | Validate and wait |
| Redirect loops to homepage | Mass redirect | Redirect to relevant pages only |
Checklist
Detect
- Open the report
- List flagged URLs
- Inspect each
- Check status code
Fix
- Gone: real 404
- Moved: 301
- Valid: add content
- Empty: handle properly
Verify
- Live test
- View tested page
- Validate fix
- Wait for recheck
Prevent
- Test 404 template
- Fix thin pages
- Avoid mass redirects
- Review monthly
What Google’s pages do not say
They do not say how Google decides a page is a soft 404 or any thresholds, how long Google keeps crawling a 404 URL, or whether soft 404s appear in sitemap filter views. The separate soft 404 article is linked from the help page and is not reproduced there.
Key terms
- Soft 404
- An error-looking page returning success.
- 404
- Not found status code.
- 410
- Gone status code.
- 301
- Permanent redirect.
Common mistakes
Custom 404 returning 200
Creates soft 404s.
Redirect all to homepage
Misleading.
Ignoring thin pages
Flagged.
Fixing all 404s
Unneeded work.
Not testing live
Unknown status.
Forgetting Validate
Report stays.
Related guides
Soft 404 questions
What is a soft 404?
A page that shows a not-found message but returns a success response code.
How do I fix it?
Return a true 404 for missing pages, or add more content to a valid page.
Is a normal 404 bad?
Not necessarily if the page was removed with no replacement.
Which 404s should I fix?
Generally those you link to or list in a sitemap.
What if the page moved?
Use a 301 redirect to the new location.
How do I see what Google sees?
Live test in URL Inspection, then View tested page.
Does Google index 404 pages?
No. A previously indexed 404 URL is removed.
How long do 404s stay in the report?
The report shows URLs that returned 404 in the past month.
The soft 404 definition, the two fixes, inspection advice and 404 handling come from Google. The decision table, step routine, WordPress notes, troubleshooting and checklists are my own.