How many URLs can a sitemap have? 50,000. That is the cap set by the sitemaps protocol and repeated in Google’s own sitemap documentation: a single sitemap file may contain at most 50,000 URLs and may not exceed 50MB uncompressed. Whichever limit you hit first is the one that counts.
That is the answer people search for. The more useful answer is that if you are anywhere near either limit, you are almost certainly building your sitemaps wrong, and the rest of this note is about that.
The limits, precisely
Three numbers matter, and they stack:
- One sitemap: up to 50,000 URLs, up to 50MB uncompressed. You can gzip the file for transfer, but the 50MB is measured on the uncompressed XML.
- One sitemap index: up to 50,000 sitemaps listed, and the index file itself has the same 50MB cap. An index cannot list another index for Google; no nesting.
- Search Console: Google’s large sitemap documentation says you can submit up to 500 sitemap index files per site.
So the theoretical ceiling through one index is 2.5 billion URLs, and through Search Console far beyond that. Google indexes whole retail platforms and news archives through this structure. Whatever size your site is, the protocol is not your constraint.
Do more sitemaps help SEO?
No. This needs saying because it is the wrong reason people ask about limits. A sitemap does not make Google index anything; it is a list of URLs you consider canonical, which Google treats as a hint for discovery. Splitting one sitemap into fifty does not earn you fifty times the crawling, and stuffing 50,000 URLs into a file does not oblige Google to index 50,000 pages. On sites I audit, the sitemap usually claims several times more URLs than Google has indexed, and the sitemap is not the reason either way.
Why I split sitemaps long before 50,000
Because Search Console reports indexing per sitemap, and that turns your sitemap structure into free diagnostics. The Pages report has a sitemap filter: submit one blob of 48,000 mixed URLs and the filter tells you almost nothing, but submit products.xml, categories.xml, blog.xml and locations.xml under one index and the same report becomes a per-template indexing scoreboard. When a client says Google dropped their pages, the first question is which sitemap the drop concentrates in, and sites with segmented sitemaps answer that in one screen. All of that assumes the report can read the file at all; when it shows Couldn’t fetch on a sitemap, that fetch failure comes first.
My working rule: one sitemap per template or content type, capped around 10,000 URLs, all under a single index file. The cap is not about the protocol; files that size regenerate fast, diff cleanly, and when one of them shows 9,000 submitted and 400 indexed you know exactly which template to investigate. I keep a status-by-status guide to what the Pages report tells you about those URLs once you find them.
What actually goes wrong with big sitemaps
The failures I meet in audits are never “too many URLs”. They are: the sitemap lists redirected and 404 URLs, so Google learns to trust it less; it lists non-canonical variants, parameters and http duplicates; lastmod stamped with the current time on every generation, which is the one condition Google attaches to using lastmod at all; and the index referencing sitemap files that 404. Every one of those hurts you inside the limits. This site’s sitemap health check catches that class of problem, and the sitemap index coverage tool reads the per-sitemap indexing numbers straight from Search Console so you can see which segment is failing.
If your platform generates one giant sitemap and you cannot change it, do not panic either. Under 50,000 URLs and 50MB it is valid, Google will read it, and your indexing problems, if you have them, live elsewhere. The split is worth doing for visibility, not validity.
Visibility is the whole argument, because the Sitemaps report will tell you the file parsed and nothing more. If yours says Success and the pages still are not in Google, that gap has its own answer, and it is not in the Sitemaps report.
Sources
- Sitemaps.org, sitemaps XML protocol
- Google Search Central, build and submit a sitemap
- Google Search Central, manage large or multiple sitemaps