Soft 404 Errors: How to Find, Diagnose and Fix Them

Soft 404 errors show up when a server answers with a 200 OK status, but the page itself tells visitors that nothing is there: an error message, an empty listing or a shell with no real content. Search Console reports them separately, and many site owners read that as a penalty. It is not. A soft 404 is a mismatch between what your server says and what your page shows.

This guide shows how to read soft 404 entries, handle the usual page types and decide between fixing and removing a page. If you are still working out why a URL is missing from Google at all, start with our step-by-step diagnosis of pages Google is not indexing.

What Soft 404 Errors Are and How They Differ from Real 404s

A real 404 is an honest answer: the server says at the HTTP level that the resource does not exist, and every client gets the same message. You can still show a friendly error page with search and navigation; code and content agree.

A soft 404 is a contradictory answer. The status code says "success", but the visible content says "not found", "no results" or effectively nothing at all. Google has to resolve that contradiction on its own, and when the content looks like an error, it treats the page as one.

It helps to keep three situations apart:

• Hard 404: status 404 (or 410), with or without a helpful custom error page. Code and content match.
• Soft 404: status 200, but the main content signals absence, failure or emptiness. Code and content conflict.
• Thin but legitimate page: status 200 and short content that still answers a real need. Not a soft 404, though it may deserve more work.

Each needs a different fix: hard 404s are often fine, soft 404s need real content or an honest status code, and thin pages need an editorial decision.

Why Google Classifies a Page as a Soft 404

Google does not take a 200 status at face value. Its documentation on how HTTP status codes and network errors affect Google Search (Opens in a new tab) notes that when content suggests an error, for example an empty page or an error message, Search Console will show it as a soft 404. The same page adds that a 2xx status code alone is not enough to get a page indexed.

Typical triggers:

• Phrases such as "not found", "unavailable" or "0 results" inside the main content area.
• Hundreds of URLs returning the same placeholder template with no distinguishing content.
• JavaScript that fails to load data, leaving only a skeleton layout.
• Removed content being sent to a page that has nothing to do with the original topic.

Read that last pattern carefully. Google's help page on 404 errors says that sending users to another page, such as the homepage, instead of returning a 404 can be problematic, and that these pages are known as soft 404s. That does not mean every redirect to the homepage is automatically classified this way, but the takeaway holds: if the target is not a genuine replacement, the redirect is not a fix.

Reading Soft 404 Entries in Search Console

In Search Console, soft 404s appear in the Page indexing report as one of the reasons pages are not indexed, under the name "Soft 404". The Page indexing report documentation (Opens in a new tab) describes it as a request that returns what Google thinks is a soft 404 response, and suggests two remedies: return a 404 for pages that are truly gone, or add enough information to show that the page is not a soft 404.

Read the report as patterns, not single URLs:

1. Export the example URLs and group them by path: /category/, /product/, /search/, /tag/, /profile/ and so on.
2. Inspect a few URLs from each group with the URL Inspection tool. Run a live test, then open the tested page and check the screenshot to see what Google actually rendered.
3. Check the raw server response separately.
4. Write down the shared cause for each group: sold out, emptied category, zero search results, rendering failure, thin template.
5. Assign one policy per pattern rather than one decision per URL.

The report shows examples, not necessarily every affected URL, so use your own crawler or a database query to find the rest. Fixing the template is cheaper than fixing URLs one at a time, and it stops the entries from coming back.

Empty Categories, Sold-Out Products and Internal Search Pages

On ecommerce sites and marketplaces, most soft 404s come from three page types, and each needs its own decision.

Out of stock product pages

If a product is temporarily unavailable, keep the page alive: a 200 status, a clear availability message, the full product details and a few relevant alternatives. If the product is discontinued and has a direct successor, such as a newer model, a permanent redirect makes sense. If there is no successor, a 404 or 410 is the honest answer. What causes trouble is leaving a discontinued product at a 200 URL that now just says "product not found".

Empty category pages

A category that is empty for a while can stay useful with a short description, links to subcategories and pointers to related ranges. A category that will never be restocked should be removed or folded into its closest parent. You will spot these long before Search Console does if you build them into a regular content audit routine that flags categories with no live products.

