Sitemap.xml Inspector
Paste a sitemap.xml URL — get URL count, section breakdown, freshness, and issues. Handles sitemap index files recursively. SSRF-guarded.
How to use this inspector
- Paste your sitemap.xml URL. Point it at the sitemap itself, not the homepage — e.g. https://yoursite.com/sitemap.xml.
- It fetches recursively. If it's a sitemap index, every child sitemap is fetched too, up to 3 levels deep and capped at 200 children per level.
- Read the breakdown. Total URL count, section split by first path segment, oldest/newest lastmod, how many entries are missing lastmod, and any issues found.
What this inspector checks
- Total URL count — across every child sitemap if it's an index.
- Section breakdown — entries grouped by the first path segment, so you can see where the bulk of your indexed URLs live.
- Freshness — the most recent and oldest
<lastmod>dates found, plus how many entries have none at all. - Sitemap index support — recursively fetches child sitemaps up to 3 levels deep, capped at 200 children per level so a malformed or malicious index can't hang the request.
- Size limit — flags sitemaps over Google's hard 50,000-URL cap.
- SSRF guard — refuses private-network hosts (localhost, 10.x, 192.168.x) before fetching anything.
Frequently asked questions
What does this tool actually check?
Total URL count, child sitemap count (if it's an index), URLs grouped by section, the most recent and oldest lastmod dates, the count of entries missing lastmod, and obvious issues (over 50k URLs, broken fetches, wrong content-type).
Why does Google care about lastmod?
Google uses lastmod to decide what to recrawl. An accurate lastmod tells Google 'this page changed' so it recrawls and re-indexes. Missing lastmod forces Google to use other signals — slower indexing of updates.
What's the maximum size of a sitemap?
50,000 URLs per sitemap, 50 MB uncompressed. Beyond that you must use a sitemap index file pointing to multiple child sitemaps.
Does this work with sitemap index files?
Yes. The inspector recursively fetches each child sitemap listed in an index file (up to depth 3) and aggregates the totals across all of them.
Why was my private/localhost URL rejected?
We block private network hosts (localhost, 10.x, 192.168.x, etc.) as a server-side request forgery (SSRF) defense. Public URLs only.
Does this check whether each URL in the sitemap actually loads?
No. It parses the sitemap's own XML — URL count, structure, lastmod dates — but doesn't fetch every listed URL to check for 404s or redirects. A sitemap can pass this inspection and still list a broken URL. For that, spot-check individual URLs with the site auditor or canonical checker, or crawl the full list with a dedicated crawler.
Can it tell me if Google has actually indexed these URLs?
No — nothing outside Google Search Console can answer that. This tool only reports what your sitemap claims; whether Google chose to index each URL is a separate question GSC's Coverage report answers.
A sitemap that maintains itself
InBuild sites serve a dynamic sitemap.xml that updates as you add routes — no stale URLs, no orphaned pages, no regenerating it by hand every time the site changes.