XML sitemap generator. Paste URLs. Done.
Paste a URL list or upload a CSV, set per-row priority, changefreq, and lastmod, optionally attach image or hreflang annotations, and download a valid sitemap.xml. Auto-splits above 50,000 URLs into a sitemap index. Nothing crawls your server.
Valid XML.
A sitemap is a table of contents for crawlers.
A sitemap is an XML file listing the URLs on your site that you want search engines to discover, along with optional metadata (last-modified date, change frequency, relative priority). Search engines use it as a seed list on top of organic crawl discovery. On a site with strong internal linking the sitemap rarely finds URLs the crawler would miss, but on large catalogs, deeply-nested archives, or new sites with few backlinks, the sitemap is the difference between a URL being indexed in days versus weeks.
The file follows the sitemaps.org protocol adopted by Google, Bing, and Yahoo. One sitemap file caps at 50,000 URLs or 50 MB uncompressed. Above that, split into multiple sitemaps and reference them from a sitemap-index file. The generator above handles the split automatically when your URL list crosses 50,000 rows and emits the index plus all child sitemaps.
Image and video sitemap extensions are valuable for ecommerce catalogs and editorial content. An image:loc element inside a url entry tells Google Image Search exactly which image belongs to the page, accelerating discovery versus crawl-only detection. Hreflang annotations inside the sitemap are one of three valid implementations (HTML link tags, HTTP headers, or sitemap xhtml:link). For sites with 50+ locale variants, sitemap-based hreflang centralizes the reciprocal graph in one file and eliminates the per-page tag drift that breaks international SEO.
Tools in the same cluster: robots.txt generator to reference this sitemap. Hreflang generator for standalone language tags. Schema markup generator for structured data on the pages listed inside.
Six answers.
What priority and changefreq values should I use?
Google has publicly stated since 2017 that it largely ignores priority and changefreq, relying instead on its own crawl signals. Bing still uses them. Set priority to reflect relative importance on your own site (homepage 1.0, category pages 0.9, product or article pages 0.7, archives 0.5), not absolute values. Set changefreq honestly based on how often the content actually changes: weekly for blogs and collections, monthly for static service pages, daily only for high-velocity news or stock feeds. The generator above ships sensible presets per site type and lets you override per row.
How do I submit my sitemap to Google and Bing?
Three steps. First, upload the generated sitemap.xml to the root of your domain so it loads at https://yourdomain.com/sitemap.xml. Second, add a Sitemap directive to robots.txt pointing at that URL. Third, submit to Google Search Console under Sitemaps, paste the sitemap URL, and click Submit. For Bing, use Bing Webmaster Tools, Sitemaps, Submit. Both engines now auto-discover sitemaps from robots.txt within 24 to 48 hours of deploy, but manual submission is faster for the first crawl. The generator includes a submission checklist in the output panel.
What happens if I have more than 50,000 URLs?
The XML sitemap spec caps a single sitemap file at 50,000 URLs or 50 MB uncompressed. Above that, split into multiple sitemaps and reference them from a sitemap-index file. The generator detects URL counts above 50,000 and auto-splits into sitemap-1.xml, sitemap-2.xml, etc., plus generates a sitemap.xml sitemap-index that references each child. Upload all files to the same directory and submit only the sitemap-index URL to Search Console; Google crawls the children automatically.
Should I include image or hreflang annotations inside the sitemap?
Image annotations (image:loc inside url entries) help Google Image Search discover product photography and editorial imagery faster than crawl-only discovery. Useful for ecommerce catalogs, news sites, and photography-heavy blogs. Hreflang annotations (xhtml:link) inside the sitemap are one of three valid hreflang implementations (HTML link tags, HTTP headers, or sitemap). For sites with 50+ locale variants, sitemap-based hreflang is less error-prone than HTML tags because it centralizes the reciprocal graph in one file. Both are toggled on per URL in the generator.
Should I compress the sitemap with gzip?
Yes, for anything above 5 MB. Google and Bing both accept .xml.gz. Gzip reduces a 20 MB sitemap to roughly 3 MB, which speeds up the crawler fetch and stays inside the 50 MB uncompressed limit with headroom. The generator offers a download-as-gzip option. For small sites under 1,000 URLs the compression gain is negligible; ship plain .xml and save the configuration step.
Does this tool save my URL list?
No. Every URL you paste or upload lives in memory for this browser tab only. The CSV file is parsed in-browser with PapaParse and never uploaded anywhere. The Download button writes the generated XML directly to your local disk. Close the tab and the URL list is gone. The tool does not ping or fetch any of the URLs you enter; lastmod values come from your input, not from a server round-trip.
One sitemap. Not enough.
Our SEO engagements ship automated sitemap generation (per-template, regenerated on deploy), sitemap-index architecture for large catalogs, hreflang-enabled multi-locale sitemaps, and image + video sitemap extensions for ecommerce brands. Written plan in 2 weeks.