What does the sitemap check verify?
It looks for your XML sitemap and confirms it's usable by crawlers. Specifically:
- Reachable — the sitemap returns a
200at a common location (such as/sitemap.xmlor a sitemap index). - Well-formed XML — it parses as valid XML with a proper
<urlset>(a list of URLs) or<sitemapindex>(a list of sitemaps). - Sensible contents — the URLs it lists should be canonical, indexable
200pages, not redirects, errors ornoindexURLs.
A reachable, valid sitemap passes; one that exists but is malformed or partial is a warning; no sitemap found at common locations is a fail.
How is it evaluated, and how is it scored?
GEObubbly fetches the sitemap at common paths (and via the Sitemap: line in robots.txt), confirms a 200 response, and parses it to check for a valid <urlset> or <sitemapindex> structure. It's a core check worth 2 points in Crawlability & Indexability — lower weight than the indexing signals because a sitemap aids discovery rather than gating it.
Why an XML sitemap matters for SEO and GEO
A sitemap doesn't force indexing, but it dramatically speeds up discovery — it tells crawlers which URLs you consider important and when they last changed, so new and updated pages get found and re-crawled sooner. That matters most for large sites, fresh content, and pages with few internal links that crawlers might otherwise miss. A malformed sitemap is worse than none, because errors can cause engines to ignore it or trust it less; and a sitemap full of redirects, errors or noindex URLs sends mixed signals about which pages you actually want indexed. For GEO, faster discovery means your latest, freshest content reaches AI engines sooner — and freshness is something answer engines weight heavily. Keep the sitemap valid, limited to canonical indexable URLs, and declared in robots.txt so it's easy to find. It complements the rest of the Crawlability & Indexability signals.