Categories SEO & Blogging

Google’s November Core Update Can’t Be Measured Properly

Google started its November 2026 core update on November 10, and if you run a website, this is the worst possible week to trust your rank tracker. Since mid-September, Google has been handing automated tools complete-looking results pages with the wrong websites on them — and the industry’s best measurement puts the problem at its worst just days before the update began. Your tracker might be telling you that you lost half your rankings. It might be lying.

Here’s the short version: the update is real, it started November 10 at about 1:07 p.m. ET, and Google says the rollout may take up to two weeks, which puts the finish around November 24 — right on top of Black Friday. But the numbers most site owners use to judge an update are compromised right now, and the only honest way to read this rollout is to check your own traffic first and your tracker second.

What “poisoned SERPs” actually means

A poisoned SERP is a full Google results page, served to a request Google suspects is a bot, with most of the usual organic results swapped out for other sites. Nothing on the page gives the swap away. It has the normal layout, the ads are in place, and if it’s an AI Overview query, that shows up too. The tracker saves it as the truth.

Rank tracker Nozzle, run by Derek Perkins, has published the most detailed numbers on this — its full study is worth reading if you want the methodology behind the figures below (Serpwatch’s summary of the year Google broke the rank tracker lays out the timeline clearly). Its study judged 42.5 million results pages, keyword by keyword, across 58 countries, from August 20 to November 3, 2026. Nozzle calls a page poisoned when fewer than half of a keyword’s usual sites show up on it. The findings, updated November 3, are stark:

  • Page 1 alone was poisoned on 15.0% of SERPs since September 13, against 0.17% before that date. The worst day for page 1 was October 27, at 34.8%.
  • Counting pages 1 and 2 together, 27.6% of judged SERPs had a poisoned page since September 13, against 0.28% before. The worst day overall was November 2, at 68.6%.
  • On a poisoned page, a tracked site was missing from the top 10 in 63.7% of cases, against 2.6% in normal conditions.
  • The good news, such as it is: 45.1% of poisoned SERPs had their usual sites back within three days, and 89.0% within two weeks.

The timeline matters. Bulk request failures started on September 13. The first altered pages arrived on September 20. On October 12, Search Engine Roundtable reported Nozzle’s early finding that 8.0% of SERPs were coming back poisoned. By November 2 — eight days before the core update started — the figure had climbed to 68.6% on the two-page measure. The poisoning didn’t start with the update. The update just walked into the middle of it.

Why Google is doing this (probably)

Google has not said a word about the poisoning in public. Its only comment came through a spokesperson, who told Search Engine Roundtable the company has “a long history of deploying technical measures against evolving forms of abuse.” That’s it. No blog post, no dashboard note, no denial.

The common theory, repeated by Semrush, Nozzle and Search Engine Roundtable, is that Google is fighting bulk scraping — companies pulling Google’s results at scale to train AI systems — and rank trackers got caught in the middle. That theory fits the mechanics: the swapped pages only show up for automated requests, and Nozzle says it hasn’t seen evidence of poisoning in logged-in results, which makes a manual check the closest thing to a clean reference right now.

There’s a second wrinkle that makes the timing worse. Derek Perkins put it plainly: “each SERP will have hundreds of links to decode.” By his count, resolving one five-page ranking now takes 500 to 1,000 requests. Google spent 2026 making automated collection slower, costlier and legally riskier — and it lost in court twice while doing it. A federal judge granted a motion to dismiss Google’s amended complaint in one scraping case on November 10, the same day the core update started.

Semrush, Ahrefs and AccuRanker have all acknowledged the poisoning problem publicly. Nozzle says it re-collects a suspect keyword up to five times through different proxy networks and keeps the raw HTML of every SERP. Other vendors say they now filter out the bulk of the bad pages. But filtering is not the same as clean data, and every vendor is filtering a different way.

The trackers can’t even agree with each other

Here’s the part that should stop you from acting on any single tool’s chart this week: on day one of the core update, Ahrefs and Semrush split. Their volatility readings disagreed about how much the update was even moving rankings. That’s not a small footnote. When two of the biggest measurement tools in SEO disagree on whether the ground is shaking, the honest conclusion is that neither reading is reliable on its own.

Glenn Gabe ran numbers for roughly 1,000 sites across a few verticals on November 11 and reported his own read — but even his check is a tracker-based sample, and he has been careful to frame Search Console as the source of truth for now. The disagreement between the big tools isn’t a bug in one of them. It’s the expected result when the underlying data source is serving different pages to different robots.

What the update itself is doing

