For a small site, a carefully reviewed URL list can be the starting point for a sitemap. The XML Sitemap Generator turns that list into an XML document with a urlset and one loc element per unique normalized address. It does not crawl a website or decide which pages belong in the list.
Supply absolute addresses from one origin
Paste complete page URLs into Absolute page URLs, one per line, then choose Generate result. Each address must use HTTP or HTTPS and contain no embedded credentials. Relative paths such as /about are rejected because the generator has no base URL field to resolve them against.
Keep the list to one site origin: scheme, host, and port must match. https://example.com/ and https://www.example.com/ are different origins for this check. So are HTTP and HTTPS versions. The tool accepts up to 5,000 unique URLs in one operation, which is its own processing limit rather than a statement of every sitemap protocol limit.
Follow normalization and escaping
Try these three lines:
https://example.com
https://example.com/
https://example.com/search?a=1&b=2The first two normalize to the same address, https://example.com/, so the result contains two URL entries. The search address is represented in XML as https://example.com/search?a=1&b=2. The & is required markup escaping produced by the generator; it does not mean the destination’s parameter names have changed.
The implementation trims each line, discards blank lines, normalizes with the browser’s URL parser, and removes exact duplicates after normalization. The first occurrence determines the retained order. It does not treat every visually similar path as identical, so /about and /about/ can remain separate entries.
Check the list before publishing
Use pages you have independently confirmed are the intended public destinations. The tool does not fetch them, follow redirects, evaluate canonical tags, or check indexing eligibility. Query strings and fragments are not automatically removed. Review whether each supplied address is actually the version you want to publish in a sitemap.
Download sitemap.xml and integrate it through your site’s normal deployment process. The generated document includes location elements only; it does not add modification dates, alternate language links, images, or other extensions. Those fields need a workflow that has reliable source information.
Processing takes place in the browser without an account connection. Keep private or token-bearing URLs out of a file intended to be public. After deploying the sitemap, you can reference its public address in a file prepared with the Robots.txt Generator.