GSC sitemap limits

Google Search Console (GSC) enforces two hard limits on sitemap submission:

1. 500 sitemaps per verified property. This includes both child sitemaps and the sitemap index referencing them.
2. 50,000 URLs OR 50 MB uncompressed per individual sitemap file. The smaller of the two applies.

These are the same limits documented in the original sitemap protocol from 2008. Google has not raised them since.

What "500 sitemaps per property" actually means

If you submit a sitemap index in GSC, the index URL counts as one sitemap. Each child sitemap it references counts as another. So a property with one index + 450 child sitemaps = 451 sitemaps, which is under the cap. A property with two separate indexes + 400 child sitemaps in each = 802 sitemaps, which exceeds the cap and gets truncated.

For sites large enough to hit 500, the workaround is to submit multiple separate properties in GSC (e.g., one per language, one per content type). Each property gets its own 500-sitemap budget.

What 50,000 URLs / 50 MB means in practice

The 50K URL ceiling matters more than 50 MB for most sites. A simple <url><loc></loc></url> entry is about 80 bytes uncompressed, so 50,000 entries = ~4 MB. You'd hit 50 MB only if every URL also carried hreflang, image, or video extensions, or had very long URLs.

If you split URLs into multiple sitemaps, the spec lets you reference them all from a sitemap index. SitemapHost auto-splits at the 50K boundary and generates the index for you.

"Couldn't process the sitemap" errors

GSC's most common sitemap error is the generic Couldn't process the sitemap. The actual cause is usually one of:

• Sitemap exceeded 50,000 URLs or 50 MB.
• Sitemap index referenced a child sitemap on a different host (cross-domain not verified).
• XML parsing error — invalid encoding, missing namespace, mismatched tags.
• Sitemap returned a non-200 status code when GSC tried to fetch it.
• Sitemap took longer than ~30 seconds to fetch.

GSC shows a more specific error after a few minutes, but the initial message is unhelpful.

Recommended file sizes

For most sites, smaller sitemaps are better:

Smaller files give GSC more granular indexing reports per sitemap, but use up more of the 500-sitemap budget. The balanced tier is the most-recommended default.

What SitemapHost does

SitemapHost auto-splits at the requested tier (default: 50,000) and generates a sitemap index. Splitting is deterministic — re-pushing the same URL list produces the same file names. We refuse to generate more than 450 sitemaps per submission to stay safely under the GSC 500 ceiling with headroom for index files.