XML sitemap validation rules
The validator checks well-formed XML, escaped entities, the sitemap namespace and entry structure. Each entry needs an absolute HTTP or HTTPS loc. Files use UTF-8 and may contain at most 50,000 entries and 50 MB (52,428,800 bytes) of uncompressed XML. The same entry limit applies to sitemap indexes.
Errors, warnings and line numbers
Errors identify malformed XML, missing locations, invalid dates and unsupported core values. Warnings highlight duplicates, future lastmod dates and cross-host declarations that need ownership or submission-scope verification. Line numbers refer to the uncompressed XML in the source column. An unavailable child file remains an unresolved fetch warning.
Sitemap indexes and extension markup
Index URLs are followed to inspect child files; a child index is reported as a nested-index error for Google submission. Image markup needs an image location. News markup needs publication name, language, date and title. Alternate-language links need the XHTML namespace, rel, hreflang and an absolute href. Reciprocal links are compared when both entries occur in the same file; other files and actual page language are not verified.
Protocol validity and search engine coverage
Validation cannot confirm ownership, truthful modification dates or indexing. Google ignores priority and changefreq, although invalid values still violate the sitemap format. Naver submission limits differ: its guide specifies a 10 MB submission size. This tool applies the sitemap protocol and Google checks and does not label a file as fully eligible for Naver.
Sitemaps protocol · Google sitemap guide · Naver sitemap submission. Checked November 14, 2026.
Coverage and run limits
Remote extraction defaults to 1,000 URLs. A run checks up to 50 live page URLs or 50 sitemap files and lasts at most 60 seconds. The result identifies coverage lost to limits or failed requests.