Sitemap Analyzer
Analyze your XML sitemap for errors and optimization opportunities
In 30 seconds
- A broken sitemap can be partly or completely ignored.
- Every URL in it should be HTTPS, canonical, and return a 200.
- Only update
lastmodwhen the page really changed.
Is your sitemap actually readable?
Enter the full URL of an XML sitemap and the analyzer downloads it, parses it and checks it, then groups what it finds into issues, warnings and information, with stats and a sample of the URLs. It looks for:
- A missing XML declaration at the top.
- A missing or wrong namespace (
http://www.sitemaps.org/schemas/sitemap/0.9). - URL entries without a
<loc>, which search engines can’t use. - HTTP URLs in a sitemap that should list HTTPS pages.
- Duplicate URLs.
lastmoddates that can’t be read as a date.priorityvalues outside 0.0 to 1.0.- More than 50,000 URLs, the limit for one file.
It also recognizes sitemap index files and counts the sitemaps they point to. Don’t know the address? Start with the sitemap finder.
Why it’s worth checking
Search engines are forgiving, but not endlessly. A sitemap with structural errors may be partly or fully ignored, and Search Console will report “Couldn’t fetch” or “Sitemap could be read, but has errors”. The pages you were counting on it to surface get found slowly, or not at all.
The contents matter too. Your sitemap says “these are my real pages”. Fill it with HTTP URLs, duplicates and redirects and you’re sending mixed signals and wasting crawl time.
Fixing what it finds
Missing XML declaration or namespace
A valid sitemap starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-01-15</lastmod>
</url>
</urlset>Quick fix
Fix the template that generates the sitemap, not the file itself, or the problem comes back on the next rebuild.
URLs using HTTP
If your site redirects to HTTPS, every entry should already be HTTPS, otherwise you’re pointing crawlers at redirects. This usually comes from a site URL setting in your CMS that still says http://.
Duplicate URLs
Usually from merging sitemaps, or the same page living at two addresses (with and without a trailing slash, or with tracking parameters). Each real URL should appear once.
Invalid lastmod dates
Use YYYY-MM-DD or a full timestamp like 2026-01-15T09:30:00+00:00.
Watch out
If every date in your sitemap is “today”, search engines learn to ignore your dates entirely.
Too many URLs
Split into files of up to 50,000 URLs and list them in a sitemap index. Splitting by type (products, categories, articles) also makes Search Console’s indexing reports much easier to read.
Valid isn’t the same as useful
A sitemap can pass every check and still be unhelpful. Skim the URL list for:
- Pages that redirect, 404, or are marked
noindex. Take them out. - Pages whose canonical points elsewhere. List the canonical version instead.
- Important pages that are missing.
- Test, staging or admin URLs that should never have been published.
The canonical checker is handy for spot-checking URLs from the list, and a site audit checks status codes across the whole site.
Quick answers
Does priority affect rankings?
No. Google ignores priority and changefreq. Fix invalid values anyway; other search engines may read them.
Can I check a gzipped sitemap?
This tool reads plain XML. For a .xml.gz file, check the uncompressed version or the index that lists it.
How often should it update?
Automatically, whenever pages are added, removed or changed. Most CMSs and frameworks can generate it for you.