Build line

XML sitemap generator for the URLs you already have

Paste a list, drop a CSV export, type rows or import an existing sitemap to edit. SitemapStudio cleans the URLs, checks every line against the protocol, splits at 50,000 and hands you valid sitemap.xml files. It all happens in this tab.

Try a template:
More options: cleaning, file names, legacy tags
0URLs in sitemap
0files
0removed
✓valid

Paste URLs, drop a CSV or pick a template. The sitemap builds as you type and is checked against the sitemaps.org protocol line by line.

Why start from a list, not a crawl

A crawler-based generator walks your links, so it can only ever report pages that are already reachable. Those are the pages search engines were going to find anyway. The pages a sitemap exists for are the others: a product added this morning, an archive four clicks deep, a landing page nothing links to yet.

You already have the full list somewhere. It might be a CMS export, a Shopify product CSV, a database query, a Screaming Frog crawl or a Search Console export. SitemapStudio turns that list into protocol-correct XML without sending a single URL to a server.

What happens to your list

  1. Parse. Delimiters, quotes and header rows are detected; blank lines and # comments are skipped.
  2. Normalise. Relative paths are resolved against your base URL, spaces are percent-encoded and #fragments are stripped.
  3. Filter. Duplicates, other hosts, non-http(s) schemes, URLs over 2,048 characters and anything matching your exclude patterns are removed and listed.
  4. Dates. Common date formats become W3C Datetime (2026-09-27). Anything ambiguous is left out rather than guessed.
  5. Escape and split. &, < and quotes are entity-escaped. Files split at 50,000 URLs or 50 MB, and a sitemap index is written.

Does a sitemap make Google index pages faster?

A sitemap is a discovery hint, not an indexing guarantee. Google describes it as a way to tell search engines which URLs you consider important and when they changed. That helps most on large sites, new sites with few inbound links, and sites with many pages that are poorly linked to each other. Google says small, well-linked sites (about 500 pages or fewer) often don't need one, but it never hurts.

What makes a sitemap useful is honesty. List only canonical URLs that return 200 and that you want indexed, and keep lastmod truthful. Google's documentation says it uses lastmod only when it is consistently accurate, and ignores priority and changefreq. The long version is in What is a sitemap?

Questions people ask

Is this XML sitemap generator free, and do I need to sign up?
It is free with no account. Everything runs in your browser, so there is no URL cap beyond what your device can handle; the generator itself splits output at the protocol limit of 50,000 URLs per file.
Why doesn’t SitemapStudio crawl my site for me?
On purpose. Crawling only finds pages that are already linked, which are the pages search engines find anyway. The URLs that most need a sitemap (new, deep or orphaned pages) usually come from your CMS, database, e-commerce export or analytics. Paste or upload that list here and nothing leaves your machine.
Can I upload a CSV of URLs?
Yes. Upload a .csv, .tsv or .txt file (gzip is fine too), or paste columns straight from a spreadsheet. The delimiter and header row are detected, and you choose which column is the URL and which holds the last-modified date.
What happens with more than 50,000 URLs?
The sitemaps.org protocol caps a single file at 50,000 URLs and 50 MB uncompressed. SitemapStudio splits automatically on both limits, writes a sitemap index that lists every file, and gives you a single .zip.
Should I set priority and changefreq?
Google has said it ignores both. They are available under “More options” for other consumers, but off by default. An accurate lastmod is the optional tag that matters. See lastmod, priority and changefreq.
Where do I put the sitemap file?
Normally at the root of your site, such as https://example.com/sitemap.xml. A sitemap can only list URLs at or below its own folder unless you reference it from robots.txt. Then add a Sitemap: line to robots.txt and submit it in Search Console.
How do I generate an XML sitemap?
Get a list of the URLs you want indexed (a CMS or shop export, a crawl, or your current sitemap via “Import a sitemap”), paste or upload it above, check the flagged rows, and download. Upload the file to your site root, add a Sitemap: line to robots.txt and submit it in Search Console. If your CMS already generates one (WordPress, Shopify, Wix), use that and keep this for the URLs it misses.
Is sitemap.xml still relevant?
Yes. Google still documents sitemaps as a primary way to tell it about new and changed URLs, and Search Console’s sitemap report is one of the few places you can see indexing per group of URLs. It matters most for large sites, new sites and pages with few internal links. It doesn’t affect ranking.
How do I find the sitemap.xml of a website?
Check /robots.txt for a Sitemap: line, then try /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml. The sitemap finder does all of that in one step.
Can I edit or merge an existing sitemap here?
Yes. Choose “Import a sitemap”, enter its URL, and its URLs and lastmod dates land in the list. Import a second sitemap to append it, remove or add rows, then download a clean, de-duplicated file, split if needed.
Is my history stored anywhere?
Only in your browser’s localStorage, so you can reopen a recent build. Clear it with one button under History, or on the privacy page.