Sitemap LarkXML sitemap & robots.txt tools

C1Check line

Sitemap validator

Paste a sitemap or open a .xml or .xml.gz file. You get the first XML error with its line and column, then every structural, URL, date and extension problem, grouped and counted.

Sitemap XML

.xml · .xml.gz

Or drop a .xml / .xml.gz file on the box. Nothing leaves your browser.

Summary

Waiting for a sitemap

Paste XML or open a file, then press Validate.

Sitemap facts
Type—
Entries
—max 50,000
Size
—max 50 MB
Host—
Extensions—

Issues

—
No report yet.Each kind of problem gets one block with a count, the line numbers and the start of the line. Click a line number to select it in the box.

What gets checked

First the file must be well-formed XML: an unescaped &, a blank line before <?xml, a missing end tag or a truncated download stops every parser, so that error is shown alone with its position. After that come the protocol rules: a <urlset> or <sitemapindex> root in the exact sitemaps.org namespace, one absolute <loc> per entry on a single host, W3C dates in <lastmod>, at most 50,000 entries and 50 MB uncompressed. Image, video, news and xhtml:link tags are checked against their own namespaces, including hreflang codes and return links.

Errors break the file or the protocol. Warnings are things search engines may mishandle. Notices are harmless but worth knowing.

FAQ

Why does it stop at the first XML error?

XML parsers, including the ones search engines use, must give up at the first well-formedness error. Fix that line and validate again to see the next problem.

Can I check a .gz sitemap?

Yes. Open or drop the .xml.gz file; it is decompressed in your browser and the 50 MB limit is applied to the uncompressed size.

Does a clean report mean Google will index every URL?

No. A sitemap is a hint. The pages themselves must return 200, be crawlable and not carry noindex, which only a live check of each URL can tell.