Sitemap checker: the five-minute check founders skip
What a sitemap checker looks at, when a small team should run one, and what it cannot tell you.
A sitemap checker tells you whether the file that lists your pages for search engines can actually be read, and which entries in it are wrong. For a founder without an SEO hire, the seogeoaeo.ai XML Sitemap Validator is the simplest one to run: paste the sitemap URL, pay 10 credits, get a list of what to fix.
You probably did not write your sitemap by hand. A CMS, a framework plugin or a build script made it, and nobody has looked at it since launch. That is exactly when it drifts: a domain move, a new subfolder or a migration leaves it pointing at the wrong places.
Why a founder should care
A sitemap is how you tell search engines which pages exist and when they changed. Google treats it as a hint, so the damage from a broken one is easy to miss: search engines get a weaker map of your site, so they rely more on finding pages through links.
For a small team, the question is not "is my SEO perfect" but "is anything obviously broken that a five-minute check would catch". A sitemap checker answers that.
What the check covers
| Question | What the checker looks at |
|---|---|
| Can a search engine parse the file? | Whether the XML is well formed |
| Is it a real sitemap? | The sitemaps.org namespace on the root tag |
| Is it too big? | Size against 50 MB uncompressed, count against 50,000 URLs |
| Does it list pages it should not? | URLs on another host, protocol or above the sitemap's folder |
| Are the dates usable? | lastmod values that are missing or in the wrong format |
The seogeoaeo.ai checker runs all five on a live sitemap and returns the entry count plus the specific URLs and dates that fail. It works on a sitemap index as well, though it checks one file per run, so a site with several child sitemaps needs one run for each.
When to run it
Three moments are worth a check:
- After a launch or redesign. New routes, new generator, new chances for the sitemap to break.
- After a domain or protocol change. Moving from
wwwto the bare domain, or from one host to another, is the classic cause of URLs that no longer match the sitemap's host. - When Search Console shows errors. Its Sitemaps report may say "Has errors" or "Couldn't fetch". A checker helps you see which entries are the problem.
Outside those, a check once a quarter is plenty for most small sites.
What it will not tell you
A sitemap checker looks at the file, not your rankings. It cannot confirm Google has read the file; Search Console's Sitemaps report does that, for free, once you verify the site. The seogeoaeo.ai validator also does not hunt for your sitemap through robots.txt, so you need its address. On most sites that is /sitemap.xml or /sitemap_index.xml.
If you want to know whether the pages listed in the sitemap work, seogeoaeo.ai's Orphan Page Finder compares the sitemap against a crawl of your links and flags entries that redirect, fail or are marked noindex. A large site that needs every page crawled is better off with a dedicated desktop crawler.
The short version
Find your sitemap URL, run it through a sitemap checker, fix what it lists, and submit the clean file in Search Console. For most early-stage companies that is the whole job, and it takes less time than reading this.