What Is a Soft 404?
A soft 404 is a page that looks empty or missing to users but returns a 200 OK status code instead of a proper 404 Not Found. Because the server reports success, search engines waste crawl budget on the dead page and may keep it indexed or flag it as low quality. Soft 404s also appear when thin, near-empty, or wrongly redirected pages behave like error pages. The fix is to return the correct status code or add real content.
- Definition
- A page returning 200 OK while showing no useful or missing content (Google Search Central)
- Where it is reported
- Flagged under the Soft 404 issue in Search Console's page indexing report (Google Search Central)
- Common cause
- CMS or builder serving a friendly not-found message with a 200 status (industry-typical)
- Correct fix
- Return a genuine 404 or 410, or restore substantive content on the URL (Google Search Central)
What is a soft 404? #
A soft 404 is a mismatch between what a page shows and what its server reports. To a visitor the page looks like an error, empty, missing, or displaying a message like nothing found, yet the server returns a 200 OK status as though everything succeeded. Search engines detect this contradiction and label the URL a soft 404, because the content signals a dead end while the status code claims success. Google identifies these pages algorithmically by analyzing the content, so even a page that technically loads can be classified as a soft 404 if it appears to be an error or has essentially no meaningful content. The problem matters because the wrong status code misleads crawlers: instead of cleanly dropping a missing page as they would with a real 404, they keep visiting and possibly indexing a page that helps no one. Understanding the gap between a real 404 and a soft 404 requires knowing how status codes work, which is covered in /wiki/what-are-http-status-codes.
What causes soft 404s? #
Soft 404s arise from several recurring patterns. The most common is a content management system or website builder that serves a friendly not-found message but returns a 200 status instead of a proper 404, so every mistyped or deleted URL becomes a soft 404. Thin pages are another cause: a page with almost no content, such as an empty category, a filter combination with zero results, or a placeholder that never got filled, can be judged an error even though it was meant to exist. Wrongly configured redirects contribute too, especially when many old URLs are redirected to an irrelevant homepage; Google may treat that as a soft 404 because the destination does not match the original intent. Out-of-stock ecommerce pages that display a bare notice, expired listings, and pages whose main content failed to load can all trigger the classification. Because the causes span platform defaults, content gaps, and redirect mistakes, diagnosing soft 404s is a standard part of the audits behind /services/website-rescue.
Why are soft 404s bad for SEO? #
Soft 404s hurt a site in several ways at once. First, they waste crawl budget: search engines keep revisiting URLs that return 200 as if they were live, spending crawl resources that should go to real content, which matters most on larger sites. Second, they clutter the index with low-value or empty pages, and a pattern of thin, error-like pages can drag on a site's overall quality signals. Third, they hide genuine problems, because a missing page returning 200 never gets cleanly removed the way a real 404 would, so dead URLs linger in results and disappoint the users who click them. Fourth, wrongly redirected pages flagged as soft 404s fail to pass the ranking authority the redirect was meant to preserve, quietly wasting link equity. Because these effects compound, resolving soft 404s is a routine efficiency win in technical SEO. Our /tools/website-grader helps surface pages that behave like errors, and the deeper fixes fold into ongoing /services/care-plans.
How do you find soft 404s? #
The primary tool for finding soft 404s is Google Search Console, whose page indexing report includes a dedicated Soft 404 category listing every URL Google has classified this way. Because the classification comes from Google's own analysis, this report reflects exactly how the search engine sees your pages, making it the authoritative starting point. Beyond Search Console, a site crawler that inspects both status codes and content can flag suspicious combinations, such as URLs returning 200 with very little text or with error-like phrases. Manual spot checks help too: visit a URL that should be a deleted page and confirm what status it returns using developer tools or a header checker, since a deleted page displaying a not-found message should return 404, not 200. Our /tools/website-down-checker and /tools/website-grader assist with quick verification. The pattern to hunt for is any page that looks empty, missing, or error-like to a human but reports success to a machine, because that gap is the definition of a soft 404.
# Request a URL you deleted and check the reported code.
curl -o /dev/null -s -w "%{http_code}\n" \
https://example.com/old-removed-page/
# 200 -> SOFT 404: server wrongly reports success
# 404 -> correct: page is properly reported as not found
# 410 -> correct: page is reported as permanently goneHow do you fix a soft 404? #
The fix depends on why the URL exists. If the page is genuinely gone and should not return, configure the server or CMS to return a real 404 Not Found, or a 410 Gone if the removal is permanent, so search engines cleanly drop it. If the page should exist but is thin or empty, add substantive, useful content so it is no longer error-like, turning a placeholder into a real page worth indexing. If the soft 404 comes from a bad redirect, point the redirect to a genuinely relevant destination rather than a generic homepage, so the target matches the original intent and the redirect passes value. For out-of-stock products expected to return, keep the page live with helpful content and alternatives rather than showing a bare notice. After making changes, use Search Console's validation feature to ask Google to recheck the URLs. Matching the response to the page's true purpose is the heart of the fix, and it is a common deliverable in /services/website-rescue and /services/ecommerce-development work.
Soft 404 versus a real 404: what is the difference? #
A real 404 is honest: the page does not exist and the server says so by returning a 404 Not Found status, which tells search engines to remove the URL from their index and stop wasting crawl attention on it. A soft 404 is dishonest by accident: the page does not exist or has no value, but the server returns 200 OK, claiming success, so search engines keep treating it as a live page. The difference is entirely in the status code, not in what the visitor sees, because both may display a not-found message. This is why a good custom 404 page must do two things at once, look helpful to the visitor and return the correct 404 code to the crawler. Many builders get the first right and the second wrong, producing friendly error pages that are technically soft 404s. Ensuring the status code matches reality is a small configuration detail with outsized SEO impact, and verifying it is standard in any technical audit.
How do redirects create soft 404s? #
Redirects create soft 404s when the destination does not genuinely correspond to the requested URL. The classic case is a migration where hundreds of old, now-missing pages are all redirected to the homepage or a single generic page as a shortcut. Because the destination bears no relationship to what the user asked for, Google may classify the redirect target as a soft 404 for those URLs, refusing to treat it as a legitimate move and declining to pass the ranking authority the redirect was meant to preserve. The lesson is that a redirect should point to the closest real equivalent of the original page, not a catch-all. If no equivalent exists, it is better to let the URL return a genuine 404 or 410 than to force a redirect that Google treats as a soft 404 anyway. This is exactly why /services/website-migrations projects build a careful redirect map that pairs each old URL with its best modern match, and it connects to the redirect concepts in /wiki/what-is-a-301-redirect.
Why soft 404s matter for local business sites #
Local business sites are especially prone to soft 404s because many are built on templates and builders that return 200 for missing pages by default, quietly generating soft 404s every time a URL is mistyped, a page is deleted, or a redesign leaves old addresses behind. The consequences are practical. Crawl budget gets spent revisiting dead URLs instead of the service and location pages that win customers. Thin or empty pages, such as a location page that was never filled in or a service page with a single line of text, can be flagged as soft 404s and drag on the site's quality signals. During a redesign, lazily redirecting every old URL to the homepage looks tidy but manufactures soft 404s that waste the authority those pages earned. Teams building for local verticals like /web-design-for-dentists and /web-design-for-roofers pair proper status-code handling with substantive page content and clean redirect maps, so that every indexed URL is a real, useful page backed by solid /services/local-seo.
FAQ
How do I know if I have soft 404s?
Check Google Search Console's page indexing report, which has a dedicated Soft 404 category listing every URL Google classified this way. This is authoritative because it reflects Google's own analysis. You can also crawl your site for pages returning 200 with little or error-like content, or manually verify that deleted URLs return 404 rather than 200.
Why does my missing page return 200 instead of 404?
Many content management systems and website builders serve a friendly not-found message but return a 200 status by default, rather than a proper 404. This makes every missing URL a soft 404. The fix is to configure the platform or server to return a genuine 404 or 410 for pages that do not exist.
Is a soft 404 worse than a regular 404?
For a page that should not exist, yes, in the sense that a real 404 cleanly removes the URL while a soft 404 keeps a dead page in circulation, wasting crawl budget and cluttering the index. A regular 404 is the correct, healthy response for missing content; the soft 404 is the misconfiguration to fix.
Can thin content cause a soft 404?
Yes. A page with almost no meaningful content, such as an empty category, a zero-result filter, or an unfinished placeholder, can be classified as a soft 404 even though it returns 200, because Google judges it error-like. The fix is to add substantive content or, if the page has no purpose, remove it and return a 404.
Do soft 404s from bad redirects lose link equity?
They can. When many old URLs are redirected to an irrelevant page like the homepage, Google may treat the target as a soft 404 for those URLs and decline to pass the ranking authority the redirect was meant to preserve. Redirect each old URL to a genuinely relevant equivalent to keep the equity flowing.
How do I fix a soft 404?
Match the response to the page's true purpose. If the page is gone, return a real 404 or 410. If it should exist but is thin, add useful content. If it stems from a bad redirect, point that redirect to a relevant destination. Then use Search Console to validate the fix and prompt a recheck.
Was this helpful?