Google

Search Console's Generative AI Report Had a Data Bug During the Core Update

Google has confirmed a data-logging bug in the Generative AI performance report in Search Console that reduced reported impressions between November 9 and 11, 2026. The bug is a reporting problem only: it does not mean sites actually lost visibility in AI Overviews or in search. The timing, though, could hardly have been worse, because the bad data landed on top of the November 2026 core update, which began rolling out on November 10.

What happened

The Generative AI report is the part of Search Console that shows how a site performs in Google's AI search experiences, including AI Overviews. Between November 9 and 11, a data-logging bug caused the report to undercount impressions, so the numbers site owners saw were lower than the real totals. Google confirmed the bug, and Search Engine Roundtable reported it on November 13, 2026.

The important distinction is between the report and reality. A logging bug changes what gets recorded, not what users see. Google's confirmation is that this was a data issue only, not a real visibility drop. Pages did not lose rankings or disappear from AI Overviews because of this bug; the report simply failed to count some of the impressions that actually happened.

Why the dates made it worse

The bug ran from November 9 to 11, and the November 2026 core update began rolling out on November 10, right in the middle of that window. Core updates move rankings across the web, and site owners watch Search Console closely during a rollout for the first signs of gains or losses. A reporting bug in the same three days means the numbers from that window cannot be read at face value.

That overlap creates a real risk of misreading the update. An SEO who compares impression counts from before the update with counts from November 9 to 11 could conclude that a site lost ground in AI Overviews, when the drop is partly or entirely a counting error. Any analysis of the core update that leans on the Generative AI report for those three days needs a warning label, and ideally the comparison should skip the affected window altogether.

How to read your own data

The practical step is simple: treat November 9 to 11 in the Generative AI report as unreliable. Annotate those dates in Search Console so that anyone looking at the chart later knows the dip is a data problem, not a performance problem. If you need to measure the core update's effect on AI visibility, compare the days before November 9 with the days after November 11, and cross-check against the regular performance report, which was not the subject of this bug.

It is also worth checking whether the dip shows up anywhere else. If the regular search performance report held steady while the Generative AI report fell, that is consistent with a logging problem in one report rather than a real change. If both fell, the core update may have played a part, but the Generative AI numbers for those three days still cannot be trusted as a precise measure of how much.

Why it matters for SEOs and link builders

Citations inside AI Overviews are a new visibility surface, and Search Console's Generative AI report is one of the few official ways to measure it. When that measurement breaks, even for three days, it weakens the evidence base for decisions about which content earns AI citations and which does not. Link builders who track AI citations as a reason to pursue a placement need to know that the numbers they cite from that window are understated.

There is also a broader lesson about trusting a single report during a volatile week. The November core update, the Black Friday season, and a reporting bug all landed within days of each other. The SEOs who will read this period correctly are the ones who check more than one data source before concluding anything, and who wait for the dust to settle before rewriting a content or link strategy on the basis of a three-day dip.

What to watch next

The open question is whether Google will restate the affected data or simply leave the dip in the historical record. Either way, the three-day window is now a known hole in the Generative AI report, and it should be flagged in any reporting that covers November. Watch for any further statement from Google about the bug, and for site owners comparing notes on how large the undercount was for their own sites. Until the data is corrected or the window is excluded from comparisons, the safest reading of November 9 to 11 is that the real impression counts were higher than the report showed.

Sources

Sources: Search Engine Roundtable, November 13, 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, November Search Console Click Spikes May Be Bots, SEJ Reports, SEJ Pulse: Core Update, ChatGPT Business Hub and AI Mode's New Model, AI Overview Citations: What 15 Studies Agree On, and Don't, and Black Friday SEO Starts Eight Weeks Out, and November Is Already Late.

More from Linkbaits

Turn this playbook into links

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