How to check an XML sitemap before submitting it
Check an XML sitemap by validating its XML structure, reviewing canonical public URLs, removing redirects and duplicates, fetching the live file, and comparing it with the site's robots and page policies before submission.
Updated 7 October 2026. Keep the output and the verification step together.
Steps
- Confirm the public hostname and protocol.
- Search the list for duplicate URLs, fragments, query strings and private paths.
- Check a representative sample for status, redirects, canonical and noindex behavior.
- Generate or validate the XML and inspect raw output.
- Publish and fetch the live sitemap.
- Submit it as a discovery hint and watch processing separately from indexing.
The list is the hard part
XML syntax is easy to generate. Choosing the right URLs is the editorial and technical work. Use a CMS export or reviewed list, not a guessed set of slugs.
Check a US and Europe release pair
For example, compare a US host with `/en-us/` paths and a European host with `/de-de/` or `/fr-fr/` paths. Confirm that each URL is public, canonical and owned by the right release team. Do not copy the US list into the European file when the markets publish different products or languages.
Check policy conflicts
A URL in a sitemap that is disallowed, noindex or redirected creates a conflict that needs a decision. Remove it or fix the page policy before submitting the file.
Check the live response
A local file can differ from the deployed file because of a proxy, cache or build step. Fetch the public URL and search for a known included URL and a known excluded path.
Treat processing as a signal
Search Console can show that a file was received or processed. It does not guarantee that every listed URL is indexed or receives traffic.
Use the sitemap reference
Google's sitemap documentation describes submission and discovery limits. Reviewed 7 October 2026; keep processing and indexing as separate measurements.
Questions
Can a sitemap contain noindex URLs?
It can, but the conflict is usually a reason to remove the URL or change the policy. Decide deliberately.
Should I submit multiple copies?
Use the stable canonical sitemap address and keep the source list current rather than creating duplicate submissions.