My sites is the portfolio screen: every site on the account with its headline numbers side by side. It is built for triage — two minutes a week, opening only what moved — rather than for analysis.
What each row reports
- Site errors detected by the daily automated checks.
- Pages the Yandex robot visited during indexing.
- Pages actually participating in search.
- Whether crawling via the Yandex Metrica tag is switched on.
The gap between the second and third numbers is the one worth watching. Pages crawled but not in search means Yandex looked and declined, and the reason is stated per URL in the Indexing reports.
Crawling by Metrica tag
Yandex can discover pages through the Metrica tag rather than only through links and sitemaps — useful for sections reachable only via forms, filters or JavaScript navigation. If the tag is already linked to the site in the console, crawling is enabled with one click; if not, a linking request has to be submitted first. This is a genuine discovery channel with no Google equivalent, and it is switched off by default.
Primary and alternate addresses
The list groups a site’s mirrors and shows the primary address. When a site moves from HTTP to HTTPS, or between www and non-www, the old address stops being primary and the new one appears in the list — which is the fastest way to confirm that a migration was actually recognised rather than merely deployed. Expanding a row shows every alternate address Yandex has grouped.
Two deletion rules that surprise people
- Removing a site from the console does not remove it from search and has no effect on indexing. The console is a window, not a switch.
- A site added but never verified disappears from the list after a month. Work that stalls at the verification step therefore has to be restarted rather than resumed.
Deleting a site properly means removing the verification marker first, then removing the entry — and doing so revokes access for every user whose rights depended on that verification.
Housekeeping that pays
Sites can be searched by name or URL fragment and pinned to the top of both this page and the main menu dropdown. On an account holding thirty client domains this is the difference between a weekly check that happens and one that does not.
How we apply this
We treat this screen as the Monday morning check on multi-domain accounts: anything whose error count or in-search count moved gets opened, everything else gets left alone. It is the cheapest way we know to catch a problem in the week it starts rather than the month it becomes visible in revenue. Sites are pinned by client, not alphabetically, so the ones under active work sit at the top.
Related services