SEO BLOG
Soft 404 in Google Search Console: What It Means and How to Fix It [2026]
Ganesh Shanmugam9 min readFix a soft 404 in Google Search Console. Learn what Google means, why thin, empty and out-of-stock pages get flagged, and when to use a 404, 410 or a 301.
![Soft 404 in Google Search Console: What It Means and How to Fix It [2026]](https://cdn.sanity.io/images/s5479b37/production/71b2f16d4982ad2d1a60580ba11275b2150578a1-1920x1080.png?w=1440&h=810)
Your page loads perfectly in a browser. The server returns a healthy 200 status. Yet the Page indexing report lists it as "Soft 404", and it has vanished from Google.
That mismatch confuses a lot of site owners. A soft 404 in Google Search Console means Google looked at the page's content and decided it behaves like an error page, whatever the status code says. Sometimes Google is right, and the page should return a real 404. Other times, the page is valid but looks empty or broken to Googlebot.
This guide explains what Google means by a soft 404, how it differs from a normal 404, the most common causes, how to diagnose each flagged URL, and which fix fits which cause. It also covers ecommerce, WordPress and JavaScript sites, where soft 404s show up most often.
Key Takeaways
- A soft 404 is about content, not status codes. The page returns 200 but looks like an error, an empty page or a "not found" message.
- Sometimes Google is right. If the page is gone for good, return a real 404 or 410 instead.
- Sometimes the page just looks empty. Thin pages, empty categories and out-of-stock products with little content often get flagged.
- JavaScript sites are especially prone. Google recommends a redirect to a real 404 URL, or a noindex tag, for client-side error pages.
- Do not redirect dead pages to the homepage. John Mueller has said Google mostly treats those as soft 404s anyway.
- URL Inspection shows what Google saw. The rendered screenshot and HTML often reveal the cause in seconds.
What Is a Soft 404 in Google Search Console?
Quick answer: A soft 404 in Google Search Console means a URL returned a success status, usually 200, but its content looks like an error page, an empty page or a "not found" message, so Google does not index it. If the page no longer exists, return a real 404 or 410. If it moved, use a 301 to a genuinely equivalent page. If it is a valid page, add real content and make sure Googlebot can render it.
Google's Page indexing report help describes it this way: the page "returns a user-friendly 'not found' message but not a 404 HTTP response code". Google's crawling troubleshooting guide adds that, in some cases, a soft 404 "might be a page with no main content or empty page".
In other words, Google reads the page and makes a judgement. When the content says "nothing here", Google believes the content over the status code.
Soft 404 vs 404
The two statuses sound alike, but Google handles them differently, and they need different fixes.
| "Soft 404" | "Not found (404)" | |
|---|---|---|
| Status code returned | 200 (success) or similar | 404 |
| What visitors see | An error message, an empty page or very thin content | A "not found" page |
| Who decides | Google, based on the page content | Your server |
| Is it a problem? | Yes, the signals contradict each other | Not necessarily, if the page was removed on purpose |
| Usual fix | Return a proper code, or add real content | Nothing, or a redirect if a replacement exists |
Google's help says 404 responses "are not necessarily a problem, if the page has been removed without any replacement". A soft 404, by contrast, always involves a contradiction that you should resolve one way or the other.
Is a Soft 404 an Error in SEO?
Yes, although what you do about it depends on the page. Google's troubleshooting guide gives two reasons soft 404s are bad. First, visitors expect a working page and instead see an error. Second, soft 404s can hurt your crawl coverage: time Googlebot spends on non-existent pages means your real URLs "may not be discovered as quickly or visited as frequently".
For valid pages wrongly flagged, the cost is more direct. The page drops out of the index, along with any traffic it earned. That is why soft 404s on product, service or category pages deserve prompt attention.
Common Causes of Soft 404s
Thin or empty pages
Pages with almost no main content look like errors to Google. Typical examples include empty category or tag archives, location pages with only an address, placeholder pages published before content was added, and profile pages with no details. Google's guide specifically mentions pages "with no main content".
Out-of-stock and discontinued products
This is the classic ecommerce case. When a product sells out, many templates strip the price, the buy button and most of the description, leaving a page that says little more than "unavailable". According to Search Engine Roundtable, John Mueller said in November 2020 that "out-of-stock or not available pages generally tend to end up as soft 404 pages", and later added that there is "no fixed timeframe" for when that happens.
Internal search results pages
Search pages on your own site, especially those with no results, are a frequent source. Google's troubleshooting guide lists "an empty internal search result page" as a common cause. These pages rarely deserve indexing in the first place.
JavaScript-rendered errors returning 200
Single-page applications often handle routing in the browser. When someone requests a URL that does not exist, the server still returns 200 with the app shell, and JavaScript then draws a "page not found" message. Google sees a success code with error content, which is a soft 404 by definition.
Missing resources and rendering failures
Sometimes the page is fine, but Googlebot cannot render it properly. Google's guide lists "blocked resources (blocked by robots.txt), having too many resources on a page, various server errors, or slow loading or very large resources" as issues that can cause a valid page to be detected as a soft 404. It also names a missing server-side include file, a broken database connection and an unloaded JavaScript file as common triggers.
Redirects to unrelated pages
Redirecting deleted pages to the homepage or a broad category is a popular shortcut, yet it backfires. As reported by Search Engine Roundtable in January 2019, Mueller said of redirecting dead pages to the homepage: "we mostly treat them as 404s anyway (they're soft-404s), so there's no upside." Google's own guidance reserves a 301 for a page that has "moved or has a clear replacement".
How to Diagnose a Soft 404
Work through each flagged URL in this order:
- In Search Console, open Indexing, then Pages, and select Soft 404 under "Why pages aren't indexed". Export the examples and group them by template: products, categories, search pages, blog tags and so on.
- For each group, decide one thing first: should this page exist? A discontinued product or an empty search page probably should not. A live service page certainly should.
- Open URL Inspection for an example URL and click Test live URL. Then select View tested page to see the screenshot and rendered HTML Googlebot produced.
- Compare the screenshot with what you see in a browser. If Google's version is blank, broken or missing the main text, you have a rendering problem.
- Check the More info tab for page resources that could not be loaded, including files blocked by robots.txt.
- Confirm the real status code with curl -I https://example.com/page. A "not found" message served with 200 is the core contradiction to remove.
Soft 404 Fixes by Cause
| Cause | Should the page exist? | Fix |
|---|---|---|
| Page deleted, no replacement | No | Return 404 or 410 |
| Page moved or clearly replaced | No, the replacement does | 301 to the genuinely equivalent page |
| Deleted page redirected to homepage | No | Replace with a 404, or a 301 to a true equivalent |
| Thin or empty page you want indexed | Yes | Add substantial, useful main content |
| Empty category or tag archive | Usually no | Add products or posts, noindex it, or remove it and return 404 |
| Temporarily out-of-stock product | Yes | Keep the full description, specs and images; state availability clearly; suggest alternatives |
| Permanently discontinued product | Usually no | 301 to the direct successor, or return 404 or 410 |
| Internal search results pages | No | Keep them out of the index with noindex, and avoid linking to empty result pages |
| JavaScript "not found" view returning 200 | No | Redirect to a URL that returns a server 404, or add a noindex robots meta tag with JavaScript |
| Valid page that fails to render | Yes | Unblock resources, fix server errors, and reduce heavy or slow resources |
The JavaScript row comes straight from Google's JavaScript SEO basics, which gives two options for single-page apps: "Use a JavaScript redirect to a URL for which the server responds with a 404 HTTP status code", or add <meta name="robots" content="noindex"> to error pages using JavaScript.
A note on the 410 status: Google's HTTP status code documentation says Google doesn't index URLs that return a 4xx code, and removes already indexed URLs that start returning one. Both 404 and 410 therefore do the job of telling Google a page is gone.
Platform Notes
Ecommerce and Shopify
Soft 404s cluster around sold-out products and empty collections. For products that will return, keep the page complete, with description, specifications, reviews and images, plus a clear stock message and links to similar items. For discontinued products, Shopify lets you create a URL redirect when you delete a product, so point it at a direct successor if one exists. Shopify only allows redirects from broken URLs, so the product must be deleted or hidden first. For broader store indexing checks, see our guide on getting Google to index your Shopify website, and for catalogue-scale work, our ecommerce SEO service.
WordPress
WordPress often produces thin tag and author archives, and some themes return a styled "nothing found" template on empty archives or search pages. Consider noindex for thin archives and search results in your SEO plugin, and delete tags that hold only one or two posts. When you remove a post with no replacement, let WordPress return its normal 404 rather than redirecting to the homepage.
JavaScript frameworks
React, Vue and similar apps need a deliberate approach to "not found" routes. Either route unknown paths to a server-side 404 URL, or inject a noindex tag on the error view. Also confirm that Googlebot can load every script and API response the page needs; a failed API call that leaves a blank template can trigger a soft 404 on perfectly valid pages.
How to Validate the Fix
Once you have fixed a pattern across the site:
- Run URL Inspection on a few fixed URLs and click Test live URL to confirm Google now sees either real content or the correct error code.
- For valid pages you want back in the index, click Request indexing. Google notes there is a daily limit on these requests, so use a sitemap for larger sets.
- In the Soft 404 report, click Validate fix.
Google's help says validation "typically takes up to about two weeks, but in some cases can take much longer", and that it stops if Google finds a single remaining instance. Fix the whole template, not just the example URLs. Note too that URLs you deliberately changed to return 404 will move to the "Not found (404)" status, which is the intended result.
If a restored page later shows "Crawled - currently not indexed", Google can now read it but has not chosen to index it yet; our guide to fixing Crawled - currently not indexed covers that stage. Similarly, if many new URLs sit unvisited, see our guide to fixing Discovered - currently not indexed.
How Billion Game Fixes Soft 404s
Soft 404s are rarely a single-page problem. Usually a template, a plugin or a stock rule is producing them in bulk. Billion Game's specialist team groups the flagged URLs by template, decides which should exist and which should not, and then fixes the status codes, content or rendering at the source. Every change is checked with URL Inspection and tracked in your own Search Console. If your Soft 404 list keeps growing, our Google Search Console issue fixing service can take it off your plate.
Frequently Asked Questions
What is a soft 404?
A soft 404 is a page that returns a success status code, usually `200`, while its content looks like an error, an empty page or a "not found" message. Google reports these in Search Console and does not index them.
What is the difference between a 404 and a soft 404?
A 404 is a status code your server sends to say a page does not exist. A soft 404 is Google's judgement that a page returning `200` actually behaves like an error page. The first is often intentional and fine; the second is a contradiction you should fix.
Is a soft 404 bad for SEO?
It can be. Valid pages flagged as soft 404s drop out of the index, and Google says soft 404s can hurt crawl coverage because Googlebot spends time on pages that do not really exist.
How do I solve 404 and soft 404 indexation issues in Google Search Console?
Decide whether each page should exist. If not, a real `404` or `410` is correct, and no further action is needed. If it should exist, add genuine content, fix rendering problems, and request indexing. Redirect only when there is a truly equivalent replacement.
Should I redirect soft 404 pages to my homepage?
No. John Mueller has said Google mostly treats redirects of dead pages to the homepage as soft 404s anyway, so there is no benefit. Return a `404` or `410`, or redirect to a genuinely equivalent page.
Why does Google show a soft 404 for a page that exists?
Usually because the page looks empty or broken to Googlebot. Thin content, a sold-out product template, blocked scripts or a failed API call can all make a valid page look like an error. Use the live test's screenshot to see what Google saw.
Final Thoughts
A soft 404 is Google telling you that your page's status code and its content disagree. The fix is to make them agree: either the page is gone and says so with a real error code, or the page is valid and shows enough content for Google to see it.
Start by grouping the flagged URLs by template, then apply the matching fix from the table above. Treated that way, a soft 404 in Google Search Console becomes a quick clean-up task rather than a mystery.
Share
Ready to Hire an AI SEO Expert?
Book a free 30 minute AI Visibility Audit. We analyze your search visibility across Google, ChatGPT, Perplexity AI and AI Overviews.
About the author

Ganesh Shanmugam
Ganesh Shanmugam is an SEO and AEO consultant based in Chennai, India, and the founder of Billion Game — a boutique agency serving clients across the US, UK, Australia, Canada, and Ireland. He previously held SEO roles at 7 Eagles and Digital Scholar before going independent, and brings 4+ years of hands-on experience
AI SEO insights in your inbox
For growth-stage brands: organic traffic, AI citations, and strategy notes. No spam—unsubscribe anytime.
By subscribing you agree to our Privacy Policy.
![Page with Redirect in Google Search Console: What It Means and When to Fix It [2026]](https://cdn.sanity.io/images/s5479b37/production/7de4ccc9a0e966a6ac06e06715a36861c975060e-1920x1080.png?w=800&h=450)
![Schema Markup for AI Search: What Helps, What Is Hype [2026]](https://cdn.sanity.io/images/s5479b37/production/9048f007bedfd48b23a6d1cac59a0efa4dcebdb0-1920x1080.png?w=800&h=450)
![Blocked by robots.txt: What It Means and How to Fix It [2026]](https://cdn.sanity.io/images/s5479b37/production/38dc10abf9ae2217a085bd156468b04d39eef1aa-1920x1080.png?w=800&h=450)