Detect and remediate soft-404 pages that return HTTP 200 but contain no meaningful content
domain: google-search-console · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Open the Page Indexing report in Search Console and filter for the Soft 404 reason to get the list of affected URLs
For each soft-404 URL, determine the root cause: expired product pages rendering empty templates, search result pages with no results, or deleted content pages returning boilerplate
For permanently removed content with no replacement, return a proper 404 or 410 HTTP status code so Google stops crawling and eventually deindexes the URL
For content that has moved, implement a 301 redirect to the appropriate replacement page rather than showing a thin 200-response page
For temporarily unavailable content, return a 503 with a Retry-After header to signal temporary unavailability without triggering deindexing
Known gotchas
Soft-404 pages consume crawl budget even though they return 200 OK, because Googlebot must recrawl them periodically to check if content has been restored; each uncorrected soft-404 represents ongoing crawl waste
Google's soft-404 detection is device-specific; a page may be classified as a soft-404 on mobile but not on desktop if the mobile template renders less content than the desktop template, creating asymmetric coverage issues
Returning 410 Gone is preferable to 404 Not Found for permanently deleted pages because it signals intentional removal; Google processes both similarly, but 410 communicates intent more clearly and may result in faster deindexing
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?