Sitemap validator

The sitemap validator checks a file against Yandex’s requirements before you commit to it. It accepts input three ways: pasted text, an uploaded file, or a URL.

The precondition

The file must return 200 OK — and Yandex adds a hard limit that is easy to miss: if the server takes more than 10 seconds to respond, the file is not downloaded by the tool and is not taken into account by the robot. On large generated sitemaps assembled per request, that is a real risk, and the remedy is to generate them ahead of time rather than on demand.

Why the paste option is the useful one

Because it validates a file that is not published yet. Errors can be corrected in place and rechecked, which means a sitemap can be proven correct before it goes near the site. Given that a bad sitemap wastes a crawl cycle and, in the worst case, the 10-refresh quota, this is the cheapest checkpoint available.

After validation

Upload the file under Indexing → Sitemap files so the robot processes it regularly and detects changes. The console then shows when it was last crawled and lets you signal an update. Validation alone tells the robot nothing.

What the validator will and will not catch

It checks the file against the format requirements — structure, tags, encoding, limits, and the rule that a sitemap in a directory may only list URLs from that directory or below. It cannot tell you whether the URLs inside are the right ones, whether they return 200, or whether they are blocked in robots.txt. Those are separate checks, and a perfectly valid sitemap full of blocked URLs is a common and silent waste.

Limits

Tool usage in the console is subject to quotas, which matter on large sites where validation is scripted rather than occasional.