XML Sitemap Errors: Types and Fixes Compared
Key takeawayThe XML sitemap is the most direct entry point for search engines to discover pages. Its errors rarely show up on the page or in the CMS — they surface as warnings at submission time, or the file is silently discarded at parse time. The latter is the most dangerous, because nothing reports it.
When this applies
- Sites where indexing does not change after submitting a sitemap
- Sites where GSC reports errors in the sitemap
- Sites where the sitemap contains far fewer URLs than the actual page count
- Sites where the sitemap is still full of old URLs after a redesign
| Error type | Symptom | Severity | Fix |
|---|---|---|---|
| Malformed XML | Submission reports the file cannot be parsed | High | Validate the structure with an XML validator |
| URL count over the limit | A single file exceeds 50,000 URLs | Medium | Split into a sitemap index file |
| Single file over 50 MB | Silently discarded with no warning | High | Split by directory |
| Contains non-200 URLs | Coverage numbers do not add up | Medium | Clean out dead URLs |
| Contains redirecting URLs | Wastes crawl resources | Low | List only final destination URLs |
| Contains noindex pages | Submitted but never indexable | Low | Remove those URLs |
| robots.txt blocks the sitemap path | Parsers are denied access | High | Never block the sitemap path |
| All lastmod values identical | Update signals become meaningless | Low | Fill in actual modification times |
Step-by-step diagnosis
- Validate the file structure with an XML validator before submission: closed tags, correct encoding, no illegal characters.
- Count the URLs in the sitemap and compare against the number of actually indexable pages — a large gap points to a broken generation logic.
- Spot-check 20 sitemap URLs for their actual status codes and remove anything that is not 200.
- If the URL count exceeds 50,000, switch to a sitemap index and split by directory or by language.
- Check whether robots.txt blocks the path where the sitemap lives — this is the most hidden and most fatal error class.
- Confirm the sitemap contains no noindex pages and no redirecting addresses.
- Review the Sitemaps report in GSC for submitted URL counts and read errors, and fix issues one by one.
Common mistakes
- Treating the sitemap as a switch that improves indexing — it only helps with discovery; it does not decide indexing.
- Placing the sitemap in a directory blocked by robots.txt.
- Submitting parameterized URLs — this creates duplicate entry points.
- Writing the same lastmod date everywhere — the update signal loses all value.
- Putting URLs in the sitemap without any clickable in-site path to them — they still will not get crawl priority.
FAQ
Is a bigger sitemap always better?
No. Prioritize URLs that have standalone content value and are not yet indexed. Stuffing the sitemap with low-value pages dilutes crawl attention.
Should redirecting URLs be submitted in a sitemap?
No. Redirecting URLs make parsers spend a request on a hop, and some parsers reduce their trust in the sitemap because of it.
How should multiple sitemap files be organized?
Use one sitemap index file as the entry point and list the individual sitemaps inside it. Splitting by language or content type is clearer than splitting by page count.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Why Google Does Not Index Infinite Scroll Product Lists — and the FixesCommon hreflang Errors on Multilingual Sites: The Full ListCanonical Tag Conflicts Causing Duplicate Indexing: How to Fix ThemWhy Breadcrumb Schema Errors Make Rich Results DisappearOn-Site Duplicate Content: Judgment Criteria and a Prevention ChecklistNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.