XML Sitemap Generator

How it works

What we check

• Existing sitemap detection — Before crawling, we check whether you already publish a sitemap. If you do, we read it and rebuild from those URLs — faster and closer to what you intend to expose than a fresh crawl.
• Crawlable pages — When there's no published sitemap, we crawl your site following internal links and list the pages we can reach. Pages with no link pointing to them won't be found by any crawler — including search engines — which is itself a useful signal.
• Valid XML structure — The output is a proper <urlset> document with the sitemaps.org 0.9 namespace, one <url> block per page, and a <loc> element holding each full, absolute URL. This is the exact format Google and Bing expect.
• Per-URL hints — Each entry carries <changefreq> and <priority> values. These are optional hints, not commands — search engines treat them as suggestions and rely far more on how often a page actually changes.
• Duplicate URLs — We de-duplicate the list so the same page doesn't appear twice. Duplicate <loc> entries waste crawl budget and can muddy which version of a URL you want indexed.
• Absolute URLs — Every <loc> uses a full, absolute URL with scheme and domain. Relative paths are invalid in a sitemap and will be rejected when you submit the file.

Common issues we catch

• Sitemap not submitted anywhere — A sitemap sitting on your server does nothing on its own if no crawler knows about it. You have to submit the URL in Search Console and Bing Webmaster Tools, add it to robots.txt, or both — otherwise it's just a file.
• Missing the robots.txt Sitemap line — A single line — Sitemap: https://yourdomain.com/sitemap.xml — in robots.txt lets any crawler discover the file automatically. It's the most overlooked step and the easiest to add.
• Including pages you don't want indexed — Listing noindex pages, redirects, login or thank-you pages, or 404s sends mixed signals. A sitemap should only contain canonical, indexable, 200-status URLs — the pages you actually want in search results.
• Exceeding the size limits without splitting — A single sitemap file is capped at 50,000 URLs and 50MB uncompressed. Larger sites must split into multiple files and reference them all from a sitemap index — a master file that lists each child sitemap.
• Orphan pages missing from a crawled sitemap — If a page has no internal link pointing to it, a crawl-based generator can't find it — and neither can search engines. A page missing here is often a discoverability problem worth fixing on the site itself.
• Stale sitemap after a redesign — Sitemaps generated once and forgotten keep listing deleted URLs and miss new ones. Regenerate after any structural change so crawlers spend their budget on pages that still exist.
• Wrong file location — Search engines expect the sitemap at a reachable URL on your domain, conventionally /sitemap.xml at the root. Bury it in a subfolder without referencing it from robots.txt or Search Console and crawlers won't stumble onto it.

Where this matters

• Google Search Console — Submit your sitemap URL under Sitemaps to tell Google where your pages live and watch how many it has discovered and indexed. This is the primary way to get a new sitemap noticed by Google.
• Bing Webmaster Tools — Bing accepts the same sitemap file. Submitting it there covers Bing and the search experiences that draw on its index, with its own crawl and indexing reports.
• robots.txt — Adding a Sitemap: line to robots.txt is supported by all major search engines and lets crawlers find your sitemap without any manual submission — useful as a backup to Search Console.
• WordPress, Shopify & Wix — Many platforms auto-generate a sitemap (often at /sitemap.xml or /sitemap_index.xml). When yours does, we read it; when it doesn't or it's incomplete, the crawl-built file gives you a clean alternative you control.
• Large & multi-section sites — Sites past the 50,000-URL limit need a sitemap index pointing to several child sitemaps. The same XML format applies — the index just lists sitemaps instead of pages.