XML sitemap generator

Enter a URL and we crawl the site, following links from page to page, then build a valid sitemap.xml you can copy or download. Handy when a site has no sitemap and you want one to submit to Google Search Console or Bing.

How it works

  • We fetch your start page, read every same-site <a href> link, then keep crawling those pages, following links outward until there are none left.
  • Only pages that respond with a 200 status and real HTML are added. Off-site links, files (images, PDFs, CSS, JS), and mailto: or tel: links are skipped.
  • To stay fast and polite, the crawl is bounded: up to 100 pages, with a time budget of around 22 seconds. If a site is bigger, we return what we reached and tell you it was partial.
  • The result is a standard sitemap.xml in the sitemaps.org 0.9 format. Copy it or download the file, then submit it in Google Search Console or drop it at /sitemap.xml on your server.

Note: this crawler reads the HTML your server sends. Pages that only render their links with JavaScript in the browser may not be discovered.

What to do with the results

  • Upload the file to your domain root so it is reachable at https://example.com/sitemap.xml. A sitemap is only valid for URLs at or below the directory it lives in, so root placement covers the whole site.
  • Add a Sitemap line to your robots.txt and submit the file in Google Search Console and Bing Webmaster Tools, so both crawlers pick it up quickly rather than waiting to discover it on their own.
  • Missing pages are usually a discovery problem, not a bug. Anything linked only through a JavaScript-rendered menu, hidden behind a login, or not linked from anywhere will not appear, since the crawl follows ordinary HTML links.
  • Truncated result on a larger site: the tool tells you the crawl was partial. Point it at a specific section, or generate one sitemap per section, rather than relying on a single pass to reach everything.

A sitemap is a snapshot the moment you generate it, and it goes stale as soon as pages are added or removed. Ongoing SEO monitoring can watch a site's structure over time and alert you when new pages appear or old ones disappear, without you needing to re-run a crawl by hand.

Frequently asked questions

It starts at the URL you enter, reads every same-site link in the returned HTML, then visits those pages and repeats until no new pages remain or it reaches the crawl caps (100 pages or roughly a 22-second budget). Only pages that respond 200 with real HTML are included. Off-site links, files like images and PDFs, and mailto: or tel: links are skipped, so the output is a clean list of actual pages.

Upload it to the root of your domain so it is reachable at https://example.com/sitemap.xml, add a Sitemap: line pointing at it in your robots.txt, and submit it in Google Search Console and Bing Webmaster Tools. Root placement matters because a sitemap is only valid for URLs at or below the directory it lives in, so the root covers the whole site.

The crawler only discovers pages reachable by following ordinary HTML links from your start page. Pages linked solely through JavaScript-rendered menus, hidden behind forms or logins, or not linked from anywhere (orphan pages) will not be found. Large sites can also hit the 100-page cap, in which case the tool tells you the crawl was partial and gives you what it reached.

No, a sitemap is a discovery aid rather than a ranking signal. It tells search engines which URLs exist so new and updated pages get found and crawled sooner, which matters most on new sites, large sites, and sites with thin internal linking. The pages still have to earn their rankings once crawled.

They are optional, and this generator deliberately emits a minimal, valid sitemap of <loc> entries, which is all search engines need for discovery. Google has said it ignores priority and changefreq, and only trusts lastmod when it is consistently accurate. If you later add lastmod values via your CMS, keep them truthful rather than stamping every page with today's date.