Xml Sitemap Generator From Url List: Paste URLs, Download sitemap.xml
Reviewed by the OnlineFree.app team · Updated
Key points
- Xml Sitemap Generator From Url List turns a pasted URL list into a downloadable sitemap.xml in your browser, with no crawling and no sign-up.
- The tool trims whitespace, drops blank lines, removes exact duplicates, and rejects anything that is not an absolute http or https URL.
- Google ignores changefreq and priority, so leaving both set to none is often the safest choice for a generated sitemap.
- The sitemaps.org protocol allows at most 50,000 URLs and 50 MB uncompressed per sitemap file.
- Upload the downloaded file to your site root as /sitemap.xml, then reference it in robots.txt or submit it in Search Console.
What does Xml Sitemap Generator From Url List do?
Xml Sitemap Generator From Url List converts a pasted list of URLs into a valid, downloadable sitemap.xml file inside your browser, with no crawling, no sign-up and nothing to install. You bring the URLs; the tool writes the XML.
That split matters. Crawler-based sitemap tools fetch your site and guess which pages exist, which is slow and misses anything behind a login or rendered only by JavaScript. This one starts from the list you already have — a CSV export, a Screaming Frog crawl, a CMS admin table, a spreadsheet a client emailed you — and does exactly one job: wrap each URL in a correct <url> element with the tags you choose.
The layout is a two-pane console: settings on the left, a live syntax-highlighted XML preview on the right with a running URL count and byte size. Change a setting and the file updates immediately, so you can iterate before you download anything.
Paste the list and read the validation summary
Paste one URL per line into the textarea of Xml Sitemap Generator From Url List. The tool trims surrounding whitespace, drops blank lines and removes exact duplicates, comparing the host in lowercase but the path case-sensitively — so https://example.com/About and https://example.com/about survive as two separate entries.
Anything that is not an absolute http:// or https:// URL never reaches the output. Those lines are collected instead in an expandable warning list next to counts for kept URLs, duplicates removed, invalid lines and URLs on other hosts.
That warning list is the fastest sanity check you will get all day. If you pasted 480 rows and the summary says 12 invalid, those 12 are usually relative paths like /pricing, mailto: links, or rows where a spreadsheet formula leaked into the URL column. Fix them in the source list rather than by hand in the XML.
How do you handle URLs from other hosts?
The generator infers your main host from the most frequent host in the pasted list and shows it right next to the host policy select. The default option, warn only, keeps every valid URL and simply flags the outsiders so you can decide.
Choosing drop other hosts keeps only URLs on the inferred host, which is the right call when you pasted a mixed export and want one clean single-site file. The keep all option writes everything into one document, which is convenient but usually wrong: the sitemaps.org protocol requires all URLs in a sitemap to share a single host, and search engines may ignore or reject entries that break that rule.
If you genuinely run two domains, generate two files. Run the list once per host and download each sitemap separately. It costs about ten extra seconds and avoids a submission that quietly gets discarded.
lastmod, changefreq, and priority: what to set
The defaults are deliberately conservative. The lastmod toggle is on with today's date applied identically to every <url>, and both changefreq and priority are set to none, which omits those tags entirely from the file.
Blanket metadata is the trap here. Tagging 5,000 pages with the same date tells a crawler nothing about what actually changed, and as of 2026 Google's sitemap documentation still states that it ignores the priority and changefreq tags altogether. Keep that in mind before you reach for the priority dropdown.
This tool applies one date to every entry, so it fits cases where a single date is genuinely true — a batch of pages published in one migration, for example. If your pages changed on different days, generate the sitemap from your CMS or a script that knows each page's real modification time. Applying 1.0 uniformly to every URL is the same as not prioritising at all, so leaving priority at none is usually the honest choice.
Sitemap limits and common mistakes
The protocol caps a single sitemap at 50,000 URLs and 50 MB uncompressed. The generator will happily format a longer list; the file just will not be accepted as-is, so split oversized lists across several sitemaps and point to them from a sitemap index.
Watch the www and trailing-slash question. If your canonical pages live at https://www.example.com/about/, then https://example.com/about is a different string and belongs in the file only if it is genuinely canonical. Deduplication here is exact-string based, not canonicalisation — the tool cannot know which version your server redirects to.
Also scan for tracking parameters such as ?utm_source=, session IDs, and paginated or filtered URLs you do not want indexed. Every unique string counts as its own URL, so a messy export can triple your file size with near-duplicates that compete against the pages you actually care about.
Where to put sitemap.xml and how to submit it
Use the Download button to save sitemap.xml — the tool writes it as text/xml in UTF-8 with no byte-order mark, which is what you want. Upload it to your site root so it resolves at https://example.com/sitemap.xml, the location crawlers check first.
Then either add a Sitemap: https://example.com/sitemap.xml line to robots.txt or submit the URL directly in Google Search Console and Bing Webmaster Tools. Double-check the live URL in a browser after upload, because a typo in the path is the most common reason a sitemap never gets read.
For the rest of the same workflow — clearing backgrounds, checking that linked PDFs are tagged — OnlineFree.app hosts a set of free browser tools built on the same paste-and-go pattern.
Frequently asked questions
Is Xml Sitemap Generator From Url List free, and where does my URL list go?
Yes, it is free and needs no account. The page processes your pasted list in the browser, so the URLs are not sent to OnlineFree.app to be crawled or stored. Keep a local copy of the list anyway, and avoid pasting URLs containing private tokens or internal staging hostnames, since anything in the preview becomes part of the downloaded file.
How many URLs can one sitemap.xml contain?
The generator will format whatever you paste, but the sitemaps.org protocol limits a single sitemap to 50,000 URLs and 50 MB uncompressed. Exceed either limit and you should split the list into multiple files, then reference them from a sitemap index hosted alongside the individual sitemaps.
Does the tool crawl my site and fill in lastmod automatically?
No. Xml Sitemap Generator From Url List never fetches your pages; it only wraps the URLs you paste in <url> elements. The lastmod toggle adds one date, today's by default, to every entry, and changefreq and priority default to none. Any real per-page dates must come from your CMS or export.
Should I set changefreq and priority values?
Usually not. Google's sitemap documentation states that it ignores both tags, and Bing has said the same. They remain valid XML, so including them will not break the file, but a uniform priority of 1.0 on every URL carries no information. Leave both at none unless another tool in your pipeline reads them.
What happens to invalid or duplicate lines I paste?
They are dropped from the XML and reported. Blank lines and exact duplicates are removed after whitespace trimming, and anything that is not an absolute http:// or https:// URL — relative paths, mailto: links, stray spreadsheet text — appears in an expandable warning panel with a count, so you can fix the source list first.