Soft 404 Checker
Check one public URL for soft 404 risk: 200 pages that behave like errors, deep paths that collapse to the homepage, pages with almost no primary content, and JavaScript-rendered error states. This is not a site-wide scanner. It is a page-level diagnostic you can verify.
Check one URL
Check one URL
Enter a public page URL. The checker fetches the live response, reads the title, H1, canonical, and robots directives, and flags the most common soft 404 patterns.
Start with the direct question: what is a soft 404?
What does this check answer?
A soft 404 is not just an ugly page. It is a mismatch where HTTP says success, but the page says missing, removed, empty, or unavailable. Google recommends returning a real 404 for truly missing URLs. If the template loads but the primary content fails, the problem is usually rendering, routing, or data logic instead.
Google Search Central: Farewell to soft 404s
Google explicitly recommends a real 404 for missing URLs instead of a 200 page that only looks like an error state.
Google: Fix Search-related JavaScript problems
Google lists client-side errors, empty states, and wrong status handling as JavaScript patterns that can trigger soft 404 classification.
Check result
Direct answer
The result shows the HTTP status, final URL, title and H1, primary-content depth, matched error phrases, and the next fix path to validate first.
Waiting for a check
The result shows the HTTP status, final URL, title and H1, primary-content depth, matched error phrases, and the next fix path to validate first.
What does this check answer?
It focuses on four high-value signals
If Page indexing or URL Inspection shows soft 404, this page helps you separate the live evidence: wrong status handling, homepage fallbacks, empty content, or rendered pages that never produce meaningful primary content.
200 that behaves like an error page
The URL returns success, but the title, H1, or main content clearly says the page is missing, removed, empty, or unavailable.
Deep paths pushed back to the homepage
Old product URLs, filters, or deleted paths that all resolve to the homepage are a common soft 404 pattern.
Templates load but the main content is too thin
Navigation, footer, and design load, yet the `main` area contains only a tiny amount of text, a no-results shell, or a placeholder.
JavaScript shell pages
If users or Google only get an empty app shell, error component, or loading state, Google’s own guidance treats that as a soft 404 risk.
Four common decisions
How to fix what you find
The page is truly gone
If there is no replacement, return 404. If the removal is permanent, 410 is also valid. A branded error template is fine, but the HTTP status cannot stay as a fake 200.
Read Google’s soft 404 guidanceAn old URL has a clear replacement
A 301 only makes sense when the old page maps closely to a new one. Sending every dead URL back to the homepage usually creates more soft 404 signals, not fewer.
Continue with the canonical checkerThe page should exist but the content is too thin
The problem may be rendering, templates, or missing data instead of the status code itself. Check the rendered page, main-text depth, component failures, and Search Console Live Test.
Use Bot Simulator for rendering checksSearch Console already shows soft 404
This tool gives live page evidence, not Google’s final classification. After the fix, re-check representative URLs in URL Inspection and then watch whether the same page type drops together.
Open the URL Inspection docsReproducible commands
If you need to align with engineering or operations, these two commands are usually enough to confirm the HTTP outcome and the rendered page state.
curl -I -L
curl -I -L https://fennecseo.app/definitely-missing-soft404-check-sample/curl -L
curl -L https://fennecseo.app/blog/openclaw-seo-automation/ | sed -n '1,120p'Examples last verified on July 27, 2026
Verification order after the fix
Verification order after the fix
- Check one affected URL and one healthy peer page so you can separate a page-level failure from a site-wide template pattern.
- Run `curl -I -L` on the suspicious URL to confirm the final HTTP status, final URL, and whether the request quietly lands on the homepage.
- If the page depends on JavaScript, use Bot Simulator or Search Console Live Test to confirm the rendered main content is not empty.
- After the fix, re-check representative URLs in Search Console URL Inspection and then monitor whether the same page type leaves the soft 404 bucket.
| Scenario | Primary fix | What to watch |
|---|---|---|
| The URL is truly missing | 404 | A helpful error template is fine. The important part is the correct status plus removing stale sitemap entries or internal links. |
| The content is permanently removed | 410 | Useful for intentionally retired products, event pages, or inventory that will not return. |
| The old page moved to a closely related new page | 301 to the new URL | Do not funnel large groups of unrelated dead URLs back to the homepage or a category root. |
| The page should exist but behaves like an empty template | Fix rendering or expand the primary content | Check failed data loading, client-only rendering, empty-result templates, login walls, and broken components first. |
Primary sources
Primary sources
Google Search Central: Farewell to soft 404s
Google explicitly recommends a real 404 for missing URLs instead of a 200 page that only looks like an error state.
Google: Fix Search-related JavaScript problems
Google lists client-side errors, empty states, and wrong status handling as JavaScript patterns that can trigger soft 404 classification.
Search Console: URL Inspection tool
After the fix, use URL Inspection on representative URLs and then verify whether the same page type drops out of soft 404 in Page indexing.
Limits and failure modes
Next tools and articles
- This is a page-level checker, not a site-wide crawler. It shows which soft 404 signals one live URL exposes right now.
- It does not replace Search Console’s final classification. Google still evaluates historical crawling, rendering, and repeated page-type patterns.
- Login-gated, geo-personalized, captcha-protected, or browser-state-dependent pages may look different here than they do to Google.
- If the page already returns 404 or 410, it is not a soft 404 problem. The next job is cleaning stale sitemaps, internal links, and homepage fallback rules.
