XML Sitemap Generator
Build a search engine ready XML sitemap from a list of URLs directly in the browser. Supports automatic priority by folder depth, change frequency, last modified dates, and automatic splitting into a sitemap index for very large sites.
Follows internal links up to 200 pages. Pages marked noindex are skipped, since they should not be in a sitemap.
Escaping is not cosmetic here. A URL containing a bare ampersand, which any search or filter URL will have, must be written as & in the XML. Without it the file is not valid XML at all, and Google rejects the entire sitemap on a parse error rather than skipping the one bad line. Every URL is escaped and the finished file is parsed back to confirm it is well formed before you can download it.
Priority is a hint, not a lever. Google has said publicly it largely ignores the priority field. Set it if you like, but it will not push a page up the rankings. What a sitemap genuinely does is help crawlers find pages that are not well linked internally.
Do not list pages you do not want indexed. Putting a noindex page in a sitemap sends two contradictory signals. The crawl mode skips them automatically for that reason.
How this sitemap generator builds spec-compliant XML, entirely offline
You paste a list of URLs, the tool validates each one and writes standards compliant XML sitemap markup in your browser. There is no upload step and no server processing your URL list. The one exception is the JSZip library, which is pulled in dynamically from a CDN only if your list is large enough to require splitting into multiple files, so a normal sized sitemap never triggers any outside request at all.
What the sitemaps.org protocol requires
An XML sitemap is a plain, well defined format. Every entry sits inside a urlset element that declares the sitemaps.org namespace, and each url block can carry four fields.
| Field | How this tool sets it |
|---|---|
| loc | The URL itself, XML escaped for ampersands, brackets and quotes before being written into the output. |
| lastmod | Either today’s date in YYYY-MM-DD, a custom date you pick, or omitted entirely if you choose none. |
| changefreq | One global value applied to every URL in the batch, or omitted if set to none. |
| priority | Either a single fixed value from 0.0 to 1.0, or automatic, based on how deep the URL sits in the site’s folder structure. |
The automatic priority curve
When automatic priority is enabled, the tool counts the number of nonempty path segments in each URL and assigns a priority that steps down as depth increases, on the reasoning that a homepage is more important than a page four folders deep.
A real sample entry
This is the literal shape of one URL block the tool writes, with a two decimal place priority rounded from the depth calculation above.
The 50000 URL split
File upload option
Instead of pasting, you can upload a plain text file of URLs, read client side with FileReader and appended to whatever is already in the textarea.
Invalid line reporting
Lines that fail URL parsing are shown separately, up to the first 20, with a count of any remainder, so you can fix source data instead of guessing what got skipped.
Sitemap protocol references
- The sitemaps.org protocol is the full specification for the XML format and the sitemap index format this tool implements.
- Google’s sitemap building guide covers submission through Search Console and how Google treats priority and changefreq, largely as hints rather than guarantees.
When a sitemap earns its keep
Generating a fresh sitemap after migrating a site to a new platform with no built in sitemap feature, producing a sitemap index for a large e-commerce catalog that has crossed the 50,000 URL mark, quickly rebuilding a sitemap after a bulk URL restructure, and creating a scoped sitemap for just the blog section of a larger site.
FAQ: XML sitemap generator
An XML sitemap is a file listing every important page on your site, helping search engines discover and crawl content they might otherwise miss, especially on large sites or pages with few internal links pointing to them. It does not guarantee ranking, but it improves crawl coverage.
Upload sitemap.xml to the root directory of your domain, so it is reachable at a path such as example.com/sitemap.xml, then submit that address in Google Search Console and Bing Webmaster Tools so both engines are aware of it.
When checked, the tool looks at how many folders deep each URL sits, your homepage gets 1.0, top level pages get 0.8, and priority steps down from there the deeper a URL is nested. This gives naturally sensible values without you having to set one manually for every page.
The sitemaps.org protocol caps a single sitemap file at fifty thousand URLs. Once your list passes that limit, the tool automatically splits your URLs across multiple numbered sitemap files and generates a sitemap index file, then bundles everything into a downloadable zip.
No. The sitemap building happens directly in your browser. Your list of URLs is processed and formatted locally and is not stored anywhere.
From the blog
Search, without the guesswork
What actually moves rankings and what is folklore.
