Text & web utilities

XML sitemap generator and editor

Create editable escaped sitemap XML from a same-origin URL list with optional metadata and a direct file download.

Your settings

Calculated on your device. Your inputs aren’t sent to us.

Your result

Ready when you are

Enter your inputs and select Generate code.

Report an issue

Try it, understand it

Explore the result

Compare explicit settings below. Examples generate local output; external previews, requests and provider navigation remain separate actions.

Worked example comparison
ExampleOutputWhat to notice
Two complete entriesUnique page URLs2The output includes optional metadata only where provided.
Only required locationsUnique page URLs2Optional metadata is omitted.
Query escapingUnique page URLs1The ampersand is escaped in XML and preserved on parsing.

Check your understanding

Does priority 1 guarantee a better ranking?

No. It is optional metadata and is not a ranking guarantee.

Do I need to fill every metadata column?

No. Leave unknown optional values blank. Each entry still needs its complete URL.

Behind the tool

How this tool works

Enter one complete URL per line. Optional pipe-separated columns are a calendar last-modified date, a supported change frequency and a priority from zero through one. Edit or delete a line to change an entry, or use Add row. The output escapes XML characters and can be copied or downloaded as sitemap.xml.

THE OUTPUT RULEUnique absolute URLs with optional truthful metadata → UTF-8 XML urlset

A worked example

Two example.com URLs create two url elements under the sitemap namespace. An ampersand in a query is written as & in XML and becomes an ordinary ampersand when parsed. Duplicate URLs and mixed origins are rejected before download.

Good to know

This editor does not crawl a website, discover hidden routes or submit anything to an engine. It supports 10,000 entries and 2,000,000 input characters, below the protocol’s larger file limits. Optional priority and changefreq do not guarantee ranking or recrawl timing. Use actual page-change dates rather than today’s date everywhere.

A little curiosity

The smallest accurate sitemap is useful

Absolute canonical URLs help avoid ambiguity about hostname, scheme and path. Keep one origin in this generated file and omit fragment identifiers, which refer to locations within a page rather than separate crawlable documents. Check that the intended destination returns a useful page before listing it.

The sitemap URL extractor can read the downloaded XML back into a table and verify the entry list. That round trip checks document structure and escaping, not whether a search engine has accepted, crawled or indexed the pages. A valid file is one part of discovery rather than an indexing command.

Keep optional metadata honest and maintenance simple

A lastmod date should reflect a meaningful change to the page. Updating it automatically every time a build runs obscures that information. Leave optional values blank when you do not have a defensible value; the loc element is the essential entry field.

Download the file and place it at a path your hosting serves as XML. Test the public URL after deployment, then reference it from robots.txt or submit it through the engine’s webmaster interface. When the file grows, update the same public location rather than creating a new submission for every added page.

A few questions, answered

Does priority 1 guarantee a better ranking?

No. It is optional metadata and is not a ranking guarantee.

Do I need to fill every metadata column?

No. Leave unknown optional values blank. Each entry still needs its complete URL.

Find your calculator

Start typing to explore the library.