Generate a sitemap.xml for any site

What is a sitemap.xml?

A sitemap.xml is a simple XML file listing the URLs on your site that you want search engines and AI crawlers to discover. It lives at the root of your domain (https://yoursite.com/sitemap.xml) and is the standard mechanism Google, Bing, and increasingly AI crawlers like ChatGPT-User and ClaudeBot use to find your pages efficiently.

Without one, crawlers have to follow links one page at a time — slower, less thorough, and prone to missing deep pages. With one, every URL you care about gets discovered on day one.

How this generator works

• Starts at your homepage. Fetches the HTML and extracts all internal <a href> links.
• Follows internal links only. Same-domain (www/non-www tolerant). External links, anchors, and non-HTML assets are skipped.
• Respects robots.txt. URLs the site disallows for our user-agent are omitted from the sitemap.
• Breadth-first crawl. Higher-level pages first. Stops at your requested page count.
• Adds <lastmod> when the server provides a Last-Modified header.
• Outputs valid XML following the sitemaps.org protocol.

What to do with the result

• Save the output as sitemap.xml and place it at your domain root (same place as robots.txt).
• Add a line to your robots.txt so crawlers find it automatically: Sitemap: https://yoursite.com/sitemap.xml
• Submit it to Google Search Console for faster indexing.
• Regenerate whenever your URL structure changes materially, or at least quarterly.

FAQ

Is the sitemap valid for Google and Bing?

Yes — it follows the sitemaps.org schema and includes the required <loc> elements for every URL. Both search engines accept it without modification.

Can I edit the output before publishing?

Yes — the textarea is fully editable. Remove URLs you don't want crawled, add ones the discovery missed, or reorder anything. Human review always improves automated output.

Does this work for JavaScript-rendered sites?

Partially. We fetch the server-rendered HTML, which means Single-Page Apps that only render via client-side JS won't expose their internal routes to our crawler. For SPAs, use your framework's built-in sitemap generation (Next.js, Astro, Nuxt all have one) or export your route list manually.

Is there a page limit?

The slider caps at 200 pages per run, which covers most small-to-medium sites. Large content sites (1,000+ pages) should generate their sitemap from their CMS or framework rather than by crawling.