What a Sitemap Is For
A sitemap is a structured list of the addresses you want search engines to discover. The format is defined at sitemaps.org and is read by the major search engines, which use it as a shortcut to pages that might otherwise be found slowly or not at all. Each entry needs a location. It may also carry a last modified date, a change frequency and a priority, but these are optional hints rather than instructions.
The companion page has two tabs. Build cleans the list you paste, lets you adjust each row, and writes the XML. Validate reads a sitemap you already have and lists the protocol problems it finds. Both run in your browser, and the tool never fetches your pages.
Control by Control
The Build tab is divided into groups, from the top of the page down. Here is what each control does and what it writes to the file.
Base URL
The Site address field turns relative paths such as /pricing into full addresses. Enter it with its protocol. A bare domain such as www.example.com gets https:// added, and anything that is not http or https is flagged in red. The base also decides which folder the sitemap index points into.
URLs, one per line
The box accepts full addresses, bare hostnames and relative paths. Blank lines and lines beginning with # are ignored. Load example fills a sample list, and Clear list empties the box and removes any per-row edits.
Defaults for every URL
Last modified sets the date written to lastmod for rows without their own date. Change frequency offers the values from always to never, or a blank choice that writes nothing. Priority must be from 0.0 to 1.0; any other value turns red and the default of 0.5 is used. Apply to all rows discards every per-row edit.
Options
The three Write checkboxes decide which tags appear in the XML. Switching one off hides that tag for every entry, but the table keeps showing the values. Sort A-Z orders entries by full address. Split into multiple sitemaps enables Max URLs per file, a whole number from 1 to 50,000. Splitting happens only when the list is longer than that size.
Notices
The notices area sits between the options and the table. Red items are errors that stop a line being used, amber items are warnings, and blue items are information such as the number of duplicates removed.
URL table
Each valid address is a row with a date picker, a change-frequency menu, a priority box and a remove cross. Editing a field records an override and marks the row with a small dot. Removing a row deletes every raw line in the box that resolves to that address. The table shows at most 300 rows.
Output
The output box shows the selected file. When you split a list, a File menu and one button per file appear. Copy and Download sitemap.xml act on the selected file, and the statistics line gives the URL count and the file size.
Validate tab
Paste a sitemap or index into the Sitemap XML box, or press Use the generated sitemap to check the file you just built. The summary counts errors and warnings, and each finding names the location it refers to.
Worked Examples
Example 1: cleaning a short list
Set the base to https://www.example.com/, set the default last modified date to 2026-10-01, keep the default weekly frequency and 0.5 priority, and paste these five lines:
/ /about /about#team /blog/ /about
The notice reads "2 duplicates removed - 1 #fragment stripped." The line /about#team loses its fragment and becomes a second copy of /about, and the final /about is a plain duplicate. Three URLs remain. If you then set the row for /blog/ to daily with priority 0.8, the generator writes this file:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.example.com/</loc>
<lastmod>2026-10-01</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://www.example.com/about</loc>
<lastmod>2026-10-01</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://www.example.com/blog/</loc>
<lastmod>2026-10-01</lastmod>
<changefreq>daily</changefreq>
<priority>0.8</priority>
</url>
</urlset>
The override changes only its own row, and priorities are always written with one decimal place.
Example 2: splitting into parts
Take the three addresses above, tick Split into multiple sitemaps and set Max URLs per file to 2. The output is two sitemap files and an index: sitemap-1.xml holds the first two addresses and sitemap-2.xml holds the last one. The statistics line reads "3 URLs across 2 sitemap files plus 1 index", and the notice names the folder the index points into. The index looks like this, dated the day you generate it:
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://www.example.com/sitemap-1.xml</loc>
<lastmod>(today's date)</lastmod>
</sitemap>
<sitemap>
<loc>https://www.example.com/sitemap-2.xml</loc>
<lastmod>(today's date)</lastmod>
</sitemap>
</sitemapindex>
Only the index is submitted to search engines; the parts are discovered through it.
Example 3: catching an invalid priority
Paste a complete sitemap into the Validate tab with one entry containing <priority>1.5</priority>. The summary reads "1 error", and the finding names the entry, for example <url> #1 (https://www.example.com/page), and reports that the priority "1.5" must be a number from 0.0 to 1.0. Change it to 0.8 and the error disappears.
A raw ampersand is a more common problem. An address such as https://www.example.com/shop?a=1&b=2 must be written with & in the file. If it is not, the browser's XML parser rejects the whole document, and the validator reports that the file is not well-formed. The Build tab escapes these characters for you.
Tips and Common Mistakes
Frequently Asked Questions
A sitemap is most valuable when a site is new, very large, has many pages with few links pointing at them, or has content that changes often. A small site with a clear menu and strong internal links can often be crawled without one. Even then, a sitemap costs little and gives search engines an explicit list of the pages you consider public.
The file can hold them, but search engines normally honour a sitemap only for addresses on the host where it is served. Make one sitemap per host, and list each one in that host's robots.txt or submit it separately in the webmaster tool for that property.
Build takes a list of addresses and produces a new sitemap file. Validate reads an existing sitemap or sitemap index and reports problems such as malformed XML, a missing namespace, an invalid date or priority, duplicate locations or unexpected elements. It does not fetch the file from your server, so paste its contents.
A fragment, the part after a # sign, tells the browser where to scroll inside a page; it does not identify a different document. Keeping fragments would list the same page several times, so the tool strips them before removing duplicates.