sitemap.xml Generator
Generate a valid XML sitemap from a list of URLs in seconds. Set per-URL change frequency, last modification date and priority, and download a sitemap.xml ready to submit in Google Search Console and Bing Webmaster. No crawl, no upload, no waiting in a queue — everything happens in your browser.
How to use
- 1
Paste your URLs
Add one URL per line in the input box. Trailing slashes and protocols are validated.
- 2
Set defaults
Pick a default change frequency, last-modified date and priority for the whole list.
- 3
Download sitemap.xml
Click Generate and download the file. Upload it to the root of your site.
Technical details
A sitemap is an XML file that lists the URLs of your site to help search engines discover and prioritise crawling. The sitemaps.org protocol is supported by Google, Bing, Yandex and other engines. While not strictly required for small sites, a sitemap dramatically speeds up indexing for new pages, large catalogues and JavaScript-heavy SPAs.
Each entry in a sitemap follows the `<url>` element and contains a required `<loc>` (the URL) plus optional `<lastmod>` (W3C datetime), `<changefreq>` (always, hourly, daily, weekly, monthly, yearly, never) and `<priority>` (0.0–1.0). Google currently ignores `changefreq` and `priority`, but Bing and Yandex still consult them, so the generator emits them by default.
A single sitemap can contain up to 50,000 URLs and weigh up to 50 MB uncompressed. For larger sites split the URLs into multiple sitemaps and reference them from a sitemap index file. The generator can produce either a single sitemap or an index — choose in the options.
Submit the sitemap to Google Search Console (Indexing → Sitemaps) and reference it from robots.txt with a `Sitemap:` line so other crawlers discover it automatically.
Frequently asked questions
How many URLs can a single sitemap contain?
Do I need a sitemap if my site is small?
Should I include URLs that return 404?
Where do I submit the sitemap?
How often should I update the sitemap?
This tool was tested and calibrated by our engineering team. All processing happens locally in your browser — your files and data never leave your device.