XML Sitemap Generator
Turn a deliberate list of canonical pages into a clean XML sitemap. This is a list-based generator for small sites, migrations and carefully selected page sets, with no account or site-wide crawl required.
Your important pages. One clear map.
IN YOUR BROWSER / PRIVATE INPUTGood input. Useful output.
Create an escaped XML sitemap from your canonical URLs.
Try the example, or make it your own.How to use the
XML Sitemap Generator
- 01
Prepare the canonical URL list
Enter up to 500 absolute HTTP or HTTPS URLs, one per line. Use the addresses you want discovered, rather than every URL variant your application can create.
- 02
Generate and inspect the XML
The tool parses URLs, removes fragments, deduplicates the normalized list and escapes XML characters. Review the resulting locations before saving sitemap.xml.
- 03
Publish and monitor
Host the file where your crawler can reach it, commonly at the site root. Reference it in robots.txt or submit it in your search-engine webmaster tools, then inspect processing feedback.
Choose URLs for discovery, not an inventory dump
These decisions belong to the site owner. The generator does not fetch the list, read noindex directives or compare canonical tags. Valid XML can still contain poor URL choices, so review your source list before interpreting a successful export as a healthy sitemap.
| Usually include | Usually leave out | Reason to review |
|---|---|---|
| Preferred public page URLs | Redirecting aliases | Send crawlers toward the final destination. |
| Published, indexable resources | Drafts and login-only pages | A sitemap is meant to describe accessible content. |
| The intended canonical address | Tracking and sort variants | Avoid multiplying equivalent locations. |
| Useful standalone pages | Fragment-only jumps | A section anchor is not a separate document. |
Three input lines can describe one page
A fragment directs a browser to a part of a document. Removing it allows the same page to appear once in the sitemap. Query strings are different: the generator preserves them because some applications use queries to identify genuinely different content.
https://example.com/guide
https://example.com/guide#steps
https://example.com/guide<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://example.com/guide</loc></url>
</urlset>What the generated file contains
The file uses a urlset root in the sitemap namespace. Each unique location is stored in a loc element. Characters with XML meaning are escaped, so an ampersand in a query string becomes & in the file while still representing the correct URL.
This tool intentionally does not invent lastmod dates, changefreq values or priorities. A fresh export is not evidence that every page changed today. If your publishing system has accurate modification dates, maintain them there. For more than 500 input URLs, use a CMS-generated sitemap or a workflow that can create and maintain a sitemap index.
When a sitemap is accepted but pages are missing
Check the page itself
A listed URL may redirect, return an error or declare noindex. Sitemap submission does not override those signals or guarantee indexing.
Look for host and protocol inconsistencies
A mixture of www, non-www, HTTP and HTTPS addresses often reflects an unreviewed export. Choose the actual preferred URLs before generating the file.
Keep the map current
Remove deleted pages, update moved locations and add new public resources through a repeatable publishing process. A manual file is useful only while someone owns its upkeep.
XML Sitemap Generator:
questions, answered.
Will this sitemap generator crawl my website automatically?
No. It works from the URLs you provide. This makes the output predictable and suitable for a selected set of pages, but it will not discover forgotten routes.
Why are URL fragments removed?
Fragments refer to locations inside a document. They do not identify separate pages for this sitemap, so /guide and /guide#examples become the same location.
Is the 500-URL limit the sitemap protocol limit?
No. It is this tool's input limit. The protocol permits larger files under its own URL and size limits. Use an automated publishing workflow for a large site.
Do I need to regenerate the file whenever I edit page text?
If the URL set has not changed, this basic location-only sitemap may not need a change. If your production sitemap includes lastmod, update that value only when it reflects a meaningful page modification.
The calculations and checks above describe this tool's implementation. Use these primary references for the underlying formats and publishing guidance.
Build and submit a sitemap ↗ (opens in a new tab)Sitemaps XML protocol ↗ (opens in a new tab)Give discovery a clean starting point.
Build the list from canonical pages, inspect the exported XML and keep the map aligned with your site.
Use the XML Sitemap Generator↑