Sitemap XML validator and splitter
Check an uploaded sitemap and split oversized files into an index.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Validate pasted or uploaded sitemap XML locally, then split a URL sitemap into complete downloadable parts and an index. Each part respects both its chosen URL-count cap and the protocol’s 52,428,800-byte uncompressed limit. Enter the real public output directory to generate correct index locations; you upload and submit the files yourself. Protocol reference: https://www.sitemaps.org/protocol.html.
A few things to know
Browser input is capped at 64 MiB and 100,000 entries; larger files need a streaming tool. No URL fetching, crawlability checks, full XSD validation, gzip decompression, extension schema validation or cross-site submission verification. Indexes are validated only. Lastmod supports full calendar dates and timestamps with timezone; reduced-precision dates are not accepted. Duplicate URLs remain in output. Generated files are not automatically uploaded or submitted.
When to use this tool
A sitemap helps describe the URLs you want a search engine to discover, but malformed XML or oversized files can make submission harder. This validator checks pasted or uploaded sitemap XML and can split a URL sitemap into complete files with a generated index. It measures uncompressed UTF-8 bytes as well as entry counts. Processing stays in your browser; validating or downloading a sitemap does not upload it, submit it or guarantee its URLs are indexed.
- Check sitemap XML before publishing a website export.
- Split a URL sitemap into smaller parts and generate an index.
- Find duplicate locations, mixed origins and invalid date values.
How to use sitemap xml validator and splitter
Supply uncompressed XML
Choose pasted XML or an uploaded UTF-8 XML file. The tool supports urlset and sitemapindex with the sitemap namespace. It does not decompress gzip files or fetch a remote sitemap URL.
Choose validation or splitting
For a URL sitemap, select Validate and split and set the maximum entries per part, from 1 to 50,000. Enter the actual public output directory URL ending in /. Use Validate only when you want diagnostics without files.
Fix issues and publish the files
Review errors, warnings and size information. Correct errors before splitting. Download every generated part and index, upload them to the stated directory, then submit or reference the index yourself. Check crawlability separately.
Split three URLs into two parts
Inputs
Use the supplied three-URL XML example, choose split, set maximum entries per part to 2 and public output directory to https://example.com/.
Result
The implemented checks pass and two sitemap parts are generated. Downloads include sitemap-1.xml, sitemap-2.xml and sitemap-index.xml. The first part holds two URLs and the second holds one.
What it means
The index names the expected public locations of both parts. Those locations are only draft references until you upload the generated files; no live file or search-engine submission is created by the tool.
Common mistakes to avoid
Using the wrong output directory
The generated index uses the directory you enter. A placeholder domain or incorrect path produces locations that will not point to your deployed files. Use your real directory before downloading.
Confusing file count with URL count
A sitemap index lists sitemap files, while a URL sitemap lists pages. This tool validates indexes but does not fetch or split their child files.
Assuming XML validity means indexability
A well-formed entry may still return an error, redirect, require login or conflict with indexing signals. The validator does not visit any listed URL.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
What is the difference between urlset and sitemapindex?
A urlset lists individual page URLs. A sitemapindex lists the public locations of sitemap files. This tool can split a urlset and build an index for its output. An input sitemapindex is validated only; its remote children are not downloaded or examined.
What size limits does splitting respect?
Each generated part stays within your selected cap of at most 50,000 entries and the protocol’s 52,428,800-byte uncompressed limit. XML wrappers and serialized entries count toward bytes. A part may contain fewer than the selected entry limit when its bytes require an earlier split.
Can I upload a compressed sitemap?
No. Supply uncompressed UTF-8 XML. Browser input is capped at 64 MiB and 100,000 entries, so very large exports need a streaming workflow instead. Decompress a gzip file separately, then check whether the resulting XML fits the input limits.
What date formats are accepted for lastmod?
The checker accepts real full calendar dates such as 2026-10-10 and supported timestamps with a timezone. It rejects impossible dates and reduced-precision dates. A syntactically accepted date does not prove that it accurately reflects the page’s last meaningful modification.
Are duplicate URLs removed when splitting?
No. Duplicates are reported as warnings and preserved in output. Review your source and remove unintended duplicates before splitting if that is your desired policy. Automatic deletion could conceal why duplicate entries appeared or alter an export you intended to inspect.
Can entries use different domains or protocols?
This checker flags mixed origins and expects a suitable same-origin output directory for splitting. Cross-site submission arrangements are outside its verification. Separate origins in your source and use the directory scope that covers the listed paths before generating the files.
Does it validate image, video or news sitemap extensions?
Extension XML is preserved during splitting, but its schema is not fully validated. The checker focuses on XML syntax, supported core fields, location formats, dates, duplicate detection and limits. Use the extension’s official requirements when those additional elements are important.
What should I do after downloading the index?
Upload both the index and every part to the directory used during generation. Check that their URLs are publicly accessible and correct, then reference or submit the index through your chosen search-engine workflow. Sitemap submission remains a discovery aid rather than an indexing promise.
Explore the topic in the blog
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.