A weekly site check in Yandex Webmaster and Search Console: what to look at in 15 minutes

Most people open Yandex Webmaster and Google Search Console for one of two reasons: traffic has dropped, or a report is due. Either way, they are late. A broken robots.txt, an expired certificate or a section that started returning 404 after a release shows up in both consoles within a day or two, but it takes weeks to show up in traffic. This article sets out a check that fits into 15 minutes a week: which reports to open, in what order, which numbers to read, and which messages you can safely ignore.

Why weekly, when Google says monthly is enough

Google's getting-started guide for Search Console says there is no need to sign in every day. Checking roughly once a month, or after you change the site's content, is enough, and Search Console will email you when it finds new issues (developers.google.com, checked 15 October 2026). For a brochure site nobody touches, that advice holds.

A site under active work changes every week: a template goes out, a batch of articles is published, catalogue filters are reworked, the CMS is updated. Any of those can break something, and a month between checks means a month in which the error accumulates in the index. Email alerts do not catch everything either. You get a message when the system recognises a problem as a problem. A section that quietly loses a third of its impressions triggers no email at all.

The monthly indexing review and the quarterly technical audit stay where they are. The weekly check has a narrower job: confirm that nothing broke this week, and catch a deviation before it turns into a decline. The full monthly routine for the index is in our guide on how to check whether your site is indexed. This article covers only what is worth looking at more often.

One-time setup: notifications and important pages

Fifteen minutes is only realistic if the consoles do part of the work for you, and that takes some setup once.

In Yandex Webmaster, start with notifications. According to Yandex's help (checked 15 October 2026), alerts can go to the Webmaster interface, to email, to Telegram or as push notifications, and you can configure them for all your sites at once or for each site separately. Switch on at least "Site errors", "Changes to robots.txt" and the alert for a change of the site's main address. The last one fires when the robot picks a different main mirror, such as the www version. The weekly site summary is also worth having. It comes by email only, covers Monday to Sunday, and lists errors, changes in the number of pages in search, click trends and resolved problems. If nothing changed, or the changes were minor, no email is sent.

The second step is Indexing → Monitoring important pages. You can add up to 100 URLs, and Webmaster shows each one's last crawl date, response code and search status. These pages get their own alerts: a change of response code, search status, title, description or canonical. Add the home page, the main categories or service pages, and the pages that bring in the most leads. Without that alert, a changed canonical on a key page usually goes unnoticed for a month.

Search Console needs almost no setup, since Google emails you about new issues it finds on the site. Check two things only: that the site is added as a Domain property, and that the alerts go to an inbox someone reads rather than to a contractor who left last year.

Minutes 1–3: diagnostics and security

The check starts with whatever could remove the site from search entirely. Rankings and clicks come later.

In Yandex Webmaster this is Website optimization → Site diagnostics. Yandex checks the site daily. Since 27 November 2025, according to the Yandex Webmaster blog, issues fall into two categories instead of the previous four: "Errors", which absorbed the old fatal and critical levels, and "Recommendations", which took over possible problems and suggestions. Guides that still talk about "fatal" and "critical" issues describe an interface that no longer exists.

Yandex's help lists these cases under the Errors tab: the home page returns an error, the server could not be reached because of a DNS error, the site is blocked in robots.txt, violations or security problems were found, slow server response (the robot flags pages that take longer than 3 seconds to load), a misconfigured SSL certificate, and duplicate pages created by GET parameters. If a new entry appears on this tab, stop the check and deal with it straight away. Once it is fixed, click "I've fixed everything", but read the caveat in the help first: if the robot finds the same error again, you cannot report a fix for another 30 days. Make sure the problem is actually gone before you press the button.

Next to it is the Security and violations section. The help gives a simple rule: if no violations are listed there, no restrictions apply to the site or its sections. All you need is to see that the list is empty.

In Search Console the same three minutes go to the Security issues report and the Manual actions report. The first covers hacked content, malware and social engineering. The second covers penalties for attempts to manipulate the index. On a healthy site both show a green check mark.