Strip away the measurement problem and the update looks, so far, like a normal core update with unusually bad timing. Google described it on its Search Status Dashboard as a regular update designed to surface relevant, satisfying content, and said the rollout “may take up to two weeks to complete.” It’s the third core update of 2026 and the first since May. It applies globally, in all languages and to all types of sites.

The chatter was muted through the first workweek and only picked up on Saturday, November 14, which suggests the update began taking visible effect three or four days after its announcement. Search Engine Roundtable’s November 16 report (Google November 2026 Core Update Ranking Volatility) collected commenters at both ends — from a 10% weekend gain to a fall of more than 20% week over week — and noted that the tools, in aggregate, also showed more volatility on Saturday, November 14, than on other days.

The properties reported hit this week include a gaming and entertainment news site in Brazil and e-commerce, news and YMYL sites in the forum chatter. One pattern keeps showing up in the reports: commercial category pages giving way to the site’s own informational articles. That’s a real signal, but it’s also exactly the kind of pattern that looks different depending on which tool you ask.

And the self-reports are genuinely mixed. One site owner of a shop and a news site reported a large drop on November 10. Another reported a minor uptick. A travel site saw better traffic but poor conversions. A gaming news site told Reddit its Search clicks fell from about 80,000 a day to 3,000. A recipe site lost most of its Discover clicks in 24 hours. Others report a slight gain or no change at all.

The most concrete self-report I’ve seen comes from a Brazilian gaming and pop-culture news site that posted on r/SEO: its analytics fell from roughly 94,000 pageviews on November 10 to 66,000 on November 11, 23,000 on November 12, and 16,000 on November 13 — an 83% drop in three days, with Search Console clicks and impressions falling sharply in the same window. That one is worth taking seriously, because both the site’s own analytics and Search Console moved together. When your own numbers and Google’s own numbers agree, that’s a real drop.

But notice what that example proves: it proves the drop by using two sources that agree. A single tracker chart proves nothing right now.

Search Console has its own problems this week

If rank trackers are compromised, the natural move is to fall back on Search Console — Google’s own data, straight from the source. And that’s the right instinct. But even Search Console has a blemish on it this exact week.

Google confirmed a logging error that lowered impressions in Search Console’s Generative AI performance report for November 9 to 11 — precisely the window in which the update started. If you run AI Overviews or AI Mode reports, your numbers for those three days are understated, and Google has said so.

There was also unexplained click-spike activity on November 3, which commentators suspected was bot traffic or a bug, and Search Console started counting robot clicks in the same fortnight the trackers went bad. So the “before” week that everyone will compare against contains bot clicks in Search Console and swapped pages in rank trackers. The baseline itself is dirty.

None of this makes Search Console useless. It is still the best single source you have, because it measures what Google actually served to real users, not what it served to a robot. But it does mean you should read it with the same skepticism you’d apply to anything else this month: check the Search Console data against your own server logs and analytics before you conclude anything.

Google actually helped with that on November 12, publishing documentation explaining how to identify Google Search traffic in your own server logs using the HTTP Referer header. That’s a useful, concrete step, and it’s the kind of thing worth doing this week if you haven’t before.

The honest-measurement framework for this update

So how do you actually judge whether this core update helped or hurt your site? Here’s the framework I’d use, built from what Nozzle, Glenn Gabe and the trade press are all saying in different words:

1. Count your own visits first. Your analytics and your server logs are the one count no tracker and no processing queue can corrupt. Before you touch a single page, check whether your actual Google-referred sessions moved. A real drop looks like both your own measurements and Search Console moving together. A tracker-only drop is a hypothesis, not a fact.

2. Compare the right weeks. Compare the week before the update (November 3–9) with the week after it finishes (after ~November 24), not day-to-day during the rollout. Rankings can keep moving until the rollout closes, and the “before” week is already noisy. Daily comparisons during a live rollout are mostly noise.

3. Sort pages by the change in clicks, not by rank. In Search Console, sort your pages by the change in clicks between the two weeks. The pages that lost the most clicks are the ones to read first — after the update closes. The advice in the Reddit threads matches Google’s own guidance here: compare the week before and after, sort pages by the change in clicks, and check Discover separately.

4. Check Discover separately. Discover traffic behaves differently from Search traffic, and at least one recipe site lost most of its Discover clicks in a single day during this rollout. Don’t let a Discover swing masquerade as a Search ranking change.

5. Ask your tool provider four questions. Nozzle suggests asking whichever tool you pay for: how do you detect poisoned SERPs, how do you re-collect them, do you keep the raw HTML, and how do you flag the uncertainty in your reports? If your vendor can’t answer, that’s information too.

6. Wait for the 45% to self-correct. Remember that 45.1% of poisoned SERPs had their usual sites back within three days, and 89.0% within two weeks. A ranking that vanishes on Monday and returns on Thursday was probably never a ranking change at all. It was a bad page served to a robot.

