XML Sitemap Validator

Validate sitemap.xml locally with URL-set and sitemap-index protocol checks, 50,000/50MB limits, duplicate/host/date evidence, extension counts, robots.txt cross-checks and exportable audit results.

XML protocol · URL/index rules · local evidence

XML Sitemap Protocol & Index Audit Studio

Paste XML, load an XML/XML.GZ file, or try a public URL directly from this browser. Audit the actual sitemap structure, URL/index rules, limits, dates, duplicates, host/path scope, extensions and robots.txt declaration without pretending a local parser is Google Search Console.

urlset + sitemapindex50,000 entries · 50 MB uncompressedNamespace · loc · duplicates · host/pathlastmod · changefreq · priorityImage · video · news · hreflang countsCSV · JSON · Print · local history

1 · Input sitemap XML

Sitemap URL / deployment location (optional)

Sitemap XML

Paste/upload is the reliable browser-local path. Cross-origin URL fetch can fail because of CORS even when Google can fetch the sitemap.

2 · robots.txt declaration cross-check

Paste robots.txt (optional)

DeclarationNot checked

InterpretationPaste robots.txt to compare Sitemap declarations.

3 · Protocol summary

Ready to validate.

Type—

Entries0

UTF-8 bytes0 KB

Errors / warnings0 / 0

Duplicates0

Primary host—

Date findings0

img/vid/news/hreflang0/0/0/0

4 · Parsed URL / child-sitemap evidence

#	loc	lastmod	host	flags

0 entries.

5 · Export & repeat use

What this validator checks

XML and protocol shape

Reject malformed XML/DOCTYPE input, verify urlset or sitemapindex, the Sitemap 0.9 namespace, direct entry parents and exactly one direct loc per entry.

Hard file limits

Audit the 50,000-entry and 50 MB (52,428,800-byte) uncompressed limits for both sitemap files and sitemap indexes.

URL and scope evidence

Check absolute HTTP(S) URLs, duplicates, fragments, long loc values and host/path differences. If a sitemap deployment URL is provided, the audit can compare location scope too.

Date and optional metadata

Validate W3C-style lastmod, flag future dates, and validate protocol values for changefreq and priority. Google currently says it ignores changefreq and priority.

Extension visibility

Count image, video, news and XHTML hreflang annotations so you can see whether extension content is present. This is not a full Google feature-eligibility validator for every extension field.

Fetch boundary

Paste/upload mode is fully local. URL fetch is a best-effort browser request and can be blocked by CORS; its success or failure is not equivalent to Googlebot, Search Console, HTTP status/indexability or canonical selection.

Truth boundary: this Studio validates the XML text and the protocol evidence available in that text. It does not crawl every listed URL, prove HTTP status/indexability/canonical choice, emulate Googlebot, validate server MIME/redirect behavior when using pasted XML, or certify Search Console acceptance. Google also has cross-site submission rules that can make multi-host configurations valid when ownership/submission is set up correctly.

Validate the file you will actually submit

Paste the exact XML or load the local XML/XML.GZ file. The Studio separates parser errors from protocol errors and warnings instead of collapsing everything into one score.

Audit both URL sets and sitemap indexes

For a URL set, inspect every direct URL entry, absolute location, duplicate, date and optional protocol field. For a sitemap index, inspect every child sitemap location and compare host/directory scope when you provide the planned deployment URL.

Keep Google-specific behavior separate

The base sitemap protocol defines XML shape and limits. Google currently documents that it ignores changefreq and priority, can use accurate lastmod, and supports cross-site submission when ownership and submission conditions are met. Those product-specific rules are explained instead of silently turned into false protocol errors.

Use the audit as handoff evidence

Copy a human-readable report, export every parsed entry as CSV, save the complete local audit as JSON or Print/PDF it for an SEO/deployment handoff. Local history stores counts and findings only, never the raw XML.

Know when to use a live crawler

Use Search Console or a live crawl when the question is whether Google can fetch the deployed file, whether listed pages return usable status codes, whether robots/canonicals conflict, or whether URLs are indexed. This local validator deliberately does not fake those network facts.