Few things spike a marketer's heart rate like watching a page that ranked on the first page slide to the third. The instinct is to panic and start changing things. Resist it. A ranking drop is almost always traceable to a specific cause, and changing things at random buries the evidence you need to find it. Here is the diagnostic we actually run, in order, and it starts with a distinction most people skip.
First, confirm it is actually a ranking drop
Before anything else, define what moved. A ranking drop and a traffic drop are not the same problem, and conflating them sends you chasing the wrong fix. Open Google Search Console, go to the Performance report, and look at average position alongside clicks and impressions for the affected pages. If average position fell, Google genuinely ranked you lower, and that is a ranking problem. If position held roughly steady while clicks and click-through rate fell, you did not lose rankings at all: the query is being satisfied on the results page, usually by an AI Overview, and the click simply never happened. That single distinction decides everything that follows. Our broader traffic-drop diagnostic covers the click-loss side in depth. The rest of this piece assumes the position actually fell.
Rule out a tracking or reporting break
Confirm the drop is real before you treat it as a ranking event.
A rank-tracking tool can glitch, quietly change its measurement location or device, or start reporting a different SERP feature as your position. Cross-check any third-party tracker against Search Console's own average position, which is measured from real impressions rather than a periodic probe. A tracker set to desktop in one city can also miss a drop that only hit mobile, or a personalized result that never reflected your true position in the first place. If the tracker says you cratered and Search Console does not, your problem is measurement, not rankings, and you have just saved yourself a week of pointless rewrites.
Check for a manual action or indexing problem
Open the Manual Actions report. A manual action is rare but unambiguous, and it tells you exactly what to fix. Far more common is an accidental deindexing that reads like a ranking collapse: a stray noindex shipped in a template, a robots.txt disallow, a canonical pointing at the wrong URL, or staging settings that reached production. Check the Page Indexing report for pages that fell out of the index. A page that is not indexed cannot rank, and no amount of content work fixes a technical exclusion. Our technical SEO field guide covers how these regressions slip in and how to catch them.
Line the drop up against Google's update dates
If tracking is clean and you are still indexed, check the timing. Google publishes the start and end dates of every core and spam update on its Search Status Dashboard, and a decline that begins on the exact date of a confirmed update is almost certainly algorithmic, not a bug. Wait until the update has fully finished rolling out, which can take two weeks or more, before you judge the damage, because rankings often move in both directions mid-rollout. For what a modern core update actually reassesses and how recovery works, see our breakdown of the March 2026 core update. The fix for a core update is never a single tweak. It is a content quality and authority question answered over weeks.
Find the pattern among your biggest losers
This is the step most people skip, and it is the one that produces the real diagnosis. In Search Console, open the Pages report, sort by the largest position decline, and export your top losers. Then look for the common thread. Are they the same content type, the same topic cluster, the same thin template, the same author or no author at all? A cluster of similar pages falling together points at a quality or relevance problem with that kind of content, not a sitewide catastrophe. A single page falling alone points at something specific to that page, a lost link, a competitor that overtook you, or an outdated angle. The pattern is the diagnosis, and you cannot see it without lining the losers up side by side. Compare the pages that held or gained against the ones that fell, because the contrast between them is often where the real answer lives.
Check technical health last
If nothing above explains it, look at technical regressions: a speed cliff after a redesign, broken internal links, mobile usability errors, or a server timing out for crawlers. Page experience is a tiebreaker, not a primary ranking factor, but a real regression can compound a borderline position and push a page that was clinging to the bottom of page one over the edge. See Core Web Vitals and rankings for what actually matters here and what is just noise.
Diagnose first, then act
The discipline is to move top to bottom and refuse to start changing things at random, because random changes destroy the evidence. Most drops resolve at the first two steps. When they do not, this sequence at least tells you whether you are dealing with a tracking artifact, an indexing fault, an algorithmic reassessment, an AI Overview squeeze, or a technical regression, and that tells you whether to wait, rewrite, or repair. Google's own core updates guidance makes the same point: there is usually nothing to fix in a technical sense after a core update, only content to improve. Diagnosis first, changes second, is how you recover rankings instead of gambling with them.