What not to do this week

Do not rewrite your best pages because a tracker says they dropped. Do not delete content, change titles en masse, or “fix” pages that were ranking fine last week. During a live rollout, a red line in your rank tracker is a statement about a page Google served a robot. It is not a statement about your visitors.

Do not announce a verdict on the update, either. Nobody has data on which sites won or lost yet — one review of 51 pages about the update found that 61% sell SEO services or audits, 59% carry advice or claims with no source, and none has data on winners and losers. The first clean post-update data week won’t exist until early December, and the rollout runs straight into Thanksgiving, Black Friday and Cyber Monday, which will distort every traffic comparison anyway.

And do not panic about the AI-content angle. When one commenter in the Reddit threads said Google is cracking down on AI content, the top reply asked for a source. There isn’t one. The update is a broad core update, not a content-type crackdown, and the sites reporting drops include plenty of human-written pages.

What this means for the future of SEO measurement

Step back from this one update and the bigger story is hard to miss: 2026 is the year Google broke the rank tracker. Three core updates, four spam updates, a court fight over scraping that Google keeps losing, and a Search Console that started counting robot clicks in the same fortnight the trackers went bad. The tools didn’t get worse. The ground underneath them changed.

That doesn’t mean rank trackers are dead. It means they’re a secondary signal now, not a primary one. The primary signals are your own analytics, your server logs, and Search Console — in that order, and only when at least two of them agree. If you’re a small publisher or a blogger, that shift actually favors you: you don’t need an expensive tracker to know whether your traffic moved. You need your own numbers and the discipline to wait.

My bet is that the vendors who survive this are the ones who start showing their uncertainty — flagging suspect keywords, publishing their re-collection rates, and admitting when a reading is weak. Nozzle is already doing some of that. The ones who keep publishing clean-looking charts built on poisoned data will lose trust fast, because site owners can now check the charts against their own traffic and see the gap.

For this update specifically, the practical advice is boring and it’s correct: change nothing yet, note the pages that lost clicks, and read them after the update closes around November 24. If you want the week-by-week action plan for the rollout itself, our earlier piece on this update — Google November Core Update: Still Rolling, What to Do — covers the steps in order. And if search traffic is your income, it’s worth knowing how the money side works too: Google AdSense Approval Requirements 2026 walks through what Google actually checks before it pays you.

The update will finish. The trackers will get cleaner, or they won’t. Either way, the sites that come out of this in the best shape will be the ones that measured the right thing and waited before they acted.

Frequently Asked Questions

Is Google really serving fake results to rank trackers?

Google hasn’t confirmed it publicly, and its only comment was a spokesperson telling Search Engine Roundtable that the company has “a long history of deploying technical measures against evolving forms of abuse.” The evidence comes from vendor data: Nozzle judged 42.5 million SERPs and found page 1 poisoned on 15.0% of them since September 13, 2026, against 0.17% before. Semrush, Ahrefs and AccuRanker have all acknowledged the problem.

How do I know if my site was actually hit by the November 2026 core update?

Check your own analytics and Search Console together. A real hit looks like both moving in the same direction over the same days — for example, the Brazilian gaming site that fell from 94,000 pageviews to 16,000 in three days while its Search Console clicks dropped in parallel. A drop that shows up only in a rank tracker, with your own traffic flat, is most likely a poisoned reading.

When does the November 2026 core update finish?

Google said the rollout, which started November 10, 2026, may take up to two weeks to complete, which puts the finish around November 24. Rankings can keep moving until it closes, so don’t judge the outcome before then — and the Thanksgiving and Black Friday week will distort traffic comparisons anyway.

Why do Ahrefs and Semrush disagree about this update?

Because they’re reading different poisoned data. Since mid-September, Google has served automated requests normal-looking pages with the usual sites swapped out, and each vendor detects and filters those pages differently. When the underlying data is corrupted, two honest tools can produce two different volatility readings from the same update.

Is Search Console reliable during this update?

Mostly, yes — it’s Google’s own data about real users, not robot-served pages, so it’s the safest single source. But it has two blemishes this week: Google confirmed a logging error that understated impressions in the Generative AI performance report for November 9–11, and Search Console started counting robot clicks around the same time the trackers went bad. Cross-check it against your own server logs before concluding anything.

Should I change my content because of this core update?

Not yet. Wait until the rollout closes around November 24, then compare the week before the update with the week after, sort your pages by the change in clicks, and read the biggest losers first. Changing pages mid-rollout based on tracker data is the most common mistake site owners make during core updates — and this time the tracker data is measurably unreliable.

Leave a Reply

Your email address will not be published. Required fields are marked *