Auditing a single page instead? Try our Meta Tag Checker →
Sitemap Validator
Enter a domain or a sitemap URL. We locate the sitemap, read every URL it declares, and check each one for a live status code — broken links, redirects and timeouts included.
What is a Sitemap Validator?
A sitemap validator reads the file that tells search engines which pages exist on your site — and then holds it to its word. Your sitemap.xml is a promise: every URL listed in it is supposed to be a live, indexable page. In practice sitemaps rot. Pages get deleted, URLs change, plugins regenerate the file with mistakes, and nobody notices for months because the sitemap itself never complains. Search engines do notice: they trust sitemaps less when they keep finding dead entries, and crawl budget gets wasted on redirects and 404s.
This sitemap checker closes that loop. Give it a domain and it finds your sitemap automatically; give it a sitemap URL and it validates that exact file. It reads up to 500 URLs from the file — following sitemap indexes to their child files — and runs a live request against every single one, the way a crawler would.
How the validation works
Locating. If you enter a domain, the validator first reads your robots.txt and follows any Sitemap: declaration — the same discovery path Google uses. If robots.txt declares nothing, it tries the common locations (/sitemap.xml, /sitemap_index.xml,/sitemap-index.xml). If you paste a full sitemap URL, that file is used directly.
Parsing. Both sitemap formats are supported: a plainurlset (one file, many URLs) and a sitemap index that points at child sitemaps — the validator follows up to five child files and merges their URLs.
Checking. Every URL gets a real request, and the table reports what came back: the status code, whether it counts as healthy, and a note explaining anything unusual. Checks run in batches of 40 in parallel, so even a full 500-URL sitemap finishes in seconds. If your sitemap declares more than 500 URLs, the first 500 are shown — enough to catch systematic problems.
What the status codes mean
- 200–299 — healthy. The page answers directly. This is what every row should say.
- 301 / 302 / 308 — redirect. The URL works but forwards somewhere else. Sitemaps should list the final URL — each redirect is a wasted crawl and a diluted signal. The note shows where it goes, so you can replace the entry.
- 404 / 410 — gone. The page no longer exists. Remove these URLs from the sitemap; a sitemap full of 404s trains search engines to trust it less.
- Other 4xx / 5xx — server-side trouble. 403 may mean blocking crawlers by mistake; 5xx means your server is failing under the request. Both need a fix on your side.
- Timeout / connection error. The page did not answer within 8 seconds or the host did not resolve. Slow pages get deprioritized by crawlers too.
Why search engines care about a clean sitemap
Search engines treat your sitemap as a statement of trust — and three things break when the file drifts from reality.
Crawl budget gets wasted. Google allocates each site a crawl budget based on how useful previous crawls proved to be. When the crawler keeps hitting 404s that your sitemap promised were live pages, it learns that following the file is a poor investment — and quietly reduces crawl frequency and depth. New pages then get discovered slower, precisely when your site is growing and needs discovery most.
Ranking signals get diluted. A URL that redirects passes only part of its equity to its destination. A sitemap full of http://, wwwor old-format addresses that all forward somewhere else tells search engines to spread signals across extra hops instead of consolidating them on the final pages. Listing final URLs directly is a free consolidation win.
Index coverage quietly drops. Listing a page in the sitemap is the clearest signal that it matters to you. Dead and redirecting entries undermine that signal for the entire file: coverage reports get noisier, real problems drown in the error list, and genuinely new pages take longer to surface.
The fix is mechanical: validate, remove what is dead, replace what redirects, revalidate. That loop is exactly what this tool automates.
How to use this tool
- Enter your domain or sitemap URL.
example.comis enough — discovery is automatic. Pasting the sitemap URL skips straight to that file. - Press Validate. The sitemap is located, parsed and every URL is requested live. Progress is shown as batches complete.
- Fix the red rows. Remove dead URLs, replace redirects with their final destination, then re-validate — a clean table is a sitemap search engines can trust.
Frequently asked questions
What is a sitemap checker?
A sitemap checker (also called a sitemap validator) fetches your sitemap, reads every URL it declares, and requests each one to confirm it actually works. It surfaces the two problems search engines punish silently: URLs listed in the sitemap that return 404 or 5xx errors, and URLs that redirect because the sitemap points at an outdated address.
How do I validate a sitemap?
Paste your domain — or the full sitemap URL — into the validator above. The tool locates the sitemap through your robots.txt declaration or the common sitemap paths, parses up to 500 URLs from it, and checks every one for a live HTTP status. The whole run takes seconds and needs no signup.
What errors should I look for in my sitemap?
Four kinds: 404s and other 4xx errors (the page no longer exists — remove the URL), 5xx errors (your server fails intermittently), redirects (your sitemap points at a URL that forwards elsewhere — list the final URL instead), and timeouts (pages too slow for crawlers to bother with). A clean sitemap contains only URLs that return 200 directly.
What's the difference between a sitemap checker and a sitemap validator?
Nothing important — they are two names for the same job, and this tool does both. A sitemap checker looks at the file itself: is it reachable, is it valid XML, does it list URLs. A sitemap validator goes one step further and verifies that every listed URL actually works, catching the errors the file alone never reveals.
How often should I check my sitemap?
Validate after every change that touches URLs — new sections, redesigns, migrations, plugin or CMS updates. Those are the moments sitemaps silently drift from reality. For a stable site, a monthly check is plenty; for an active blog or store, a quick validation right after each big publish keeps the file trustworthy.
Check the pages your sitemap points to
A live URL is only half the job — make sure each page's meta tags and share preview are healthy too.