← All Tools
XML Sitemap Compiler🔒 100% local
Generate sitemaps. Privacy-first, no server uploads, no tracking.
XML Sitemap Compiler: related tools
XML Sitemap Compiler turns a base URL plus a list of paths into the body of a sitemap.xml file. The first entry must be an absolute URL and supplies the origin; every following entry, split on commas or new lines, becomes a <loc> under that origin. Duplicate paths are dropped, each <loc> gets today's date as <lastmod>, and <priority> is derived from how deep the path is.
XML Sitemap Compiler: how to use it
- Put the site's absolute base URL first, for example https://example.com.
- Add the page paths after it, separated by commas or on separate lines.
- Press Process, then copy everything from the XML declaration to </urlset> into sitemap.xml.
XML Sitemap Compiler: worked example
https://example.com, /page1, /page2becomesCompiled sitemap with 2 URLs (priority by depth: home 1.0, depth-2 0.6…).
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/page1</loc>
<lastmod>2026-09-27</lastmod>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/page2</loc>
<lastmod>2026-09-27</lastmod>
<priority>1.0</priority>
</url>
</urlset>
Steps: save as sitemap.xml in your site root → add to robots.txt: "Sitemap: https://example.com/sitemap.xml" → submit in Search Console.Every lastmod is the date you generated the file, so the output changes from one day to the next.
XML Sitemap Compiler: when to use it
- Building a small sitemap by hand for a static site of a dozen or so pages.
- Generating the url block to paste into an existing sitemap file.
- Creating a sitemap for a staging host so you can test a Search Console submission.
XML Sitemap Compiler: what it does not do
- The priority rule does not match the sentence in the header line: a top-level path such as /page1 comes out at 1.0 and /blog/post at 0.8, while the summary text mentions a depth-2 value of 0.6.
- Paths are copied literally. They are not percent-encoded, and trailing slashes or query strings stay exactly as written.
- The base URL's own path is discarded - only its origin is used, so a base of https://example.com/app/ still yields https://example.com/page1.
- There is no changefreq element and lastmod is just the generation date, so search engines will treat the dates as unreliable if you regenerate the file often.