Pre-deployment validation
Paste generated XML and catch structural errors before publishing it at a public URL.
Crawling and indexing tool
XML Sitemap Validator
Enter a sitemap URL or paste its XML to check the file. Find structural problems and review duplicates, dates, and mixed origins before publishing or submitting it.
FreeNo loginNo data stored
Live sitemap diagnosis
Fetch the deployed file and separate response failures from XML validation issues.
Migration review
Find old origins, duplicates, or malformed dates that entered a rebuilt sitemap.
What it checks
Use the result as evidence, not a score.
- URL set and sitemap index root structures
- Paired XML elements and required location values
- Absolute HTTP and HTTPS locations
- Duplicate URLs, lastmod formats, origin count, and the 50,000-entry limit
What it cannot check
- Whether every listed URL is canonical, indexable, useful, or current
- Google Search Console submission and processing state
- Whether search engines will crawl, index, rank, or display any submitted URL
How it works
Input, inspect, improve, verify.
The tool processes what you enter, shows a plain-language result, and gives you a safer next step. Make the change on your website, deploy it, then test the live page again.
Understand the result
How to use this sitemap validation tool
Paste the full public sitemap URL, rather than the homepage URL, and select Validate sitemap. If you do not know the file’s location, use Sitemap Finder first. You can also paste XML before deploying it; when both fields contain input, pasted XML takes precedence.
Read Validation issues first, then Review items. The checker reads at most 2 MB from a public response and does not fetch every listed page or recursively validate child sitemaps. A larger file needs a validator that supports its size, even if it is within the sitemap protocol limits.
- Validate a sitemap index and its child files separately.
- Keep a copy of the original file before changing the generator.
- After deployment, check the public URL again rather than relying only on pasted XML.
Understand the result
Fix relative URLs and missing location values
For a page at https://example.com/about, a location value of /about is incomplete. Put https://example.com/about inside the <loc> element, with the intended protocol, hostname, and path. Each page entry in a URL set needs its own location; in a sitemap index, each location points to a sitemap file.
If a closing tag does not match its opening tag, correct the XML source and rerun the check. Fix the CMS template or generator that creates the error so the next rebuild does not restore it. This tool checks selected structural rules; it is not a complete XML schema or extension validator.
- Keep absolute HTTP or HTTPS locations.
- Review each reported missing or invalid location in the source file.
- Valid syntax does not establish that a URL is canonical or indexable.
Understand the result
Review duplicates and lastmod separately from syntax errors
A repeated location can indicate that two content sources feed the same sitemap. Deduplicate the source inventory after confirming the preferred URL. Multiple origins can be intentional in a verified cross-site setup, so review ownership and submission context before changing them.
A date can have a supported format and still be inaccurate. Use lastmod only for a meaningful page change, and omit it when the source cannot supply a trustworthy date. This validator cannot establish when the content actually changed or whether Google has processed the file.
- Keep one deliberate canonical location for each intended page.
- Use Search Console for Google’s submission and processing feedback.
- Check page responses and indexability as a separate step.
Popular use cases
Useful before and after publishing.
Pre-deployment validation
Paste generated XML and catch structural errors before publishing it at a public URL.
Live sitemap diagnosis
Fetch the deployed file and separate response failures from XML validation issues.
Migration review
Find old origins, duplicates, or malformed dates that entered a rebuilt sitemap.
Pro tips
Small checks that prevent avoidable mistakes.
- Validate XML and URL selection as two separate questions.
- Use absolute canonical URLs and keep protocol and host choices intentional.
- Only publish lastmod when it reflects a meaningful page update.
- Split files before exceeding 50,000 URLs or 50 MB uncompressed.
Common issues and solutions
What to review when the result looks wrong.
The XML is well formed but still unhelpful
A syntactically valid file can still contain redirects, errors, noindex pages, duplicates, or alternate URL versions.
lastmod dates are inaccurate
Remove mechanically refreshed dates unless they represent meaningful page changes that search engines can trust.
More than one origin appears
Cross-site sitemaps need deliberate ownership and submission context. Confirm the setup rather than changing every URL automatically.
Frequently asked questions
Short answers before you make a change.
How do I validate an XML sitemap?
Enter the full sitemap URL or paste XML, then select Validate sitemap. Correct reported structural and location issues, review warnings, and check the deployed file again.
Does valid XML guarantee that Google accepts a sitemap?
No. Validation catches observable file issues. Search Console can show processing feedback for a verified property, and submission still does not guarantee indexing.
Can I validate a sitemap index?
Yes. The validator checks the index file’s location entries. It does not recursively fetch its child files; validate each child sitemap separately.
Does the validator crawl every listed URL?
No. It validates the sitemap file itself. URL accessibility and indexability need separate bounded checks.
Read the practical guide
Valid XML is only the first sitemap test
Understand the evidence behind this tool, where its result stops, and the safer next steps to verify on a live page.
Read the guideEvidence · Limitations · Verification