Free Tool · Technical SEO

XML Sitemap Checker

Check any XML sitemap in seconds: parse errors, URL count vs the 50,000 cap, file size, lastmod coverage, plus a live spot-check that listed URLs return 200. Free, no signup.

Free · No signup · Runs in your browser · Updated

Paste a full sitemap URL, or enter a bare domain and we'll try /sitemap.xml automatically.

A sitemap checker fetches your XML sitemap and parses it the way Googlebot does, so you know whether search engines can actually use it before they silently fail to. Paste a full sitemap URL — or just a bare domain, and this tool tries /sitemap.xml for you — and the sitemap validator returns a verdict in seconds: whether the XML parses, whether it's a URL set or a sitemap index, how many URLs it lists against the 50,000-per-file cap, how large the file is against the 50 MB limit, what share of entries carry <lastmod>, and a live spot-check that fetches a sample of the listed URLs to confirm they really return 200. It's free, requires no signup, and the results render right in your browser.

Broken sitemaps fail silently, which is what makes them dangerous. A sitemap can 404 for months while your CMS keeps linking to it. A stray byte-order mark or an unescaped ampersand in one URL can make the whole file unparseable, so every entry after it is invisible to crawlers. Sitemaps routinely list redirected URLs, deleted pages that now 404, http versions of https pages, or staging URLs that should never be public — and each of those teaches Google to trust the file less, until it stops treating your sitemap as a reliable signal at all. None of this shows up on the page; it only shows up in slower discovery, wasted crawl budget, and new content taking weeks instead of days to index.

Use this tool to check a sitemap whenever you launch, migrate, change CMS plugins, or notice indexing lag in Search Console. It's the manual version of what Black & Gold SEO does continuously — monitoring your sitemap alongside your live pages, catching the drift between what the file claims and what the site actually serves, and shipping the fixes instead of just listing them.

