Free XML Sitemap Generator: Create and Submit in 5 Minutes (2026)

Free XML sitemap generator: create and submit in 5 minutes (2026)

Searches for free XML sitemap generator spike after site migrations, framework upgrades, or when Google Search Console shows "Couldn't fetch sitemap." A valid sitemap is straightforward XML that lists URLs you want crawled and indexed. But having a valid XML file is only part of the job. Crawl budget, canonical tags, what you include or exclude, and how you submit all determine whether a sitemap actually helps your site rank.

Google Search Central documents sitemap guidelines and limits — including the 50,000 URL maximum per sitemap file and the requirements for encoding, format, and submission (Learn about sitemaps). This guide explains when and why to use a sitemap, the difference between static and dynamic approaches, what to include and exclude, submission steps, and where LaunchGPT Sitemap Finder helps you verify your sitemap is accessible after deploy.

Quick answer: do you actually need a sitemap?

For most websites, yes. Google can discover pages through internal links, but a sitemap makes crawling faster and more reliable — especially for new sites, large sites, sites with deep content, or sites updated frequently. Sitemaps do not guarantee indexing, but they help search engines understand your site structure and prioritize crawl time on your important pages.

Small static sites with clear internal linking sometimes rank fine without a sitemap. Large e-commerce sites, content sites with hundreds of posts, multi-locale sites, and sites that have just migrated all benefit significantly from a well-maintained sitemap.

Static vs dynamic sitemaps

What to include in your XML sitemap

Include pages that represent the canonical, publicly accessible content you want Google to index and rank. For most sites this means:

• Homepage
• Key landing pages (product, service, pricing, about)
• Blog posts and articles — all published, canonical content
• Category and tag archive pages if they have unique content
• Product pages for e-commerce
• Locale-specific URLs for international sites (pair with hreflang)

What to exclude from your XML sitemap

This is where many teams go wrong. Including low-quality or duplicate pages does not help and can waste crawl budget on pages that should not rank.

Exclude:

• Paginated pages beyond page 1 (e.g. /blog/page/2, /products?page=3)
• Filter and facet URLs that duplicate product listings
• Session IDs and tracking parameters in URLs
• Admin, staging, or preview URLs
• Thank-you and confirmation pages
• Duplicate content pages already covered by canonical tags
• Search results pages
• Thin or auto-generated content that adds no value

The goal is to tell search engines what your best pages are, not to submit every URL your site can render.

XML sitemap structure and format

A minimal valid sitemap looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-05-01</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://example.com/blog/example-post/</loc>
    <lastmod>2026-04-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Key rules:

• Use HTTPS URLs, not HTTP, even if you redirect.
• <lastmod> should reflect actual content changes, not today's date on every page.
• <changefreq> and <priority> are hints, not commands — Google may ignore them.
• Encode special characters: & becomes &, spaces become %20.
• Keep each sitemap file under 50,000 URLs and 50 MB uncompressed.

Five-minute submit checklist

Step-by-step: generate and submit a sitemap

Step 1: generate the sitemap

Framework sites (Next.js, Nuxt, Astro): Use the built-in sitemap module or a plugin. Verify output by visiting /sitemap.xml on your live domain.

WordPress: Install a plugin like Yoast SEO or Rank Math. Sitemap is generated automatically.

Custom or static sites: Use a command-line tool, a browser-based generator, or write the XML manually for small sites. Tools like sitemap-generator-cli (Node.js) can crawl your site and output a valid XML file.

For very small sites: A free online XML sitemap generator can crawl your public pages and output a downloadable file. These work for sites with fewer than a few hundred pages and no authentication.

Step 2: check robots.txt

Add this line to your robots.txt file:

Sitemap: https://yourdomain.com/sitemap.xml

This helps all search engines — not only Google — discover the sitemap automatically.

Step 3: verify the sitemap is accessible

Before submitting to Google, confirm the sitemap loads without errors. It should return HTTP 200 at a stable HTTPS URL. No login required, no redirect to the homepage, no server error.

Use LaunchGPT Sitemap Finder to probe common sitemap paths (sitemap.xml, sitemap_index.xml, WordPress plugin patterns) and confirm expected status codes after deploy.

Step 4: submit to Google Search Console

Open Google Search Console → select your property → Sitemaps in the sidebar → enter the sitemap URL → click Submit.

