Small static website
Turn a reviewed route inventory into a clean XML file without running a crawler.
Crawling and indexing tool
XML Sitemap Generator
Paste your chosen canonical URLs, one per line, to generate sitemap XML. Review the list, fix input errors, then copy or download your file. No website crawl or login needed.
FreeNo loginNo data stored
Migration URL set
Prepare the intended new canonical URLs after redirects and templates have been reviewed.
Developer handoff
Copy a deployment prompt that preserves the XML and requires live validation after implementation.
What it checks
Use the result as evidence, not a score.
- Absolute HTTP and HTTPS URL syntax
- Duplicate URL removal and fragment normalization
- Optional lastmod date format
- Origin count and the 50,000-entry limit
What it cannot check
- Which pages belong in your canonical indexable set
- Whether entered pages redirect, return errors, contain noindex, or declare another canonical
- Deployment, submission, crawling, indexing, rankings, or traffic
How it works
Input, inspect, improve, verify.
The tool processes what you enter, shows a plain-language result, and gives you a safer next step. Make the change on your website, deploy it, then test the live page again.
Understand the result
How to use the free XML sitemap generator
Paste a complete HTTP or HTTPS URL on each line in Canonical URLs, one per line. Add an optional last-modified date after a comma or tab. The tool updates the input-row, valid-URL, and origin counts as you type.
Review Fix before downloading and any Review items, then use Copy XML or Download. Download and Copy deployment prompt are disabled when there are no valid entries or input errors remain. Copy XML can still copy a partial draft, so resolve errors before using it.
- Enter full URLs rather than relative paths.
- Use View example for an Overhyped URL list or Clear to start again.
- Select the intended canonical pages first; the generator does not fetch or choose them.
Understand the result
A sitemap generation example with duplicates
Try three lines using an example domain: https://example.com/, https://example.com/about, and https://example.com/about#team. Enter each on its own line. The tool reports three input rows, two valid unique URLs, and one origin.
Fragments are removed before duplicate detection, so the third line repeats the about URL. The XML contains two URL entries. To add a lastmod value, place a comma and a genuine YYYY-MM-DD change date after a URL; omit the date when you cannot maintain it accurately.
- Exact duplicates are removed after URL normalization.
- Mixed origins produce a review warning, not confirmation of cross-site ownership.
- A syntactically accepted URL is not proof that its page exists, is indexable, or belongs in this sitemap.
Understand the result
What this sitemap generator creates
The output is a standard XML URL set containing loc values and optional lastmod dates. URL values are escaped for XML. This tool does not build a visual sitemap, crawl your website, or add video, image, news, priority, or changefreq fields.
After reviewing the URL set, validate the generated XML with the related XML Sitemap Validator. Publish it through your site’s normal workflow, then check the live response. The deployment prompt provides a handoff for a coding agent; copying it does not deploy or submit anything.
- For frequently changing sites, prefer sitemap generation within the CMS or build pipeline.
- Check that the live file returns the intended XML and HTTP 200.
- Sitemap creation, publication, discovery, and indexing are separate steps.
Popular use cases
Useful before and after publishing.
Small static website
Turn a reviewed route inventory into a clean XML file without running a crawler.
Migration URL set
Prepare the intended new canonical URLs after redirects and templates have been reviewed.
Developer handoff
Copy a deployment prompt that preserves the XML and requires live validation after implementation.
Pro tips
Small checks that prevent avoidable mistakes.
- Generate from your source-of-truth route or database output when the site changes frequently.
- Include preferred canonical URLs, not every reachable parameter or redirecting version.
- Leave lastmod out when you cannot maintain it accurately.
- Deploy, validate, advertise, and inspect processing as separate steps.
Common issues and solutions
What to review when the result looks wrong.
Several hosts appear
Confirm whether cross-site submission is intentional and owned. Most ordinary website sitemaps should contain one deliberate origin.
A URL appears twice
The generator removes exact duplicates after fragment normalization and shows the affected input row.
The generated file becomes stale
Move generation into the CMS or build pipeline once manual maintenance is no longer reliable.
Frequently asked questions
Short answers before you make a change.
Can I generate a sitemap from a website URL?
This generator needs a list of page URLs, not a single address to crawl. Use your route inventory or CMS export to select the intended canonical pages first.
Why does the sitemap URL count differ from my input rows?
Blank lines are ignored, fragments are removed, and duplicate normalized URLs are omitted. Invalid URLs or dates appear as errors; review those before using the XML.
Is this free XML sitemap generator limited to Blogger or WordPress?
No. It creates XML from an entered URL list. It is not a CMS plugin and does not replace a platform’s existing sitemap automatically.
Does this generator crawl my website?
No. It converts the URLs you enter. This makes selection explicit and avoids pretending a shallow crawl found every canonical page.
Should I add priority or changefreq?
This generator omits them. Focus on accurate canonical locations and meaningful lastmod values where you can maintain them.
Where should sitemap.xml be published?
The site root is the simplest location for broad coverage, but the correct path depends on how the sitemap will be hosted and submitted.
Read the practical guide
Which URLs belong in an XML sitemap
Understand the evidence behind this tool, where its result stops, and the safer next steps to verify on a live page.
Read the guideEvidence · Limitations · Verification