XML Sitemap Generator
Create XML sitemaps from manual URLs or local CSV, review per-URL options and fix validation errors before downloading.
Build a URL list
Blank lines are ignored. Up to 200,000 characters and 1,000 entries; URLs are never visited.
Generated XML
Review your entries, then generate a sitemap to see validation results and XML.
This local tool is capped at 1,000 URLs and 2 MiB output, below the standard sitemap limit of 50,000 URLs / 50 MiB uncompressed. Sitemap indexes, crawling and submission are outside its scope; indexing is never guaranteed.
Understand your results
For maintainers creating a small sitemap from a reviewed list of canonical public page URLs.
Manual lines are trimmed and blank lines ignored. CSV uses the existing quote-aware parser, with url/loc and optional lastmod/changefreq/priority columns, or a one-column URL-only fallback. Imported entries remain editable. Generation validates each URL and metadata field, rejects duplicate serialized URLs and mixed hosts, then escapes values into a standard UTF-8 urlset. No crawl or network requests are involved.
How to use this tool
- Paste URLs or import a local UTF-8 CSV. Review the entries before generating XML.
- Correct or remove invalid rows and set only genuine optional metadata. Defaults fill empty metadata fields; they never invent a modification date.
- Generate, review errors/warnings, then copy or download sitemap.xml. Validate the deployed file and submit it yourself if appropriate.
What the observations mean
The URL count describes accepted entries; byte size measures the generated UTF-8 XML. A generated file is a discovery aid, not evidence of server availability, canonical correctness or indexing. Errors block output; warnings explain limits or optional metadata hints.
Worked example
Create a sitemap from two pages without inventing modification dates.
https://example.com/
https://example.com/search/?tag=paper&sort=newThe generator creates a urlset with two loc entries and escapes the query ampersand as &. Optional date/frequency/priority tags are omitted unless supplied. Review whether the second URL really deserves inclusion as a canonical public page.
Limits and processing
Local manual/CSV generation only: 1,000 URLs, 200,000 input characters, 800 KB CSV bytes and 2 MiB output. No sitemap index, crawling, status/canonical checking, submission or indexing guarantee. Protocol upper bounds are 50,000 URLs / 50 MiB uncompressed.
Common problems and practical fixes
- A row fails URL or metadata validation
- Correct the HTTP(S) URL, real date, allowed frequency or 0–1 decimal priority, or remove that row explicitly.
- A CSV import is ambiguous
- Choose headers explicitly and use url or loc, not both. Headerless input is strictly one URL column, and quoting must be well formed.
- The list exceeds a local limit
- Split it into smaller files within the 1,000-entry/2 MiB local caps. A larger sitemap/index workflow is outside this generator.
Best practices
Maintain an authoritative list of canonical pages, use accurate dates only when known and validate the published XML. Keep crawling, indexation and sitemap generation as distinct checks.
Practical tips
- Use the preferred HTTP(S) URLs on one host, without fragments, credentials or duplicates.
- lastmod should reflect a real significant change. changefreq and priority are optional hints, and Google ignores them.
- The protocol permits 50,000 URLs and 50 MiB uncompressed per sitemap. This browser tool uses lower 1,000-URL and 2 MiB output limits; it does not create sitemap indexes.
Frequently asked questions
Practical answers for using the XML Sitemap Generator.
Does it crawl or submit my website?
No. It only serializes the supplied list locally. It does not check response status, canonical tags, crawl access or indexing, and submitting a sitemap does not guarantee indexing.
What CSV format is supported?
Comma-delimited UTF-8 CSV, with quoted fields/escaped quotes. Use either url or loc, plus optional lastmod, changefreq and priority. Without headers, only one URL column is accepted. Extra named columns are ignored with a warning.
What happens to invalid or duplicate URLs?
Generation is blocked until you correct or remove the affected entries. The results identify row numbers, and Remove invalid entries removes those rows explicitly; no partial XML is presented as complete.