Fix it

Soft 404 in Search Console: what triggers it and how to fix it

A soft 404 is a mismatch between what your server says and what your page shows. The server answers success, the page reads like an error or an empty shell, and Google files it as not found. The fix depends on whether the page should exist.

By Adem ÇakalPublished 3 sources5 min read
Short answer

Google's report help says a soft 404 is a page that returns a friendly not-found message without a 404 response code. Fix it by deciding what the page should be. If it is gone, return 404 or 410. If it has a close replacement, redirect it. If it is a real page that looks empty, add substantive content so it no longer reads as an error.

What Google means

Two Google pages describe the same mechanism from different sides. The Page indexing report help gives the status as a user-friendly not found message served without a 404 code. The crawling documentation describes a server that returns a 2xx success code while the content suggests an error, and says Search Console then reports it as a soft 404. Neither page defines a threshold such as a word count, so there is no documented line between a thin page and an error page. Treat any claim of an exact cutoff with suspicion.

Common causes and the right response

Page typeWhy Google may call it soft 404Best response
Deleted product or post whose template shows "not found" with status 200The code says success, the text says errorReturn 404, or 410 if removal is deliberate
Deleted page with a close replacementSame mismatch301 to the replacement. Google's report help advises a 301 for moved pages
Empty tag, category or date archivePage lists nothingDelete the empty archive so it returns 404, or add content if it should exist
Internal search page with "no results"Looks like an error messageKeep these out of the index, and return 404 for empty result pages if your platform allows it
Very thin page: a heading and a sentenceLittle content to indexExpand with real information, or merge into a stronger page
Single-page app route for a missing itemClient-side routing returns 200 for everythingRedirect in JavaScript to a URL that returns 404, or add a noindex tag, per Google's guide
Page that failed to load data and shows an error textRendered result reads as an errorFix the failing script or API call. Test the rendered page, not only the source

Rows about empty archives and search pages are our reading of the mechanism, since Google's pages give no list of causes. Check each against your own URLs.

How the response should line up

Soft 404 is a 200 status with error content. The fixes are a 404 or 410 status, a 301 redirect, or real content on a 200 Soft 404Status: 200Page: "nothing here"code and content disagree Gone for good: 404 or 410 Has a replacement: 301 to it Should exist: real content on a 200
Each fix makes the status code and the page content agree.

Find the real status

A browser shows the page, not the code. Run the URL through the noindex checker to see the status code, redirects, noindex and canonical in one view, or use a terminal:

curl -sI https://example.com/old-product/ | head -1
# HTTP/2 200   <- success code on a "not found" page: soft 404

For JavaScript sites, also open the live test in URL Inspection and look at the rendered HTML, because the error text may only appear after scripts run.

After the change

  1. Remove 404ed and 410ed URLs from your sitemap and from internal links.
  2. For pages you kept, confirm they are not caught in crawled, currently not indexed, which often follows thin content.
  3. Use the validation action in the report once the fixes are live.

Google's crawling documentation says newly encountered 404 pages are not processed, that crawl frequency gradually decreases, and that indexed URLs returning these codes are removed. If you only want a page out of results, see how to remove a page from Google.

Deciding between the three fixes

Ask what a visitor who lands on the URL should get. If the honest answer is nothing, return 404 or 410. If there is a nearby page that answers the same need, redirect to it, and avoid sending everything to the homepage, which can itself look like an error to a crawler. If the visitor should get something useful but the page is empty, fill it with real content or stop publishing the URL.

A 404 is not a failure. Google's own report help says 404 responses are not necessarily a problem when a page was removed without replacement. Fix the soft 404 label, not the existence of missing pages.

Questions people ask

Does a soft 404 hurt the rest of my site?

Google's pages we read describe the status and its fix but give no site-wide penalty for it. The practical effect is that the affected URL is not indexed. If the page was valuable, that is the loss to fix.

Should I use noindex on soft 404 pages?

Only for error pages you cannot make return a 404 code. Google's JavaScript guide offers noindex as one of two options for single-page apps, the other being a redirect to a URL that returns a real 404.

Is 410 better than 404?

Google's crawling documentation groups 404 and 410 with the other 4xx codes and says they are treated the same, apart from 429. Choose by what is accurate: 410 says the page is gone on purpose.

I fixed it, why is the report still full?

The report reflects past crawls. Use the validation option in the report, or inspect a URL live, and expect to wait. Google gives no fixed timeline.

Sources

  1. Search Console Help: Page indexing report, accessed 2026-11-12.
  2. Google Search Central: HTTP status codes, network and DNS errors, accessed 2026-11-12.
  3. Google Search Central: JavaScript SEO basics, accessed 2026-11-12.