Skip to content

Soft 404s: pages that say 'not found' but do not act like it

Up to date as of 16 November 2026

A soft 404 is a page that tells visitors "this doesn't exist" while telling the browser everything is fine1. The words and the behind-the-scenes code don't match, and search engines notice.

How a soft 404 looks to a search engineA page says 'not found' to the visitorThe server sends a success codeThe search engine sees a mismatchIt flags the page as a soft 404
The message and the code disagree.

What's a status code, and why does it matter here?

Every page the server sends comes with a three-digit status code the visitor never sees. A code of 200 means success1. A real "not found" page should send a not found code instead.

A soft 404 error is a URL that returns a page saying the page doesn't exist, and also returns a 200 (success) status code1. Some sites report "not found" this way by mistake, which Wikipedia calls a soft 4042.

Why did Search Console flag my page?

Google's report uses the label when it decides a page looks like an error page, based on what's on it. Google describes it as a page that returns a user-friendly "not found" message but not a 404 HTTP response code3.

The page doesn't have to say "not found" in so many words. It might be nearly empty. Examples Google gives include an empty internal search result page and an unloaded or otherwise missing JavaScript file1.

It's a bad user experience to return a 200 (success) status code but then show an error on the page, and these pages are excluded from Search1. So the label can cost you real visibility.

What are the common ways it happens?

  • A custom error page set up wrongly. Custom 404 pages must return a 404 status code, or they may be seen as soft 404s1.
  • Missing pages sent to the home page. Sending them to the domain root or home page instead of showing an error can give a "soft 3XX" version of the same fault2.
  • Thin or empty pages. A page with no main content may be treated as an error1.
  • Search results with nothing in them. An empty internal search result page is a Google example1.
  • A good page that didn't load properly. If an otherwise good page is flagged, Google says it may not have loaded for Googlebot, or may have shown a prominent error message1.

How do I fix it?

The fix depends on the page. Work out which of these fits.

  1. The page is gone and nothing replaces it. Return a 404 (not found) or 410 (gone) response code1. A separate page sets out when each one fits.
  2. The page moved. If it moved or has a clear replacement, return a 301 (permanent redirect) to the new address1.
  3. The page still exists and is fine. Check why Google saw it as empty. Run a live URL inspection test against the page3. Then look at the rendered screenshot and the returned code.

The page looks the same to a visitor either way, so you need a tool that shows the status code. The Search Console URL Inspection tool can verify the code a URL returns1. A status checker works too.

Should every error page return 404, then?

Yes, with one detail. Google advises returning a 404 response code for truly "not found" pages3. Your custom "page not found" page can look as friendly as you like. It just has to send the 404 code with it. See what a helpful custom 404 page includes.

Automatic link checkers can miss these too, as that page on link-checking tools explains. If you're new to codes, start with the basics of a not found error, which also covers the status code idea2.

Reference list

  1. Troubleshoot Google Search Crawling Errors (soft 404 errors), Google Search Central
  2. HTTP 404, Wikipedia
  3. Page indexing report, Google Search Console Help