Calculator
What the XML Sitemap Validator does
XML Sitemap Validator: checks Verdict, URLs and File size from Paste your sitemap XML. Example: the sample loaded on the page gives verdict Invalid XML.
Point it at Paste your sitemap XML and it returns Verdict, URLs and File size. Edit a field and the answer updates in place.
Typical users are site owners checking their markup. Structured data is easy to get subtly wrong and hard to notice when you do.
Nothing leaves the tab. You can watch your browser network panel while you use it and see for yourself.
The sections that follow cover the fields, the method, and one full example computed from the defaults.
What do the XML Sitemap Validator fields mean?
The XML Sitemap Validator uses 1 input. Each input has a default that makes sense on its own, so a partial edit still gives a valid result.
| Field | What to enter | Default |
|---|---|---|
| Paste your sitemap XML | paste or type any amount of text | <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url><loc>https://example.com/</loc></url> </urlset> |
How does the XML Sitemap Validator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same check.
Nothing is computed until the inputs pass their checks, so you will not get a confident answer built on a typo.
Worked example
These are the values the XML Sitemap Validator loads by default, and the result it produces from them. Here is the calculation as it stands the moment the page loads.
| Paste your sitemap XML | <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="htt… |
|---|
| Verdict | Invalid XML |
|---|---|
| URLs | 0 |
The checks that matter versus the ones that are cosmetic
A handful of these validation checks are protocol-breaking. Google may reject or mishandle the file entirely. The rest are best-practice hygiene that will not stop the sitemap from working.
Worth knowing
- The xmlns namespace, a valid root element (urlset or sitemapindex), and well-formed XML are non-negotiable. Getting any of these wrong means the file may not be read as a sitemap at all.
- An unescaped ampersand in a URL is a surprisingly common real-world failure. & must be written as & inside XML, and a URL parameter containing a raw & can break the parser for that entry or the whole file, depending on how strict the consumer is.
- Duplicate URLs and relative paths are hygiene issues rather than hard failures in most implementations, but both indicate the sitemap was likely generated incorrectly and are worth fixing at the source.
- The 50,000-URL / 50MB uncompressed limits are hard protocol limits, not guidelines. Exceeding either means splitting into multiple sitemaps referenced from a sitemap index.
How to use it
- Paste your content into Paste your sitemap XML.
- The result appears as you type. There is no button to press.
- You get Verdict, URLs and File size back.
- Copy Link is the quickest way to send the exact scenario to someone else.
What this tool does not do
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- This checks what is visible in the page you provide; it cannot see server headers or your live rankings.
- The output is a number, not a judgement. Deciding what it means is still your job.
Frequently asked questions
Just Paste your sitemap XML. Nothing starts empty, which makes it easy to isolate the effect of a single variable.
With the values loaded when the page opens, verdict comes out as Invalid XML. Any edit re-runs the calculation, so there is no stale number on screen.
Nothing leaves your machine. The only network traffic is loading the page itself.
Nothing at all. There is no registration, no paywall and no per-use quota.
The output is deterministic. The same inputs always give the same answer, and the method is documented above so you can check it.