This page turns a list of addresses into an XML sitemap. Paste one URL per line, choose whether to add a last-modified date, a change frequency and a priority, and the generator writes the XML, removes duplicates, strips fragments and rejects lines it cannot use.
It does not crawl your site. The list is the input, so the sitemap contains exactly the URLs you paste and nothing else. That makes it predictable and fast, and it also means an out-of-date list produces an out-of-date sitemap.
What the generator does to each line
A line is trimmed and, if it contains a comma, cut at the first comma. That makes a pasted CSV work, with the URL in the first column, but it also means anything after a comma is silently dropped. Do not use a comma inside a URL.
A bare domain such as toolshub4u.com/page gets https:// added. A line with a space is rejected, because a space is not valid in a URL. A line with a scheme other than http or https is rejected. A fragment is counted and removed, because /page#section points at a part of a page, not a separate URL.
Duplicates are removed after normalisation, so the bare-domain version and the https version of the same address collapse into one. The output is limited to 50,000 URLs, the limit for a single sitemap file. The file size is checked against 50 MB.
A worked example
Six lines were pasted: a homepage, a section index, a bare-domain page, the same page with a fragment, a PDF tool page and a second copy of the homepage. The result was a sitemap with four URLs, two duplicates and one fragment cleaned, at 824 bytes.
| Input | Result |
|---|---|
https://toolshub4u.com/ | Kept |
https://toolshub4u.com/tools/seo-tools/ | Kept |
toolshub4u.com/tools/seo-tools/keyword-density-checker.html | Kept, https added |
https://toolshub4u.com/tools/seo-tools/keyword-density-checker.html#faq | Fragment removed, then counted as a duplicate |
https://toolshub4u.com/tools/pdf-tools/merge-pdf.html | Kept |
https://toolshub4u.com/ | Duplicate, removed |
The fragment line explains why the summary says two duplicates and one fragment when only one line was an exact duplicate. Once the fragment was removed, that URL matched the bare-domain page from the line above, so it was counted in both totals. The sentence is accurate in its numbers and clumsy in its grammar: 2 duplicate and 1 fragment URLs cleaned.
The optional lastmod was set to 2026-10-01 and was accepted, so every entry carried the same date. A single date for a whole site is rarely accurate. Google uses lastmod only when it is consistently and verifiably correct, so a blanket build date is worse than leaving the tag out.
Index mode is not a full sitemap index
The index option does not build an index of several sitemaps. It takes the first URL in the list, replaces the last path segment with sitemap.xml and writes a single <sitemap> entry containing that one location. The rest of the list is ignored.
In the test, two URLs were pasted and the file contained one entry, https://toolshub4u.com/sitemap.xml. The status still said Built a sitemap with 2 URLs and the stats counted two, because those numbers describe the input, not the output. If you need a real index, list each child sitemap and build the index by hand or with a server-side tool.
Priority and change frequency are not written in index mode. Only lastmod is carried into the <sitemap> entry, which is the correct shape for an index.
<sitemap> elements before uploading.lastmod, changefreq and priority
Google ignores <priority> and <changefreq>. They are part of the sitemaps protocol and other systems may read them, but they do not influence Google's crawl or ranking. Writing them is harmless and can make a file look more complete than it is.
<lastmod> is the one optional value Google uses, and only when it is reliable. The date should reflect a significant change to the page, such as new content or updated structured data, not a template change or a copyright year. If you cannot maintain it per URL, leave it out.
The generator accepts YYYY-MM-DD or a full ISO 8601 timestamp. Anything else is omitted and the checklist warns. Priority is written only when it is greater than 0 and at most 1, rounded to one decimal place; leave it at 0 to omit it.
Rejected lines and CSV input
Four lines were pasted in a second test: not a url, an ftp address, a URL containing a space and one valid https URL. Three were rejected and listed with a reason, and the sitemap contained only the valid page. The same run used 01/10/2026 as the lastmod, which is not an accepted format, so the tag was left out of the file.
Rejected lines are not guessed at. A typo becomes a missing URL, not a wrong one, which is the safer failure. Read the rejected list before uploading; a sitemap that silently omits a section is harder to notice later.
The comma rule is the other quiet failure. A CSV with URL,lastmod,priority will use the URL and ignore the other two columns, and every entry will get the same settings from the form. If you need per-URL dates, build the file elsewhere or edit the XML.
Publishing and checking
Save the output as sitemap.xml and put it at the site root. A sitemap in a subdirectory only affects URLs below that directory unless you submit it through Search Console, so the root is the simplest choice. Add a Sitemap: line to robots.txt or submit the file directly in Search Console or Bing Webmaster Tools.
Submitting directly gives you processing feedback that a robots.txt line does not. A sitemap is a hint, not a guarantee: Google may choose not to download it or not to crawl every URL in it. Check the report after a few days rather than assuming success.
Finally, compare the sitemap with what crawlers actually request. The log file analyser shows whether listed URLs are being fetched and whether any return errors. A sitemap full of 404s is a signal to fix the list, not to submit it again.