How to use it

  1. 1

    Enter your sitemap URL or just your domain

    Paste the exact sitemap URL if you know it (https://example.com/sitemap.xml, sitemap_index.xml, or a section file like post-sitemap.xml). If you only enter a domain, the tool automatically tries /sitemap.xml — the conventional location. If nothing is found there, check your robots.txt: the Sitemap: line at the bottom points to the real file.

  2. 2

    Read the verdict and the stat tiles

    A green banner means the XML parsed cleanly and nothing blocks search engines from using it; a red banner counts the problems found. The tiles show the type (a urlset lists pages directly, a sitemap index lists other sitemaps), the URL count against the 50,000-per-file limit, the file size against the 50 MB uncompressed limit, and lastmod coverage — the share of entries that declare when they last changed.

  3. 3

    Work through the issues list

    Red callouts are blocking: broken XML, a dead sitemap URL, empty files, or entries search engines can't use. Fix those first — a sitemap that doesn't parse contributes nothing. Amber callouts are hygiene advisories, like missing lastmod values or http:// URLs on an https site: not fatal, but each one weakens the signal the file sends.

  4. 4

    Check the live spot-check table

    The tool fetches a sample of the URLs your sitemap lists and shows their real HTTP status. Every entry should be 200. A 3xx means the sitemap lists a redirecting URL — update it to the final destination. A 4xx or 5xx means you're inviting Google to crawl a dead page, which wastes crawl budget and erodes trust in the entire file.

  5. 5

    Expand the URL list and sanity-check it

    Open the first-20-URLs view and read it like a human: are these the pages you actually want indexed? Watch for staging or dev hostnames, URL parameters, http instead of https, and paths that shouldn't be public. A syntactically valid sitemap full of the wrong URLs passes every validator and still hurts you.

  6. 6

    Fix, resubmit, and verify in Search Console

    After fixing issues, re-run the check to confirm a clean result, then make sure the sitemap is referenced in robots.txt (Sitemap: https://example.com/sitemap.xml) and submitted in Google Search Console's Sitemaps report. Google retired its sitemap ping endpoint in 2023 — robots.txt and Search Console are how engines find the file now.

The limits are exact and worth memorizing: one sitemap file may contain at most 50,000 URLs and 50 MB uncompressed — gzip compression is allowed for transfer, but the decompressed size is what counts. Past either cap, split into multiple files referenced by a sitemap index, which can itself list up to 50,000 child sitemaps. In practice, don't wait for the limit: segmenting sitemaps by section (posts, products, categories) at a few thousand URLs each makes Search Console's page-indexing report dramatically more useful, because you can see exactly which section Google is ignoring instead of staring at one 40,000-URL blob.

Only list URLs that are canonical, indexable, and return 200. Every entry in a sitemap is a statement — 'this page matters, crawl it' — and entries that redirect, 404, carry noindex, or canonicalize elsewhere are contradictions. Google has said it treats lastmod as a signal only when it's consistently accurate: a CMS that stamps every URL with today's date on every deploy trains Google to ignore your lastmod entirely, which forfeits the fastest recrawl trigger you have. Set lastmod when content genuinely changes, and omit <priority> and <changefreq> without guilt — Google ignores both. Also mind scope: a sitemap at /shop/sitemap.xml can only describe URLs under /shop/ unless it's declared in robots.txt, which lifts that restriction.

In 2026, your sitemap serves more than Googlebot. AI crawlers building answer indexes — the ones behind ChatGPT, Perplexity and Google's AI Overviews — use sitemaps to discover and prioritize content, so a stale or broken file now costs you AI-search visibility too, not just organic rankings. And a sitemap is only ever as good as the moment you last checked it: every plugin update, migration, or template change can silently corrupt it. Test your sitemap after each of those events, or put the checking on autopilot.

More free SEO tools

See all free SEO tools or compare Black & Gold SEO vs other platforms.

Questions

Frequently asked

What is a sitemap checker and is this one free?

A sitemap checker (or sitemap validator) is a tool that fetches your XML sitemap, verifies the XML actually parses, counts the URLs, checks the file against the protocol's 50,000-URL / 50 MB limits, and tests whether the listed URLs are live. This one is completely free with no signup — paste a sitemap URL or a bare domain and get a full verdict in seconds.

How do I validate my sitemap if I don't know its URL?

Try the conventional location first: yourdomain.com/sitemap.xml — this tool does that automatically when you enter a bare domain. If it's not there, open yourdomain.com/robots.txt and look for a Sitemap: line, which declares the real location. WordPress sites often use /sitemap_index.xml (Yoast) or /wp-sitemap.xml (core).

What are the XML sitemap size limits?

A single sitemap file may contain at most 50,000 URLs and must be no larger than 50 MB uncompressed — you can serve it gzipped, but the decompressed size is what counts. Bigger sites split URLs across multiple sitemap files and reference them from a sitemap index, which can itself list up to 50,000 child sitemaps. This xml sitemap checker flags files approaching either cap.

What's the difference between a urlset and a sitemap index?

A urlset is a standard sitemap that lists page URLs directly. A sitemap index is a sitemap of sitemaps — it lists other sitemap files instead of pages, which is how large sites stay under the 50,000-URL per-file limit. Both are valid to submit to Google; this sitemap tester detects which type you have and validates it accordingly.

Should every page on my site be in the sitemap?

No — only canonical, indexable pages that return 200. Leave out redirects, 404s, noindexed pages, parameter variants, and paginated duplicates. Every sitemap entry tells Google 'crawl this, it matters,' so entries that contradict themselves (a listed URL that redirects or blocks indexing) erode Google's trust in the file. A smaller, clean sitemap beats a bloated one every time.

Does an XML sitemap improve my Google rankings?

Not directly — a sitemap is a discovery mechanism, not a ranking signal. What it does is get your pages found and recrawled faster, which matters most for new sites, large sites, sites with weak internal linking, and freshly updated content. An accurate lastmod is the practical win: it tells crawlers exactly which pages changed so they recrawl those first. A broken sitemap, on the other hand, can absolutely delay indexing — which is why you should check your sitemap regularly.

Validate one sitemap here. Keep the whole site index-ready automatically.

A sitemap check is a snapshot — the file drifts the moment a plugin updates, a migration ships, or a page is deleted. Black & Gold SEO monitors your sitemap continuously alongside your live pages, catches the 404s, redirects and noindex contradictions it accumulates, finds the indexable pages it's missing, and ships the fixes through one-click processes instead of handing you another audit PDF. Plans start at $49.99/mo for one site.