How to use Sitemap XML Generator and Validator
- Choose Build a sitemap and enter full HTTP(S) URLs, one per line. Start with url,lastmod for CSV with individual dates. Choose Check XML instead to inspect an existing sitemap.
- For a build, set the eventual published directory ending in /. Blank uses the first accepted URL’s site root; all page URLs must share its host/protocol and lie within that directory.
- Use accurate last-modified dates or leave them out. A global date fills entries without a per-row date. Google ignores the optional priority/change-frequency hints.
- Set Addresses per file to split the accepted set, or keep 0 for one file. Generate and inspect skipped lines, XML and absolute index locations.
- Download the XML/index and optional gzip copies. Keep referenced filenames and their eventual URLs consistent; this page neither hosts nor submits them.
Example: Sitemap XML Generator and Validator
Build one sitemap from the three supplied same-site URLs without optional dates or hints.
Options
- What to do
- Build makes a sitemap from a list. Check reads sitemap XML you paste.
- Addresses, one per line
- Used by Build. One full http or https address per line. A first line of url,lastmod switches this box to CSV, so every row can carry its own date. The build reads a list you supply; it never crawls a site.
- Last modified (optional)
- Applied to every address in the built sitemap. Leave empty to omit it.
- Change frequency (optional)
- Google ignores this hint, so leaving it out keeps the file smaller.
- Priority (optional)
- Google ignores this hint, so leaving it out keeps the file smaller.
- Addresses per file
- Used by Build. 0 writes one file. A higher number writes that many addresses per file and adds a sitemap index; one file never holds more than 50,000.
- Sitemap XML to check
- Used by Check. The reader handles the sitemap subset only and never fetches these addresses.
- Published sitemap directory (optional)
- Enter the HTTP(S) directory ending in / where you will publish the files. Pages must use the same host and protocol and be within that directory. Blank uses the first listed URL’s site root. Review absolute index locations before publishing.
Supported inputs and limits
- Build: up to 10,000 entries within 500,000 input characters, at most 25 output chunks and no more than 50,000 URLs per file.
- HTTP(S) URLs must be within 2,048 characters, encoded without spaces/fragments and share the declared directory’s host/protocol/path scope.
- Check: up to 500,000 XML characters, 200,000 elements and 50 levels.
- Supports the stated urlset/sitemapindex subset with loc, lastmod, changefreq and priority; standard entities/CDATA are read, but DTDs, custom entities and namespace prefixes are refused.
More details
No crawl, submission, image extension, full XML-schema or live canonical/indexability validation.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
What a sitemap can and cannot say
A sitemap is an index of addresses, not a publishing step. It helps a crawler find URLs and read a last modified date, and search engines treat that as one input among many. Listing an address cannot make a thin or blocked page indexable, and leaving an address out does not remove it from results when other pages link to it. After you upload the file, confirm it loads at the address you declared in robots.txt and review the coverage report for the addresses the engine passed over.
Questions about Sitemap XML Generator and Validator
Does listing a page in a sitemap make it appear in search results?
No. A sitemap provides discovery and update hints; it does not publish pages or guarantee indexing. Google uses lastmod when consistently accurate, so use the last significant content update rather than changing every date on each build.
How many addresses can one sitemap hold?
The protocol permits 50,000 URLs and 50 MB uncompressed per sitemap. This builder accepts up to 10,000 entries per input and can split them into at most 25 smaller files plus an index. Its intake limit remains the same when splitting.
Why was one of my lines skipped?
The builder lists invalid rows and removes repeated normalized URLs; empty input lines are ignored. URL/date errors can skip a row, while mixed host/protocol or an incompatible published directory stops the build. Inspect the reported reason instead of assuming every skipped URL is unsuitable for search.
Does the check open the addresses in the file?
No. The XML is read in this browser and the checker does not request the listed addresses, so the check describes the shape of the file and its values, not the live pages.