After submission, return to Sitemaps and check the coverage report. Look for:

• Submitted URLs: should match the count in your sitemap file.
• Indexed URLs: may be lower — not everything submitted gets indexed.
• Errors: red items need investigation; common causes are 404s, noindex tags on sitemap URLs, or server errors.

Step 5: submit to Bing and others

Submit to Bing Webmaster Tools separately. Bing also respects the Sitemap: line in robots.txt for automatic discovery.

Probe sitemaps with LaunchGPT utilities

After deploy, run Sitemap Finder & Checker to confirm common paths return expected HTTP status codes. This catches misconfigurations like a 301 redirect chain on the sitemap URL, a cached 404 from a previous migration, or a sitemap that only works on www but not the naked domain.

Browse all developer utilities on the Tools utilities hub.

Common sitemap mistakes

Mistake 1: Including every URL the site generates. Paginated pages, session-ID URLs, filter pages, and thin content pollute your sitemap and waste crawl budget.

Mistake 2: Submitting a sitemap on a site with canonical conflicts. If pages have conflicting canonical tags, submitting them in the sitemap does not override the canonical. Fix canonical tags first.

Mistake 3: Using today's date on every <lastmod> field. Google tracks this. If every page shows today's date regardless of actual updates, the signal becomes meaningless and may be ignored.

Mistake 4: Not excluding staging or preview URLs. Check that your staging environment does not end up in the generated sitemap for your production domain.

Mistake 5: Forgetting the sitemap index for large sites. Once you exceed 50,000 URLs, you need a sitemap index file that points to individual child sitemaps.

Mistake 6: Failing to update after migrations. After a domain change, URL structure change, or CMS switch, regenerate and resubmit the sitemap. Old URLs in the sitemap trigger crawl errors that GSC tracks.

Sitemaps for specific platforms

Next.js: Use the built-in sitemap.ts export (Next.js 13+) or next-sitemap package. Exclude draft routes and preview URLs.

WordPress: Yoast SEO, Rank Math, or All in One SEO handle sitemap generation. Verify exclusions include tag/category pages with thin content if applicable.

Shopify: Shopify generates sitemap.xml automatically. Add it to GSC. You cannot fully control which product pages appear, but most standard Shopify sitemaps are clean.

Webflow: Sitemap is auto-generated. Toggle per-page SEO settings to exclude specific pages.

Custom builds: Use a build-step script that reads your route manifest and outputs clean XML. Version-control the sitemap generator config.

Monitoring sitemap health over time

Submitting a sitemap once is not enough. Search engines crawl it on their schedule, and your site changes over time. Set a recurring monthly task to:

• Open Search Console → Sitemaps → check for new errors.
• Compare submitted URL count against indexed URL count. A large gap signals crawl issues, noindex tags on submitted pages, or thin content being excluded.
• Check Coverage report for "Submitted URL seems to be a Soft 404" or "Submitted URL not selected as canonical" warnings.
• Verify no staging or preview URLs appeared after a recent deploy.
• Regenerate the sitemap if you changed URL structure, added a new blog category, or launched a new product line.

For fast-changing sites like e-commerce or news, automate sitemap regeneration as part of your deploy pipeline so the live sitemap always matches current published content.

Sitemaps and site migrations

Site migrations are the highest-risk moment for sitemaps. When you change domains, restructure URLs, or switch platforms, your old sitemap becomes inaccurate immediately. Steps for migration:

1. Generate a new sitemap reflecting the final URL structure before migration day.
2. Set up 301 redirects for every old URL.
3. Submit the new sitemap in Search Console immediately after migration.
4. Monitor Coverage daily for the first two weeks.
5. Keep the old property verified in Search Console to watch for crawl errors on old URLs.

Missing any step can cost weeks of ranking recovery. The sitemap tells Google where your canonical pages are; the redirects and canonicals enforce it.

FAQ

Conclusion: ship clean URLs, then submit

Free XML sitemap generator tools work when the URLs inside are clean, canonical, and worth indexing. Generate from your CMS or framework, exclude thin and duplicate content, probe with LaunchGPT Sitemap Finder, submit to Google Search Console, and monitor coverage regularly.

Related: Sitemap Finder & Checker · Free URL shortener with analytics · Discover