Minutes 4–6: crawl statistics and response codes

The second block answers one question: what did the robot get from your server this week? Release problems surface here first.

In Yandex Webmaster, open Indexing → Crawl statistics and switch to recent changes. Yandex's help says the data is updated daily, within six hours of the robot's visit, and the list of changes shows pages whose response code changed, with the old code in one column and the new code in the next. Filter the list by 404 or 5xx. If it was empty yesterday and today a hundred URLs from one section have gone from 200 to 404, you have found broken routing before your users did. URLs that never existed on your site usually mean the robot found malformed links elsewhere on the web. That can wait.

Look at the crawl history chart, but do not draw conclusions from a single data point. The same help page says the number of crawled pages varies from day to day and has no effect on indexing or ranking. A worrying pattern looks different: crawling drops close to zero, or a visible share of 5xx responses appears in the history.

In Search Console the equivalent report sits under Settings → Crawl stats. Google calls it a report for advanced users and says sites with fewer than a thousand pages should not need it (support.google.com, checked 15 October 2026). On larger sites the host status panel is useful: robots.txt fetching, DNS resolution and server connectivity. Green means no significant availability problems in the past 90 days. Yellow means a problem within that period, but more than a week ago. Red means a problem in the last week, and red is exactly what a weekly check is there to catch.

Minutes 7–9: pages in search and excluded pages

The third block is the index. There is no need to go through it in full every week; you only need to see which way the numbers moved.

In Yandex Webmaster, this is Indexing → Pages in search, in recent changes mode. It shows which pages entered search and which dropped out, with the reason for each exclusion. Look at which pages dropped out. A few dozen URLs marked as duplicates after you cleaned up filters is expected. An important category marked as a loading error or as blocked by robots.txt is a reason to open the robots.txt file and read our explainer on robots.txt vs noindex. Drops like these are most often caused by a rule that blocks crawling when the intention was to block indexing.

In Search Console, open the Page indexing report filtered to all submitted pages. It answers the main question of the week: how many URLs from your sitemap are indexed, and whether the count of non-indexed pages has grown for one particular reason. If you clicked "Validate fix" last week, check the validation status. Google's help says validation usually takes about two weeks, so expect the result in a later check.

Sitemaps get a quick look too: Indexing → Sitemap files in Yandex Webmaster, the Sitemaps report in Search Console. You only need to confirm that each file is read without errors and that the last read date is recent. Do not use the "indexed" figure on the Search Console sitemap report here. The API marks that field as deprecated, and the report lags behind the index; our indexing guide explains the details.

Minutes 10–13: queries, clicks and rankings

Visibility comes last. A drop in clicks is nearly always the result of something in the three blocks above, and it helps to know the cause before you look at the chart.

The two consoles have different delays, and that decides which day you run the check. Yandex's search query statistics update daily, but they count impressions and clicks only down to position 50, and the "Popular queries" group takes the top 3,000 phrases by impressions over the last three months (Yandex help, checked 15 October 2026). For Search Console, Google's help says collected data is normally available in 2–3 days, and daily figures follow California time. If you open the report on a Monday, the last days of the previous week are incomplete and the week will always look worse than the one before. Run the check on Wednesday or Thursday instead, and compare the last full week with the week before it.

What to look at:

• clicks and impressions for the week against the previous week, in both consoles;
• the Favorites group in Yandex Webmaster. Add the queries you are targeting once, and you get a separate trend line for them;
• the Performance report in Search Console broken down by page, to see which page lost the most clicks;
• for a seasonal business, the same week last year, if you have the data.

Do not trust site-wide average position over a single week. It shifts when the site starts appearing for new, low-ranking queries, so a falling average can be a sign of growth. Why this metric should never go into a report without explanation is covered in our guide to the monthly SEO client report. For a weekly check, clicks and impressions are enough.

Treat week-on-week swings of 10–15% with no obvious cause as normal. A bigger drop that repeats two weeks running, or one concentrated in a single section, needs investigating.

