Xml Sitemap Generator From Url List: Tips and Common Mistakes
Reviewed by the OnlineFree.app team · Updated
Key points
- Xml Sitemap Generator From Url List turns a pasted URL list into a valid sitemap.xml without crawling or an account.
- Invalid lines never enter the output; they appear only in the validation warning list.
- Duplicates are removed with a lowercase host but a case-sensitive path, so /About and /about both survive.
- One lastmod, changefreq and priority value is applied to every URL, so use none when unsure.
- The sitemap protocol caps files at 50,000 URLs and 50 MB; the preview shows both counts.
What Xml Sitemap Generator From Url List produces
It converts a pasted list of absolute URLs into a valid, downloadable sitemap.xml in seconds — no crawling, no site fetch, no account. You paste one URL per line and the live preview pane shows the exact XML that will be saved, alongside the URL count and the file's byte size.
The layout is deliberately two-pane: controls on the left, syntax-highlighted XML on the right. That matters because the value is the feedback loop — you change the host policy, lastmod date, changefreq or priority, and you watch the file update before you download it. Output is UTF-8 with no BOM and served as text/xml, which is what search engines expect from an XML sitemap.
By default the tool warns about URLs on other hosts but keeps them, adds today's date as lastmod, and omits changefreq and priority entirely. Everything is processed in the browser as part of OnlineFree.app, so there is nothing to install and no sign-up step.
How do you turn a URL list into sitemap.xml?
Paste your URLs into Xml Sitemap Generator From Url List, one absolute URL per line, starting with https:// or http://. The tool trims whitespace, drops blank lines, and removes duplicates before anything reaches the XML — invalid lines never enter the output, they only appear in the warning list.
Then read the validation summary before you download. It reports four counts: kept URLs, duplicates removed, invalid lines, and URLs on other hosts. Expand the offending lines, fix them in your source spreadsheet or Screaming Frog export, and paste again. This is faster than re-exporting a whole crawl.
Next, decide the host policy. The tool infers your main host from whichever host appears most often in the list and displays it next to the select control. "Warn only" keeps everything and flags the strays, "drop other hosts" removes them, and "keep all" stays silent. Finally set lastmod if you want it, choose changefreq and priority or leave both as none, then hit Download or Copy.
If you are re-generating the same file for a large site, Xml Sitemap Generator From Url List behaves identically — same paste, same download — so it fits a repeatable monthly workflow rather than a one-off.
Common mistakes when pasting URL lists
The most frequent problem is relative URLs. Lines like /about or about-us are not absolutes and will be rejected, because a sitemap entry must be a full URL including scheme and host. CSV exports often carry stray commas, quotes or a byte-order-mark character on the first line, which makes line one invalid while the rest look fine.
Mixed http and https, and mixing www with the non-www version of the same host, are the second most common issue. They are different hosts as far as the tool is concerned, so your host inference can land on the wrong one if most of your list uses a variant you did not expect. Normalise the list to one host and one scheme before pasting — this is usually a find-and-replace in your editor.
Deduplication is case-sensitive on the path but lowercases the host. That means https://example.com/About and https://example.com/about are treated as two different pages and both kept, which is the behaviour you want on a case-sensitive server. Duplicate URLs produced by pagination or tracking parameters, however, are real duplicates worth removing in the source list.
Finally, remember the tool does not encode anything for you beyond what is valid XML. URLs containing spaces, raw ampersands or non-ASCII characters should already be percent-encoded or supplied as clean UTF-8 before you paste.
Should you set lastmod, changefreq and priority?
Set lastmod only when the date is genuinely accurate, because Google has said it uses lastmod when it is consistently trustworthy and ignores it when it is not. Leave changefreq and priority as none unless you have a specific reason; Google has publicly stated it ignores both, and the sitemaps.org protocol treats them as optional hints.
The honest limitation here is that the tool applies one lastmod value to every <url> in the file. If your homepage changed today but 400 blog posts changed at various dates last year, a single date of today is false for those 400 entries. Either toggle lastmod off, or edit the downloaded file to set per-URL dates from your CMS data.
The same logic applies to priority and changefreq: one value is written to every entry, not a per-URL value. For a small site where everything is roughly equal, that is fine and keeps the file small. For a large site with clearly different sections, generating a few separate files by section — each with its own settings — is usually cleaner than one flat file.
There is no penalty for omitting these tags. A minimal sitemap containing only <loc> elements, properly escaped, is fully valid and is often the most defensible option.
Watch the 50,000-URL and 50 MB limits
The sitemap protocol caps a single file at 50,000 URLs and 50 MB uncompressed. Because the preview reports both URL count and byte size, you can see when you are approaching either ceiling before you download rather than after a search engine rejects the file.
When you cross the limit, split the list and generate two or more sitemap files, then create a sitemap index listing them. The tool produces individual sitemaps, not an index, so that final index step is manual — but it is only a handful of <sitemap><loc> entries pointing at your split files.
Also keep every URL in a sitemap on the same host as the sitemap file itself. That is why the host policy select exists: a handful of stray URLs from a staging domain or a sister site can make an otherwise fine file confusing to debug.
Submitting your sitemap and verifying it
Download sitemap.xml, place it at your site root, and reference it in robots.txt with a line such as Sitemap: https://example.com/sitemap.xml. You can also submit the URL directly in Google Search Console; Bing and other engines accept the same robots.txt reference.
Verify in two places. First, open the file in a browser and confirm the URL count matches your validation summary. Second, check the sitemap report in Search Console after a few days to see whether the discovered URL count lines up. Expect small differences — redirects, canonical tags and noindex rules all change what gets indexed.
Be realistic about what a sitemap does. It tells search engines which URLs exist; it does not guarantee crawling, indexing or ranking. If your list contains redirecting URLs or pages marked noindex, the sitemap is simply not the right place for them, and the validation summary in the tool will not catch that for you because it never fetches your pages.
For accessibility or document-related files, use a dedicated checker such as the PDF accessibility checker rather than trying to validate them through a sitemap workflow.
Frequently asked questions
Does Xml Sitemap Generator From Url List crawl my site to find URLs?
No. It never fetches your site and never discovers pages for you — you supply the URL list, one absolute URL per line. If you need discovery, export URLs from a crawler such as Screaming Frog or from your CMS admin, then paste that list into the tool. This makes it fast and predictable, but it also means the output is only as complete as the list you paste.
Is Xml Sitemap Generator From Url List free, and do I need an account?
It is free to use and requires no account, no email and no installation. The generator runs in your browser as part of OnlineFree.app, produces a UTF-8 sitemap.xml with no BOM, and gives you Download and Copy buttons on the result. There is no paid tier to unlock extra URL capacity, only the protocol limits of 50,000 URLs and 50 MB per file.
Does it submit the sitemap to Google for me?
No. The tool's job ends at producing a valid file. You download sitemap.xml, host it on your domain, and either add a Sitemap: line to robots.txt or submit the URL manually in Google Search Console. Submission is a separate step that requires access to your own verified property, which a browser-based generator cannot and should not have.
Are the URLs I paste sent to a server?
The generator processes the list in the browser page, so pasting and previewing do not require an upload step. Even so, treat any web tool with normal caution: do not paste private staging URLs, signed links, or anything containing credentials. If your URL list itself is sensitive, test with a small subset first and confirm the output before pasting the full list.
Can I set a different lastmod date for each URL in the file?
Not through the controls. The lastmod toggle applies one date, today by default, to every <url> element in the output. If your pages were updated on different dates, either toggle lastmod off completely or download the file and edit the <lastmod> values manually to match your CMS timestamps. Honest, consistent dates matter more than having the tag at all.