XML Sitemap Generator
Turn a list of URLs into a valid sitemap.xml.
What you paste
Parsed in your browser — never uploadedHow this reads your output
Each line is parsed as a URL with optional trailing values: a date in ISO format becomes lastmod and a decimal becomes priority. Invalid lines are skipped and counted rather than silently dropped, duplicates are removed, and ampersands in URLs are escaped so the XML stays valid. Two checks run alongside: whether every URL is on the same host, and whether the file stays inside the fifty-thousand-URL limit.
What the results mean
- lastmod
- The only hint here that carries real weight with search engines, and only if it is accurate. A date that changes on every deployment is worse than none.
- Hosts
- A sitemap may only list URLs from the host serving it, unless you have verified ownership of the others. More than one host is usually a mistake.
- Plain HTTP URLs
- Flagged because listing the insecure version of a page you serve over HTTPS wastes crawl budget on a redirect.
Common problems and fixes
- Pages in the sitemap are not being indexed
- A sitemap is a discovery aid rather than a promise, and inclusion does not oblige anyone to index a page. Check the more likely causes first: a noindex directive, a canonical pointing elsewhere, a robots.txt rule blocking the crawl, or a page with genuinely thin content. Internal links matter more for discovery than the sitemap does.
- Search Console reports errors for the sitemap
- The usual causes are URLs that redirect, URLs returning 404, and URLs whose canonical points at a different address. A sitemap should contain only final, canonical, indexable URLs. Everything else dilutes the signal and spends crawl budget on pages you did not want crawled.
Frequently asked questions
Do priority and changefreq do anything?
Very little. Major search engines have said publicly that they largely ignore both, partly because almost every sitemap sets every page to the highest priority. Accurate lastmod dates are the one element that still influences crawling.
Where should the file go?
Anywhere on the same host, though the root as /sitemap.xml is conventional. Reference it from robots.txt with a Sitemap line, and submit it in Search Console, which also reports errors you would not otherwise see.
What if I have more than 50,000 URLs?
Split into several files and create a sitemap index that lists them. The same limits apply per file, and the index itself can hold fifty thousand entries, which is enough for any site that a browser-based tool should be building sitemaps for.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/sitemap-generator/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="XML Sitemap Generator" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/sitemap-generator/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.