Minutes 14–15: what to write down

The last two minutes go on a log. It is an ordinary spreadsheet with one row per week and the same columns every time:

The last column matters most. Six months from now nobody will remember why impressions fell in March unless "new catalogue went live" is written next to the number. The log turns separate snapshots into a history you can read causes from, and the monthly report can be built from it without another tour of every console.

What you can skip each week

Most messages in both consoles do not need a weekly response. Trying to handle all of them stretches the check to an hour, and an hour-long check soon stops happening.

• The Recommendations tab in Yandex diagnostics. Yandex's help puts things like a missing favicon, an unset region, and duplicate titles and descriptions there. These belong in the backlog and can be reviewed quarterly.
• IKS, Yandex's site quality index. The help says it is "regularly recalculated", and you can get an alert when that happens, so there is no reason to go looking for it. It does not drive any weekly decision. What it does and does not measure is covered in our article on site authority metrics.
• The total number of excluded pages. Yandex's help says outright that having excluded pages, and how many, should not affect the site's position in search. A look at the reasons for exclusion is enough.
• Swings in the crawl chart when the responses show no errors.
• Broken external links pointing at URLs that do not exist. Review them monthly, sorted by the linking site's IKS, and decide which ones deserve a redirect.
• 404s on URLs that never existed on your site. Yandex's HTTP status code reference advises ignoring these; someone probably published a bad link.
• Daily ranking swings on individual queries. Over a week one query can move across the whole of page two and mean nothing.

When the weekly check turns into an investigation

The weekly check does not fix anything by itself. It ends in one of two ways: "nothing broke this week", or a specific signal that needs separate work. These are the signals that justify stopping and investigating the same day:

1. A new entry on the Errors tab in Yandex Webmaster, or a red host status in Search Console.
2. Any entry in the security or violations reports.
3. A robots.txt change alert that nobody planned.
4. A monitored important page changed its response code or canonical, or dropped out of search.
5. A sharp rise in new 404s, or 5xx responses appearing in the crawl statistics.
6. Clicks down more than 15% two weeks in a row, or down a third in one section at once.

The first five usually have a targeted fix: roll back a rule, restore a page, repair the server. The sixth, with no obvious technical cause, needs a wider view. Work through our technical SEO audit checklist in order, starting with the index and response codes, and compare how the site behaves in the two search engines. If the drop appears in only one, the cause is nearly always something that engine treats differently. Our article on Yandex vs Google collects those differences.

If all six are clear, add a row to the log and close the tabs. Most weeks end that way. The habit pays off in the week a release does break something: with a weekly check the breakage lives for a few days, with a monthly one for up to four weeks.

Frequently asked questions

What should I check first in Yandex Webmaster?

The Errors tab in Site diagnostics and the Security and violations section. Those hold the problems that can take individual pages or the whole site out of search. Rankings and clicks come after them.

Where did the fatal and critical errors go in Yandex Webmaster?

Since 27 November 2025, according to the Yandex Webmaster blog, diagnostics uses two categories: Errors (the former fatal and critical issues) and Recommendations (the former possible problems and recommendations).

How often should I check Google Search Console?

Google says there is no need to sign in daily and that about once a month, or after changes to the site, is enough. If your site changes every week, a weekly check catches an error up to three weeks sooner.

Why don't Webmaster and Search Console numbers match Yandex Metrica or Google Analytics?

The consoles count impressions and clicks on the results page. Analytics counts visits where the tracking code fired, and a click can go unrecorded if the page failed to load or the code did not run in time. Compare trends within one source rather than figures across sources.

Which day of the week is best for the check?

Wednesday or Thursday. Search Console data normally arrives within 2–3 days, so by midweek the previous week is complete. On a Monday the last few days are partial, and the chart will show a drop that is not there.

Should I act on Yandex's diagnostic recommendations?

Yes, but outside the weekly check. A favicon, a region setting or duplicate titles are backlog tasks. Only the Errors tab needs urgent attention.