Technical SEO

XML Sitemap Validator

Check your sitemap structure and catch issues before search engines do.

Local content or remote URL analysis · No account required

Validate a sitemap

This bounded browser validator accepts up to 2 MiB. The sitemap protocol permits larger files; exceeding this tool’s limit does not make your sitemap invalid.

Validation results

Add your input, then run the tool to see results.
WORK WITH CONFIDENCE

Understand your results

For developers and SEO teams checking sitemap content before submitting it.

This tool checks XML parsing and core sitemap rules, including the namespace, entry structure, locations, dates, optional priority and changefreq values, duplicates, and counts. A sitemap index is checked without fetching its children. Extensions are accepted but not validated against extension schemas. This is not an XSD or indexing-status validator.

How to use this tool

  1. Paste XML or choose an uncompressed UTF-8 .xml file up to 2 MiB.
  2. Run Validate sitemap to inspect a urlset or sitemapindex.
  3. Use entry-numbered errors to fix the source, then validate again before publishing.

What the observations mean

A urlset lists page locations; a sitemapindex lists sitemap files. The standard namespace and loc structure are required. The protocol allows up to 50,000 entries and 50 MB uncompressed per sitemap, larger than this tool’s local 2 MiB limit and remote bounds.

Worked example

Validate one canonical page entry using the standard sitemap namespace.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://example.com/notebooks/</loc></url>
</urlset>

This has a urlset root, the expected namespace and an absolute location. A core-rule pass says the supplied XML is well formed and meets the implemented checks; it does not confirm that the URL returns 200 or has been indexed.

Limits and processing

Pasted/uploaded XML is local; configured URL mode fetches a bounded public XML response. Neither mode recursively crawls sitemap children or validates every extension against a full XSD. Do not add invented lastmod dates.

Common problems and practical fixes

Malformed XML
Close elements and escape & as &amp;. A parser error must be fixed before semantic checks can complete.
Invalid location or date
Use absolute canonical URLs and genuine W3C-format lastmod values. Omit dates you cannot verify.
Valid file, missing page in search
Submission supports discovery, not guaranteed indexing. Inspect status, canonical, robots access, and content separately.

Best practices

Validate the final exported file, publish it on the intended host, and submit it through a verified Search Console property. This tool does not fetch entries or child files.

Practical tips

  • Escape ampersands as &amp; inside XML locations.
  • Use real modification dates. The tool checks date formatting and calendar validity, not whether a date matches an actual update.
  • The protocol permits up to 50,000 entries and larger files than this tool’s 2 MiB browser limit. Split a large file for local checks.
A LITTLE MORE CLARITY

Frequently asked questions

Practical answers for using the XML Sitemap Validator.

Does a valid sitemap guarantee indexing?

No. Passing these checks says nothing about crawl access, canonical selection, content quality, or search-engine indexing decisions.

Are image or hreflang extensions accepted?

Yes, namespaced extension elements are retained and flagged as not schema-validated. Their own rules require separate checks.

Will the tool fetch URLs in my sitemap?

No. Pasted and uploaded content is processed locally, and remote URL mode uses the API only when configured. It fetches only the submitted sitemap, without fetching entries or child indexes.