XML Sitemap with Over 50k URLs

What the 50,000 URL limit really means

The sitemaps.org protocol that Google and Bing both follow sets two hard ceilings on a single sitemap file: a maximum of 50,000 URLs and a maximum uncompressed size of 50 MB. Hit either ceiling and the crawler stops reading at the limit, so every URL past it is invisible through that sitemap. The file can be gzip compressed on the wire, but the 50 MB test is measured on the uncompressed document, which is the limit teams forget most often on sites with long URLs and many optional tags.

The fix is a two level structure. You keep each individual sitemap under both ceilings, then you create a sitemap index file, the one that opens with a <sitemapindex> root element, that points to each child file. The index itself can list up to 50,000 sitemaps, which gives you a theoretical ceiling of 2.5 billion URLs before you need a second index. In practice you will paginate long before that for crawl and reporting reasons.

A worked example

Say an ecommerce catalog has 250,000 product URLs. You divide them into five files of 50,000 (or, more comfortably, eight files of about 31,000 each so you have headroom to grow). Each file is a normal urlset. The index then ties them together:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-products-1.xml</loc>
    <lastmod>2026-07-22</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-products-2.xml</loc>
  </sitemap>
</sitemapindex>

Then you add one line to robots.txt so any crawler can discover the whole tree without a manual submission: Sitemap: https://example.com/sitemap_index.xml. In Search Console you submit only the index URL. Google expands it and reports coverage per child file, which is exactly why splitting by content type (products, categories, blog) makes debugging far easier than an arbitrary numeric split.

How platforms handle this for you

On WordPress, Yoast and Rank Math both paginate at 1,000 URLs per file by default and emit an index automatically, so you rarely touch this by hand. Shopify caps its generated sitemaps at 50,000 URLs and shards them for you. The manual work almost always appears on custom or headless builds where an engineer wrote the sitemap route and never anticipated the catalog growing past 50,000 rows. That is the case this check is designed to catch.

How to detect the problem

1. Count with Screaming Frog. In list mode, load your sitemap URL under Configuration then Spider then Crawl Linked XML Sitemaps. The crawl summary shows URLs per file.
2. Read the Search Console sitemaps report. A discovered count that plateaus at exactly 50,000 while your catalog is larger is the classic fingerprint.
3. Check the raw file size. Download the sitemap and confirm the uncompressed document is under 50 MB, not just the gzip.

If your crawl budget is already tight, an oversized sitemap compounds the problem because it hides the very URLs you most want discovered. Our guides on crawl budget and index bloat cover the discovery side, and the Screaming Frog advanced usage guide walks through counting sitemap URLs at scale. For the full family of sitemap checks, see the XML sitemaps hub.

Frequently asked questions