New researchTechnical SEO & AI Search · 2027Explore the framework

Sitemap index SEO: split large XML sitemaps without losing coverage

When and how to split large XML sitemaps, build a sitemap index, submit it to Google and diagnose missing or stale URL groups.

Part of the Enterprise Technical SEO series. For the full picture, start with Enterprise technical SEO: a scalable audit framework.

A growing site often reaches a point where one sitemap.xml becomes difficult to maintain or exceeds the size limit. The solution is not to drop older URLs. Split the inventory into valid files and give search engines one index that points to them.

What is a sitemap index for SEO?

A sitemap index is an XML directory of sitemap files, not a list of page URLs. Google’s sitemap index documentation recommends it when a sitemap exceeds the limits, so several smaller files can be submitted together. It also makes a large site’s sections easier to inspect separately.

This is a more specific task than the general XML sitemap audit, which checks URL quality and discoverability regardless of size.

When should you split a sitemap?

Google’s sitemap building guide sets two limits for an individual sitemap: 50,000 URLs and 50 MB uncompressed. Reaching either means you need another file. You may also choose smaller, stable groups so you can locate a faulty product or article feed quickly.

Split strategy Useful when Watch for
Page type Products, categories and articles update differently A URL moving between groups without duplicate entries
Site section Teams own distinct sections Empty or retired sections left in the index
Fixed-size chunks One template has a huge inventory Chunks reshuffling every build, making changes hard to track
Update cadence News or inventory changes much faster than evergreen pages Stale lastmod values that reflect a build, not real changes

Choose a rule you can regenerate reliably. Splitting does not rescue weak URLs: each child should still contain the canonical, indexable pages you want in search, not redirects, 404s or tracking variants.

How do you build and submit a sitemap index?

Generate the child files first, then list their absolute URLs inside <sitemapindex>. Google requires each entry to have a <loc> and allows an optional <lastmod> for when that sitemap file changed. The referenced sitemaps normally need to be on the same site and at the same directory level or deeper than the index; Google’s documentation explains the cross-site submission exception.

<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap><loc>https://example.com/sitemaps/products.xml</loc></sitemap>
  <sitemap><loc>https://example.com/sitemaps/articles.xml</loc></sitemap>
</sitemapindex>

Put the index at a path that can reference those children, submit its URL in Search Console, and optionally list it in robots.txt. Fetch the index and every child as an unauthenticated visitor. Validate that each returns 200, parses as XML and contains only current absolute URLs.

What should you check after submission?

Open the Sitemaps report for the index and each child. A successful fetch means Google can read the file, not that every listed page was indexed. Compare each child’s submitted URLs with the intended section inventory, then inspect representative missing URLs in the Page indexing report.

If one child has many excluded pages, isolate whether the cause is canonical selection, noindex, errors or low-value duplicates. A crawl can compare the generated list with actual page responses; the crawling and indexing guide explains why discovery and indexing are separate decisions.

Large-sitemap checklist

  • Each child stays under both size limits
  • Index and children return 200 and valid XML
  • Child paths meet the index location rules
  • URLs are absolute, canonical and intended for indexing
  • Removed pages disappear from regenerated files
  • Search Console reports are reviewed per child, not only for the index

A sitemap index makes a large inventory manageable. The useful outcome is an accurate, inspectable set of URLs, not a larger count of submitted pages.

Frequently asked questions

How many URLs can one XML sitemap contain?

Google limits one sitemap to 50,000 URLs or 50 MB uncompressed, whichever limit you reach first. Split a larger inventory across child sitemaps and list them in a sitemap index.

Does a sitemap index improve rankings?

No. It organizes discovery and submission for large URL inventories, but neither a sitemap nor an index guarantees crawling, indexing or ranking.

Should I split sitemaps by page type?

You can split by section, template or update cadence if that makes errors easier to isolate. The important part is keeping each file valid and generated from the current canonical URL inventory.

Can a sitemap index contain another sitemap index?

Google's sitemap index documentation describes child entries as sitemaps, not nested indexes. Submit separate index files when needed instead of assuming nested indexes will be processed.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows