RevealTheme logo

Sitemap Inspector

Fetch any public XML sitemap by URL and see its type, total URL count, sub-sitemap list, and how many entries carry a lastmod date.

How to use this tool

  1. 1

    Paste the full URL of your XML sitemap (for example https://example.com/sitemap.xml) into the input field.

  2. 2

    Run the tool — our server fetches the file over HTTPS (falling back to HTTP) and parses it as XML.

  3. 3

    Read the summary cards: detected Type, URL count, sub-sitemap count, and number of lastmod entries.

  4. 4

    Scan the listed sub-sitemaps and the first 200 URLs to confirm the structure looks right.

What is an XML sitemap and what does this tool check?

An XML sitemap is a file that lists the URLs on a site so search engines can discover them more easily. It follows the sitemaps.org protocol: a <urlset> root wrapping <url> entries, each with a <loc> and optional <lastmod>, <changefreq>, and <priority>. A sitemap index instead uses a <sitemapindex> root containing <sitemap> entries that point to other sitemap files — needed because a single sitemap is capped at 50,000 URLs or 50 MB uncompressed. This tool fetches the URL you give it server-side, parses it in XML mode, and reports four things: the detected type (it labels the file a sitemap index whenever it finds any <sitemap><loc> elements, otherwise a urlset), the count of <url><loc> entries, the count of sub-sitemaps, and how many <url> entries include a <lastmod>. It is a quick structural inspector, not a validator. It does not check schema conformance, parse changefreq or priority, or recursively crawl into the sub-sitemaps an index points to — you would open those individually. Fetches are limited to 5 MB and a 20-second timeout, and private or internal hosts are blocked.

Common use cases

  • Confirm a newly generated sitemap actually contains every URL you expected before submitting it in Google Search Console.

  • Check whether a site uses a flat urlset or a sitemap index, and grab the list of child sitemap URLs to inspect each one.

  • Audit lastmod coverage by comparing the lastmod-entry count against the total URL count to spot missing change dates.

  • Spot-check a competitor's public sitemap to gauge how many indexable URLs their site exposes.

  • Verify that a sitemap moved to a new domain or path still returns valid XML after a migration or redirect.

  • Debug why search engines may not be picking up pages by confirming the expected URLs appear in the first 200 listed entries.

Frequently asked questions

Is my sitemap data uploaded anywhere?▼
The URL you enter is sent to our server, which fetches that public sitemap on your behalf and parses it — the fetch does not happen in your browser. We do not store the sitemap; we read it, count the entries, and return the summary for that single request.
What is a sitemap index?▼
A sitemap that points to other sitemaps using <sitemap><loc> entries under a <sitemapindex> root. You need one when a single sitemap would exceed the protocol limit of 50,000 URLs or 50 MB uncompressed. This tool labels a file a sitemap index whenever it detects any <sitemap> elements.
Does it follow and count URLs inside the sub-sitemaps?▼
No. It parses only the file at the URL you submit. For a sitemap index it lists the child sitemap URLs (up to 50) but does not fetch them, so the URL count reflects this one file, not the whole site. Run the tool again on each child sitemap to inspect those.
Why does it only show the first 200 URLs?▼
The summary caps the displayed URL list at 200 entries and the sub-sitemap list at 50 to keep the response fast and readable. The URL count card still reflects the true total parsed from the file.
Does every URL need a lastmod date?▼
No. lastmod is optional in the sitemaps protocol. Google uses it as a hint to decide when to recrawl a page but ignores it if it looks unreliable, and changefreq and priority are largely ignored. The lastmod count here just tells you how many <url> entries declare one so you can judge your coverage.
Can it inspect a gzipped (.xml.gz) sitemap?▼
No. The tool decodes the response as UTF-8 text and parses it as XML, so it expects an uncompressed .xml file. Point it at the plain XML version if your CMS serves both.
Why did the fetch fail?▼
Common causes are a sitemap larger than the 5 MB limit, a response slower than the 20-second timeout, more than five redirects, or a private/internal host, which is blocked for security. The tool returns the error message so you can tell which applies.

Related tools

Meta Tags Analyzer

Extract and analyze every meta tag from any URL.

Heading Hierarchy Analyzer

Audit H1-H6 structure for SEO and accessibility issues.

Schema Markup Validator

Extract and validate JSON-LD schema from any page.

Open Graph Inspector

Preview how a URL appears on Facebook, Twitter, and LinkedIn.

robots.txt Inspector

Parse robots.txt and flag common mistakes.

Page Word Count

Count visible words on any URL.

Subscribe for updates

We do not sell your email. We do not spam.

© 2026 RevealTheme. All rights reserved.