SitemapScan Blog

Sitemap Index vs URL Set: How to Tell the Difference and Why It Matters

A sitemap index and a sitemap URL set are not interchangeable. Knowing which one you're looking at changes how you audit coverage, child sitemaps, and the overall structure of a site's crawl map.

The structural difference

A URL set sitemap contains actual page URLs wrapped in <url> entries. A sitemap index contains <sitemap> entries that point to other sitemap files. One is a leaf-level URL inventory; the other is a coordination layer that helps large sites organize many sitemap files.

Why the distinction matters in audits

If you mistake a URL set for an index, you may expect child sitemaps that do not exist. If you mistake an index for a URL set, you may undercount site coverage because you never expand into the child files. This is one of the easiest ways to misread a large site's sitemap estate.

Where people get confused

A compressed sitemap URL or a file with 'sitemap' in the hostname can look important even when it is just one child file. Conversely, the real coordinating file may be a .xml.gz index that you ignore because it is not the first file declared in robots.txt. The XML root element, not the filename, tells you the truth.

About this article

This article is part of the SitemapScan blog and covers XML sitemap, robots.txt, crawlability, or related technical SEO topics.

FAQ

How can you tell whether a sitemap is an index or a URL set?

Inspect the XML root element. A sitemapindex contains child sitemap entries, while a urlset contains actual page URLs.

Why does this distinction matter in an audit?

Because confusing a sitemap index with a URL set changes how you interpret coverage, structure, and child sitemap expansion.

Related pages

Open the full article