Who Benefits From Xml Sitemap Generator From Url List
Reviewed by the OnlineFree.app team · Updated
Key points
- Xml Sitemap Generator From Url List converts a pasted URL list into a valid sitemap.xml in the browser, with no sign-up or install.
- The tool formats the file — it does not crawl, fetch or verify URLs, so broken links must be checked elsewhere.
- Deduplication is case-sensitive on the path, so /About and /about survive as two separate entries in the output.
- A single sitemap.xml can hold up to 50,000 URLs and 50 MB, according to the sitemaps.org protocol.
- Google uses lastmod when it is verifiable and ignores changefreq and priority entirely.
What does Xml Sitemap Generator From Url List do?
It converts a pasted list of URLs into a complete, downloadable sitemap.xml file — no crawling, no sign-up, no install. You supply the URLs one per line and Xml Sitemap Generator From Url List handles the XML scaffold, the urlset namespace, deduplication and validation, then hands you a UTF-8 file with no byte-order mark that you upload to your server as-is.
The layout is split on purpose: controls on the left, a live syntax-highlighted XML preview on the right, with the URL count and byte size above it. Change the host policy or add a lastmod date and the file redraws immediately. That instant loop is the point — you iterate on settings while watching the output change instead of downloading, inspecting and re-checking.
It also assumes something specific about you: you already have the list. That is a design decision, not a missing feature. If your URLs live in a CSV, a Screaming Frog export or your CMS admin, running a crawler first would add minutes of waiting and pull in URLs you deliberately left out.
Who benefits most from a paste-only sitemap tool
The core user is an SEO freelancer or small-site developer holding 50 to 5,000 URLs copied out of a spreadsheet, who needs a spec-valid file within about 30 seconds. They do not want a subscription, a desktop app installed on a client's machine, or a crawler that rediscovers pages they just exported.
Migrations are the second fit. When a site moves from staging to production, the URL list already exists in the redirect map or the old sitemap, so pasting it produces the new file in one pass. The same applies to regenerating a sitemap after a bulk CMS reorganisation, where the admin panel exports canonical URLs directly.
Small sites gain for a less obvious reason: hand-writing XML gets the boring parts wrong. The namespace declaration, the required loc element, ampersand escaping in query strings and the date format are all easy to mistype, and a malformed sitemap fails quietly. It sits alongside the rest of the free online tools we build on one principle: bring your own data, get a correct output, no account required.
How do you paste URLs and get a valid sitemap.xml?
Start with one absolute URL per line in the textarea. The tool trims whitespace, drops blank lines and ignores anything that is not http:// or https://, so a bare example.com/about without a scheme is counted as invalid rather than quietly used.
Then read the validation summary before downloading. It reports four counts: kept, duplicates removed, invalid lines, and other-host lines. Deduplication is case-sensitive on the path with the host lowercased, so https://Example.com/About and https://example.com/about both survive as separate entries. If you want one canonical form, fix the casing in your source list first.
The host policy select comes next. The tool infers your primary host from the most frequent host in the list and shows it beside the select: warn only keeps everything and flags outliers, drop other hosts excludes them from the output, keep all writes every valid line. Choose the middle option when the file must describe a single domain.
Finally set lastmod (on by default, dated today), changefreq and priority, then press Download. The result is text/xml, UTF-8, no BOM — and for a few hundred lines the paste-to-file cycle usually finishes in well under a minute.
Which sitemap tags actually change anything?
Google's documentation is blunt: the search engine ignores changefreq and priority, and it uses lastmod only when the value is consistently and verifiably accurate. As of 2026 that guidance still stands, which shapes how you should treat this tool's three optional fields.
Leaving changefreq and priority at none omits those tags entirely. That is the honest default, because it matches what Google does with them anyway. Other consumers, including Bing, Yandex and some internal SEO dashboards, still read the values, so they are not worthless — just not the ranking lever people assume.
The lastmod date deserves more thought. The tool stamps the same date on every url entry, which is only truthful if the whole set really changed that day. If your pages have genuinely different modification dates, generate the file from your CMS or post-process the download, and if you cannot keep the date honest, switch lastmod off rather than backdating it.
Common mistakes that break sitemap files
The most frequent problem is host drift: half the list on https://www.example.com, half on https://example.com, plus a few http:// leftovers. To a search engine those are different URLs. Check the other-host count in the validation summary and normalise your list before generating.
The second is the wrong list entirely. Because nothing is crawled or fetched, nothing stops you pasting 404s, staging URLs or noindexed pages. The generator will produce a flawless file full of pages you never wanted indexed, so review the list, not just the XML.
The third is size. The sitemaps.org protocol allows up to 50,000 URLs and 50 MB uncompressed per sitemap file; past that you split the list and point to the parts from a sitemap index. The byte count next to the preview gives early warning: a 5,000-URL list is nowhere near the cap, a 100,000-line export needs splitting.
The fourth is hand-editing after download. Query strings containing & must appear as & in XML, and some text editors silently add a byte-order mark that strict parsers reject. Generate the file rather than patching it.
How do you publish and verify the file?
Upload sitemap.xml to your site root so it resolves at https://example.com/sitemap.xml, add a Sitemap line to robots.txt pointing at that full URL, and submit the same URL in the Sitemaps report of Google Search Console and, if you care about Bing, in Bing Webmaster Tools.
The report tells you whether the file was read and how many URLs were discovered. It does not promise that every URL gets indexed, so treat a Success status as confirmation that the file parses and was fetched, and nothing more.
For freelancers managing several sites, keep one sitemap per host and set host policy to drop other hosts each time. Verification is also per-artefact: if your site publishes PDFs, run them through the PDF Accessibility Checker and check each file on its own terms, because a parser-valid sitemap says nothing about the quality of the pages it lists.
Frequently asked questions
Is Xml Sitemap Generator From Url List free, and do I need an account?
It is free and needs no account, install or email sign-up. You paste your URLs, the XML is assembled instantly, and you download sitemap.xml straight away. Because there is no server-side queue or crawling step, the paste-to-download cycle typically finishes in seconds even for a few thousand lines.
Does Xml Sitemap Generator From Url List crawl my site or check that the URLs work?
No. The tool never fetches your site or sends requests to the URLs you paste; it only formats the list into valid XML. That means broken links, redirects and 404s are invisible to it. Check status codes separately with your own crawler or Search Console before submitting the file.
How many URLs can one sitemap.xml file hold?
The sitemaps.org protocol caps a single sitemap at 50,000 URLs and 50 MB uncompressed. Past that limit you split the list into several files and point to them from a sitemap index. For most small sites and freelance projects, one file covering 50 to 5,000 URLs is comfortably inside the limit.
Should I include lastmod, changefreq and priority values?
Google uses lastmod when it is consistently accurate and ignores changefreq and priority, so leaving those two set to none is usually the safer choice. This tool applies one lastmod, changefreq and priority value to every URL, so a single date only makes sense if all pages genuinely changed that day.
Where do I put the downloaded sitemap.xml file?
Upload it to your site root so it resolves at https://example.com/sitemap.xml, reference that URL in robots.txt, then submit it in Google Search Console and Bing Webmaster Tools. Submission tells search engines the file exists; it is not a guarantee that every listed URL will be indexed.