What is a Sitemap Site validator and how does it parse XML Sitemaps and robots.txt files?
A Sitemap Site validator parses W3C Sitemaps 0.90 XML trees (<urlset>, <sitemapindex>, <loc>, <lastmod>) alongside RFC 9309 robots.txt exclusion directives. It verifies that every canonical URL in page-sitemap.xml returns HTTP 200, remains below the 50,000-URL / 50MB protocol ceiling, and is not blocked by wildcard User-agent: * or bot-specific Disallow rules.
How does the robots.txt checker evaluate wildcard User-agent: * versus AI bot-specific rules?
Per IETF RFC 9309, our robots.txt tester evaluates wildcard User-agent: * directives as the baseline and applies specific User-agent blocks (such as OAI-SearchBot, PerplexityBot, Claude-SearchBot, Googlebot, and GPTBot) as overrides. If User-agent: * contains Disallow: / without an explicit bot-specific Allow: /, all 6 AI search citation bots are flagged as BLOCKED.
How do you find a sitemap of a website or competitor domain automatically?
To find the sitemap of a website, our sitemap finder probes 5 deterministic endpoints in parallel: (1) Sitemap: declarations inside /robots.txt, (2) /sitemap_index.xml, (3) /sitemap.xml, (4) /page-sitemap.xml, and (5) /feed.xml or /atom.xml syndication feeds.
Why does Google Search Console ignore <priority> and <changefreq> while enforcing <lastmod> accuracy?
Google Search Central documentation confirms that Googlebot ignores <priority> and <changefreq> attributes in XML sitemaps because webmasters routinely hardcode 1.0 and daily. Conversely, Googlebot actively parses ISO-8601 <lastmod> timestamps whenever they reflect genuine content modifications.