Sitemap Generators (2026): How to Create a Sitemap That Actually Helps

Before you go hunting for a sitemap generator: there’s a good chance you don’t need one. If your site runs on WordPress, Shopify, Squarespace, Astro, Next.js or basically any modern platform, a valid XML sitemap is already being generated and kept up to date for you. Generators matter for a narrower set of cases — hand-coded sites, awkward migrations, and large sites that need splitting. Here’s how to tell which situation you’re in, the tools worth using when you do need one, and the rules that decide whether Google pays any attention.

What a sitemap actually is (and what it isn’t)

An XML sitemap is a structured list of the URLs on your site that you want search engines to know about. Each entry carries the URL and, optionally, when it last changed.

What it does: helps crawlers discover pages, particularly on large sites, new sites with few backlinks, and sites with pages that aren’t well linked internally.

What it doesn’t do — and this is where most of the myths live:

• It doesn’t get you indexed. It’s a discovery hint, not an instruction. Google routinely crawls sitemap URLs and decides not to index them. If you’re stuck there, the problem isn’t your sitemap — see discovered, currently not indexed.
• It doesn’t improve rankings. There is no ranking bonus for having one.
• priority and changefreq are ignored. Google has said so plainly for years. Don’t let a tool sell you on tuning them.

lastmod is the one optional field that still earns its place — but only if it’s honest. If your generator stamps today’s date on every URL every time it runs, Google learns to distrust the signal and ignores it.

Do you already have one? Check first

Thirty seconds, before you install anything. Try these in order:

1. yoursite.com/sitemap.xml
2. yoursite.com/sitemap_index.xml (the classic WordPress/Yoast pattern)
3. yoursite.com/wp-sitemap.xml (WordPress core, since 5.5)
4. Check yoursite.com/robots.txt — a sitemap is usually declared at the bottom

If any of those return XML, you have a sitemap. Your job is to check it’s correct, not to generate a new one.

The generators worth using

WordPress: you already have three options

WordPress has generated sitemaps in core since version 5.5 at /wp-sitemap.xml. It works, and for a small blog it’s genuinely enough. If you run Yoast SEO or Rank Math, either will take over and give you finer control — which post types and taxonomies are included, and which are excluded. That control is the real reason to use a plugin rather than core.

The setting most people should change: exclude tag and author archives unless you’ve deliberately made them useful pages. Thin archive pages in a sitemap invite Google to crawl and judge your weakest URLs.

Static sites and frameworks: it’s built in

Astro, Next.js, Hugo, Eleventy and Gatsby all generate sitemaps natively or via a first-party plugin. This site’s sitemap is a small hand-written endpoint listing only the pages I actually want indexed — which is the point: a generated-from-routes sitemap will happily include pages you’d rather keep out of it.

Screaming Frog SEO Spider — the one I’d reach for

For hand-coded sites, or when you need to build a sitemap from what’s actually crawlable rather than from a database, Screaming Frog is the tool. The free version crawls up to 500 URLs and can export an XML sitemap — genuinely enough for most small sites. Beyond that it’s an annual licence (around £199/$279 at the time of writing).

The advantage over an online generator is that you see the crawl first: redirects, 404s, noindex pages and canonicalised duplicates all surface before you export, so you don’t bake broken URLs into the file.

XML-Sitemaps.com — fine for a quick one-off

The best-known online generator. Free up to 500 pages, no install. It’s the right tool if you need a sitemap once for a small static site and don’t want to download software. It’s the wrong tool for anything you’ll need to regenerate regularly, or for a site of any real size.

A note on the old guard

If you’ve read an older version of this article, it recommended tools like FreeSitemapGenerator and WebCEO. I’ve dropped them. The category has consolidated hard: the platforms generate sitemaps themselves now, and Screaming Frog covers the cases they don’t. Recommending a standalone paid sitemap tool in 2026 would be padding this list, not helping you.

The rules that decide whether it works

These are Google’s stated limits, and breaking them is the most common reason a sitemap silently underperforms:

Rule	Limit	What happens if you break it
URLs per sitemap	50,000	Google ignores everything past the first 50,000
File size	50MB uncompressed	Google may reject the whole file
Larger than that	Use a sitemap index	Submit the index, not each child

Two details worth knowing: the file may be gzipped (the 50MB limit is on the uncompressed size), and only primary <loc> URLs count toward the 50,000 — hreflang alternates don’t consume your quota.

The rules that aren’t about limits matter more in practice:

• Only include URLs you want indexed. No noindex pages, no redirects, no 404s, no non-canonical duplicates. A sitemap full of URLs that resolve to something else is a credibility problem.
• Use absolute, canonical URLs. Exactly the form you want indexed — right protocol, right host, right trailing slash.
• Keep it in sync. A stale sitemap is worse than none, because it actively points crawlers at URLs that have moved.

