Case Studies XML Nest Creator: nested sitemaps for large sites
XML Nest Creator: nested sitemaps for large sites
TL;DR One giant sitemap does not scale, and search engines cap how many URLs a single file may hold. XML Nest Creator builds a nested structure, a sitemap index pointing at child sitemaps, so a large WordPress site stays within limits and gets crawled efficiently.
Small sites get one tidy sitemap and never think about it again. Large ones hit a wall: a single sitemap file cannot hold everything, and cramming it does not help crawlers either. XML Nest Creator builds the nested structure that big WordPress sites need.
The problem
A sitemap file has hard limits: 50,000 URLs and 50 MB. A large site, a news archive, a big catalogue, a long-running publisher, blows past that. Beyond the limit, a single sitemap is not just discouraged, it is invalid.
The answer is a nested structure: a sitemap index at the top that points at multiple child sitemaps, each holding a slice of the URLs. But building and maintaining that by hand, and keeping it correct as content grows, is exactly the kind of thing a plugin should handle.
The approach
XML Nest Creator generates the nested structure automatically.
- A sitemap index at the top, listing the child sitemaps.
- Child sitemaps that each stay within the URL and size limits.
- Logical grouping, so URLs are split into sensible child files rather than arbitrary chunks, which helps crawlers focus on what changed.
The site owner does not manage the structure by hand; the plugin keeps it valid as the site grows.
What shipped
XML Nest Creator builds nested XML sitemap structures for large WordPress sites, keeping every file within the limits and letting search engines crawl the site efficiently. A site that had outgrown a single sitemap gets a valid, well-organised index without anyone hand-editing XML.
What I learned building it
The lesson was that scale changes the shape of a problem, not just its size. A sitemap is trivial until you cross the limit, at which point the naive approach is not slow, it is invalid, and the whole thing has to be restructured. Designing for the nested case from the start, rather than bolting it on when a site grows, is what makes the plugin useful to the sites that actually need it.
XML Nest Creator is one of my WordPress plugins. The full set is in the products section of the site.
FAQ
Why split a sitemap into a nested structure?
A single sitemap file is limited to 50,000 URLs and 50 MB. Large sites blow past that, so you use a sitemap index that points at multiple child sitemaps. That keeps each file within limits and lets crawlers fetch them in parallel.
Does a nested sitemap help crawl efficiency?
It helps in two ways: it keeps each file small enough to parse quickly, and grouping URLs into logical child sitemaps, by type or section, lets you signal freshness per group so crawlers focus on what changed.
Who needs this?
Large WordPress sites, thousands or tens of thousands of URLs, news and catalogue sites especially. A small blog is fine with one sitemap; the nested structure matters once you exceed what a single file can hold.