Free tool · no signup, one sitemap in a few seconds

Sitemap Checker

Paste your sitemap address, or just your domain and we'll find it. We fetch it the way a crawler does and check it against Google's sitemap rules. If Google can't read it, you get the reason, the Search Console message it causes and the fix.

ContextBolt · sitemap checker free, no signup
Your sitemap, your robots.txt and a few listed pages, fetched as ContextBolt, never disguised as Googlebot. Results are kept for an hour.
Trusted by 300+ users across the globe

What the sitemap checker checks

  1. The fetch The exact address, fetched as a crawler would, with no JavaScript. Every redirect is shown, and the address to submit is the one that answers with the sitemap itself.
  2. robots.txt Whether a rule blocks the sitemap for Googlebot, and which Sitemap lines the file lists. Type a domain and those lines are where the search starts, then /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml.
  3. The file gzip unpacked, UTF-8, the root element and its namespace, and every tag and entity. A broken one comes back with its line number.
  4. Google's limits 50,000 URLs and 50 MB per sitemap. A sitemap index has up to 5 of its child sitemaps opened and checked.
  5. Every URL it reads Absolute, valid, on the same host and protocol as the sitemap, and not blocked by robots.txt. Each lastmod is checked for format and for dates in the future, and priority and changefreq are counted, though Google ignores both.
  6. A sample of pages Up to 8 listed pages, spread through the file, fetched for a 404, a redirect or a noindex: the Page indexing statuses a sitemap should never point at.

The checker has limits. We fetch as ContextBolt from a data center, so a 403 to us is not proof Google gets a 403, and the result says so instead of guessing. We read up to 10 MB of a sitemap, open up to 5 child sitemaps and fetch up to 8 listed pages, so a big site gets a sample, not a full crawl.

Search Console sitemap errors it checks

Each problem is named the way Search Console names it, so you can match the result to your report. The full list, with the fix for each, is in our guide to the Sitemaps report.

  • Couldn't fetch Sitemaps Google could not download the file. The details page says "Sitemap could not be read". Checks: The status code, the redirects, robots.txt and bot checks
  • HTTP error / General HTTP error Sitemaps The server answered with an error, such as a 404. Checks: The exact status our request got
  • Parsing error Sitemaps The XML is broken, often by an unescaped & in a URL. Checks: Every tag and entity, with the line
  • Unsupported format / Incorrect namespace Sitemaps Not a sitemap Google reads, a wrong header or namespace, or a web page. Checks: The root element and its namespace
  • Invalid URL / URLs not followed Sitemaps A URL that does not parse, has spaces, or is relative. Checks: Every URL it reads
  • URL not allowed / Path mismatch Sitemaps URLs on another host, another protocol, or the other side of www. Checks: Every URL against the sitemap's address
  • Invalid date Sitemaps A lastmod that is not a W3C date, or a time with no time zone. Checks: Every lastmod
  • Too many URLs / Sitemap file size error Sitemaps Over 50,000 URLs or 50 MB uncompressed. Checks: The count, and the size up to the 10 MB we read
  • Compression error Sitemaps A .gz file that will not unpack. Checks: gzip files, unpacked
  • Empty sitemap Sitemaps The file lists no URLs. Checks: The count
  • Nested sitemap indexes Sitemaps A sitemap index lists another index. Checks: Up to 5 child sitemaps
  • Sitemap contains urls which are blocked by robots.txt Sitemaps The sitemap lists pages Google is told not to crawl. Checks: Every same-host URL against robots.txt
  • Not found (404) / Page with redirect / Excluded by 'noindex' tag Page indexing Listed pages that are gone, moved or kept out of the index. Checks: A sample of up to 8 listed pages

What happens after Google reads it

A sitemap Google can read is a list of suggestions. Google still decides what to crawl and index.

Google's own help calls submitting a sitemap "merely a hint", and says there is no guarantee a page discovered in a sitemap will be crawled or indexed. A clean result here means the list arrives intact.

What happens to the pages on it shows in Search Console's Page indexing report. A page Google knows and has not fetched is Discovered, currently not indexed. A page it fetched and passed on is Crawled, currently not indexed.

Frequently asked questions

Something else on your mind? Get in touch.

What does a sitemap checker do?

It fetches your sitemap the way a search engine would and checks it against Google's sitemap rules: the server's answer, robots.txt, the XML, the URLs inside and their dates. This one also names the message Search Console would show for each problem, in Search Console's own words, so you can match it to your report.

Does my site need a sitemap?

Not always. Google's help says a site of about 500 pages or fewer, where every page can be reached by links from the homepage, probably does not need one, and that hosts such as Squarespace or Wix probably manage it for you. A bigger site, a new one, or one with pages few links reach is where a sitemap earns its keep.

How is this different from the Sitemaps report in Search Console?

Search Console shows what happened the last time Google fetched a sitemap you submitted in your own property. This checks any sitemap now: before you submit it, right after a fix, or on a site you do not own. Search Console has the final word on what Googlebot got, because we fetch from a data center and a firewall can treat us differently. Sitemap could not be read covers every message the report shows.

Why does it tell me to submit a different address?

The address you typed redirects. Google's help says the Sitemaps report holds the exact URL you submitted and that redirects are not followed, so submit the address that answers with the sitemap itself. The result shows the whole redirect chain and the address to use.

Does Google use lastmod, priority and changefreq?

Google says it ignores priority and changefreq. It uses lastmod when the dates are consistently and verifiably accurate. The checker counts all three and flags lastmod dates that are not valid W3C dates or sit in the future. Sitemap lastmod covers when to change the date.

How do I find a website's sitemap?

Type the domain above. The checker reads the Sitemap lines in the site's robots.txt, then tries /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml, and shows everywhere it looked. To do it by hand, see how to find the sitemap of any website.

Does it check every page in my sitemap?

It checks the format, host and robots.txt rule of every URL it reads, and fetches a spread sample of up to 8 listed pages for 404s, redirects and noindex. For a sitemap index it opens up to 5 child sitemaps. ContextBolt SEO runs a full site audit from Claude, Cursor or Codex that starts from your sitemap.

Try ContextBolt SEO free

ContextBolt SEO connects your Search Console to Claude, Cursor or Codex. Its site audit finds your sitemap the same way, checks the most important pages first and flags listed pages that error or redirect, and your AI can fix what it finds in the same chat.

Start your free trial See what ContextBolt SEO does