Skip to content
100% local

Sitemap parser

Turn a sitemap.xml into a readable URL list and check it for common errors.

Input
Output

Sitemap parser

Paste the contents of a sitemap.xml or sitemap-index.xml and this tool lists every URL it contains, along with its metadata — lastmod date, changefreq, priority and the number of hreflang alternates attached to it. It is built for the moment you need to actually read a sitemap rather than just submit it: auditing what a CMS generated, checking a competitor's sitemap, or reviewing what you are about to hand to Google Search Console.

Toggle which columns to show with the show lastmod, show changefreq, show priority and show hreflang alternate count options, sort the list by lastmod or priority, and narrow it down with the path filter, which keeps only URLs containing the text you type. Pick an output format that matches what you need next: a plain URL list, a table for scanning, CSV for a spreadsheet, or JSON for a script. A sitemap index is detected automatically and its nested sitemap entries are listed the same way.

With validity checks turned on, the tool flags what actually breaks a sitemap in production: more than 50,000 URLs in one file, a lastmod that is not valid ISO 8601, a priority outside the 0–1 range, duplicate URLs, relative URLs where an absolute one is required, a protocol or domain that does not match the rest of the file, and hreflang alternates that do not link back to each other. Each issue names the affected URL, so you can jump straight to the fix.

Everything runs in your browser — the sitemap never leaves your device, which matters when it lists unlaunched pages or an internal staging domain. Copy the result, download it as a .txt file, or send the output straight back into the input to filter or re-sort it again.

FAQ

Does it support sitemap index files?
Yes. When the input is a <sitemapindex>, the tool lists its nested <sitemap> entries with their lastmod dates instead of individual page URLs.
What counts as an invalid lastmod date?
Anything that isn't a valid ISO 8601 date or date-time, such as 01/15/2024 or a value that fails to parse as a real calendar date.
How is the protocol/domain mismatch check decided?
The tool finds the origin (protocol and host) used by most URLs in the file and flags any URL on a different origin, since a sitemap should describe one site.
Can it handle very large sitemaps?
Yes, including files with thousands of URLs. If a sitemap exceeds the 50,000-URL limit set by the sitemap protocol, that is flagged as an issue too.
Is my sitemap uploaded anywhere?
No. Parsing runs entirely in your browser — the file you paste never leaves your device.