The Sitemap Generator builds an XML sitemap from a list of page addresses that you paste in, one per line. It does not crawl your site, so it contains exactly the pages you give it. It adds https:// where it is missing, removes duplicates, skips and lists invalid lines, and can add a last-modified date, change frequency and priority. Copy the XML or download it as sitemap.xml, then upload it and submit it in Search Console. It runs in your browser.
Made for marketers and seo. Typical uses:
Pasting https://example.com/, https://example.com/about, example.com/blog/post, a repeat of the about page and the text "not a url" gives 3 addresses, with 1 duplicate removed and 1 invalid line skipped. With a custom last-modified date of 2026-10-05, each entry has a loc line and a lastmod line.
It does not crawl your website or discover pages; it only uses the addresses you paste. A sitemap file can hold 50,000 addresses and 50 MB, and every address must belong to the host that serves the file. A sitemap helps discovery but does not guarantee indexing.
Accuracy: Results show what the tool can measure at the moment you run it and can differ from what search engines see. Use them as guidance.
Expert Tip
List only final, canonical addresses that return a 200 status and that you want indexed. Add a last-modified date only when the page really changed, because dates that always say "today" teach crawlers to ignore them.
The Sitemap Generator builds an XML sitemap from a list of addresses that you paste in, one per line. It does not crawl your website, so it only includes the pages you give it. That makes it the right tool for small sites, new sites and lists exported from a spreadsheet or a CMS, and the wrong one if you expect it to discover pages by following links. You can add a last-modified date, a change frequency and a priority, and then copy the XML or download it as sitemap.xml.
The tool checks your list and tells you what it did.
Paste five lines: https://example.com/, https://example.com/about, example.com/blog/post, a repeat of the about page, and the text "not a url". The tool reports 3 addresses, 1 duplicate removed and 1 invalid line skipped. With the last-modified option set to a custom date of 2026-10-05, each of the three entries has a loc line with the address and a lastmod line with that date, inside a urlset element that uses the standard sitemaps.org namespace.
Google uses the loc address and, if it proves reliable, the lastmod date. It ignores the priority and change-frequency fields, so leaving them out is fine. Only set a last-modified date if it reflects a real change to the page, because dates that always say "today" teach crawlers to ignore them. List only the final, canonical addresses that return a 200 status and that you want indexed: no redirects, no pages blocked by robots.txt, no noindex pages and no duplicate versions with tracking parameters.
A single sitemap file can hold up to 50,000 addresses and 50 MB uncompressed, and all addresses must belong to the host that serves the file. A larger site needs several sitemaps joined by a sitemap index file. A sitemap helps discovery, but it does not guarantee that a page will be indexed. Pages are indexed when Google judges that they are useful, so good internal links and quality content matter more.
Upload sitemap.xml to the root of your site, add a Sitemap line to robots.txt with the Robots.txt Generator, and submit the address in Google Search Console and Bing Webmaster Tools. To check that a list of addresses is well formed first, use the URL Validator, and to confirm that the XML is valid, use the XML Validator. The guide to robots.txt, sitemaps and canonical tags covers the full picture. Everything is built in your browser.
Three small technical SEO pieces that are easy to get wrong: what robots.txt, XML sitemaps and canonical tags each control, common mistakes, and how to test them.
Explore more in SEO Tools, read the guides and articles, or see how we test our tools.
Generate a robots.txt file for your website.
Best for keeping crawlers out of admin, cart, checkout and internal search pages
Validate URLs for correct format and structure.
Best for validating URLs in web applications
Validate XML documents for well-formed syntax and structure.
Best for debugging a broken RSS or Atom feed that's failing to parse in a feed reader
Check HTTP status codes for any URL.
Best for confirming a page returns 200 OK after deploying a fix for a broken link
Check canonical tags on any webpage to prevent duplicate content issues.
Best for verifying a migrated site's pages canonicalize to the correct new URLs