Sitemap Generator
Paste one URL per line, pick a default change frequency, priority and whether to stamp today's date as <lastmod>, and get a valid sitemap.xml — checked against the sitemaps.org schema, ready to copy or download.
Nothing is uploaded: the URLs you paste and the XML this page builds never leave your browser tab — there's no server involved, and the download link is a local data: file built on the spot.
What counts as a valid line
Each non-blank line must be a complete, absolute URL starting with http:// or https:// — for example https://example.com/pricing, not /pricing or example.com/pricing. Blank lines are skipped silently; anything else that isn't a valid absolute URL is flagged, not dropped — you'll see exactly which line and why, so you can fix your list instead of ending up with a sitemap that's silently missing pages. The sitemaps.org protocol also caps each <loc> at 2,048 characters, so an over-length line is flagged too. Valid URLs are normalised (scheme lower-cased, spaces and other special characters percent-encoded) the way a browser's own URL parser would, before being written into the XML.
- If I set changefreq to "daily", will search engines really crawl the page every day?
- No. The sitemaps.org protocol is explicit that this value "is considered a hint and not a command" — crawlers "may consider this information when making decisions", but the spec itself warns they "may crawl pages marked 'hourly' less frequently than that, and they may crawl pages marked 'yearly' more frequently than that." Priority works the same way: it only ranks a site's own pages against each other and, per the spec, "does not affect how your pages are compared to pages on other sites."
- Where does the finished sitemap.xml file go, and does it matter which host the URLs use?
- Upload it to your site — commonly the root, e.g.
https://example.com/sitemap.xml— then tell search engines it exists by adding one line to yourrobots.txt, in the exact form the protocol gives:Sitemap: https://example.com/sitemap.xml. The protocol also requires that "all URLs in a Sitemap must be from a single host" and "use the same protocol… and reside on the same host as the Sitemap" itself — so URLs on different domains, or a mix ofhttpandhttps, belong in separate sitemap files rather than one. - Is there a limit to how many URLs one sitemap file can hold?
- Yes — the protocol caps "each Sitemap file that you provide" at "no more than 50,000 URLs" and "no larger than 50MB (52,428,800 bytes)". Larger sites split their URLs across several sitemap files and list those files in a separate sitemap index file. This generator produces one sitemap file, so keep each paste under that limit.
FAQ
Sources
Method: this page calls no external service and stores nothing. It validates each pasted line as an absolute http/https URL, normalises it with the browser's own URL parser, checks the result is under 2,048 characters, then writes it into the <urlset> / <url> / <loc> structure the sitemaps.org protocol defines, adding whichever <lastmod>, <changefreq> and <priority> tags you chose. Every field name, allowed value and limit below comes from that protocol document.
- sitemaps.org — Sitemaps XML format — the
urlset/url/loc/lastmod/changefreq/priorityschema and thexmlns="http://www.sitemaps.org/schemas/sitemap/0.9"namespace; W3C Datetime (YYYY-MM-DD) format forlastmod; the seven changefreq values; the 0.0–1.0 priority range with a 0.5 default; the "hint and not a command" wording for changefreq and priority; the single-host / same-protocol rule; therobots.txtSitemap:line; the 2,048-character<loc>limit; and the 50,000-URL / 50MB per-file limit.