Comprobador de soft 404: prueba tu página 404

You fixed internal links, submitted the sitemap, and Search Console still shows URLs that should not exist. Sometimes the problem is not the link — it is what your server returns when a URL is missing. A proper 404 or 410 tells crawlers the page is gone. A soft 404 looks like an error to humans or algorithms but sends the wrong HTTP signal — usually 200 OK with thin "not found" copy, or a redirect to the home page . Google's crawling documentation groups these under HTTP status and network issues and describes soft 404s as pages that return success codes while behaving like errors. You can monitor indexing reasons in Search Console ; this guide focuses on server behaviour you control. The Soft 404 Checker fetches your URL and one random missing path on the same origin, then compares status codes, redirects, titles, and visible text. It is a heuristic, one-sample test — not a copy of Google's Page indexing report. ! Three steps: fetch two URLs, compare status and content, output verdict and fixes What a real 404 and 410 look like 404 Not Found means the server has no representation for that URL right now. 410 Gone means the resource was removed intentionally and is not expected to return. Both are valid ways to drop dead URLs from crawl queues when used consistently. A good missing-URL response: Expected shape: The body can be a helpful HTML page with navigation — the critical part is the status line , not the design. What a soft 404 looks like in practice Common patterns: Error template with HTTP 200 — Title says "Page not found" but the status is 200. Redirect missing URLs to / — Users land on the homepage; crawlers may treat it as a soft 404.…