Lorixen.
EN

Soft 404s in Search Console: what they are and how to fix them

Short answer: A soft 404 is a page that tells visitors it doesn't exist, or shows almost nothing, while your server still answers "200 OK". Google treats it as an error page and leaves it out of Search. The fix depends on what the page should be: if it's gone, return a real 404 or 410; if it has moved, 301-redirect it to the replacement; and if it's a real page, make sure it loads properly for Googlebot and has genuine content. Then use Validate fix in Search Console.

A soft 404 warning isn't a penalty. It's Google telling you that the status code your server sends and the content on the page disagree. The trick is working out which of the two is wrong.

What Google means by "soft 404"

Google's crawling troubleshooting guide defines a soft 404 as a URL that returns a page telling the user the page doesn't exist, together with a 200 (success) status code; it can also be a page with no main content or an empty page. Examples it gives include a missing server-side include, a broken database connection, an empty internal search results page and a JavaScript file that didn't load. When Google's systems decide from the content that a page is really an error page, Search Console shows it as a soft 404 in the Page indexing report, and the page is excluded from Search.

Google's page on HTTP status codes adds that a 2xx response doesn't guarantee indexing, and if the content suggests an error, an empty page or an error message, Search Console reports a soft 404.

Cause and fix at a glance

What you find on the flagged URL Likely cause Fix
A friendly "page not found" message The CMS shows an error template but sends 200 Make the server send 404 (or 410) with that template
A category or tag page with no items Empty archive pages still exist Add content, merge the category, or remove it and return 404
"No results" from on-site search Internal search pages are crawlable Keep search result pages out of crawling and indexing
"This product is no longer available" and little else A discontinued product kept live with no useful content 301 to a direct replacement, or return 404/410 if there isn't one
A blank or half-loaded page when inspected Scripts, images or styles fail to load for Googlebot Fix blocked or failing resources; check the rendered page
An old URL that redirects to the home page A blanket redirect for removed pages Redirect only to a real equivalent; otherwise return 404
A page that looks fine to you Intermittent database or server errors Check server logs and hosting around crawl times

How to fix each case

The page is gone

If you've removed a page and there's nothing similar on the site, Google's guidance is to return 404 (not found) or 410 (gone). MDN's 410 reference describes 410 as meaning the resource is no longer available and probably won't be again; if you don't know whether the removal is permanent, use 404. In practice, either keeps the page out of search.

You can still show a helpful custom 404 page with your navigation, popular links and a search box. Google's point is only that the server must send the 404 status alongside it.

The page has moved

If there's a clear replacement, use a 301 (permanent) redirect to it. Google suggests checking the result with the URL Inspection tool. What doesn't work well is sending every old URL to the home page: a visitor looking for a specific service lands somewhere unrelated, which is the same mismatch that triggers the warning in the first place.

The page is real and should be indexed

Google says that if a good page was flagged, it probably didn't load properly for Googlebot, was missing critical resources, or showed a prominent error message during rendering. Common reasons include resources blocked by robots.txt, too many resources, server errors, and slow or very large files.

Steps:

  1. Run a live URL inspection in Search Console and click View tested page to see the screenshot and returned HTTP code, as the Page indexing report help suggests.
  2. If the render is blank or nearly blank, check whether scripts or stylesheets are blocked or failing.
  3. If the page is thin (say, a location page with just an address), add genuine content: services, hours, photos, a short description.
  4. For shops, make sure a temporarily out-of-stock product still shows the product details, rather than replacing the whole page with "not available".

Fixing at the source

Soft 404s on small sites usually come from a template or setting, not from individual pages. Look for:

  • Your CMS's "not found" behaviour. Some themes and page builders show a custom error page with a 200 status. Check with any HTTP header checker or your browser's developer tools (Network tab, status column).
  • Auto-generated archives. Tag, author and date archives can create many near-empty pages. Turn off the ones you don't use.
  • Search and filter URLs. Keep internal search results out of the index.
  • Redirect plugins. Check rules that send all missing pages to the home page.
  • Hosting reliability. If flagged pages work for you, look for intermittent errors in the server logs.

Validating the fix

Once every affected URL is fixed:

  1. Open the Page indexing report and click the Soft 404 issue.
  2. Click Validate fix, once. The help page warns not to click it again until validation has succeeded or failed.
  3. Watch the progress. Google says validation typically takes up to about two weeks, sometimes much longer, and you'll get a notification when it succeeds or fails.
  4. If it fails, open the details, find the URL that failed, fix it, check the other pending URLs, and restart validation.

Pages you've deliberately turned into real 404s will move to the "Not found (404)" category. That's expected and fine.

FAQ

Do soft 404s hurt my whole site's rankings?

Google describes them as pages excluded from Search, not as a site-wide penalty. They matter when the flagged pages are ones you want found.

Should I use 404 or 410?

Either removes the page from search. Use 410 when you're sure the page is permanently gone; use 404 when you're not.

Why is a working page flagged?

Usually because Googlebot saw something different: a failed script, a blocked resource, or an error at crawl time. The live URL inspection screenshot shows what it saw.

How long until the warning clears?

After you fix and validate, Google rechecks the URLs; its help page says validation typically takes up to about two weeks.

When the Page indexing report keeps filling with warnings you can't trace to a cause, we can find the template or setting behind them.

Sources

WhatsAppLet’s talk