Tool usage limits

The console’s tools work without adding a site and without verifying ownership — with restrictions. Exceeding a limit produces a warning and reduced functionality.

The reset

All limits reset at 00:00 Moscow time (UTC+3). That is a practical detail for anyone working outside that zone: quota planning for a large batch of checks has to be done against Moscow midnight, not local midnight.

What verification changes

Verifying ownership lifts the restrictions and unlocks the rest of the service. This is the same gate as everywhere else in Yandex — indexing detail, query data, regional settings, re-check requests — and the tools follow the same rule.

Why the unverified mode still matters

It means the server response check, the robots.txt analyser, the sitemap validator, the structured data validator and the IP check can be run against any site, including one you do not control. For competitive analysis, for auditing a prospective client before an engagement begins, or for diagnosing a partner’s site, that is genuinely useful — and it is why these tools appear in audits of sites the auditor has no access to.

Planning around the limits

Two practices avoid hitting them. Verify the sites you work on regularly, which removes the question entirely. And batch checks deliberately rather than scripting hundreds of calls — the quotas are generous for interactive diagnosis and not designed for bulk automation.

The honest reading

Limits exist to stop the free tools becoming an anonymous crawling service. For ordinary technical work they are invisible; the only people who meet them are running the console as a data source, and the answer there is verification rather than persistence.