Sitemap Pro
Enter any website above and instantly explore its live sitemap as a tree — every URL with its priority, change frequency and last-modified date. Then build, validate, split and analyze sitemaps with the full XML engineering suite below.
Paste a domain — it auto-discovers the sitemap (via robots.txt + common locations), follows sitemap-index files, and renders every URL as an interactive tree.
Fetches the site's public sitemap & robots.txt through a CORS proxy (browsers can't read cross-origin files directly). Nothing of yours is sent. Large sites are capped to keep the tree fast.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/blog</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/blog/sitemaps-explained</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/pricing</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/contact</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/products?id=42&ref=home</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/legal/terms</loc>
<lastmod>2026-06-19</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
</urlset>
Protocol check & host breakdown
A sitemap is a discovery aid, not a ranking lever
An XML sitemap is a list of the URLs you want crawled, wrapped in a <urlset> element from the sitemaps.org 0.9 namespace, with each URL in a <url> block carrying a mandatory <loc> and optional <lastmod>, <changefreq> and <priority>. It doesn't raise rankings; it makes sure pages get discovered, which matters most for large sites, deep or orphaned pages, and brand-new sites with few inbound links. The Generate tab here builds a correct urlset from a plain list, XML-escaping the ampersands, angle brackets and quotes that constantly break hand-written sitemaps.
The protocol caps each file at 50,000 URLs and 50 MB uncompressed. Cross either limit and you split the URLs across several sitemap files and publish a sitemap index — a <sitemapindex> document whose <sitemap> entries point at each child file by URL. You then submit the index, not the individual files. The Split tab does both: it chunks your list at a size you choose (50,000 max) and emits the matching index referencing sitemap-1.xml through sitemap-N.xml under your base URL.
Be honest with lastmod — it's the one annotation search engines still use, and they stop trusting it the moment every page claims to have changed today. changefreq and priority are explicitly treated as hints that the major engines largely ignore; set them if you wish, but don't expect priority 1.0 to buy faster crawling. The Validate tab enforces exactly the rules a crawler cares about: valid http(s) locs, priority within 0.0–1.0, a recognised changefreq, a W3C-formatted lastmod, no duplicates, and the size limits.
Once your sitemap validates, reference it from your robots.txt with a Sitemap: line and submit it in Search Console, then watch coverage in your analytics and reporting tools. This tool deliberately doesn't crawl your live site to discover URLs — that needs a backend and runs into cross-origin restrictions in the browser — so you supply the list and everything stays local and private.
Trusted by SEO & Web Engineering Teams
“We regenerate sitemaps for a 400k-URL catalogue and the Split tab plus the generated index is exactly the workflow we needed — chunk at 45k, get the file count and a ready index pointing at sitemap-1…N.xml. The validation caught a batch of priority 2.0 values our old script was emitting. All in the browser, so our staging URLs never left the machine.”
“Pasting a URL list and getting a correctly XML-escaped urlset in one step is so much faster than hand-rolling it. I'd been forgetting to escape query-string ampersands; this just does it. The entry count and copy button mean I can drop it straight into the repo.”
“The Validate tab is the part I keep coming back to — it flags the things Search Console would reject (bad lastmod dates, non-http locs, duplicates) before I ever submit. I'd love a live-crawl option, but I understand why an in-browser tool can't do that, and supplying the list is fine.”
“The Stats view changed how we audit: seeing the changefreq and priority distribution and the per-host breakdown instantly showed us a chunk of URLs pointing at the wrong subdomain. Clear, honest about changefreq/priority being hints, and genuinely private. It's part of every release now.”
Love using our calculator?
Related tools
Related Articles
Dive deeper with our expert guides and tutorials related to Sitemap Pro
generate · validate · split · index · in-browser · Last reviewed: 2026-06