Soft 404 error: diagnose the cause and choose the right fix

    A soft 404 error is a page that reports HTTP success but Google interprets as missing or broken. To fix it, first determine whether the resource has disappeared, has a relevant replacement or no longer loads its main content. The right action may be a genuine 404 response, a redirect or a rendering repair. Deleting every reported URL would be the wrong approach.

    Franck Gordi, SEO and GEO consultant

    Franck Gordi

    · 9 min read

    Contact me
    Soft 404 error

    HTTP response

    Rendered content

    Appropriate fix

    Key takeaways

    • A soft 404 combines a successful HTTP response with content that Google interprets as missing, empty or an error.
    • A deleted page without a relevant replacement should return 404 or 410, even when it displays a custom error page.
    • A useful page classified as a soft 404 needs a rendered-content check, not automatic deletion or a new error status.
    • A 301 redirect suits a relevant replacement, not a blanket rule sending every missing URL to the homepage.
    • Search Console lets you compare the indexing diagnosis with a live test and a screenshot of the rendered page.

    What is a soft 404 error, and how is it different from a 404?

    A soft 404 is Google’s diagnosis, not an HTTP response code. The server reports success, usually with a 200 status, but the content looks missing, empty or broken. A genuine 404 instead reports that the resource is missing through the HTTP response itself.

    Google’s HTTP status documentation separates these two layers: a 2xx response allows content to be processed, but does not guarantee indexing. If that content suggests an error, Search Console may report a soft 404. A prominent “Page not found” heading therefore does not fix a 200 response.

    The reverse matters just as much. An existing page may look empty to Google because its content fails to load. In that case, restore access to the content. Turning the page into a 404 would remove a resource you intended to keep.

    Compare three layers before making a change

    HTTP response
    Does the server return 200, 404, a redirect or a server error?
    Rendered content
    Does Google see the main content, an error message or only the template?
    Page purpose
    Does the resource still exist, and should it remain accessible?
    Decision
    Choose the fix after comparing these layers, never from the Search Console label alone.
    Diagnostic framework based on Google’s documented distinctions, with no claimed performance measurements.

    Does a soft 404 prevent indexing?

    Search Console’s Page indexing report lists URLs classified as soft 404 under pages that are not indexed. For a deleted page, absence from search is the expected outcome. For a useful page, the problem is that Google did not receive or recognise the intended content.

    This diagnosis is not a site-wide penalty. Do not confuse it with “Crawled, currently not indexed” either: the labels describe different situations. Google’s report documentation explains each reason separately.

    Priority depends on the URL’s purpose. An active service page needs prompt investigation. An old URL removed without an equivalent needs the right status and removal of internal links that still present it as available. The alert count alone does not determine the importance of the work.

    What causes a soft 404 error?

    A missing page served with a 200 status

    The error template displays a clear message, but the server or hosting returns the same successful response used for existing pages. The design can be helpful and provide useful navigation, but it still needs a genuine 404 response when the resource does not exist.

    Main content missing after rendering

    The navigation and footer load, but the product details, article or central content do not. An inaccessible JavaScript resource or a failed data request is worth investigating. Google recommends checking rendered HTML, errors and loaded resources in its JavaScript troubleshooting documentation.

    This connects with JavaScript SEO, but the intention here is narrower: explain why this URL reports success without delivering the intended content. The cited sources do not specify a minimum word count that prevents a soft 404.

    A redirect that does not genuinely replace the page

    Redirecting an old page to the homepage does not recreate its content. In its soft 404 explanation, Google recommends redirecting to a more appropriate URL when one exists and returning an error when the page has genuinely disappeared. Check the relevance of each destination individually.

    Should you repair the page, redirect it or return 404?

    First decide whether the resource still exists and whether a replacement genuinely meets the same need. The status should communicate that decision, not conceal it.

    Match the fix to the resource’s actual state

    Existing page
    Keep 200 and restore accessible, correctly rendered main content.
    Moved page
    Permanently redirect to a relevant replacement, then check the destination.
    Deleted page
    Return 404 or 410 when no relevant replacement exists.
    Temporary outage
    Restore service and use an appropriate server-error status instead of an empty page reporting 200.
    Operational standard based on Google’s guidance about HTTP responses and missing pages.

    Google treats 404 and 410 responses like other 4xx errors, except 429, for indexing. The cited sources therefore do not justify promising faster removal with 410. A 5xx error works differently: Google temporarily slows crawling and may eventually remove URLs if the error persists.

    For moved pages, use the mapping process described in the SEO migration article. For pages you retain, check useful content rather than adding filler in an attempt to change the classification.

    How do you diagnose a soft 404 in Search Console?

    Compare what Search Console observed during indexing with what Google can receive now. A live test does not replace the historical report: a recent repair may not yet appear in the indexing data.

    • Open the “Soft 404” reason in the Page indexing report and choose a representative URL from each affected template.
    • Inspect the URL and note the last crawl date to put the diagnosis in context.
    • Run the live test, then view the tested page to compare the screenshot and rendered HTML with the expected content.
    • Check the HTTP status separately, including the final destination when the URL redirects.
    • If content is missing, investigate blocked resources, JavaScript errors and data loading.
    • After the repair, repeat the test and use the report’s fix-validation action when it is available.

    To understand when Googlebot received a particular response, SEO log file analysis complements inspection. Logs show requests and statuses, but do not by themselves prove that Google rendered and indexed the page correctly.

    Which apparent fixes leave the problem unresolved?

    Blocking crawling repairs neither the status nor the content. A robots.txt rule may prevent Google from seeing the fix. A noindex directive asks for a page not to be indexed; it does not turn a 200 response into a 404.

    A canonical tag consolidates equivalent versions, rather than replacing missing content. Redirecting every error to the homepage or adding generic paragraphs treats the symptom, not the actual state of the resource.

    The pre-release check comes down to three questions: is the status appropriate, is the main content available, and do internal links still point to valid pages? If the error affects several templates, an SEO audit can define the inventory and correction priorities, without promising an indexing deadline.

    Frequently asked questions about soft 404 errors

    What is a soft 404 error?

    A soft 404 is a page that returns a successful HTTP response while Google interprets its content as missing, empty or an error. It is not a separate HTTP status code.

    Source: Google documentation

    What is the difference between a soft 404 and a 404?

    A genuine 404 reports a missing resource in the HTTP response. A soft 404 reports success, but the content suggests to Google that the page is missing or broken.

    Source: Google documentation

    Should you redirect a soft 404 to the homepage?

    Not as a blanket rule. Redirect to a relevant replacement page when one exists. Without an appropriate replacement, a deleted page should return 404 or 410.

    Source: Google documentation

    Can an existing page be classified as a soft 404?

    Yes. Empty content or an error message served with a successful response can produce this diagnosis. Check rendered content and JavaScript resources before deleting a useful page.

    Source: Google documentation

    How do you check what Google sees?

    Run the live URL Inspection test in Search Console, then view the tested page. Compare its screenshot and rendered HTML with the content the page should display.

    Source: Google documentation

    Is 410 better than 404 for Google?

    Google treats 4xx errors, except 429, the same way for indexing. Both codes indicate an unavailable resource; choose the code according to its meaning without promising a removal deadline.

    Source: Google documentation

    Sources and scope

    Documentation reviewed on October 30, 2026. The frameworks are an operational standard drawn from Google’s sources, with no client case or measured outcome.