Your Rank Tracker Says You Tanked? Check Search Console Before You Panic
Analytics
Step-by-step
Rank tracker drop
Trigger Marketing
The Trigger team
⊹
Monday morning. You open your rank tracker. Your best page fell off a cliff overnight. Your stomach falls with it.
Before you call your web person, your mom, or a priest: check whether that drop is even real.
Since September 2026, Google has been showing rank-tracking tools broken result pages. Kasra Dash broke it down on Oct 29, 2026. Here's what's going on and the 4-step check that tells you what's real.
Quick words (one line each):
Rank tracker: a paid tool (Ahrefs, Semrush and friends) that searches Google for your keywords and records where you show up.
SERP: "search engine results page," the page of results you see after a search.
Google Search Console: Google's free dashboard built from real searches by real people.
Average position: where your page shows up on average for a search, in Search Console.
API: a way for software to pull data straight from a service, no clicking.
What's actually happening
Rank trackers check Google by running searches automatically. Google is now handing many of those searches a different set of results than real people get (0:00:00).
What the trackers see: result pages where most normal sites are missing and the gaps are filled with Facebook, Instagram and YouTube. People call it "SERP poisoning" (0:01:20-0:01:40).
The numbers, as Kasra reports them:
Nozzle: under 1% of result pages looked like this before September, about 1 in 5 since, and close to half on the worst days (0:01:20-0:01:40).
Ahrefs: says 5-20% of results are affected (0:02:00).
Semrush: calls it industry-wide. AccuRanker, SE Ranking, Sistrix and BrightLocal have posted about it too. Google has said nothing (0:02:00).
Translation: your tracker is reading a funhouse mirror. Search Console reads the real thing.
Step 1: Compare in Search Console
Open Google Search Console and pick your site.
Click Performance.
Set the date range to the last 3 months.
Click Compare and choose previous period (0:03:00-0:03:20).
Now you're looking at Google's own data, from real searches.
Step 2: Check the page that "dropped"
Click the Pages tab.
Click the page your tracker says tanked.
Click the Queries tab.
Look at average position for its main searches. If it barely moved, the tracker drop isn't real (0:03:20-0:03:40). Breathe out.
Step 3: Export it
Click Export and pick CSV or Google Sheets (0:03:40).
Heads up: the tables only show 1,000 rows. On a big site, go page by page instead of exporting everything at once.
Step 4: Let AI build the report
Upload that export to ChatGPT or Claude and ask it to:
Build a table of each search with its position now vs before.
Flag only the real drops.
Write a short, plain summary you can send a client or your boss.
That's Kasra's workflow (0:04:00). Ten minutes instead of an afternoon.
Step 5: Got lots of sites? Automate it
The Search Console API pulls up to 25,000 rows at a time, and it runs on a schedule (0:04:20-0:04:40). No exports, no row limit headaches.
The friendliest way in: our guide to search-console-mcp, a free tool that lets an AI assistant read your Search Console for you (link below).
The new reporting rule
Until this settles, treat Ahrefs and Semrush rankings as estimates (0:04:20-0:04:40). Never send a "rankings dropped" message based on a tracker alone. Search Console first, page by page, every time.
Do this today
Open Search Console, Performance, last 3 months, Compare to previous period.
Check your top 5 pages: Pages tab, then Queries.
Write down which "drops" are real and which aren't.
Add one line to your reports: "Rankings source: Google Search Console."
Stop panicking at tracker emails. Check first.
Related reading
Sources
Don't worry if this seems like it's a pain in the ass for someone who doesn't build websites. That's because it is. The good news: just click the link below, pull the trigger, and we'll take care of the rest.
Share This Article
