XML sitemaps
Free XML sitemap generator, up to 5,000 pages
A sitemap should list the pages you want in search results and nothing else. Most generators list whatever they managed to fetch: redirects, error pages, pages you marked noindex. Search engines then spend their visits on addresses that were never going to be indexed.
Enter a domain. When the crawl finishes, Download an XML sitemap on the results page gives you a file of only the pages that answer 200 and can be indexed.
How to make the sitemap
- Enter your domain in the form above and start the scan. You get a private link to the results straight away.
- Wait for the crawl to finish. A few hundred pages take a few minutes; leave an e-mail address on the form to be told when it is done.
- On the results page, choose Download an XML sitemap, or Image sitemap for the image version.
- Upload the file to the root of your site as
sitemap.xml. - Tell search engines where it is: add the line below to robots.txt, and submit the address under Sitemaps in Google Search Console and Bing Webmaster Tools.
Sitemap: https://yourwebsite.com/sitemap.xmlThen run the sitemap validator on the live address to confirm it is found, parses and lists what you expect.
What the file looks like
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://yourwebsite.com/</loc><lastmod>2026-11-02</lastmod></url>
<url><loc>https://yourwebsite.com/services</loc></url>
<url><loc>https://yourwebsite.com/services/repairs</loc></url>
</urlset>Pages are listed shallowest first: the home page, then the pages one click from it, and so on. The order has no effect on search engines; it makes the file readable by a person checking it. Addresses are escaped for XML, and the file stays inside the protocol's limit of 50,000 URLs.
Why a crawl makes a better sitemap
Every entry is known to work. Each address was fetched minutes ago and answered 200. A sitemap written from a database lists pages the site no longer serves.
Nothing contradicts itself. A noindex page in a sitemap asks to be indexed and refuses at once. Pages with a canonical pointing elsewhere are duplicates by their own account. Both are left out.
You see what was left out, and why. The same scan's Sitemap coverage check compares your existing sitemap with the crawl: listed pages that are broken, redirect or are noindex, and crawled pages the sitemap forgot.
What a crawl-built sitemap misses
A crawler finds pages by following links, so a page nothing links to is not in the generated file. That is the one thing a sitemap is most useful for, and it is worth knowing. If you have such pages, either link to them, which is the better fix, or add them to the file by hand. The orphan page checker explains how to find them.
The file is also a snapshot. It does not update when you publish a page. For a site that changes weekly, generate it again after changes, or have the site produce its own. A free account can re-run the scan on a schedule; uploading the new file is still yours to do.
Pages blocked by robots.txt, pages behind a login and, unless you tick the JavaScript rendering option, pages reachable only through links that scripts add are not crawled, so they are not listed.
The rest of the crawl
The sitemap is a by-product. The same crawl runs 37 checks, among them broken links, titles and noindex pages, and the whole crawl can be downloaded as a SQLite database.
Questions people ask
- Is there a free sitemap generator for more than 500 pages?
- Yes, this one. Free online generators commonly stop at 500 URLs and sell the rest. A crawl here covers up to 5,000 pages, and the sitemap built from it has no separate limit, no account and no watermark.
- Which pages go into the sitemap?
- Every page the crawl fetched that answered with a 2xx status, was served as HTML, does not carry
noindex, and does not name a different page as its canonical. Redirects, errors, blocked pages and duplicates that point elsewhere are left out, because a sitemap is a list of the pages you want indexed. - Why is there no priority or changefreq?
- Because Google has said it ignores both, and a file full of invented values is harder to trust than one without them.
lastmodis included only when your server sent aLast-Modifiedheader for the page: a date that is merely the day of the crawl tells a search engine nothing. - Do I need a sitemap generator if I use WordPress or Shopify?
- Probably not. WordPress, Shopify, Wix, Squarespace and most other platforms publish a sitemap themselves and keep it current as you edit. Use theirs. A generated file suits a hand-built or static site, a custom application, or a platform whose sitemap is wrong and cannot be changed.
- Can it make an image sitemap?
- Yes. Beside the XML sitemap there is an image sitemap: each indexable page with the images it shows, in Google's image sitemap format, leaving out images that answered with an error.
Generate a sitemap from a real crawl
Read next
- Find all pages on a website — five ways to list every URL of a site, what each one misses, and a crawl that gives you the list as a CSV.
- Website source code search — search the HTML of every page for text, a regular expression or a CSS selector, and export what it pulls out.
- SEO MCP server — point Claude or another assistant at a finished crawl of your site over MCP: one command, nothing to install.
- The free site crawler — the crawl all of these checks read from, and what else it records.