Google is deliberately degrading the search results it serves to suspected scrapers, and rank tracking tools are struggling to read the November core update as a result. SEO consultant Glenn Gabe reported on November 11, 2026 that multiple SERP tracking tools may be struggling to report volatility accurately because Google is poisoning the results pages to prevent third-party AI tools from scraping them. The claim, recapped by RankMath on November 17, 2026, explains why the loudest update of the year has produced some of the quietest tracking data.
The day after the November 2026 core update began rolling out, Gabe warned that the volatility numbers coming from tracking tools should not be taken at face value. His argument was that Google has been serving altered or degraded results to automated requests it believes come from scrapers, including the third-party AI tools that harvest Google results to train or feed their own products. A tracker that fetches results through those same channels can end up measuring the poisoned results rather than what real users see.
The context matters. Search Engine Roundtable reported on November 16 that ranking flux and chatter around the core update were unusually muted for a typical core update, even as creators complained about ranking changes and traffic drops. The gap between what trackers showed and what site owners felt is exactly what you would expect if a chunk of tracking data was being polluted at the source.
Google has spent the year fighting to keep its search results from becoming raw material for rival AI products. Its results pages are scraped at enormous scale by tools that repackage the rankings, and by AI companies that use them as training or retrieval data. Serving degraded results to suspected bots is a cheap defence: the scraper gets data it cannot trust, while real users in browsers see the real page.
The tactic is not new, but the timing is pointed. The core update is the moment when every tracker, tool and agency is fetching results at maximum volume, which is also the moment when scraping is hardest to distinguish from legitimate monitoring. Google has not confirmed the poisoning, and it does not comment on anti-abuse measures in general. Gabe\'s report is the public evidence, and the muted tracker data is consistent with it.
The immediate lesson is about how to read this core update. If tracking tools are under-reporting volatility, the update may be bigger than the charts suggest, and the site owners reporting drops may be the better signal. Google\'s own advice already says to wait until the rollout finishes, then wait at least a full week before comparing Search Console data with the week before the update began. That advice is doubly important when the third-party data is unreliable.
The longer lesson is about dependence. An industry that leans on rank trackers for its daily read on Google is exposed whenever Google changes what those trackers can see. Search Console data, server logs and real traffic remain the ground truth, and they are the sources that cannot be poisoned, because they come from your own site rather than from a scraped results page. Trackers that fetch through residential proxies or real browsers may see cleaner data, but those methods are slower and more expensive, which is why most tools do not use them by default.
Watch whether tracking tools acknowledge the problem or adjust their methods, and whether the volatility readings climb as the rollout continues and the tools adapt. Also watch for any statement from Google, though one is unlikely. The practical move for now is to trust your own analytics over any single tracker, and to hold off on big site changes until the rollout ends around November 24 and the clean comparison week is available.
Sources: RankMath, November 17, 2026, recapping Glenn Gabe, November 11, 2026.
Related reading on this site: November Core Update Collides With Black Friday, and a Clean Read Will Not Come Until December, Core Update Volatility Started Days Before Google Announced It, Search Console's Generative AI Report Had a Data Bug During the Core Update, Google Explains How to Find Search Traffic in Analytics and Server Logs, SEJ Pulse: Core Update, ChatGPT Business Hub and AI Mode's New Model, and AI Overview Citations: What 15 Studies Agree On, and Don't.
Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.
Start free trial