The change log is the fastest way to learn that a tool you rely on now behaves differently, or that a metric moved because its definition did rather than because your site did.
What the recent entries show
- December 2025 — the GET parameter configuration tool, letting you declare which parameterised URLs should be crawled and which treated as duplicates.
- November 2025 — site diagnostics reorganised into errors and recommendations, plus a manual checklist.
- October 2025 — the IP address check tool.
- July 2025 — new roles for site access.
- April 2025 — My sites grouped by primary and alternate addresses, with errors shown in the table; query monitoring extended to 18 months of monthly averages.
- April 2025 — Turbo pages discontinued.
- 2024 — the menu reorganised into Website optimisation and Efficiency; query monitoring linked to landing URLs; the beta query selection and product analytics tools; links reporting rebuilt around internal links, external links and clicks on broken links.
- 2021 — IndexNow support, and duplicate title and description reporting.
How to use it
Read it when a number moves without an obvious cause. Matching the date of a change to the date in your report answers the question faster than any analysis of the site. A metric that steps on one specific day is usually a definition change; a metric that drifts is usually the site.
What the log tells you about the product
Two things worth noting. Tools arrive frequently and are often not announced anywhere else — the GET parameter tool and the IP check both appeared this way. And features are genuinely retired: Turbo pages were a significant investment for many publishers and are simply gone. A Yandex strategy built on a current feature needs the log checked periodically, not once.
How we apply this
When a client’s Yandex report shows a step change on a single day, we check this page before investigating the site. More than once the “drop” was a reporting change and nothing had moved. We also scan it quarterly, because useful tools appear here and nowhere else — the GET parameter configuration is one we would have missed entirely.
Related services