Key takeaways
- A practical guide to the GSC status "Submitted URL seems to be a soft 404": why Google flags 200 pages as "not found", the most common causes, and how to validate fixes
Table of Contents
This status means: you submitted the URL (usually via sitemap), Google fetched it, and decided the page behaves like a "not found" page.
Start with the map:
Related:
Common causes
1) Missing content returns 200
A dynamic route has no data, but still returns a full template with an empty state.
Fix: return a real 404 (or 410 if intentionally gone).
2) Redirects to irrelevant destinations
If many old URLs redirect to a generic page, Google may treat it as a soft-404 pattern.
Fix legacy cleanups correctly:
3) Thin pages with no intent match
Pages that do not satisfy any query intent can get classified as soft 404 even if they return 200.
Fix: add real value (examples, steps, constraints) or do not publish.
Fix checklist
- Confirm the URL returns the correct status for missing content (404/410).
- Make sure the main content exists in the HTML (not only after JS).
- Avoid redirect chains and irrelevant destinations.
- Re-test in URL Inspection.
Validation
- URL Inspection: check screenshot + rendered HTML.
- Pages report: soft 404 counts should trend down (with delay).
Next in GSC statuses
Browse the cluster: GSC indexing statuses.
- GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)
- Page with redirect (Google Search Console): What it means and how to fix it
- Redirect loop: How to find it and fix it (SEO + GSC)
- GSC redirect error: The fastest fix checklist (chains, loops, and canonical URLs)
- Submitted URL marked 'noindex': The fastest fix checklist (GSC)
- Submitted URL blocked by robots.txt: What it means and what to do (GSC)
Next in SEO & Search
Up next:
Redirect loop: How to find it and fix it (SEO + GSC)A practical guide to redirect loops: common causes (www/apex, http/https, trailing slash), how to diagnose quickly, and how to fix without creating chains.