An XML sitemap is a discovery signal and a canonical-URL inventory. It does not force indexing, override a noindex directive, repair poor content, or replace internal links. Troubleshooting should begin with the exact public response Google receives, not the file visible in a CMS screen.
Decision snapshot
| Decision | Practical approach | Watch for |
|---|---|---|
| Inspect the final response | Check status, redirect chain, content type, and body from the submitted URL. | A pretty HTML error page can return 200 and still not be a sitemap. |
| List canonical URLs only | Include successful, indexable preferred URLs on the intended host and protocol. | Redirects, errors, noindex pages, and alternate hosts create conflicting signals. |
| Separate discovery from selection | Use indexing reports and URL inspection to diagnose excluded pages. | A valid sitemap does not guarantee that every URL should be indexed. |
Reproduce the reported response
Request the exact submitted URL with redirects visible. Record DNS host, HTTPS certificate, status chain, final URL, content type, encoding, and first body bytes.
Validate XML structure and limits
Confirm XML declaration, urlset or sitemapindex namespace, escaped entities, absolute URLs, file and URL limits, reachable child sitemaps, and compression behavior.
Audit every listed URL class
Sample and programmatically check status, canonical, robots meta and headers, robots.txt access, host, protocol, language alternate logic, and whether the page is useful and internally linked.
Compare deployment and cache layers
Check application routing, static-file precedence, rewrites, CDN behavior, content negotiation, www versus apex rules, stale cache, security challenges, and custom error handling.
Resubmit and monitor correctly
Submit the canonical sitemap URL, retain stable location, review last-read and discovered counts, inspect representative excluded URLs, and allow recrawl time before judging changes.
Action checklist
- Submitted URL returns supported XML rather than HTML
- Redirects end on the intended canonical host and sitemap path
- All entries are absolute canonical indexable 200 URLs
- XML is escaped, namespaced, encoded, and within documented limits
- Child sitemaps and compressed responses are publicly readable
- Indexing investigations use URL-level evidence beyond sitemap status
Working worksheet
Record these fields in the same working document so the decision can be reviewed and handed off:
- Submitted URL, status chain, final URL, content type, and body signature
- XML parser result and URL count
- Sample URL status, canonical, robots, internal-link, and index state
- Rewrite, cache, CDN, host, or application layer responsible
- Fix, deployment time, resubmission date, and monitoring result
Common failure patterns
- Submitting an HTML resource directory and naming it sitemap.xml
- Listing both www and apex versions while canonicalizing to only one
- Regenerating timestamps daily even when page content has not materially changed
Connect this work
Robots controls and sitemap declarations serve different purposes. Read check crawl access separately from sitemap validity.
Search Console provides URL-level evidence after submission. Read interpret sitemap and URL inspection reports.
A sitemap error may reveal a broader deployment problem. Read investigate sitewide canonical inconsistencies.