How to submit a sitemap

1. Declare it in robots.txt. One line, and every crawler that respects robots.txt finds it: Sitemap: https://yoursite.com/sitemap.xml
2. Submit it in Google Search Console. Indexing → Sitemaps → paste the path → Submit. Come back a few days later and read the report — it tells you how many URLs were discovered versus indexed, which is the genuinely useful number.
3. Submit it in Bing Webmaster Tools. Same idea. Bing also supports IndexNow for faster change notification, which is worth enabling if your platform offers it.

You don’t need to resubmit after every update. Search engines re-fetch a submitted sitemap on their own schedule.

Where sitemaps sit in the AI-search era

A fair question in 2026: does any of this matter when a growing share of discovery happens through AI answers? Yes, and for an unglamorous reason — the AI engines that cite sources still need to find and crawl your pages, and most of them lean on the same crawl infrastructure and conventions. A clean sitemap remains part of being findable.

What it doesn’t do is tell an AI engine what your site is about. That’s the gap llms.txt is proposed to fill, and it’s a different file with a different job — I’ve written honestly about whether llms.txt actually works and how it differs from robots.txt. If you want to try one, I built a free llms.txt generator that validates the format as you go.

When a sitemap won’t fix your problem

If pages aren’t getting indexed, the sitemap is rarely the cause. In rough order of likelihood, check:

1. The page is noindex — deliberately or accidentally (see noindex vs disallow)
2. It’s blocked in robots.txt, so Google can’t crawl it to see anything
3. It’s canonicalised to another URL
4. Google crawled it and chose not to index it — usually a quality or duplication judgement
5. Nothing links to it internally, so it looks unimportant

A crawl-based audit surfaces all five quickly. Screaming Frog’s free tier will do it for a small site; for anything larger, Semrush’s Site Audit flags sitemap-specific problems — orphan pages, URLs in the sitemap that redirect or 404, and pages missing from it entirely — alongside the rest of your technical issues. That cross-check between “what’s in the sitemap” and “what’s actually crawlable” is the bit generators can’t do for you.

Run a free site audit→

The short version

Check whether you already have a sitemap before generating one — you probably do. If you need to build one, use Screaming Frog’s free tier for up to 500 URLs, or your platform’s built-in generator. Include only canonical, indexable URLs. Declare it in robots.txt, submit it once in Search Console, and then go and read the coverage report, because that’s where the actual information is.

If practical SEO notes like this are useful, I send them occasionally — subscribe below, and grab the free GEO Starter Checklist while you’re there.

Related reading: if your pages are found but not indexed, start with discovered, currently not indexed. For the wider picture, see technical SEO in the AI era, and if you’re auditing a site properly, the Semrush Site Audit guide covers what to fix first.

Frequently asked questions

Do I still need an XML sitemap in 2026?

Most small sites do not strictly need one, because search engines find well-linked pages on their own — and modern platforms generate a sitemap automatically anyway. A sitemap genuinely helps large sites, brand-new sites with few backlinks, and sites with pages that are poorly linked internally. It never hurts, provided it only contains canonical, indexable URLs.

What is the best free sitemap generator?

For most people it is whatever their platform already provides — WordPress core, Yoast, Rank Math, or the built-in sitemap in Astro, Next.js or Hugo. For hand-coded sites, the free version of Screaming Frog SEO Spider crawls up to 500 URLs and exports an XML sitemap, and it shows you the redirects and errors before you export. XML-Sitemaps.com is a reasonable browser-based alternative for a one-off.

How many URLs can a sitemap contain?

A single sitemap file is limited to 50,000 URLs and 50MB uncompressed. If you exceed either, split the file and submit a sitemap index that points to each part. Google ignores anything past the first 50,000 URLs in a single file and may reject a file over 50MB entirely.

Does a sitemap help my rankings?

No. A sitemap aids discovery, not ranking. It helps search engines find URLs; it does not persuade them the pages deserve to rank, and it does not guarantee indexing. Submitting a sitemap and then seeing pages excluded in Search Console is normal and means the decision was made on other grounds.

Should I set priority and changefreq in my sitemap?

No — Google ignores both. The only optional field worth including is lastmod, and only if it reflects genuine content changes. If your generator stamps the current date on every URL each time it runs, the signal becomes noise and gets ignored.

Where do I submit my sitemap?

Declare it in robots.txt with a Sitemap: line, then submit it in Google Search Console under Indexing → Sitemaps and in Bing Webmaster Tools. You do not need to resubmit after each update; search engines re-fetch it on their own schedule.