XML Sitemap Generator

1. Official Sitemaps.org Protocol XML Namespace

XML sitemaps list authoritative URLs for crawlers. As documented in Sitemaps.org Official Protocol Specification, specifying valid XML tags allows search engines to discover all published pages.

2. Why lastmod Timestamps Matter to Googlebot

Google uses <lastmod> timestamps in W3C Datetime format (YYYY-MM-DD) to prioritize re-crawling updated pages.

3. Validating Existing XML Sitemaps

Validate live sitemap URLs in our XML Sitemap Validator.

4. Sub-50ms Static Sitemap Serving via Nimbica Edge

Nimbica pre-renders sitemap XML files into static assets served across 300+ global edge locations, giving search crawlers sub-50ms TTFB response times.

5. How to Use This Sitemap Generator

There are two ways to add URLs. Option 1 (Bulk Paste) is fastest if you already have a URL list — paste one URL per line into the text box and click “Import Bulk URLs.” Any line that does not start with http is automatically prefixed with https://. This replaces whatever entries were already in the list, so use it before making individual edits, not after.

Option 2 (Individual Entries) gives you per-URL control. Click “+ Add URL Entry” to create a new row, then set the loc (the full URL), lastmod (the date the page content last changed), changefreq (a rough hint of how often the page updates), and priority (a relative 0.1–1.0 weighting versus your other pages). The XML on the right regenerates instantly as you type — there is no submit step.

Once the output looks correct, either click “Copy XML” to paste it into your own file, or “Download sitemap.xml” to save it directly. Empty loc fields are automatically excluded from the generated XML, so you can leave placeholder rows blank without breaking the file.

6. Sitemap Size Limits & Sitemap Index Files

Per the official protocol, a single sitemap file may list at most 50,000 URLs and must not exceed 50MB uncompressed. Most small business and blog sites never come close to that limit, so this tool's single-file output is sufficient. If your site has tens of thousands of pages — a large catalog or a high-volume publisher — split the URLs into multiple sitemap files (for example by content type or date range) and reference each one from a separate sitemap_index.xml file. This generator produces one flat <urlset> file at a time; for a multi-file setup you would run it once per batch and hand-assemble the index file that links them.

7. Common Mistakes When Building Sitemaps by Hand

The most common issue is listing URLs that do not actually resolve to a live, indexable page — typos, pages that were later deleted, or staging/dev URLs left in by accident. This tool does not fetch or verify the URLs you enter, so double-check each one loads and returns a normal 200 response before publishing the sitemap. Related mistakes include mixing http:// and https:// versions of the same domain, including both www and non-www variants of a URL, and listing pages that have a noindex meta tag or are canonicalized to a different URL — all of which send Google conflicting signals about what you actually want indexed. Finally, setting every lastmod date to “today” regardless of whether the page changed is a known trust-eroding pattern; only update lastmod when the content genuinely changes.

8. Who Should Use This Tool

This generator is aimed at static sites, small marketing sites, landing pages, and any project without a CMS that auto-generates sitemaps. It is also useful for developers who want to quickly hand-assemble a sitemap for a client site, a documentation microsite, or a JAMstack project where a plugin-based solution is not available. If you run WordPress with an SEO plugin (Yoast, Rank Math, All in One SEO) or use a platform with built-in sitemap generation, that automated sitemap is usually the better long-term choice since it updates itself as content changes — use this tool instead for one-off sitemaps, quick fixes, or sites those plugins do not cover.

9. Limitations

This tool does not crawl your website — it has no way to discover pages on its own, so any URL you do not manually add will simply be missing from the sitemap. It also does not validate that entered URLs actually exist, return a 200 status, or are canonical; that verification is your responsibility, or you can check the finished file with our XML Sitemap Validator. Because generation happens entirely in your browser, the sitemap is a static snapshot: if you add or remove pages later, you need to come back and regenerate it manually — unlike a CMS plugin, this tool has no way to keep the file in sync automatically over time.