Internal search results

Site search can generate a new URL for every query, and a query with zero results is, by definition, an empty page. Many sites keep internal search results out of the index and avoid linking to empty result pages. When a search pattern shows steady demand, it is usually healthier to publish a curated category or guide for it than to let a search URL carry that traffic.

Thin Pages and Template-Heavy Copy

Soft 404s are not limited to pages that display an error. A page can be so light on its own content that it becomes indistinguishable from an error page. This tends to happen wherever the template dominates: tag archives with a single post, author or seller profiles with nothing filled in, location pages that only swap the city name, product variants without their own descriptions.

Padding the page to hit a word count is not the fix. As our piece on the ideal word count for SEO content argues, length is an outcome of covering a topic properly, not a target in itself. Ask these questions instead:

• What does this page offer that no other page on the site already covers?
• Which search intent brings someone here, and does the page satisfy it?
• Is the unique content clearly separable from the shared template?
• If the page type is generated automatically, is there a rule that stops empty versions from being published?

If the first two answers are "nothing" and "none", merge or remove the page instead of filling it.

Soft 404 Risk on JavaScript-Rendered Pages

Single page applications that handle routing on the client are especially prone to soft 404s. The server returns the same HTML shell with a 200 status for every path, whether the route exists or not, and JavaScript fills in the content afterwards. When the API reports that a record does not exist, the app displays a "not found" view, but the HTTP response has already gone out as a success.

Google's JavaScript SEO basics documentation describes two ways to avoid this: use JavaScript to redirect to a URL for which the server responds with a 404 (such as a dedicated /not-found path), or add a robots meta tag with noindex to error views using JavaScript.

A quieter failure mode is content that never renders: if a script is blocked or an API call times out, Google may only see the empty layout. The URL Inspection screenshot and rendered HTML tell the two cases apart. For a deeper look at how rendering works and where it commonly breaks, see our guide to JavaScript SEO, rendering and indexing. Where you can, render critical page types on the server and let the server return the 404 directly when a record is missing.

Choosing the Right Status Code: 200, 301, 404 or 410

Every soft 404 fix comes down to the same idea: make the status code match reality. You have four main options.

• 200 OK: the page offers real, useful content. If it is currently flagged, strengthen the main content and remove error wording from it.
• 301 Moved Permanently: the content moved, or there is a page that genuinely replaces it. The target has to satisfy the same need.
• 404 Not Found: the content was removed and there is no replacement. You can still serve a helpful custom error page with this status.
• 410 Gone: you want to state that the removal was deliberate and permanent.

The 404 vs 410 choice matters little. Google's help page on 404 errors (Opens in a new tab) states that Google currently treats 410s the same as 404s, and also that 404s do not harm a site's indexing or ranking.

The same page recommends returning a 404 or 410 when content has been permanently deleted with no replacement, and adding a redirect when content has moved. It also lists practices to avoid: creating fake content, redirecting to the homepage, and blocking 404s with robots.txt.

Fix the Page or Remove It: Decision Criteria

Not every soft 404 should end with a deletion. Score each group of URLs against these criteria first:

1. Search intent: would someone searching this topic actually want to land on this page?
2. Unique value: does the page answer something no other page on the site answers?
3. External signals: has the page attracted links from other sites or meaningful organic visits?
4. Cost to fix: can the page be made genuinely useful with a reasonable amount of work?
5. Durability: once fixed, will it stay useful, or will it empty out again?

Imagine a fictional outdoor gear retailer that opens new collection pages every season and archives the products when the season ends. Evergreen ranges like "ultralight tents" restock every year and are searched all year round, so they get a permanent category description, a block pointing to related ranges when stock is empty, and a restock notice. One-off collections tied to a specific season and year will never refill, so they are redirected to the closest evergreen category or, where no close match exists, allowed to return a 404.

For articles and guides that you decide to keep, the steps in our guide to refreshing and updating old blog posts make the rescue work repeatable.

Validating Fixes and Monitoring Afterwards

