Fix a soft 404 error by checking what a missing page returns
A page can say it can't be found and still send a success response. Google calls that mismatch a soft 404.
What is a soft 404 error?
A 200 response says the request succeeded even if the content describes an error or is empty. For a page that no longer exists and has no replacement, return 404 or 410. Google's status-code guide explains how those responses are treated.

Make a custom 404 page return a missing-page status
Keep useful navigation on the error page, but set the server to return a missing-page status too. If you've moved the content to a real replacement, redirect there rather than showing an error.
Check soft 404 responses in a single-page app or Next.js
A single-page app's route fallback can return the app shell for an unknown path. Google suggests using JavaScript to redirect to a URL where the server returns 404, or to add a noindex robots meta tag to the error view. Check the response at an address that shouldn't exist, as well as the error message shown after JavaScript runs.
In Next.js, a
not-foundview can return404before streaming starts and keep200once streaming has begun. Next.js addsnoindexin both cases. Next.js documents this behavior. Check the status and indexing instruction together.
Frequently asked questions
Do I need to fix "Not found (404)" errors in Search Console?
No. A removed page with no similar replacement can correctly return 404 or 410. Redirect a moved page to its replacement, but not many old pages to the home page, which Google says may be treated as a soft 404.
Review redirects and indexability after a soft 404
Website quality
Find the leftovers that make people say your site looks like AI slop.
Redirects
Choose the right redirect for a move and remove unnecessary steps to the destination.
Indexability
Find the noindex tags and other blocks that stop a page from being indexed.