Drag-n-Drop
to upload your archive
Sitemap Generator
Build an XML sitemap from a list of URLs
Paste the URLs you want indexed, one per line, and get a valid sitemaps.org XML file you can upload to your site root and submit to Google Search Console. No crawling, no waiting, no account. Everything runs in your browser, so your URL list never leaves your computer.
Absolute URLs are used as-is. Bare paths like /about are resolved against the base domain below. Blank lines and lines starting with # are ignored, and repeated URLs are removed automatically.
Only needed if your list contains relative paths. Every URL in one sitemap must live on the same host as the sitemap file itself.
Default values for every URL
These fill the optional <lastmod>, <changefreq> and <priority> tags. Leave any of them on “Omit” if you would rather ship a lean sitemap with nothing but <loc> tags.
Per-URL values
Leave a row on “Default” to follow the values above
Split your URL list into files named sitemap-1.xml, sitemap-2.xml and so on, upload them next to this index, and submit only the index in Search Console.
-
Valid sitemaps.org 0.9 output
You get the exact document Google, Bing and Yandex expect: an XML declaration, the
urlsetnamespace, and one<url>block per address, indented two spaces so it stays readable in a diff. -
Query strings escaped correctly
A raw
&inside a<loc>tag makes the whole file unparseable, which is the single most common reason a sitemap gets rejected. Every ampersand, angle bracket and quote is escaped for you. -
Nothing is uploaded
The generator does not crawl your site and does not send your URL list anywhere. It reads the textarea, builds the XML in JavaScript, and hands you a file. Safe for staging URLs and unreleased pages.
How to generate an XML sitemap
-
1
Paste your URLs into the box, one per line. Add a base domain if your list uses relative paths like
/pricing. -
2
Pick your defaults, then click Generate sitemap. Tick “Edit values per URL” if a few pages need their own settings.
-
3
Download
sitemap.xml, upload it to your site root, and submithttps://yourdomain.com/sitemap.xmlin Search Console.
What actually matters inside a sitemap
-
lastmod is the one Google reads
Google has said it uses
<lastmod>as a recrawl signal, but only while it stays honest. If every URL claims today's date on every deploy, the field is discounted and stops helping. Set it to the day the page content genuinely changed, or omit it. -
changefreq and priority are hints, not orders
Google ignores both. They remain part of the 0.9 protocol and other crawlers still read them, so the tool supports them fully, but setting every page to
dailyand1.0buys you nothing. That is why both default to “Omit” here. -
50,000 URLs and 50 MB per file
One sitemap file may hold at most 50,000 URLs and 50 MB uncompressed. Past either ceiling you split the list across numbered files and list those in a sitemap index. This tool watches both limits and hands you a starter index when you cross one.
Built your sitemap? Publish the site it describes with free static hosting
Select File
or drop your archive to upload
Frequently asked questions
What is an XML sitemap?
An XML sitemap is a file listing the URLs on your site that you want search engines to know about, together with optional hints such as when each page last changed. It does not guarantee indexing, but it makes discovery reliable, which matters most for new sites, large sites, and pages that are not well linked internally.
Does this tool crawl my website?
No, and that is deliberate. You paste the URLs you want included, which means you decide exactly what goes in the file instead of hoping a crawler guessed right. It also means the whole thing runs in your browser with nothing uploaded, and it works for sites that are not published yet.
How many URLs can one sitemap hold?
A single sitemap file may contain at most 50,000 URLs and must not exceed 50 MB uncompressed. Beyond that you split it into several files and list them in a sitemap index file. The tool counts your URLs and warns you before you cross either limit.
Do changefreq and priority do anything?
Very little. Google has stated it ignores both. lastmod is the one optional field it does use, and only when the dates are consistently accurate, so set it honestly or leave it out. Other engines may still read changefreq and priority, which is why the fields are here, but do not expect ranking effects from them.
Which URLs should I leave out?
Exclude anything you would not want as a search result: redirects, pages that return errors, URLs blocked by robots.txt, pages marked noindex, and non-canonical duplicates. A sitemap full of URLs that do not resolve to indexable canonical pages sends mixed signals. Use one absolute URL per page, matching the canonical exactly, including the trailing slash.
How do I submit my sitemap?
Upload sitemap.xml to your site root, add a Sitemap: line to your robots.txt, then submit the URL in Google Search Console and Bing Webmaster Tools. Search Console will report how many of the listed URLs it actually indexed, which is a useful diagnostic on its own.
Do I need to escape characters in URLs?
Yes, and the tool does it for you. Ampersands and angle brackets in query strings must be XML-escaped, so ?a=1&b=2 becomes ?a=1&b=2 in the file. Forgetting this is the single most common reason a hand written sitemap fails validation. You can inspect the output with our XML Viewer.
How often should I regenerate it?
Whenever you add, remove or meaningfully change pages. For a small static site that is usually at deploy time. Regenerating a sitemap on a schedule when nothing changed is pointless, and bumping every lastmod date to today when the content did not change teaches Google to stop trusting the field.