Soft 404 Error: What It Means in Search Console and How to Fix It

A soft 404 error is a mismatch between what the server says and what the page shows. The server answers "everything is fine", the visitor and Googlebot see nothing useful. The term dates back to a 2004 research paper by Ziv Bar-Yossef and colleagues, as the Wikipedia article on HTTP 404 recalls, and Google has been detecting these pages automatically for years. This guide explains how Google decides a page is a soft 404, the causes behind each case, how to diagnose a flagged URL in a few minutes and which fix to apply.

What is a soft 404 error?

Every HTTP response carries a status code. A real missing page returns 404 (not found) or 410 (gone): the browser shows an error page and search engines know the URL has nothing to index. A soft 404 returns 200 (success) instead, so the server claims the page exists, while the content says the opposite.

Google's documentation on troubleshooting crawling errors defines it as a URL "that returns a page telling the user that the page does not exist and also a 200 (success) status code", and adds that "in some cases, it might be a page with no main content or empty page." When its algorithms detect that a page is an error page based on its content, Search Console shows a soft 404 and the page is excluded from Search.

Two points follow from that definition:

• The verdict is based on content. Google reads the rendered page. A valid product page that fails to load its main content can be flagged the same way as a deliberate "no results" page.
• It is an indexing exclusion, not a penalty. The flagged URL stays out of the index; the rest of the site is not demoted because of it.

Soft 404 vs 404: what is the difference?

The two look identical to a visitor and behave very differently for a crawler.

A clean 404 is a healthy answer. Google's guide to managing crawl budget calls a 404 "a strong signal not to crawl that URL again" and states that "soft 404 pages will continue to be crawled, and waste your budget." On a small site the waste is marginal; on a store with thousands of empty filter pages it delays the crawl of pages that matter (see our glossary entry on crawl budget).

What causes soft 404 errors?

Google lists four technical causes: a missing server-side include file, a broken database connection, an empty internal search result page and an unloaded or missing JavaScript file. In audits, the flagged URLs fall into six families.

1. Deleted content served with a 200

The CMS or the theme displays a "Page not found" template but keeps the 200 status code. This happens with some custom 404 setups, catch-all routes and frameworks that render a generic error component without setting the status.

2. Empty listings

Category pages with zero products, tag archives with no posts, internal search pages with "0 results" and filter combinations that match nothing. The template loads, the main content area is empty, Google sees an error page. Our guide to ecommerce category page SEO covers how to keep listings worth indexing.

3. Out-of-stock and expired pages

Product pages that switch to "This product is no longer available" with no price, no description and no alternatives, or job and event pages reduced to "This offer has expired". The wording alone is enough for Google to treat them as missing.

4. Redirects to an irrelevant page

Sending every removed URL to the homepage, or to a generic category, looks like a convenient cleanup. Google tends to treat a redirect to a page that does not replace the original as a soft 404, so the redirect passes nothing and the old URL is reported anyway. Our guide to SEO redirects explains when a 301 is legitimate.

5. Thin pages

Pages with a header, a footer and two lines of text, placeholder pages ("Coming soon"), or very short profiles generated in bulk. Google does not always distinguish a nearly empty page from an error page. If this is your case, read our definition of thin content.

6. Rendering failures

A good page can be flagged when Googlebot does not see its content. Google's guide says such a page "didn't load properly for Googlebot, it was missing critical resources, or it displayed a prominent error message during rendering." Typical reasons: JavaScript or CSS blocked by robots.txt, API calls that fail or time out for the crawler, too many or too heavy resources, and client-side apps that render an error component on unknown routes. Our guide to JavaScript SEO details how Google renders scripts.

How to find soft 404 errors

Three sources, from the most official to the most exhaustive.

1. Search Console. Open Indexing, then Pages, and look under "Why pages aren't indexed" for the "Soft 404" reason. Click it to see example URLs (up to 1,000) and the date of the last crawl. Google's Page indexing report documentation recommends returning a 404 response code for truly "not found" pages.
2. A crawl of your own site. Crawlers such as Screaming Frog can flag pages with a 200 status and very little content, or containing "not found" text. Sort by word count and look at the shortest pages first.
3. A test of the 404 handling. Request a URL that cannot exist (for example /this-page-does-not-exist-123) and read the status code it returns. If it answers 200, every broken link on the web pointing to your domain creates a potential soft 404. Our free HTTP headers checker shows the exact code in seconds.

How to fix a soft 404, case by case

Google's guide sorts fixes by the state of the page. Decide first what you want the URL to become, then apply the matching answer.

Content removed: 404 or 410

If the page is gone and nothing on the site replaces it, a 404 or 410 is the correct answer. Google treats all 4xx codes except 429 the same way and removes the URL from the index if it was there. Keep the error page useful for visitors: clear message, site navigation, links to popular pages, but always with the 404 status code.

Content moved: a relevant 301

If an equivalent page exists (new URL, newer model of the product, merged article), use a 301 to that page and nowhere else. Check the chain with our redirect checker: one hop, final status 200.

Page should be indexed: repair it

Use the URL Inspection tool in Search Console, run a live test and look at the screenshot and the rendered HTML. A blank or nearly blank render points to blocked or failing resources. For a client-side app, Google's JavaScript SEO basics recommend either a JavaScript redirect to a URL that returns a 404, or adding a noindex robots meta tag to error routes; our guide to single-page application SEO covers server rendering, the lasting fix. Once the page renders correctly, our indexability checker confirms nothing else blocks it.

Out-of-stock products

A product coming back soon should stay live with its full description, an availability notice and alternatives. A product discontinued for good gets a 301 to its successor or closest category if one fits the need, or a 404 if nothing does. For empty listings you want to keep reachable, a noindex tag keeps them out of the index without breaking navigation.

How long does it take for soft 404s to clear?

Nothing changes until Google recrawls the URLs. After a fix, start a validation from the Soft 404 detail page: according to Google's help center, it typically takes up to about two weeks and sometimes much longer. URLs switched to a real 404 move to the "Not found (404)" reason and then drop out of the report over time; repaired pages can move to "Indexed" or, if Google still judges them weak, to Crawled, currently not indexed. For the levers that speed up recrawling, see our guide to Google indexing.

Soft 404s, SEO and GEO: why AI visibility depends on clean status codes

For Google, a soft 404 means a page that cannot rank and a crawl budget spent on nothing. For AI assistants such as ChatGPT, Gemini or Perplexity, the stakes are similar: their crawlers read what your server returns, and many fetch the raw HTML without running JavaScript. A page that renders only in the browser can look empty to them, and an error page served with a 200 tells them nothing reliable about your site. Clean status codes and content present in the initial HTML help both Googlebot and AI crawlers understand which pages exist and which can be cited.

The practical routine is short: watch the Page indexing report after every migration, catalogue update or template change, and test new templates before release. The free Sorank Chrome extension flags on-page problems on the page you are viewing, and the Sorank GEO and SEO dashboard follows clicks, impressions and positions from Search Console so you spot a drop as soon as a batch of pages leaves the index.

A soft 404 is a page whose status code contradicts its content: decide whether the URL should exist, then make the server and the page say the same thing. Return a real 404 or 410 for what is gone, a relevant 301 for what moved, and real, renderable content for what should rank.