Free Tool · No Sign-up Required

XML Sitemap
Validator

Instantly check any website's sitemap for errors, structural issues, duplicate URLs, and Google compliance problems — before they quietly damage your SEO.

XML structure check Duplicate URL detection Google limit checks
Validation Summary
Valid XML structure
4,218 URLs — within limit
All URLs use HTTPS
312 URLs missing lastmod
14 duplicate URLs found
Accepts a domain (example.com) or a direct sitemap URL. We auto-discover /sitemap.xml, /sitemap_index.xml, and any sitemap declared in your robots.txt.  ·  10 free validations/day

Fetching and validating your sitemap…

Parsing XML, counting URLs, and running compliance checks
—
Score
Issues Found 0
What's Good
URL Sample
# URL Last Modified Priority Change Freq
what it does

What Is an XML Sitemap Validator?

An XML sitemap validator reads your sitemap file and checks it against Google's published requirements — then tells you exactly what's wrong and how to fix it. Think of it as a spell checker, but for your sitemap.

A sitemap with broken XML, duplicate URLs, or missing <lastmod> tags doesn't cause a dramatic failure — it quietly underperforms. Pages get crawled less frequently, new content takes longer to index, and Google's crawl budget gets wasted on the wrong pages.

This tool catches all of that before it becomes a problem. Enter your domain or a direct sitemap URL and you'll have a full report in seconds — no account, no setup, no fluff.

XML Syntax Validation
Catches malformed XML, encoding errors, and invalid tag structures that break crawling.
Sitemap Index Support
Handles both standard urlset sitemaps and sitemap index files that reference multiple child sitemaps.
Duplicate URL Detection
Finds identical URLs listed more than once — a common issue with CMS and e-commerce platforms.
Google Limit Checks
Verifies you're under the 50,000 URL and 50 MB limits Google enforces per sitemap file.
step by step

How to Validate Your XML Sitemap

From finding your sitemap URL to fixing every issue — here's the full process in six steps.

