Skip to content
Free tools Sitemap Validator

Sitemap Validator — check your XML sitemap for errors

Find your sitemaps through robots.txt, validate them against the protocol and Google's rules, and check the URLs they list for 404s, redirects, noindex and canonicals that point elsewhere.

100% free No signup Sitemap indexes & gzip 50 URLs checked live CSV of every URL

How it works

  1. Enter a site or a sitemap

    We read robots.txt for its Sitemap: lines (or try the usual addresses) and follow a sitemap index to its sitemaps, gzipped ones included.

  2. Every file, every URL validated

    XML, namespace, size limits, absolute same-host URLs, duplicates, lastmod dates, the image, video, news and hreflang extensions — and every URL against robots.txt.

  3. Listed URLs checked live

    Up to 50 URLs spread across your sitemaps are requested live. 404s, redirects, noindex and canonicals pointing elsewhere are flagged, each with the fix.

What an XML sitemap is for

A sitemap is a list of the pages on a site that you want search engines to find and index, with the date each one last changed. Crawlers still discover most pages through links, but a sitemap is how new, deep and rarely linked pages get found quickly — product pages, articles, landing pages — and it's the list Google Search Console checks your index coverage against. That makes it a promise: every URL in it should be a live, indexable, canonical page. A sitemap that lists redirects, 404s or noindex pages breaks that promise, and search engines learn to trust it less.

What this sitemap checker validates

Finding the sitemap

Enter a domain and the validator reads robots.txt for its Sitemap: lines, the way Bing, Apple and AI crawlers find sitemaps. If there are none, it tries the addresses CMSs and plugins use — /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml — and tells you to declare what it finds. Enter a sitemap's own address to check that file directly. A sitemap that redirects, answers with an error, or returns an HTML page instead of XML is flagged first, because nothing else matters if a crawler can't read the file.

The XML itself

Each file is parsed the way a search engine parses it: well-formed XML (one unescaped & in a URL makes the whole file unreadable — the error shows the line and column), the http://www.sitemaps.org/schemas/sitemap/0.9 namespace, UTF-8 encoding, and the limits of 50,000 URLs and 50 MB uncompressed per file. Sitemap indexes are followed to their sitemaps — up to ten, spread across the index — and nested indexes or child sitemaps on another host are pointed out. Gzipped sitemaps are decompressed in your browser.

Every URL in it

All listed URLs are checked without a single request: they must be absolute, on the sitemap's own host (www and non-www are different hosts), https on an https site, properly encoded and under 2,048 characters, and listed only once. <lastmod> dates must use the W3C format and not lie in the future; when nearly every URL has the same timestamp, the date is the generation time, not the page's. Image, video, news and hreflang entries are recognised and checked for their required fields — a news sitemap's two-day window and 1,000-article limit, an hreflang group that forgets to list itself. Finally every URL is tested against your robots.txt for Googlebot, catching the "Submitted URL blocked by robots.txt" error before Search Console does.

A live sample of the pages

Up to 50 URLs, spread across all the sitemaps read, are requested live — as a browser or as Googlebot — following redirects hop by hop. The validator reports pages that are gone (404 or 410), server errors, URLs that redirect (list the destination instead), pages marked noindex in an X-Robots-Tag header or a robots meta tag, and pages whose canonical tag names a different URL. Pages behind a firewall that turns away our checker are reported as unverifiable, not broken.

How the score works

The grade starts at 100. Critical problems — no sitemap, unreadable XML, URLs blocked by robots.txt, listed pages that are gone or marked noindex — cost the most; warnings such as redirects, duplicates or invalid dates cost less; suggestions cost nothing. The share of live-checked URLs with a problem lowers the score further. Every finding comes with what it means and how to fix it, and checks that passed are listed too.

Export every URL

Download CSV exports every URL the sitemaps list — with its sitemap file, lastmod, changefreq, priority, image and hreflang counts, the robots.txt verdict and the live-check result where there is one. It's the quickest way to get a full page inventory into a spreadsheet, to compare it with your analytics, or to hand a list of problem URLs to a developer.

Watch a competitor's sitemap for new pages

A sitemap is a public list of everything a site wants found, so it's also the earliest signal of what a competitor is launching: new product pages, new landing pages, new articles, often before they're promoted. Run any site through the validator to see its sitemaps, then let Monity watch one and alert you when new URLs appear — see how new-page alerts work.

