Base URL
Defaults for every URL
URL table
| # | URL | Last modified | Change frequency | Priority |
|---|
What an XML Sitemap Does
An XML sitemap is a plain file that lists the web addresses you want search engines to know about. It follows the schema published at sitemaps.org: each entry carries one required location and can add optional hints - when the page was last modified, how often it tends to change, and how important it is relative to other pages on the same site. A sitemap does not guarantee that anything is indexed or ranked. It makes discovery easier, which matters most for new sites, deep pages with few inbound links, and very large catalogues.
Because the file is just structured text, it is easy to produce and easy to get subtly wrong. A stray ampersand in a query string, a date written as 10/10/2026, or a priority of 1.5 can make a whole file unreadable to crawlers. This page builds the XML for you and includes a validator so you can check any sitemap, including one generated elsewhere, before you submit it.
How to Use the Generator
Practical Use Cases
Launching a new site. Paste the list of public pages from your CMS export and generate one file before go-live, so search engines have a complete map from the first crawl.
Large catalogues. An online shop with tens of thousands of product pages needs several files. Turn on splitting, set a size per file, and upload the parts together with the index that points at them.
Checking an existing file. Paste a sitemap a developer or plugin produced into the Validate tab. It reports malformed XML, wrong namespaces, out-of-range priorities, invalid dates and duplicate entries, with the offending location named.
Cleaning a messy export. Spreadsheet dumps often contain duplicates, tracking fragments and mixed relative and absolute links. The normaliser removes duplicates, strips #fragments and resolves paths, so the output is consistent.
Protocol Limits at a Glance
| Item | Rule |
|---|---|
| URLs per file | 50,000 maximum. Larger lists must be split and listed in a sitemap index. |
| Size per file | 50 MB uncompressed maximum. |
| Length of one location | 2,048 characters maximum. |
| Last modified | W3C date such as 2026-10-10, or a full timestamp with a time zone such as 2026-10-10T08:30:00+05:30. |
| Change frequency | One of always, hourly, daily, weekly, monthly, yearly or never. |
| Priority | A number from 0.0 to 1.0. When omitted, the protocol default of 0.5 applies. |
| Sitemap index | Up to 50,000 sitemap entries, each pointing at one sitemap file. |
Every location must be entity-escaped XML, so an ampersand is written as & inside the file. The generator does this automatically; hand-written files often miss it.
Frequently Asked Questions
No. The generator never visits your site or any other address. It only reads the list of URLs you paste, tidies it up, and writes the XML. You supply the pages yourself, for example from a CMS export, a server log or a spreadsheet.
Upload sitemap.xml to the root of the host it describes, so it is reachable at a clear address such as https://www.example.com/sitemap.xml. Then submit that address in Google Search Console or Bing Webmaster Tools, or add a Sitemap line to robots.txt. A sitemap is normally honoured only for URLs on the same host it is served from.
The notices above the table explain each case. Lines are skipped when they are empty or start with #, when they are relative paths and no base URL is set, when they use a scheme other than http or https, when they cannot be parsed as a URL, or when the address is longer than 2,048 characters. Duplicate addresses are merged, and #fragments are removed because they do not change the page.
Not in the way many people expect. Search engines treat both as optional hints, and several have said they largely ignore them. The last modified date is more useful when it reflects real content changes, because it helps crawlers decide what to revisit. Only include the fields you can keep accurate.