Skip to content

Free tool · Free, no signup

Sitemap checker and XML sitemap validator

This sitemap checker asks the question that matters, beyond whether the file is valid XML: would a crawler actually get a usable list of your pages out of it? It reads your robots.txt, follows the sitemaps it declares, validates each XML sitemap, and tells you how many URLs it really found. Free, no signup.

We read your robots.txt first, follow whatever Sitemap line it declares, and fall back to /sitemap.xml. Sitemap indexes get followed one level down.

How it works

Free, no signup. Up to seven requests.

  1. Enter your site or a sitemap URL

    A domain is enough. If your sitemap lives somewhere unusual, paste its full URL instead.

  2. We follow the trail a crawler follows

    robots.txt first, then the Sitemap lines it declares, then /sitemap.xml as the fallback. An index is opened one level down, up to five child sitemaps.

  3. See what a crawler would get

    How many URLs it submits, whether robots.txt points at it, the newest lastmod date, and any finding worth fixing, with the first few URLs we read so you can see it is your data.

A real run

Example result

notion.com, checked on 9 October 2026. Its robots.txt declares twelve sitemaps, and the main one is an index of 169 child sitemaps. We opened the first five, which list 667 URLs between them. The count covers those five only, and the result says so.

Result · https://notion.com

667 URLs submitted

https://www.notion.com/sitemap.xml

Sitemap foundDeclared in robots.txtSitemap indexNewest lastmod 2026-10-08T23:17:01.434Z

This is an index declaring 169 child sitemaps. We opened 5 of them, so the URL count above covers those only.

1 finding

  • This is a sitemap index with 169 children. We read the first 5, so the URL count below covers those only.

Declared in your robots.txt

  • https://www.notion.com/sitemap.xml
  • https://sitemaps.notion.com/sitemap-categories.xml
  • https://sitemaps.notion.com/sitemap-collections.xml
  • https://www.notion.com/sitemap-root.xml
  • https://www.notion.com/blog/sitemap.xml
  • https://www.notion.com/customers/sitemap.xml
  • https://www.notion.com/help/sitemap.xml
  • https://www.notion.com/md/sitemap.xml
  • https://www.notion.com/releases/sitemap.xml
  • https://www.notion.com/use-case/sitemap.xml
  • https://www.notion.com/feature/sitemap.xml
  • https://www.notion.com/front-static/sitemap.xml

First few URLs we read

  • https://www.notion.com/es-es
  • https://www.notion.com/es-es/about
  • https://www.notion.com/es-es/affiliates
  • https://www.notion.com/es-es/product/ai
  • https://www.notion.com/es-es/product/ai-meeting-notes

Four ways a sitemap quietly does nothing

A sitemap either works or it does not, and the failures are quiet. Nothing warns you. These are the four this sitemap validator looks for:

Nothing points at it. The file is fine and robots.txt never mentions it. Crawlers that do not guess /sitemap.xml never learn it exists.

It returns HTML with a 200 status. A misconfigured server answers the sitemap path with a soft 404 page. The status code says success, so retries do not happen, and the crawler reads an empty sitemap forever.

Cross-host URLs. The sitemap lives on one host and lists URLs on another. Those entries are discarded, silently, in full.

An index pointing at dead children. The index parses, declares twelve children, and four of them 404. You get two thirds of the pages you think you are submitting.

Be honest about what this is worth

A sitemap is plumbing. It gets your pages considered for indexing; it does not make them rank, and it certainly does not make an AI engine cite you. Sites with immaculate sitemaps go uncited every day, because citation is decided by what other people wrote about your category, not by how tidily you enumerated your own URLs.

It is on this list because it is a ten-minute check that occasionally turns up something genuinely broken, not because it is the lever. If your sitemap is clean and you are still invisible in AI answers, the problem was never here, and the visibility checker is where you find out where it actually is.

Every day, not once

The GEO audit

The free check runs once, on one URL. The GEO audit keeps the results for your site, turns failures into To-dos, and rechecks a page after you fix it.

Questions

What does this validator check?

Whether the file is reachable at a path a crawler would try, whether it parses as XML, whether robots.txt points at it, how many URLs it really submits, whether any of those URLs sit on a different host, and whether lastmod dates exist. It follows a sitemap index one level down and reads the first few children.

Why does robots.txt matter for a sitemap?

Because it is how most crawlers find the file. /sitemap.xml is a convention, not a rule, and a crawler that does not guess the path has no other way of knowing the file exists. A perfectly good sitemap nobody points at is an easy thing to miss, and the fix is one line.

Do sitemaps help with AI visibility?

Indirectly and modestly. Answer engines mostly retrieve through search indexes rather than crawling your sitemap directly, so a sitemap is not what gets you cited. What it does is make sure your pages are in the index that gets searched in the first place. Necessary plumbing, not a growth lever, and anyone selling it as the latter is selling something.

My sitemap has 200 child files and you only read 5.

Yes, on purpose. This is a free tool fetching a stranger’s server, so it opens at most five children of an index. That is enough to confirm the index resolves to real URL sets. The count it reports covers only what it read, and it says so in the result rather than implying it counted everything.

It says my URLs are on a different host.

A sitemap may only list URLs on the same host it is served from. Crawlers discard cross-host entries outright, so if your sitemap at example.com lists www.example.com URLs, or vice versa, those pages are not being submitted at all. This one bites sites that changed canonical hosts and left the generator configured for the old one.

Do you keep the sites people check?

Each run is logged with the URL, a summary of what we found and the network it came from, so we can spot abuse and see which tools get used. It is not tied to an account.

What about lastmod — does anyone actually use it?

Search crawlers use it to prioritise what to re-read, and they discount it when it is obviously wrong. A CMS that stamps today’s date on every page in every build is worse than no lastmod at all, because it trains the crawler to ignore the field. If yours updates honestly, it helps your genuinely-changed pages get recrawled sooner.

Track it every day instead of once

CueScout runs these checks on a schedule and turns the gaps into To-dos.