404s inside your XML sitemap
Sitemaps should list indexable 200 URLs. How 404s and redirects get stuck in the file, what Search Console does with them, and how to verify.
sitemap.xml is a hint: “these URLs matter.” If the file still lists deleted products, old pagination, or staging leftovers, you send crawlers to dead ends and pollute coverage reports.
Google’s own sitemap guidance is boring on purpose: canonical, indexable, 200. Redirects and 404s do not belong there. They belong in server rules or in the trash.
How they get in
- The generator dumps “every post ever”, including drafts that 404 for guests
- After a redesign the plugin keeps the old ID list
- A CDN or language prefix changed; the sitemap did not
- Images and attachments stay listed after the file was deleted (broken images)
Check
- Open
/sitemap.xml(and the child sitemaps it indexes). - Sample URLs in the browser. Note status and final address.
- Compare with Search Console: 404s “submitted in sitemap” are the expensive ones.
- Run a whole-site crawl from Chrome if the file is huge; export CSV and filter status.
Fix
Regenerate from live, public URLs only. Drop noindex, canonical-to-elsewhere, 3xx, 4xx. If a URL moved, the sitemap should contain the destination, not the hop.
A clean sitemap will not rank you by itself. A dirty one keeps teaching bots the old map of the site.
Check the page you just read about
Install Advanced Broken Links Search and scan the live page — links, images, redirects. Free, no account.
Add to Chrome — free