IndexVerdict
Content & responses

Soft 404

Google thinks the page behaves like a missing or empty page, even though the server may report success. Check what a visitor actually receives, not only the status code.

Troubleshooting guide · Public signals and practical next steps

What this means

A soft 404 is Google’s assessment of an error-like page rather than a literal HTTP 404 status. A public technical checker cannot reproduce that judgment.

When it’s normal—and when to investigate

Often expected

Removing a page can be intentional, but its response should accurately signal removal. A genuine 404 for a deleted page without a replacement is usually appropriate.

Worth investigating

Act if a real product, article, or service page is classified as missing, or if your error template returns HTTP 200 for URLs that do not exist.

Work through these checks

  1. Check the HTTP response and the body together

    Look for “not found,” empty results, a generic error message, or an incomplete layout inside an apparently successful response. Check a known nonexistent URL in your application too.

  2. Compare server HTML with rendered content

    If a script must fetch all useful content, investigate failed API calls or blocked resources. Use URL Inspection’s rendered view to see evidence that this checker cannot provide.

  3. Decide whether the content still exists

    An unavailable product is not automatically a deleted page. Useful product details and alternatives may still help visitors; an empty “unavailable” screen may not.

  4. Review redirects for removed pages

    Sending every deleted URL to an unrelated homepage can obscure whether a replacement exists. Choose a destination that actually fulfills the old page’s purpose.

FREE URL DIAGNOSTICOne page. Public signals.

Use a public HTTP or HTTPS URL. No login needed. Don’t submit private links or URLs containing access tokens.

HTTP & redirectsCrawl & index controlsCanonical & content

Common causes

  • An error template returns 200 instead of 404.
  • A failed API leaves an otherwise successful page empty.
  • A page contains only a missing-content message.
  • Removed pages redirect to an irrelevant destination.

Possible fixes

  • Return 404 or 410 for truly removed content with no suitable replacement.
  • Restore meaningful content on a page that should remain available.
  • Repair data loading and ensure essential content is reliably served.
  • Use a relevant redirect only when there is a genuine replacement.

Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.

What this tool can and cannot verify

It can

Report HTTP status, raw text quantity, and signs of a very thin JavaScript shell that may help you investigate.

It cannot

Declare that a URL is a soft 404, evaluate the rendered user experience, or reverse Google’s classification.

Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.

A useful follow-up

Is every short page a soft 404?

No. Brevity is not a missing-page signal by itself. The page’s purpose, content, and behavior matter; this checker’s text count is only a prompt for review.

Official reference: Google: HTTP status and network errors. See also the Page indexing report documentation.