Key takeaways
- What 'Submitted URL not found (404)' means in Google Search Console, why it happens (bad sitemap / old URLs), and the fastest cleanup steps with validation
Table of Contents
Start with the map:
Related:
What "Submitted URL not found (404)" means
You submitted the URL (usually via sitemap), and Googlebot got a 404.
That is different from regular 404s.
A normal 404 can be just legacy noise.
A submitted 404 means: your sitemap is asking Google to crawl/index a URL that does not exist.
That is a quality signal problem.
Why this happens (common causes)
1) Old URLs still in your sitemap
Typical after:
- site rebuild
- CMS migration
- slug changes
2) Multiple sitemaps / cached sitemaps
Sometimes:
- you changed sitemap generation but old sitemap is still accessible
- external systems keep linking to old sitemap URLs
3) Internal links still point to deleted URLs
Even if you fix the sitemap, internal links can keep feeding dead URLs.
Fix checklist (fast)
Step 1: Remove dead URLs from the sitemap
Sitemap is "please index this".
If the URL is not real, it should not be there.
Step 2: Decide what the URL should be
For each submitted 404, choose exactly one outcome:
- restore (bring the page back) -> 200
- move (true successor exists) -> 301 to that page
- remove (no successor) -> 410 (or keep 404)
Deep dive on the decision:
Step 3: Fix internal links
If your own site links to the dead URL, you are sending mixed signals.
Step 4: Re-submit the sitemap
Once cleaned:
- submit sitemap again
- do not spam URL inspection on every URL
Validation
- In GSC -> Sitemaps: make sure the sitemap is processed.
- Spot-check 10 random URLs from the sitemap:
- should return 200
- should not redirect
FAQ
Should I request indexing again?
If you already requested indexing today, don't spam. Fix, deploy, and request again only for the top core pages if needed.
Is it OK to leave legacy 404s?
Yes. You cannot fix the whole internet. The goal is to stop you from submitting dead URLs.
How to find where the submitted URL came from
For a submitted 404, you want to identify the source:
- sitemap (most common)
- internal link
- an old sitemap URL that is still accessible
Practical workflow:
- Export a sample list from GSC.
- Look for patterns (old directories, old slugs, pagination).
- Fix the generator (do not chase single URLs).
The fastest cleanup routine
- Remove the URLs from sitemap.
- Fix internal links if they exist.
- If a true successor exists: 301.
- If the content is gone: 410.
Timeline expectations
Even after fixes:
- GSC can show submitted 404s for days/weeks
- Google needs to recrawl and process the signals
The goal is not instant cleanliness. The goal is "no new submitted 404s".
Common mistakes
- keeping submitted 404 URLs in the sitemap "until Google forgets"
- redirecting everything to the homepage (often creates soft-404 patterns)
- 301-ing dead URLs to unrelated pages
Quick decision table
- URL should exist -> make it 200
- URL moved -> 301 to the true successor
- URL intentionally removed -> 410
- random junk/scanning -> 404
FAQ
Is it bad if I still see submitted 404s after I fixed the sitemap?
Not necessarily. GSC reports lag and Google needs recrawls to update classifications. The key KPI is: do you keep generating new submitted 404s?
Should I request indexing for the removed URLs?
No. Request indexing only for pages you want indexed (200 OK canonical pages). For removed URLs, the right move is sitemap cleanup + correct status codes.
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:
Blocked due to other 4xx: The real causes and the fix checklist (GSC)A practical guide to 'Blocked due to other 4xx' in Google Search Console: what codes it usually hides (410/429/451/401/403), how to choose the right strategy, and how to validate fixes.