Sitemap XML Parser
Parse a sitemap.xml or sitemap index and extract every URL with its lastmod, changefreq and priority — as a Markdown table, CSV, JSON or a plain URL list, with spec-conformance warnings. Runs entirely in your browser.
Input
Options
Output
| Metric | Value |
|---|---|
| No data yet | |
| Type | Message |
|---|---|
| No data yet | |
Guides
Paste a sitemap.xml or a sitemap index and instantly get every URL laid out with its lastmod, changefreq and priority — as a Markdown table, CSV, JSON, or a plain list of URLs. This free online sitemap parser also flags spec-conformance problems (a missing <loc>, an out-of-range priority, a malformed date) so you can spot a broken sitemap before search engines do. Everything runs in your browser — nothing is uploaded.
How to use it
- Paste your sitemap XML into the input box, or upload a
.xml/.txtfile. - Pick an Output format: a Markdown table for reading, CSV or JSON for piping into another tool, or a plain URL list.
- Optionally filter by lastmod (last 7/30/90/365 days, or entries with no lastmod at all) and sort the results by URL, date or priority.
- Read the Summary for quick counts and the Validation table for anything worth fixing.
The parser accepts both sitemap shapes defined by the sitemaps.org protocol:
- A regular
<urlset>— a list of<url>entries, each with<loc>, and optionally<lastmod>,<changefreq>and<priority>. - A
<sitemapindex>— a list of<sitemap>entries (each just<loc>and<lastmod>) pointing at other sitemap files, used when a site's full sitemap is split across multiple XML files.
What validation checks does it run?
For every entry: a missing or non-http(s) <loc> is reported as an error, and a <priority> outside 0.0–1.0 is an error too. A <lastmod> that isn't a valid W3C Datetime (YYYY-MM-DD or full ISO 8601) or a <changefreq> outside the seven values the spec defines (always, hourly, daily, weekly, monthly, yearly, never) is a warning. It also flags a sitemap with more than 50,000 entries, since that's the protocol's hard limit for a single file.
Does it handle namespaced tags?
Yes — elements are matched by local name, so a document using a namespace prefix (<ns:url>, <ns:loc>) still parses correctly regardless of the prefix used.
Is my data private?
Completely. Parsing runs entirely in your browser using a self-contained XML tokenizer — your sitemap is never sent to a server, logged, or stored.
Need to generate a sitemap instead of parsing one?
Use the Sitemap XML Generator to build a sitemap.xml from a list of URLs, or the Robots.txt Tester to check which of those URLs your robots.txt actually allows. For converting other XML documents to CSV, see the XML to CSV Converter.