Traffic drop after an update: diagnosing and recovering rankings in Google and Yandex

One morning you open analytics and see organic traffic down 30, 50, sometimes 70 percent. The first instinct is to panic and change everything at once. That is the worst thing you can do. A sharp drop after an update calls not for frenzy but for cold diagnosis: what exactly fell, when, on which pages and queries, and whether it lines up with a known algorithm update. This guide is a step-by-step plan: how to find the cause of a drop in Google and Yandex and how to methodically recover rankings without making it worse.

Step 1: confirm it is an update, not something else

Before fixing anything, rule out simpler causes — they are faster and safer to fix. Seasonality: demand for your topic may fall every year at this time (check year-over-year dynamics). A technical glitch: the site may have gone down, returned 5xx, been accidentally blocked in robots.txt or shipped with a noindex — check availability and indexing first. Manual actions: look at "Manual actions" in Google Search Console and "Security and violations" in Yandex Webmaster — if there is a message, it is a penalty, not an algorithm, and it is fixed differently. Only if everything is clean and the drop is sharp and date-aligned with a known update is it an algorithmic update.

Step 2: update types and what they target

Knowing the update type points you to where the cause lives. On the Google side there are several main kinds:

• Core Update — a re-evaluation of overall quality and relevance. Hits sites with thin, non-expert or intent-mismatched content. Recovery comes through quality improvement, not point hacks.
• Spam Update — targets spam practices: cloaking, manipulation, mass auto-generation, spam links. If hit, look for guideline violations.
• Helpful Content (now part of core) — demotes content made "for the engine, not people": mass AI text with no value, articles about nothing, aggregated material with no added benefit.
• Product Reviews / niche updates — affect specific content types (product reviews etc.) and demand expertise and first-hand experience.

Yandex has its own filters and updates. Baden-Baden demotes pages with over-optimization and keyword-stuffed text. Minusinsk targets bought SEO links. There are also general algorithmic updates (historically Palekh, Korolev, the Y-update series) re-evaluating relevance with neural models. Yandex leans harder on behavioural factors, so behavioural manipulation is a separate cause of sanctions. If the drop is in Yandex only while Google is stable, it is almost certainly Baden-Baden (text) or a behavioural/link factor.

Step 3: diagnose — what exactly fell

Updates rarely hit the whole site evenly. Open Search Console and Yandex Webmaster and compare the period before and after the drop: which pages lost the most clicks and impressions, which queries fell, in which topics/sections the decline is steeper. Often a specific group of pages fell — say thin category pages or old un-updated articles — while the rest is stable. That narrows the cause: if thin pages fell, it is a quality signal (core/Helpful Content); if keyword-stuffed pages fell, it is over-optimization (Baden-Baden); if pages with bought links fell, it is a link filter.

Step 4: the recovery playbook

Recovery from an algorithmic update is not "undo one change" but restoring the quality the new algorithm version demands. Act in priority order:

• Improve the fallen pages substantively: add expertise, first-hand experience, current data, cut the fluff. Not cosmetics — real value for the reader.
• Deal with thin and duplicate content: weak pages should be strengthened, merged, or noindexed. A mass of useless pages drags the whole site down.
• Remove over-optimization (especially for Yandex): rewrite keyword-stuffed text into natural language. That is exactly what fixes Baden-Baden.
• Clean the link profile: if there are bought/toxic links, prepare a disavow (for Yandex via Webmaster). Especially when Minusinsk or a Spam Update is suspected.
• Strengthen E-E-A-T: authorship, expert bios, sources, transparency about the company. For YMYL topics this is critical.
• Wait for the next update: recovery from a core update is often locked in only at the next algorithm rollout, not immediately. This takes patience.

What NOT to do

• Panic and change everything at once — then you will not know what helped and what hurt. Change deliberately and track.
• Mass-delete pages in a panic — you can lose the ones that brought traffic too. Diagnose first.
• Buy links "for a quick recovery" — that is the road to an even deeper filter.
• Roll back recent useful changes just because traffic fell after them (correlation ≠ cause; an update may have coincided).

How not to miss the next drop

The sooner you spot a drop, the more precisely you tie it to a cause and the faster you respond. Set up position and traffic monitoring with alerts: so the system itself notifies you when key queries fall out of the top or traffic drops by a set percentage week-over-week. Without automatic monitoring, drops are often noticed weeks later, when recovery is already harder. Site Metrics Tool tracks positions in Google and Yandex every few hours, keeps up to 16 months of history (to separate an update from seasonality via year-over-year dynamics) and alerts you to a sharp fall — so you learn about the problem the same day, not a month later.

Traffic-drop checklist

• Ruled out seasonality, tech glitch and manual actions (GSC "Manual actions", Webmaster "Violations").
• Cross-checked the drop date against known updates.
• Identified which pages and queries fell (GSC + Webmaster, before/after period).
• Matched the drop pattern to the update type (quality / over-optimization / links).
• Shipped substantive improvements, without panic or mass deletions.
• Set up monitoring with alerts so you do not miss the next wave.

Updates are not the end but a re-evaluation. Sites that methodically grow quality, expertise and intent-match more often rise after updates than fall. The key is not to panic, to diagnose from data, and to act on a plan. And to catch drops the day they happen and tell an update from seasonality, keep positions and traffic for both engines under automatic monitoring.