Why your rankings dropped, and how to tell if it matters

A ranking drop produces a specific kind of panic, and the panic produces bad decisions: rewriting pages that were fine, buying links to plug a hole that was never about links, or switching agencies over something that would have recovered on its own. The causes are countable and they have almost nothing in common, so the first job is diagnosis, in an order that rules things out cheaply before touching anything expensive.

First, establish it is real

A surprising share of reported drops are measurement artifacts.

Check the traffic, not the rank tracker. Rank trackers sample from one location, one device, one moment. If your tracker shows a fall but organic traffic and enquiries are flat, the drop may exist only in the tracker’s viewpoint. Search Console’s average position is a better witness because it averages across every real impression.

Check for a tracking break before a ranking break. A consent banner update, a Tag Manager change, a new subdomain: any of these can cut reported traffic while the actual visits continue. If sessions fell but Search Console impressions and clicks did not, your rankings are fine and your analytics are broken.

Separate one page from the site. A sitewide slide and a single page’s collapse are different diseases. Pull the pages that lost the most clicks in Search Console and see whether the loss is concentrated or smeared everywhere.

Then check the boring mechanical causes

These account for more real drops than anything algorithmic, and they are all self-inflicted.

Somebody changed the page. A rewrite, a new template, a heading restructure, a URL change without a redirect. Check the page’s history against the drop date. This is the most common cause of a single-page collapse and the easiest to reverse.

Somebody changed the site. A migration, a new theme, a plugin update that altered rendering, a robots.txt edit, a noindex tag that escaped from staging. The staging-noindex-in-production mistake alone has erased more rankings than most algorithm updates.

The page stopped being crawlable or fast. Server errors, a lapsed certificate, a hosting move, a Core Web Vitals regression from a new script. Search Console’s crawl stats and page experience reports show most of this directly.

Then look outward

An algorithm update landed. Check the drop date against the documented update history. If they align, look at what else moved: updates reorder categories of sites, so identify what now ranks above you and what those pages have in common. Recovery from a core update is usually about overall quality and rarely about one tweak, and the worst response is thrashing: making rapid changes you cannot evaluate because the update is still rolling out.

A competitor got better. Rankings are relative. Sometimes nothing happened to you at all: someone else published a genuinely better page, earned real links, or restructured their site. If your position fell one or two spots while your page stayed identical, look at who moved up before assuming you did something wrong.

The results page itself changed. An AI Overview, a map pack, a video carousel or more ads can push the same organic position further down the page and cut its clicks in half. Your rank did not drop; the real estate did. This shows up as stable position with falling click-through rate in Search Console, and the response is a strategy question, not a fix.

How to tell whether it matters

Not every drop deserves a response. Three questions sort the urgent from the ignorable:

1. Did clicks fall on pages that produce enquiries or revenue? A drop on a blog post that never converted anyone is a curiosity. A drop on a money page is a priority.
2. Is it stabilising or accelerating? Look at a two-week trend, not a two-day one. Positions oscillate constantly; trends are what carry information.
3. Did impressions fall too, or only clicks? Falling clicks with stable impressions points at the results page changing around you. Falling impressions points at an actual visibility loss.

What not to do

Do not rewrite the page the day of the drop. Do not buy links in a hurry. Do not change URLs. Do not deploy three fixes at once, because if it recovers you will not know why, and if it does not you will have three new suspects. Diagnose first, change one thing, and give it time to register.

If the drop is on pages that pay your bills and the cause is not obvious from the checks above, that is the point where an outside audit earns its fee: not because the steps are secret, but because the person running them is not emotionally invested in any particular answer.