Step 1
Find your sitemap URL
Most sites have a sitemap at yourdomain.com/sitemap.xml. WordPress sites with Yoast SEO use /sitemap_index.xml. Shopify uses /sitemap.xml and references product, collection, and blog sitemaps inside it. If you're unsure, check your robots.txt — a properly configured site will have a Sitemap: line pointing to it.
Step 2
Enter the domain or URL above
You can paste your raw sitemap URL (https://example.com/sitemap.xml) or just the domain (example.com) and this tool will discover your sitemap automatically. It checks robots.txt for Sitemap directives, then tries /sitemap.xml and /sitemap_index.xml in order.
Step 3
Review your score and issues
The results show a health score from 0 to 100 alongside a categorised list of issues — critical (fix immediately), warnings (fix soon), and informational (nice to have). Each issue includes an explanation and an exact fix so you know what to do.
Step 4
Check the URL sample
Scroll down to the URL sample table to spot patterns — pages missing lastmod dates, unexpected priority values, or URLs that look like parameter duplicates. This is often where you'll spot the source of a systemic issue.
Step 5
Fix the issues in your CMS
Most sitemap issues come from plugin or CMS settings rather than manual file edits. In WordPress, check your Yoast or Rank Math sitemap settings. In Shopify, use a sitemap app. For custom builds, review your sitemap generator's configuration or template.
Step 6
Re-submit to Google Search Console
After fixing issues, re-validate here, then go to Google Search Console → Sitemaps and submit your sitemap URL again. This triggers Google to re-crawl it. You'll typically see the updated URL count reflected within 24–48 hours.
types

Types of XML Sitemaps

Not all sitemaps are the same. Knowing which type your site uses helps you understand what you're validating.

Standard XML Sitemap (urlset)

The most common type. Contains a list of <url> entries, each with a <loc>, and optionally <lastmod>, <changefreq>, and <priority>. Limited to 50,000 URLs and 50 MB per file.

<urlset xmlns="...">\n  <url><loc>https://example.com/page</loc></url>\n</urlset>
Sitemap Index

An index file that references multiple child sitemaps. Use this when your site has more than 50,000 URLs. Each <sitemap> entry points to a separate sitemap file. Most large e-commerce and news sites use this structure.

<sitemapindex>\n  <sitemap><loc>https://example.com/posts-sitemap.xml</loc></sitemap>\n</sitemapindex>
Image Sitemap

An extended urlset that includes image-specific tags (<image:image>, <image:loc>, <image:caption>). Helps Google discover and index images that might be loaded via JavaScript or that don't appear in regular page links.

<url>\n  <loc>https://example.com/page</loc>\n  <image:image><image:loc>https://example.com/img.jpg</image:loc></image:image>\n</url>
News Sitemap

Required for Google News inclusion. Uses the <news:news> namespace and must only include articles published in the last two days. A regular XML sitemap won't get your articles into Google News — you need a dedicated news sitemap.

<url>\n  <loc>https://example.com/article</loc>\n  <news:news><news:publication_date>2024-06-15</news:publication_date></news:news>\n</url>
what to watch for

8 Common XML Sitemap Errors and How to Fix Them

These are the issues we see most often — and the ones that quietly hurt crawl efficiency the most.

1. Malformed XML (unescaped & characters)
A URL like https://example.com/page?a=1&b=2 will break your sitemap's XML if the ampersand isn't escaped. Every & in a URL must be written as &amp; in your sitemap file. This is the single most common XML parse error we see.
2. Sitemap not accessible (404 or redirect)
If your sitemap returns a 404 or redirects to a login page, Google can't read it. Always verify the URL is publicly accessible with no authentication required. Test in an incognito window to confirm.
3. Exceeding the 50,000 URL limit
Google stops reading a sitemap file after 50,000 URLs. Any URLs beyond that point are simply ignored. Split large sitemaps into multiple files using a sitemap index and verify the count with this validator.
4. Including non-indexable pages
If a page has noindex set or is blocked by robots.txt, there's no point putting it in your sitemap. Including these pages confuses Google and dilutes the signal about which pages actually matter.
5. Setting all lastmod dates to "today"
Some CMS plugins set every URL's <lastmod> to the current date on every sitemap regeneration. Google has publicly stated they detect and ignore sitemap files where all dates are identical and constantly changing. Only set lastmod to the actual last-modified date of each page.
6. Duplicate URLs from URL parameters
E-commerce and CMS platforms often create the same page at multiple URLs via query parameters (?color=red, ?sort=price). These duplicates waste crawl budget. Use canonical tags and remove parameter URLs from your sitemap.
7. Missing lastmod on all URLs
Without <lastmod>, Google can't tell when a page was last updated and has to decide on its own crawl frequency. Adding accurate last-modified dates helps Google prioritise crawling your freshest content.
8. Not declaring your sitemap in robots.txt
Submitting to Search Console is great, but adding Sitemap: https://example.com/sitemap.xml to your robots.txt means every crawler — not just Google — discovers it automatically, without you having to manually submit to each search engine.
after validation

How to Submit Your Sitemap to Google Search Console

Once your sitemap is validated and clean, here's how to make sure Google actually reads it.

Go to Google Search Console
If you haven't set it up yet, visit search.google.com/search-console and verify ownership of your domain. You'll need access to either your DNS settings, Google Analytics account, or the ability to upload a verification file to your server.
Click Sitemaps in the left menu
Once you're inside Search Console, select your property from the dropdown at the top. Then look for Sitemaps under the Indexing section in the left-hand navigation panel.
Enter your sitemap URL and submit
In the "Add a new sitemap" box, paste just the path portion of your sitemap URL (e.g. sitemap.xml or sitemap_index.xml). Click Submit. Google will fetch the file and display how many URLs it found.
Monitor for errors
Check back within 24–48 hours. If Search Console reports errors, they'll appear in the Sitemaps report. Common issues include "Couldn't fetch sitemap" (access problem) or "Sitemap could not be read" (XML error). Fix the issue, re-validate here, and resubmit.
Also add the Sitemap line to robots.txt
For belt-and-braces coverage, add Sitemap: https://yourdomain.com/sitemap.xml to your robots.txt file. This means Bing, DuckDuckGo, and other search engines can discover your sitemap without a manual submission. Use our Robots.txt Generator to do this quickly.
FAQ

Frequently Asked Questions About XML Sitemaps

1 Do I really need an XML sitemap?
For small sites with good internal linking, Google can discover most pages through crawling alone. But for larger sites, new sites with few inbound links, sites with lots of dynamic or JavaScript-rendered content, or any site that updates frequently, a sitemap is practically essential. It's also low-effort to add — there's no real reason not to have one.
2 How often should I update my sitemap?
Your sitemap should update automatically whenever you publish, update, or delete content. Most CMS plugins (Yoast SEO, Rank Math, Shopify, etc.) handle this automatically. If yours doesn't, set up a cron job or regenerate it at least weekly. A sitemap that's months out of date provides very little crawl guidance.
3 What's the difference between a sitemap and a sitemap index?
A sitemap (urlset) contains the actual list of URLs. A sitemap index contains references to multiple sitemap files — it's a table of contents for your sitemaps. Use a sitemap index when you have more than 50,000 URLs or when you want to separate your content types (posts-sitemap.xml, products-sitemap.xml, etc.) for easier management.
4 Should I include every page on my site in the sitemap?
No. Only include pages you want Google to index. Leave out pages with noindex meta tags, login and account pages, search results pages, parameter-based duplicate URLs, and staging or development pages. Adding non-indexable pages to your sitemap doesn't get them indexed — it just wastes Google's time and dilutes your sitemap's usefulness.
5 Why does Google Search Console show fewer URLs than my sitemap?
This is normal and doesn't necessarily indicate a problem. Google indexes pages based on quality and authority, not just because they're in your sitemap. Reasons for lower counts include: thin or duplicate content being excluded, pages with crawl errors, new pages that haven't been crawled yet, or pages blocked by robots.txt or noindex tags that you accidentally included in your sitemap.
6 Does sitemap priority actually affect rankings?
Not directly. Google's John Mueller has confirmed they largely ignore the <priority> tag. However, <lastmod> is used — if it's accurate, it genuinely helps Google prioritise crawling your updated content. Focus on keeping lastmod dates accurate rather than tweaking priority values.

While you're here — check your robots.txt too

A clean sitemap and a properly configured robots.txt work together. Make sure your robots.txt isn't accidentally blocking the pages in your sitemap.