What does a soft 404 actually mean?
A soft 404 is a URL that tells the user, in substance, that the page does not exist or has no main content, while the server still returns a 200 success status.
Google’s algorithms can classify that as an error page and exclude it from Search. Search Console then lists it under soft 404 in the Page indexing report. Source: Troubleshoot Google Search crawling errors.
Signal
200 OK, but it looks empty or like an error Search Console reports a soft 404 when the content does not match a real page.Gone
No replacement Return a real 404 or 410. A custom not-found page still needs that status code.Moved
Equivalent page exists Use a server-side permanent redirect to the matching location or service URL.Still valid
Fix what Googlebot rendered Blocked scripts, empty shells, “coming soon” copy or failed location APIs can look like nothing is there.Check
URL Inspection rendered HTML Confirm the useful local content is in the rendered document, not only on a finished browser tab.
Why can local pages trigger it?
Local templates often return 200 for closed locations, empty store-locator searches, “coming soon” city pages, failed location APIs, or JavaScript apps that never fill the shell.
Google also lists missing includes, broken database connections, empty internal search results and unloaded JavaScript as typical generators of this pattern. A thin location page that looks like a placeholder can be grouped with true error pages. Cleanup of doorway-style city sets is a different decision: should you delete thin or duplicate city pages.
How do I confirm the cause?
Use URL Inspection and look at the rendered HTML and the HTTP code Google received.
If the rendered page is blank, nearly blank, or dominated by an error message, Google may be missing resources — robots.txt blocks, too many resources, server errors, or slow files. That is a rendering failure, not proof the business should delete the location. Source: the same crawling-errors documentation.
The page should no longer exist
If you removed the page and there is no similar replacement, return 404 or 410. Custom not-found pages are for people; they still need a 404 status so they are not indexed.
Old local URLs that still attract links need a separate decision about redirects versus gone: what to do with old local URLs that still have backlinks.
The content now lives elsewhere
If the location or service now has a clear replacement URL, use a server-side permanent redirect to that page.
Confirm with URL Inspection that the old address no longer 200s with empty content. Chains of redirects are a further problem: whether redirect chains are hurting location and service pages.
The page is still a real page
If the location is open and the page should rank as a useful document, keep 200 and fix what Googlebot rendered.
Client-side apps that show “not found” without a 404 should redirect to a server 404 URL or add noindex on the error state. Source: JavaScript SEO basics.
Soft 404 outcome table
| Business reality | Correct HTTP outcome | Typical local example | Wrong response |
|---|---|---|---|
| Permanently gone, no equivalent | 404 or 410 | Closed suburb page with no remaining branch | 200 with “sorry, this location closed” |
| Moved to a new URL | Permanent redirect | Renamed location path after a CMS change | 200 empty template on the old path |
| Still a real location or service | 200 with useful rendered content | Branch page whose API failed for Googlebot | Deleting the URL because Search Console listed it |
| Empty locator filter | 404, noindex, or do not mint the URL | Store finder with zero results for a query string | Indexing every empty filter combination |
What should I not do?
Action checklist
- Export soft 404 URLs and group them: gone, moved, still valid, filter junk.
- Inspect a sample of each group. Save rendered HTML and the HTTP status.
- Apply 404/410, a single permanent redirect, or a rendering fix — one outcome per URL.
- Unblock resources required to render location names, hours and main copy.
- For JavaScript apps, return a real 404 URL or noindex on empty states.
- Request recrawl after the live response matches the intended outcome.
When professional help makes sense
Help is useful when a locator generates thousands of empty 200s, when a SPA cannot return HTTP 404, or when soft 404s and thin city templates are mixed in one report. Correcting status codes does not guarantee reindexing.
Sources and further reading
- Google Search Central: Troubleshoot crawling errors (soft 404)
- Google Search Central: JavaScript SEO basics
Local URLs listed as soft 404s and you are unsure which should still exist?
Otepsphere can group those URLs by whether they are gone, moved or still valid, then match each group to a status code, redirect or rendering fix before the template is rewritten.
Contact OtepsphereWho writes this
This page is published by Otepsphere, a specialist Local SEO consultancy. A named founder biography, photograph and professional profiles will be added here only when they have been verified. Until then, treat Otepsphere as the responsible organisation rather than a fictional expert.