Where they come from
Custom error pages that forget to set the status, empty search results pages, thin pages generated for every filter, a CMS that redirects missing pages to the home page and parked or default host pages after a hosting change.
Why they matter
Search engines may drop such URLs from the index, and monitors that trust the status code report a failing site as healthy. Both views point to the same fix: send the right status for what the page is.
A quick test
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/this-page-does-not-exist should print 404. If it prints 200 and the page says “not found”, or redirects to the home page with a 200, search engines see a soft 404 and a status-code monitor sees a healthy site. Fix it at the source: the CMS or server must send 404 or 410 for a missing page and 503 for maintenance.
Search Console lists soft 404 URLs in its page indexing report. Work through the list by template rather than URL by URL, because one broken template usually produces hundreds of them.
What to check
That missing pages return 404 or 410, that maintenance returns 503, that important pages contain expected text and that Search Console’s soft 404 list is empty or understood.
Sources
Read on . Standards and vendor pages change; confirm the current text before you rely on it.
- Google Search Central, How HTTP status codes, network and DNS errors affect Google Search (developers.google.com)