Rendering

Soft 404 fix

Find and fix soft 404s, where a missing page returns status 200, which is common in single-page apps. Use when Search Console reports "Soft 404" or when unknown URLs show the home page or an empty page with status 200.

soft-404-fix/SKILL.md

Goal

Every URL that has no content returns status 404 or 410, or a correct redirect.

Facts to use

  • A soft 404 is a page that tells the user it does not exist but returns status 200, or a thin page that Google treats as missing.
  • In a single-page app the server often returns the app shell with 200 for every path. Google's JavaScript SEO guide gives two fixes when the server cannot return 404: redirect to a URL where the server returns 404, or add <meta name="robots" content="noindex"> with JavaScript on the error view.

Workflow

  1. Request three made-up URLs, for example /this-page-does-not-exist-123. Record the status code.
  2. Export the Soft 404 list from Search Console (Pages report) and Bing Webmaster Tools.
  3. For each URL decide:
    • The page moved: 301 redirect to the closest real page.
    • The page is gone: return 404 or 410.
    • The page is real but thin: add real content, or noindex it.
  4. Fix the host: configure the SPA fallback so known routes get the app and unknown routes get a 404 status. If the host cannot do this, use the noindex or redirect fix from Google's guide.
  5. Do not redirect every missing URL to the home page. Google can treat that as a soft 404 too.

Checks

  • Made-up URLs return 404.
  • Real routes still return 200.
  • Validate the fix in Search Console.

Output

A table: URL, old status, new status or redirect target, reason.

Sources

  • Google: Understand JavaScript SEO basics (soft 404 errors in single-page apps). https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics
See all 30 skills