XML Sitemap Analyzer

Instructions

1. Enter the URL of your sitemap in the "Sitemap URL" field above — for example https://example.com/sitemap.xml.
2. Click "Analyze" to fetch and analyze the sitemap.
3. Read the results. For a regular sitemap you get the total URL count, the oldest and newest lastmod dates, and a breakdown of URLs by path segment. For a sitemap index you get each child sitemap and its own URL count.

The sitemap is fetched through this site's server rather than from your browser, which sidesteps the cross-origin restrictions that would otherwise block reading another domain's sitemap.

What you get back

URL count. The number of <url> entries in the sitemap. Worth comparing against the indexed count in Search Console — a large gap in either direction is the signal, and which direction it goes tells you whether you have an indexing problem or a sitemap that is advertising pages you didn't mean to submit.

Directory structure — URLs by path segment. Every URL is bucketed by its first path segment, and the counts are sorted largest-first:

/blog     412
/products 288
/docs      96
(root)      1

URLs with no path segment at all are counted as (root). This is the fastest read available on how a site is actually shaped, as opposed to how its navigation implies it is shaped. A section you thought was small holding 400 URLs is usually a pagination or faceting leak.

Lastmod range. The oldest and newest <lastmod> values found. If the newest is months old, the sitemap isn't being regenerated. If every URL shares one identical timestamp, the lastmod values are being stamped rather than tracked, and search engines will learn to ignore them.

Sitemap index files

If the URL you enter is a sitemap index — a <sitemapindex> root rather than a <urlset> root — the tool lists each child sitemap it declares and fetches them to report a URL count for each one:

<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/post-sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://example.com/page-sitemap.xml</loc>
  </sitemap>
</sitemapindex>

Children are fetched one at a time and capped at the first 10, to stay polite toward the site being analyzed. If a child sitemap can't be fetched, that row reports the failure instead of a count rather than failing the whole analysis — one broken child sitemap is itself a finding.

Indexes are expanded one level. If a child is itself an index, its URL count reads as 0, since it contains <sitemap> entries rather than <url> entries. Analyze that child directly to go deeper.

Notes on what it reads

The parser reads the elements that matter for structure — <loc> and <lastmod> — and ignores <changefreq> and <priority>, which search engines largely ignore too. Values that don't parse as URLs are skipped in the path breakdown rather than counted under a junk segment.

Once you know which section you want to look at, the Bulk URL Opener will open a list of URLs in tabs all at once.