Sitemap.xml Generator
Paste your URLs, set the optional lastmod, changefreq and priority, and get a sitemap you can upload as-is. Malformed lines and unescaped ampersands are caught before they reach the file.
Lines that were skipped
Your sitemap.xml
What this tool does
A sitemap is a plain XML file that lists the URLs on your site so a crawler can find them
without having to guess its way through your navigation. This tool takes a list of URLs and
produces a valid one: the right XML declaration and namespace, one url entry
per address, and the optional lastmod, changefreq and
priority elements written the way the protocol expects them.
It also does the unglamorous part that actually breaks sitemaps: rejecting lines that are not absolute URLs instead of silently writing them, escaping ampersands in query strings so the file stays well-formed XML, and removing duplicates. The honest limitation is that it has no idea what your site contains — it does not crawl anything, so you supply the URLs, and it cannot tell you whether any of them actually returns a 200. A sitemap full of 404s or redirects is worse than no sitemap.
How to use it
- Paste your URLs into the box, one per line. Fragments are stripped and duplicates are dropped for you.
- Set a last modified date if the pages genuinely changed on one date. If they did not, leave it empty — a wrong
lastmodteaches the crawler to distrust the whole file. - Choose a change frequency and priority only if you have a reason to. Google ignores both, so "Omit" is usually the better answer.
- Click Generate Sitemap, fix any lines that were skipped, then copy the XML and save it as
sitemap.xmlat your site root.
Common use cases
-
A new site with no internal links yet
On a fresh domain nothing points at your pages, so a sitemap is often the fastest way to get them discovered at all.
-
Orphan pages
Landing pages and campaign URLs that nothing links to will not be crawled on their own — listing them is the only reliable way in.
-
Large catalogues and archives
When you have thousands of product or post URLs, a generated sitemap beats hoping the crawler reaches page 40 of your pagination.
-
After a migration
Building the list from your new URL structure is a quick way to spot addresses you forgot to redirect.
-
Client handover
Generate the file, then hand over a sitemap you can explain line by line rather than one exported from a plugin nobody understands.
Frequently asked questions
Do I need a sitemap to rank?
Not strictly. Google discovers pages by following links, and plenty of sites rank well without one. A sitemap earns its place on large sites, on pages that are poorly linked internally, and on a new domain where nothing points at you yet. It tells a crawler what exists — it is not a ranking factor, and submitting one will not lift a page that nothing links to.
How many URLs can one sitemap hold?
Up to 50,000 URLs, and the uncompressed file must stay under 50 MB. Past that limit you need a sitemap index: a small file listing several sitemap files. This is a protocol rule rather than a preference — search engines reject a file that exceeds it, which is why the tool warns before you get there.
Do changefreq and priority affect ranking?
Almost never. Google has said plainly that it ignores both, deciding when to recrawl from
its own scheduling and from lastmod. They remain valid protocol elements that
other crawlers may read, so setting them is harmless — but leaving them out is cleaner than
publishing values you cannot back up.