A soft 404 is Google’s classification for a URL whose content appears to be missing or an error, although the response does not report a normal HTTP 404. A common example is a page that says “not found” while returning 200 OK. Diagnose the response and the rendered content together.
What is a soft 404?
The “soft” part describes a mismatch. The server can report success while the page tells the visitor that the requested content is unavailable. It can also deliver a mostly empty page because an essential resource failed to load. Google explains these cases in its crawling-error guidance.
A short page is not automatically a soft 404. A concise definition can satisfy its purpose. Nor does a tool’s word-count filter establish Google’s classification: it only helps you find pages worth inspecting.
Common causes of soft 404s
Start with the page’s intended purpose, then check what visitors and Google actually receive. These are illustrative failure patterns, not reported theStacc customer incidents:
- A deleted article still loads the site’s navigation but no article body.
- A search or filter URL returns an error-like message with no useful results.
- A product template replaces the description with an availability notice.
- A database request or JavaScript resource fails, leaving the main content blank.
- A retired URL redirects to an unrelated page that does not meet the original request.
Being out of stock does not, by itself, mean a product page is missing. Check whether the page still provides accurate product details and useful availability information before deciding to remove it.
How soft 404s affect search
Google’s documentation says pages it identifies as soft 404s are excluded from Search. If a working page is affected, restore the content Google should see. If it is genuinely gone, make the HTTP response reflect that state.
Repeated requests for empty URLs can consume server resources, but the presence of soft 404s does not prove a site-wide ranking penalty. It also does not establish that important pages lost crawling time. Check the actual indexing and request evidence instead of inferring a domain-wide effect from a count.
How to find and investigate soft 404s
- Check the reported reason. In Google Search Console, open the Page indexing report and inspect URLs listed under Soft 404.
- Compare historical and live evidence. Note the last crawl date. Run a live URL inspection and examine the tested page, its screenshot, content and response.
- Inspect the template. Check whether similar URLs share a blank body, an error message, a failed resource or the same incorrect redirect.
- Use crawl and log data as supporting evidence. Logs show requests and response codes; a local crawl shows what your tool received. Neither, alone, proves a Google soft-404 classification.
The Page indexing report documentation explains both the Soft 404 reason and the difference between a previous crawl and a live test. A URL that is crawled but not indexed can have other causes, including duplicate selection.
Choose a fix that matches the page’s purpose
| Page state | Action | What to verify |
|---|---|---|
| Content should still exist | Restore the main content or repair the loading failure. | The rendered page contains the intended information. |
| Content moved | Use a 301 redirect to the relevant replacement. | The destination answers the same need and works. |
| Removed with no replacement | Return a genuine 404 or 410. | The response is an error even if the page offers helpful navigation. |
| Useful utility page that should stay out of search | Use an appropriate indexing rule, separate from repairing missing content. | Google can access the rule and the page still serves users. |
Sources: Google’s soft-404 repair guidance and noindex documentation. A redirect should have a relevant replacement; a homepage fallback is not a substitute for that decision.
If a service page is meant to attract visitors from search, excluding it does not restore its missing content. Repair the page first. Use noindex when exclusion is the intended outcome, not as a blanket repair.
Soft 404, HTTP 404 and HTTP 410
A 404 error reports that the requested resource was not found; HTTP 410 says it is no longer available and the condition is likely permanent. A soft 404 is a search classification rather than a status you deliberately return. See RFC 9110, sections 15.5.5 and 15.5.11.
Google treats 404 and 410 alike for its documented handling of missing content. Do not promise that choosing 410 will remove a URL faster. Google’s HTTP-status guidance describes how affected URLs are removed from the index over time.
Prevent the same failure from returning
Test a deleted URL, a moved URL and a working content page whenever you change a CMS template or routing rule. Check both status and content. Keep a removal map so a later redesign does not turn deliberate errors back into empty 200 pages.
Keep crawl control and indexing control separate. Google does not support a noindex rule in robots.txt. A crawler must be able to fetch a page to see its noindex meta tag or HTTP header; blocking the fetch can prevent the rule from being read.
Frequently asked questions
Is every thin page a soft 404?
No. Word count alone does not establish a soft 404. Check whether the page delivers its intended content and whether Google reports it as missing or error-like. A useful short definition and an empty error template are different cases.
Should an out-of-stock product automatically return 404?
No. First decide whether the product page still has a purpose and accurate information. An unavailable item is not automatically a missing URL. Retain useful content when appropriate; remove or redirect the page only when that reflects the actual page state.
How quickly will a fix appear in Search Console?
Compare the report’s last crawl date with the live page. Google needs to process the changed URL before historical reporting reflects it. A successful live test is useful evidence, but it is not a promise of indexing or a fixed reporting deadline.
Related glossary terms
Sources and editorial note
This entry was revised with AI assistance against the primary references listed above. Examples describe possible failure patterns, not first-hand customer tests. No named-human review is claimed, and the original publication date is preserved.