Check whether sitemap.xml is reachable and parseable
The checker first looks for a sitemap declared in robots.txt on the same origin and otherwise tests the conventional /sitemap.xml location. It reports the final URL and HTTP status instead of assuming the file exists.
The XML is then inspected for url entries, child sitemap entries, loc values and lastmod tags. A sitemap index and a normal URL set are counted separately because they represent different layers of a sitemap architecture.
Count sitemap URLs and inspect a sample
Entry counts are useful for catching accidental empty sitemaps, missing sections or a sitemap index that stopped including a child file. The sample URLs provide a quick sanity check that the sitemap points to the expected canonical host and path structure.
This is a lightweight validator, not a full crawl. It does not fetch every submitted URL or prove that Google has indexed them; it verifies the live sitemap file and its visible XML structure.
lastmod should represent meaningful page updates
The checker counts lastmod elements so you can see whether update dates are present. Search engines may use trustworthy modification dates as a crawl signal, but repeatedly changing dates without meaningful page changes reduces their usefulness.
For large sites, keep sitemap generation deterministic, submit canonical indexable URLs and split oversized URL sets into sitemap indexes according to search-engine limits.