XML Sitemap Validator

1. The XML Sitemap Protocol

A valid sitemap follows a specific XML structure — an <urlset> root element (or <sitemapindex> for index files) containing one <url> entry per page, each with at minimum a <loc> tag holding the absolute URL. Google's own documentation notes that a sitemap doesn't guarantee indexing — it's a discovery aid, not a directive — but a malformed or unreachable sitemap actively hurts discovery of pages that have few internal links pointing to them.

2. Sitemap Index vs. Urlset File Structures

A standard sitemap (<urlset>) lists actual page URLs directly. A sitemap index (<sitemapindex>) instead lists the locations of multiple child sitemap files — used once a site exceeds the 50,000-URL / 50MB single-file limit, or simply as an organizational pattern (splitting sitemaps by content type: posts, pages, products, categories). This tool identifies which structure a given URL uses and counts direct <loc> entries either way, though for a sitemap index the counted entries are the child sitemap URLs themselves, not the underlying pages inside them.

3. Declaring Sitemaps in Robots.txt

Referencing a sitemap's location via a Sitemap: directive in robots.txt is the standard way to make it discoverable without manual submission to each search engine's webmaster tools. If you're validating a sitemap because search engines don't seem to be finding it, confirm it's actually declared correctly with the robots.txt Validator.

4. Sitemap Delivery via Nimbica Static Edge

Nimbica serves XML sitemaps as pre-rendered static files from its edge network for connected sites, so a sitemap fetch — whether from a search engine crawler doing routine re-checks or a large site with a substantial sitemap index — never triggers origin PHP execution.

5. How to Use This Validator

1. Enter the sitemap URL directly — usually at a predictable path like /sitemap.xml or /sitemap_index.xml for WordPress SEO plugins.
2. Confirm the HTTP status is 200 and the XML declaration check passes — either failing means search engines can't reliably parse it.
3. Check the URL count against your rough expectation (roughly how many published pages/posts you have) — a count far lower than expected suggests missing content; far higher suggests stale or duplicate entries.
4. If it's a sitemap index, spot-check a few of the listed child sitemaps individually with this same tool to confirm they're each valid too.

6. Common Sitemap Mistakes

• Including non-indexable URLs. Pages marked `noindex`, blocked by robots.txt, or redirecting elsewhere shouldn't appear in the sitemap — their presence sends search engines a contradictory signal.
• Sitemap not updating after content changes. A cached or statically-generated sitemap that doesn't refresh when new content publishes defeats the purpose of using one for faster discovery.
• Forgetting the robots.txt declaration. A perfectly valid sitemap that's never referenced anywhere still needs manual submission via each search engine's webmaster tools to be found.
• Mixing HTTP and HTTPS URLs, or www/non-www inconsistently, within one sitemap. Every listed URL should match the site's canonical protocol and hostname exactly.

7. Who Should Use This Tool

Site owners and developers confirming a sitemap was generated correctly after a CMS or plugin change, SEOs auditing a client's technical setup, and anyone troubleshooting why certain pages aren't getting indexed who wants to rule out a sitemap-level problem first.

8. Limitations

This check validates structural presence (XML markers, `<loc>` entries, HTTP reachability) — it does not fetch and verify each individual listed URL, validate optional fields like `lastmod` date formatting, or check the file against the full formal XML schema. A sitemap index's child sitemaps are identified but not automatically crawled and validated in turn; check each one individually if needed.