Problems with optimization for mobile devices

Yandex judges mobile optimisation at site level, not page level, and it does so with a separate mobile robot. The diagnostics entry has several distinct wordings, and each one means something different — including two that are not about your design at all.

The failure messages and what they actually mean

• The home page is not optimised. A design and layout problem, diagnosable page by page in Tools → Audit pages for mobile compatibility.
• The home page could not be loaded for audit, or 90% of requested pages could not be loaded. These are availability problems, not design problems. The pages were unreachable at check time. Nothing in the CSS will fix them; the server or the hosting provider will.
• Many pages are not optimised. The threshold is dynamic, calculated from the number of indexed pages, so there is no fixed percentage to aim at. A site crossing this line usually has one failing template rather than many failing pages.
• Could not load the site for audit at all. The mobile robot was blocked. Check the server response and check robots.txt for a rule that catches the mobile agent — it identifies itself as YandexMobileBot/3.0 inside an iPhone-style user agent string, which is exactly the shape that over-eager bot filters block.
• No auditable pages. Support territory.

The redirect anti-pattern

One entry has nothing to do with rendering: many pages with different content redirecting to the same page of the mobile version. A separate mobile site that funnels every desktop URL to its mobile home page destroys the relationship between the two versions and strands the user who arrived looking for something specific. Yandex lists the offending pages. Where a genuine one-to-one mapping does not exist — several desktop pages genuinely merged into one mobile page — the guidance is to keep only the redirects that make sense and drop the rest, rather than redirect everything.

The confirmation loop

Diagnostics shows the result of a check on a specific date. After editing, re-run the affected pages through the audit tool, then click the confirmation control next to the entry so the site is re-checked. Skipping the audit step and simply declaring it fixed is how sites end up waiting another cycle for no reason.