Sitemap Index Files: When One sitemap.xml Isn't Enough

A single sitemap.xml file is capped at 50,000 URLs and 50MB uncompressed by the Sitemap Protocol spec — limits most sites never come close to, right up until they do, usually as a result of steady growth rather than a deliberate decision. A sitemap index file is the spec's answer to what happens next.

What a sitemap index actually is

Structurally, it's a different root element — <sitemapindex> instead of <urlset> — containing a list of <sitemap> entries, each pointing to the location of a real, separate sitemap.xml file with its own <lastmod>. It's a sitemap of sitemaps: instead of one URL going into Search Console, you submit the index, and it tells crawlers where to find each of the actual child sitemaps.

<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
    <lastmod>2026-07-10</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-blog.xml</loc>
    <lastmod>2026-07-15</lastmod>
  </sitemap>
</sitemapindex>

When you actually need one

Strictly, only once a single sitemap would exceed 50,000 URLs or 50MB. In practice, plenty of sites split into multiple sitemaps well before hitting that ceiling anyway — organizing by content type (pages, blog posts, products) makes each individual sitemap more maintainable and easier to debug, even without an index tying them together formally. Whether that split needs a formal <sitemapindex> or can just be several independent sitemaps each submitted separately to Search Console depends mostly on whether you want one submission point or several.

Splitting by content type vs. splitting by size

Two different reasons lead to multiple sitemaps, and they call for different structures. Splitting by content type (a sitemap for products, a separate one for blog posts) is an organizational choice, useful regardless of size, since it makes each sitemap's purpose clear and each one independently regenerable when just that content type changes. Splitting purely because of the 50,000-URL ceiling is a mechanical requirement — a single content type (say, a product catalog) that itself exceeds the limit has to be split into several numbered sitemaps (sitemap-products-1.xml, sitemap-products-2.xml) regardless of any organizational preference, since the limit is per-file, not per-content-type.

Do you have to use a sitemap index, or can you just submit several sitemaps separately?

Search Console accepts either — you can submit multiple independent sitemap URLs one at a time, or submit a single sitemap index that references all of them. The index is mainly a convenience: one submission instead of several, and one place to see all child sitemaps' last-modified dates at a glance. Neither approach is required by the other; plenty of sites run multiple sitemaps with no index at all, submitting each one separately.

Validate the whole set

FreeToolDev's bulk sitemap validator checks both regular sitemaps and sitemap index files for structural validity, and can validate several files — a full split sitemap set — in one pass, which is useful for confirming every child sitemap referenced by an index actually has the required tags before submitting the whole set.