XML Sitemap Validator
Validate your XML sitemap for SEO compliance and search engine compatibility
How it works
About XML Sitemaps
SEO Benefits
Sitemaps help search engines discover and index your pages more efficiently
Validation
Ensure your sitemap follows the standard protocol for maximum compatibility
Sitemap Index
Large sites can use sitemap index files to organize multiple sitemaps
Freshness
Use lastmod tags to indicate when content was last updated
Sitemap Best Practices
- *Maximum 50,000 URLs: Each sitemap file should contain no more than 50,000 URLs
- *File size limit: Keep sitemaps under 50MB uncompressed
- *UTF-8 encoding: Always use UTF-8 encoding and escape special characters
- *Absolute URLs: All URLs must be absolute (include full domain)
- *Submit to Search Engines: After validation, submit your sitemap via Google Search Console
What This Validator Checks
When you supply a URL, the validator fetches the file and parses it as XML; when you paste content directly, it works from exactly what you provide. Either way it first confirms the document is well-formed XML and that its root element is either <urlset> for a standard sitemap or <sitemapindex> for an index that points to other sitemaps. It then walks each entry, verifying that every <loc> holds a properly formed absolute URL and that optional tags such as <lastmod>, <changefreq>, and <priority> use valid values.
The report separates errors from warnings because they carry different weight. An error (malformed XML, a missing <loc>, or a relative URL) will cause search engines to reject or skip entries. A warning flags something allowed by the protocol but worth reviewing, such as a lastmod date far in the future or a priority set on every URL, which search engines largely ignore. Optionally, the accessibility check requests a sample of up to 50 listed URLs to confirm they respond rather than returning 404s or redirects, catching the common problem of a sitemap that lists pages which no longer exist.
Standard Sitemap vs. Sitemap Index
A single sitemap is capped at 50,000 URLs and 50 MB uncompressed. Large sites break past those limits by splitting their URLs across several sitemap files and listing all of them in a sitemap index, a small file whose entries point to sitemaps instead of pages. Submitting the index alone lets a search engine discover every child sitemap in one step. This tool detects which format you have and reports the counts accordingly, so an index shows the number of nested sitemaps rather than a raw URL total.
A valid sitemap is a discovery aid, not a ranking guarantee. It tells crawlers which URLs exist and roughly how often they change; it does not force indexing. Pages blocked by robots.txt, marked noindex, or judged low quality can still be excluded even when listed. The practical value of validating is catching the mechanical mistakes (bad encoding, stray relative paths, dead links) that quietly stop crawlers from using the file at all.
Frequently Asked Questions
What is the difference between an error and a warning in the results?
Errors are problems that will actually break how search engines read your sitemap: invalid XML, a missing location tag, or a relative instead of absolute URL. Warnings point to things that are technically permitted but questionable, such as a future lastmod date or a priority value applied uniformly to every URL. Fix errors first; review warnings as time allows.
How many URLs can one sitemap contain?
A single sitemap file may hold up to 50,000 URLs and must stay under 50 MB uncompressed. If your site exceeds either limit, split the URLs across multiple sitemaps and reference them all from a sitemap index file, then submit the index.
Does validating a sitemap guarantee my pages get indexed?
No. A sitemap helps search engines discover URLs and understand how often they change, but indexing remains their decision. Pages blocked by robots.txt, tagged noindex, or considered low value can be listed in a valid sitemap and still not appear in search results.
Can I check a sitemap without hosting it publicly first?
Yes. Switch to the "Paste XML" tab and drop your sitemap content straight in. This is handy for validating a file you are generating locally or reviewing changes before deploying them to your live server.
Do changefreq and priority tags actually affect crawling?
Their influence is minimal. Major search engines have stated they largely ignore priority and treat changefreq as a weak hint at best, relying more on their own crawl signals. A reliable lastmod date is the more useful metadata, since it can help crawlers prioritize genuinely updated pages.
Discussion
Start the conversation
Leave a comment
Loading comments...