You open Google Search Console, go to the Pages report and find a line that reads “Soft 404”. The URLs listed there load perfectly well in your browser. There is no error message, the server is fine and nobody on the team deleted anything. So why does Google treat them as if they do not exist?
Soft 404 errors are one of the most confusing statuses in Search Console because they describe a mismatch rather than a crash. Your server says “this page is fine”, but what Google sees on the page says “there is nothing useful here”. This guide explains why Google flags soft 404 errors, the page types that trigger them most often on Singapore SME websites, and how to decide between fixing the page, redirecting it or letting it return a proper error.
If you are dealing with ordinary broken links and redirect planning, our guide on fixing 404 errors and using 301 redirects covers that side. Here we focus only on the soft 404 problem: how to diagnose it, page type by page type.
What a soft 404 error actually is
Every time a browser or Googlebot requests a URL, the server replies with an HTTP status code. A 200 means “here is the page”. A 404 means “not found” and a 410 means “gone”. A soft 404 happens when the server sends a 200, but the page itself looks like an error page or has no real main content.
Google’s documentation on HTTP status codes and network errors describes a soft 404 as a URL that returns a page telling the user the page does not exist together with a 200 (success) status code, and notes it can also be a page with no main content or an empty page. In other words, “soft 404” is not a status code your server sends. It is a label Google applies after looking at the page and concluding that the 200 is misleading.
Google takes this view because a misleading 200 wastes everyone’s time. Searchers land on empty pages and crawlers revisit URLs with nothing to offer. When Google decides a URL is a soft 404, it does not index it, so it simply drops out of search results until the signals line up again.
Soft 404 vs hard 404 at a glance
| Hard 404 / 410 | Soft 404 | |
|---|---|---|
| What the server sends | 404 or 410 status code | 200 (success) status code |
| What the visitor sees | An error or “page not found” message | An error message, an empty template or very thin content |
| Who decides it is an error | Your server | Google, after reading the page |
| Effect on indexing | URL is dropped from the index over time | URL is excluded from the index |
| Is it a problem? | Usually not, if the page really is gone | Yes, because the signals contradict each other |
Why Google flags pages as soft 404s
Google cannot ask you what you meant, so it compares the status code with the content it renders. When the two disagree, it trusts the content. These are the patterns that most often tip the balance.
Error messages served with a 200 status
Some themes, page builders and custom scripts show a friendly “Sorry, this page could not be found” message but forget to send a 404 header. This is the classic soft 404. It is common after a website rebuild, when a developer creates a custom error template but routes it through a normal page.
Empty or near-empty pages
Pages with almost nothing in the main content area are another frequent trigger: an empty blog tag page, an internal search results page with zero results, a placeholder “coming soon” service page, or a location page that only contains a heading and a contact form. To Google, these look like dead ends, even if you meant them to be useful one day.
Out-of-stock and discontinued products
For e-commerce stores, product pages that suddenly say “This item is no longer available” and remove the description, images and price can start to look like error pages. Google has said publicly that unavailable product pages can end up treated as soft 404s, especially when little useful information remains. A page that keeps the full product details, shows clear availability and links to alternatives is far less likely to be flagged.
Redirects to irrelevant pages
Redirecting many old URLs to the home page, or to a broad category that does not match what the old page was about, is a common shortcut during clean-ups. Google may treat those redirects as soft 404s because the destination does not replace the original content. A redirect only helps when it points to a genuine substitute.
Rendering and JavaScript problems
If your site depends on JavaScript to load content, a failed script, a blocked resource or an API that returns nothing can leave Googlebot looking at a blank shell. Google’s JavaScript SEO basics guide specifically covers avoiding soft 404s in single-page apps, where client-side routing often makes it hard to send a real 404 status.
How to find soft 404 errors on your site
Start in Google Search Console. Open Indexing → Pages, look under “Why pages aren’t indexed” and select Soft 404. Export the list of example URLs so you can group them by page type. Search Console shows a sample rather than every affected URL on very large sites, so treat the list as a starting point.
Next, check a few URLs from each group with the URL Inspection tool and run a live test. The screenshot and rendered HTML show what Google actually sees. If the screenshot is blank, or your main content is missing, you are looking at a rendering issue rather than a content issue. Our guide on getting pages indexed faster walks through the URL Inspection tool in more detail.
Finally, confirm the real status code. A browser extension that shows HTTP headers, or a crawler such as those used in a full SEO audit, will tell you whether your error template is sending 200 or 404. On WordPress, test by visiting a URL that cannot exist, for example /this-page-does-not-exist-123/, and check the response header.
How to fix soft 404 errors, by page type
There is no single fix, because the right answer depends on whether the page should exist. Use the decision table below, then work through each group of URLs.
| Situation | Right response | Why |
|---|---|---|
| Page is genuinely gone with no replacement | Return 404 or 410 | Tells Google and users clearly that the content no longer exists |
| Content moved to a new URL | 301 redirect to the specific new page | Passes visitors and signals to the true replacement |
| Page should exist but is thin or empty | Add real content and keep the 200 | Gives Google a reason to index it |
| Page is useful to visitors but not to searchers | Keep the 200 and add noindex | Removes it from search without breaking navigation |
| Content exists but Google renders a blank page | Fix scripts, blocked resources or server-side rendering | The problem is what Google can see, not what you wrote |
| Product is temporarily out of stock | Keep details, show availability, link alternatives | The page remains a useful answer for that product |
Make real error pages send a real 404
If your custom “page not found” template returns a 200, fix it at the source. On WordPress, the theme’s 404.php template is served with a 404 status by default, so problems usually come from plugins, page builders or redirect rules that send missing URLs to a normal page. Remove those rules and keep a helpful error page with search, popular links and contact options. A good 404 page helps visitors without confusing search engines.
Redirect only to genuine replacements
Map each old URL to the closest equivalent: an old service page to the updated service page, a discontinued product to its direct successor. If no close match exists, a 404 or 410 is more honest than a redirect to the home page. Our SEO migration checklist includes a redirect-mapping step if you are dealing with hundreds of URLs after a redesign.
Add substance to thin pages you want indexed
For pages that should rank, the fix is content. A location page needs details specific to that area, such as the services offered there, travel or parking notes, relevant FAQs and real photos. A category page with two products needs an introduction, buying guidance and links to related categories. If you cannot add meaningful content, consider merging the page with a stronger one and redirecting, or using noindex. Deciding which version to keep is closely linked to handling duplicate content and canonical tags.
Handle empty archives and search results
Empty tag, author and date archives are common soft 404 sources on WordPress blogs. Either remove unused tags, or set thin archive types to noindex in your SEO plugin. Internal site-search result pages generally do not need to be in Google at all; keep them out of your sitemap and consider noindex. Our article on XML sitemaps explains why only index-worthy URLs belong there.
Treat out-of-stock products deliberately
For items that will return, keep the product page live with its description, specifications and photos, mark availability clearly in the page and in your Product structured data, and link to similar products. For items that are permanently discontinued, redirect to a direct successor if there is one, or let the URL return 404 or 410 if there is not. The e-commerce SEO checklist covers product page structure more broadly.
Fix what Google renders
If the URL Inspection screenshot is blank, check whether robots.txt blocks important scripts or stylesheets, whether an API call fails for Googlebot, and whether content only appears after a user interaction. For single-page apps, Google suggests either redirecting missing routes to a URL that returns a real 404, or adding a noindex robots meta tag to error views.
A step-by-step plan to clear soft 404s
For a typical SME website with a few dozen affected URLs, this plan fits into two to three weeks alongside normal work.
- Day 1 – Export and group (marketing lead). Export the Soft 404 examples from Search Console and tag each URL by type: error template, empty archive, thin page, product, redirect or rendering.
- Day 2 – Check status codes (web developer). Confirm what each group actually returns and run URL Inspection live tests on two or three samples per group.
- Days 3–5 – Decide per URL (owner and marketing lead). Mark each URL as keep and improve, redirect, noindex or remove. Use the decision table above.
- Week 2 – Implement (developer and content writer). Fix error templates, add redirects to genuine replacements, write content for pages you are keeping, and tidy archives.
- Week 2 – Update internal links and sitemap (developer). Remove links to deleted URLs and keep only index-worthy pages in the sitemap.
- Week 3 – Validate (marketing lead). Click “Validate fix” in the Soft 404 report and note the date.
- Weeks 4–8 – Monitor (marketing lead). Validation can take several weeks. Re-check the report fortnightly and investigate any new patterns.
How AI can help with soft 404 errors
AI tools are useful for the repetitive parts of this work. A crawler combined with an AI model can group hundreds of flagged URLs by pattern, summarise what each page template contains and suggest which pages look thin. It can draft the extra content for location or category pages from your own notes, and propose redirect maps by matching old URL topics to new ones.
Marketing2u’s AI SEO Agent monitors Search Console indexing and technical health, including status codes, redirects and index drops, and flags meaningful changes rather than daily noise. For broken pages and links across the site, the AI Website Agent reports issues and suggests changes, which only go live with your approval.
Keep a person in charge of the decisions. AI cannot know whether a product is coming back next month, whether a service page matters to an important customer or whether a redirect target is truly equivalent. Treat AI suggestions as a draft list, check a sample by hand, and never let a tool bulk-redirect or delete URLs without review.
Common mistakes to avoid
- Redirecting everything to the home page. It feels tidy, but it often produces more soft 404s and frustrates visitors who wanted something specific.
- Using noindex and robots.txt together. If robots.txt blocks a URL, Google cannot see its noindex tag. Choose one approach per URL.
- Panicking about every flagged URL. A handful of soft 404s on empty archives or old test pages is normal. Prioritise pages that should bring in customers.
- Ignoring internal links. If your own menus and articles still link to removed pages, Google keeps finding them. Our guide to internal links explains how to keep them clean.
Conclusion: make the status code tell the truth
Soft 404 errors are Google’s way of saying your server and your page disagree. The fix is to make them agree: real errors send 404 or 410, moved content redirects to its true replacement, and pages you want in search carry enough substance to deserve a 200. Work through your flagged URLs by page type, decide deliberately for each group, then validate and monitor. Handled this way, soft 404 errors become a short, manageable clean-up rather than a recurring mystery.
Frequently asked questions
Do soft 404 errors hurt my whole website’s rankings?
Soft 404s mainly affect the flagged URLs, which are left out of Google’s index. They are not a penalty on the rest of the site. A large number of them can, however, waste crawling effort and point to wider quality or technical problems worth fixing.
How long does it take for Google to clear soft 404 errors?
After you fix the pages and click Validate fix in Search Console, validation commonly takes from several days to a few weeks, depending on how often Google crawls your site. Keep monitoring the Pages report rather than resubmitting repeatedly.
Should I use a 404 or a 410 for deleted pages?
Both tell Google the page is not available. A 410 signals more explicitly that the removal is permanent, but in practice either works for pages that are gone. Choose one approach and apply it consistently.
Can a page with content still be flagged as a soft 404?
Yes. If the main content area is very thin, shows an error-like message, or fails to render for Googlebot because of JavaScript or blocked resources, Google may still flag it. Use the URL Inspection live test to see what Google actually renders.
Sources and further reading
- Google Search Central: HTTP status codes, network and DNS errors
- Google Search Console Help: Page indexing report
- Google Search Central: JavaScript SEO basics
- Google Search Console Help: URL Inspection tool
- MDN Web Docs: HTTP response status codes
Related guides
- How to Fix 404 Errors and Use 301 Redirects Correctly
- How to Get Your Pages Indexed Faster by Google
- How To Do An SEO Audit: 9 Things To Check For
- E-commerce SEO Checklist: 26 Crucial Steps To Boost Google Rankings
- 23-Step SEO Migration Checklist For A Seamless Website Migration
Browse every article in our SEO guides.