Sitemap index vs. URL sitemap: which format should you use?
Understand the difference between sitemapindex and urlset files, when to split sitemaps, and how to organize large URL inventories.
Direct answer
Use a URL sitemap with a urlset root when one file can hold the intended canonical URL inventory. Use a sitemap index with a sitemapindex root when the site needs multiple sitemap files by size, content type, locale, or operational ownership. A sitemap index lists sitemap files, not page URLs.
Use urlset for page locations
A URL sitemap contains one url element per submitted location. The loc value is required; lastmod is optional and should reflect a meaningful page update rather than an automated timestamp change.
A small site can use one sitemap.xml file. Multiple files are not inherently better and should not be introduced without an operational reason.
Use sitemapindex to group sitemap files
A sitemap index contains sitemap elements whose loc values point to child sitemap documents. It is useful when the inventory exceeds one file's limits or when separate systems publish product, article, locale, image, or video sitemaps.
Do not place page URLs directly under sitemapindex. Validators and search engines expect child sitemap locations at that level.
Choose boundaries that help maintenance
Split files along boundaries that let a team diagnose change and failure. Product templates, editorial content, languages, and separately deployed applications are usually more useful than arbitrary numeric batches.
Every child sitemap still needs successful delivery, valid structure, and eligible URLs. A valid parent index does not make a failed child document acceptable.
- Keep one file when the inventory is small and centrally generated.
- Split by template or system when ownership and debugging improve.
- Use a parent index when multiple child files must be submitted together.
- Monitor child sitemap failures separately.
Implementation checklist
- ✓urlset documents contain page URL entries.
- ✓sitemapindex documents contain child sitemap entries.
- ✓Every child sitemap is reachable and valid.
- ✓File boundaries reflect real templates or ownership.
- ✓The inventory remains within the URL and size limits.
Frequently asked questions
Can one website have multiple sitemap indexes?
Yes, when separate applications or large inventories require them. Keep discovery and ownership clear rather than creating unnecessary layers.
Should each content type have a separate sitemap?
Only when it improves generation, monitoring, or diagnosis. The format does not require one file per content type.
Primary sources
These references support the standards and product behavior described above. They do not imply endorsement of Index Instrument.