Find your XML sitemap the way a crawler does, validate its structure, and fetch the URLs inside it to catch the dead and blocked ones. Free, no account.
Most sitemap tools stop at the XML: well-formed, right namespace, done. That catches almost nothing that matters. The damage is usually one level down — a sitemap generated months ago that still lists deleted pages, URLs on the version of the domain that redirects, or pages the site's own robots.txt forbids.
Search engines treat a sitemap as a claim about which URLs are worth crawling. When a large share of that list 404s or redirects, the claim stops being trusted, and the genuinely new pages in the same file get discovered more slowly.
So this checker walks it the way a crawler would: it finds the sitemap where a crawler finds it, follows a sitemap index down to its children, and then actually requests a sample of the URLs inside to report what they really return. The walk has limits — a time budget, a ceiling on how many child sitemaps and URLs it reads — and the report says outright when it hit one.
example.com is enough. We resolve www against non-www first, then look for the sitemap exactly where a crawler would: the Sitemap: lines in robots.txt, then the usual locations.
If you already know where it lives — including a sitemap index or a gzipped .xml.gz — paste that instead and we'll start from it.
You get the file's type and size, how deeply the index nests, how many URLs it declares in total, and a per-child breakdown when it's an index rather than a flat URL set.
We take up to ten of the listed URLs at random, request each one live, and report its real status code plus whether your own robots.txt blocks it — the contradiction search engines flag most often.
The limits, the fields that actually matter, and the contradictions search engines flag.
50,000 URLs and 50 MB uncompressed, per file. Past either limit you split into several sitemaps and list them in a sitemap index, which can itself hold 50,000 sitemaps. Gzipping is allowed and counts against the uncompressed limit, not the compressed one.
No — it's a direct contradiction. A sitemap says “please crawl this”, robots.txt says “don't”, and search engines report it as an error in Search Console. Either the page belongs in the sitemap and the Disallow is wrong, or the Disallow is right and the URL shouldn't be listed. This checker flags every sampled URL where the two disagree.
No. A sitemap is a discovery aid, not an instruction — it helps search engines find URLs, especially deep ones with few internal links. Whether a page is then indexed depends on its content, its canonical, its meta robots tag and whether the crawler judges it worth keeping.
lastmod does, if it's honest — Google has said it uses it when it's consistently accurate, and ignores it when a site stamps every URL with today's date. changefreq and priority are effectively ignored by Google. They do no harm, but nothing you set there will change how often you're crawled.
Whichever one your site actually canonicalises to. Listing the version that redirects means every URL in the file costs an extra hop before the real page is reached. This checker states plainly which version your domain serves on and whether the other redirects there properly.
Three per tool per day, with no account and nothing to sign up for. The counter resets automatically and the page tells you how long that takes. Inside TaskGlaze the same checks run as part of the full site audit, with no daily cap.
TaskGlaze crawls your whole site on a schedule — sitemaps, robots.txt, canonicals, redirects, broken links and on-page signals, with no daily cap.