How to tell if a Google update caused your ranking drop

Two checks tell you whether a Google update caused your ranking drop: the date the drop starts, and how far it spreads across your templates. An update moves a whole class of pages at once, on a date Google often publishes. A change you shipped moves the pages you touched, starting the day you touched them. Run both checks in that order and most drops get an answer inside an hour.

Start with your own work. The cheapest explanation is the one you can verify in ten minutes, and it is the only one you control.

Check your own change log before you check Google

Pull everything your team shipped in the 14 days before the drop. Deploys, CMS edits, template changes, redirect rules, robots.txt, CDN config, plugin upgrades. Line those dates up against the first day rankings moved.

The usual causes are dull. A noindex tag that rode a staging config into production. A canonical pointing at a parameter URL. A nav redesign that cut the internal links into a section. A redirect chain added during a URL cleanup. A CDN rule that started serving Googlebot a challenge page.

If the drop starts within a day or two of a release, treat it as yours until you can show otherwise. Some self-inflicted drops arrive slowly instead, which is why two pages competing for the same query can bleed positions for a month with no deploy to blame.

Match the date against the Search Status Dashboard

Google publishes confirmed ranking updates on the Search Status Dashboard, each with a start time and a duration. The August 2026 spam update started on 18 August and ran 2 days 16 hours. The May 2026 core update started on 21 May and ran 11 days 21 hours. If your drop starts inside one of those windows, an update is a live suspect. If it starts three weeks after the last one closed, it is not.

A miss on the dashboard still leaves Google in the frame. Google’s own testing page reports 719,326 search quality tests and 4,781 launches in 2023, and almost none of them ever got a dashboard entry. That is the argument in most Google ranking updates go unannounced, and the practical use of it here is narrow: the dashboard confirms, it never clears.

Segment the drop by template

A site-wide average position hides the cause. Open Search Console, filter by page path, and compare the week after the drop against the week before it. Do it one directory at a time: /blog/, /product/, /docs/, whatever your structure is.

Three patterns cover most cases. One template falls while the rest hold flat, which points at a technical change on that template. Every informational page falls while your product pages hold, which points at an update reweighting a content type. One query family falls across several templates, which means Google reinterpreted the intent behind those searches and the pages winning now look different from yours.

Timing changes the reading. Google’s core update documentation asks you to wait “at least a full week after a core update completes” before you analyze your site in Search Console, and to compare that week against a week before the rollout started. Read the data mid-rollout and you get a diagnosis you will throw away.

Use volatility trackers as a second opinion

Mozcast, Semrush Sensor, Sistrix’s Update Radar and AccuRanker’s Grump all work the same way. Each watches a fixed sample of keywords across many domains and reports how much the results moved that day. They tell you whether the day was noisy for everyone.

They know nothing about your site, so they can corroborate a date and nothing else. A red day on three trackers plus a drop on one template is corroboration. A calm day plus a drop anywhere on your site sends you back to the change log.

What to do with each verdict

Your change: ship the fix, request indexing on a sample of the affected URLs, and give it two weeks before you judge the recovery.

An update, small move, say position 2 to 4: hold. Google recommends avoiding changes to content that is already performing well, and small position moves are noise you can chase forever.

An update, large move, still there after a month: the work sits in content quality on the affected template. Google says its systems can take several months to learn a change, and it offers no guarantee that any edit moves the result. Plan for a quarter, not a sprint.

Then write the verdict down with the date and the evidence behind it. Six months from now, when someone asks why traffic dipped in September, the answer should already be in a file.

Ranking drops read faster when someone has already worked through a hundred of them. If you want help turning a drop into a plan, that is the work we do.