XML Sitemap Generator
Paste a list of URLs and get a valid sitemap.xml with lastmod, changefreq and priority, deduplicated and escaped.
Generate a sitemap.xml
Paste URLs one per line. Override a line with: https://example.com/ | 1.0 | daily
sitemap.xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
</urlset>
What the XML Sitemap Generator does
An XML sitemap is a list of the URLs on a site that you want search engines to know about, with optional hints about when each page last changed and how important it is relative to the rest. Google and Bing read it to find pages that internal links reach poorly and to pick up changes faster. Most content systems generate one automatically, but a static site, a landing-page builder or a hand-coded brochure site often has none, and that is where this tool fits.
Paste the URLs one per line. Every line is validated as an absolute http or https address, duplicates are removed, and characters that would break XML (ampersands, quotes, angle brackets) are escaped the way the sitemap protocol requires. The defaults for lastmod, changefreq and priority apply to every line, and any line can override them with the form "url | priority | changefreq". The generated file appears as you type, with a count of the URLs it contains, ready to copy or download as sitemap.xml.
The protocol allows 50,000 URLs and 50 MB per file. Above that the tool warns you to split the list into several sitemaps and reference them from a sitemap index. Nothing you paste leaves the browser.
Step by step
- 01Paste your URLs, one per line. Lines that are blank or not valid absolute URLs are listed as skipped.
- 02Set the default last-modified date (today is preselected), change frequency and priority.
- 03Override a line where it matters, for example "https://example.com/ | 1.0 | daily" for the home page.
- 04Check the URL count and the skipped list, then copy the XML or download sitemap.xml.
- 05Upload it to the site root, add a Sitemap: line to robots.txt and submit it in Search Console.
Common questions
No. Google has said it ignores both; Bing reads them as weak hints. They do no harm, and priority can still document which pages you consider most important, but do not expect either to change crawl behaviour. lastmod is the one field Google does use, when it is accurate.
The date the page content last changed meaningfully, in W3C format (YYYY-MM-DD or a full timestamp). Setting every page to today on every export teaches crawlers that the value is noise, so update it only for pages that actually changed.
A line is skipped if it is not an absolute URL starting with http:// or https://, if it contains spaces, or if it repeats a URL already in the list. Relative paths such as /about/ cannot be used because a sitemap must list full addresses on the host it describes.
Only if the sitemap is submitted through a verified Search Console property that covers all of them, or if robots.txt on each host points to it. The simple rule is one sitemap per host, placed at that host's root.
No. A sitemap should list only canonical, indexable URLs that return 200. Including redirected, blocked or noindex pages wastes crawl budget and produces warnings in Search Console. Use the sitemap validator to catch those after you upload.
Keep checking
XML Sitemap Validator
Validate an XML sitemap or index: well-formed XML, URL count, loc, lastmod, priority and changefreq, limits and live URL checks.
Free toolRobots.txt Generator
Build a robots.txt with per-bot allow and disallow rules, crawl-delay and sitemap lines, from presets or by hand.
Free toolCanonical Tag Checker
Find every canonical tag and Link header on a page and check it is absolute, self-referencing and free of conflicts.
Free toolBroken Links Checker
Test up to 50 links on a page and list the broken, redirected and working ones with their HTTP status.
Want these fixes done for you?
Our team runs the audit, makes the changes and reports the result.