Related tools

The Robots.txt Tester shows which rule blocks a URL and which search and AI crawlers can reach it, the Redirect Checker traces a redirect chain hop by hop, the Broken Link Checker finds dead links inside your pages, and the SEO & AI Visibility Audit checks titles, canonicals and structured data page by page.

Get alerted when pages drop out of the index

Sitemap problems rarely arrive alone: a deploy adds noindex to a template, a migration leaves old URLs redirecting, a plugin update starts blocking a folder in robots.txt. Monity re-checks the pages that matter on a schedule and alerts you in email, Slack or Teams when one turns noindex, starts returning a 404, or its canonical or robots rules change. The free plan includes three monitors, forever.

FAQ

Common questions

What does the sitemap validator check?

Three layers. Discovery: whether robots.txt lists your sitemap, and whether each sitemap answers 200 with XML. The files: well-formed XML (an unescaped & breaks a whole file), the sitemaps.org namespace, the 50,000-URL and 50 MB limits, sitemap indexes, and every URL in them — absolute, on the sitemap's own host, properly encoded, listed once, with valid lastmod dates and valid image, video, news and hreflang entries, and not blocked by robots.txt. The pages: up to 50 listed URLs are requested live and checked for 404s, server errors, redirects, noindex and a canonical tag that names a different URL.

Where do I find my sitemap?

Enter just your domain: the validator reads /robots.txt for its Sitemap: lines and, if there are none, tries /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml. WordPress serves one at /wp-sitemap.xml (SEO plugins like Yoast and Rank Math replace it with /sitemap_index.xml); Shopify, Wix and Squarespace use /sitemap.xml. Wherever it is, list it in robots.txt so every search engine — not only the ones you submit it to — can find it.

Why shouldn't a sitemap list redirects, noindex or non-canonical pages?

A sitemap tells search engines "these are the pages I want indexed". A URL that redirects, carries noindex, names another page as canonical or is blocked by robots.txt contradicts that, and Google Search Console reports each one ("Page with redirect", "Submitted URL marked 'noindex'", "Alternate page with proper canonical tag", "Submitted URL blocked by robots.txt"). A sitemap full of them also teaches crawlers to trust it less. List only final, indexable, canonical URLs that answer 200.

What are the sitemap size limits?

One sitemap file may list at most 50,000 URLs and be at most 50 MB uncompressed. Larger sites split their URLs into several sitemaps and list those in a sitemap index (which can itself list up to 50,000 sitemaps). Files can be gzipped to save bandwidth — the 50 MB limit applies to the uncompressed size. The validator follows an index to its sitemaps (up to ten, spread across it) and decompresses gzipped files in your browser.

Does Google use lastmod, changefreq and priority?

Google uses <lastmod> — when it's consistently accurate — to decide what to recrawl, and ignores <changefreq> and <priority>. The validator checks that lastmod uses the W3C date format (2026-10-14 or 2026-10-14T09:30:00+00:00), isn't in the future, and isn't the same timestamp on every URL — the sign of a generator stamping the build time, which makes the dates worthless.

Is anything stored, and is there a limit?

Nothing is stored: files are fetched through Monity's relay and analysed in your browser. The live check shares a fair-use limit per network with Monity's other free tools; if you reach it, the results so far stay on screen and you can resume a few minutes later. Very large files are checked from their first 2 MB.

Can I get alerted when pages drop out of the index — or a competitor's sitemap grows?

Yes. Monity re-checks your key pages on a schedule and alerts you in Slack, Teams or email when one turns noindex, starts returning 404, or its canonical or robots rules change. It can also watch any sitemap — yours or a competitor's — and tell you when new URLs appear: new products, landing pages, articles. The free plan includes 3 monitors.

Powered by Monity

Sitemaps break quietly.
Monity notices the day they do.

Monity re-checks your key pages on a schedule and alerts you when one turns noindex, redirects or returns a 404 — and can watch any sitemap for new URLs.

  • Free 7-day trial
  • No credit card
  • 3 monitors free, forever
Kamil, Alex and Martyna Median reply under 6 hours

Have a question?

Pricing, security, or scoping - pick a route and you will land in a real person's inbox.