Shipping the fix is half the job; the other half is confirming that Google receives the new response:

1. Check the server response. Do removed pages really return 404 or 410? Do moved pages redirect in a single 301 step? Do rescued pages return 200 with full content?
2. Run a live test. Inspect sample URLs in Search Console and review the rendered screenshot.
3. Start validation. From the issue's details page in the Page indexing report, click "Validate fix". Search Console checks a sample of pages first, then re-evaluates the remaining affected URLs.
4. Clean up the sitemap. Remove URLs that now return 404 or 410, swap redirected URLs for their targets, and confirm the file is otherwise healthy with our XML sitemap audit and error fixes guide.
5. Update internal links. Make sure menus, filters and related product blocks no longer point to removed pages.

How long re-evaluation takes depends on how often Google crawls your site and how many URLs are involved, so do not plan around a fixed timeline. If validation fails, fix the URLs listed as still failing.

Publishing Rules That Prevent Soft 404s

Most soft 404s can be prevented with rules agreed before anything goes live, so that no empty or broken state leaves the server with a 200 status:

• The error template always ships with the correct status code; a "not found" view is never served as 200.
• Product lifecycle follows a written policy, with separate rules for temporary stockouts, permanent removal and products with a successor.
• New category, tag and profile pages go live only when they meet a minimum content threshold, or stay out of the index until they do.
• Empty internal search result pages are not linked from anywhere on the site and are kept out of the index.
• Client-rendered pages signal missing records explicitly, either through a server-side 404 or a noindex tag.
• Bulk removals and migrations map every URL to a specific destination; nothing is mass-redirected to an unrelated page.

These rules involve editors as much as developers: a category without a description or a profile with no information produces a thin page however good the template is.

Sample Template: Soft 404 Diagnosis and Decision Table

The sample template below helps you classify soft 404 URL groups by page type and record one decision per group. The rows are illustrative; adapt them to the page types your own site produces.

Add an owner and a target date to each row to track implementation.

Frequently Asked Questions

Do soft 404 errors directly hurt rankings?

No, a soft 404 is not a penalty. It means Google has judged a page to behave like a "not found" page, so that URL is generally not indexed and cannot rank. The real cost is that valuable pages can stay invisible because of a misleading signal, and crawling effort goes to empty pages.

Is an out-of-stock product page treated as a soft 404?

A page that clearly shows product details, stock status and alternatives is not usually treated as a soft 404. The problem starts when the page turns into a bare error message or loses its product information entirely. For permanently discontinued items, a 301 to a true successor or a 404/410 is the more honest response.

Is returning a 410 better than leaving a soft 404?

If the content is permanently gone, yes: a 404 or 410 is more accurate than a soft 404 because it states the situation plainly. According to Google's help documentation, Google currently treats a 410 the same as a 404. Applying one of them consistently matters more than which one you pick.

How soon is a page re-evaluated after a soft 404 fix?

There is no fixed timeframe. Re-evaluation depends on when Google recrawls the page and how often it crawls your site in general. Starting validation in Search Console and requesting indexing for a few key URLs makes it easier to track progress than waiting on a calendar.

Can an empty category page stay live with noindex?

Yes, if the category will refill soon and you do not want it showing in search in the meantime, noindex is a reasonable temporary measure. Avoid using it as a permanent parking spot, though. If the category is not coming back, a redirect or a 404 is a cleaner outcome.

Does redirecting soft 404 pages to the home page fix the problem?

Usually not. Google notes that sending users to another page such as the homepage instead of returning a 404 can be problematic, and calls these pages soft 404s. A redirect only makes sense when the target is a genuine replacement for the old content; otherwise return a 404 or 410.

Conclusion and Next Step

A soft 404 is Google's way of saying "this page appears to exist, but it has nothing to say". The fix is not always deletion or a redirect. Group the report by page type, check whether the server response reflects what is really on each page, then decide between rescue and removal using intent, unique value and durability.

For the category, product and guide pages you decide to rescue, the real work is producing original copy that genuinely helps the reader. If your team lacks the capacity for that, take a look at our content writing service, where you can brief writers on exactly the pages that need strengthening.