About XML Sitemaps
What is an XML sitemap?
An XML sitemap is a machine-readable list of the pages on a site that you want search engines to know about, usually annotated with when each was last changed. It is written for crawlers rather than people, which is why it looks like a data file instead of a page.
It is a hint, not an instruction. Listing a page does not guarantee it will be indexed, and omitting one does not prevent it. What a sitemap does is remove the discovery problem: instead of finding your pages by following links and hoping the path is short enough, a crawler is handed the list.
An XML sitemap checker answers the first question worth asking, which is simply whether one exists and can be found. A surprising number of sites have a sitemap that nothing references and no crawler has ever requested.
Do XML sitemaps still matter in 2026?
For a small, well-linked site they add little, and that is worth saying plainly. Search engines are good at following links, and a fifteen page site is not a discovery challenge.
For everything else they remain valuable, for three distinct reasons. Large sites have pages buried too deep to be crawled promptly, sites publishing frequently need new content noticed quickly, and any site with archives has pages that no longer receive internal links but still deserve to be indexed.
They are also the cheapest diagnostic available. Comparing the number of URLs submitted against the number indexed exposes problems that nothing else surfaces as clearly.
How sitemaps relate to AI search
AI crawlers face the same discovery problem as search crawlers, and a sitemap is the same shortcut. Content that is hard to reach by following links may simply never enter the pool a model draws on.
The last-modified dates carry more weight here than they used to. Freshness is a strong signal when a system is choosing between several sources on a subject that changes, and an accurate modification date is one of the few pieces of provenance a site can state directly.
That makes honesty about those dates more valuable than keeping them recent. A site resetting every date on every build teaches crawlers to disregard the field entirely.
Sitemap best practices
- Include only canonical, indexable URLs that return a 200 status.
- Leave out redirects, blocked pages and anything marked noindex; contradictory signals get disregarded.
- Keep last-modified dates accurate rather than resetting them on every deployment.
- Split into multiple files with an index once you pass 50,000 URLs or 50MB uncompressed.
- Reference the sitemap from robots.txt and submit it in Search Console.
- Regenerate it when the site changes structurally, not once at launch and never again.
What this tool checks
The tool looks for an XML sitemap for the domain and passes when it finds one containing URLs.
It confirms presence rather than correctness, so a sitemap listing redirects, blocked pages or addresses that no longer exist will still pass. Whether the contents are sound is a separate question, and one worth answering.
Where to go next