Google undercounted AI impressions as the core update began

November 9: a logging error that undercounted impressions; November 10: core update started rolling out; November 12: compare forward from November 12

Summary

Google says a logging error undercounted impressions in Search Console's Generative AI report on the days the November core update began rolling out, so the dip in AI impressions over those days is a recording gap.

For the Generative AI report, end any pre-update baseline on November 8 and start the after window on November 12.

Google has confirmed a logging error that undercounted impressions in Search Console’s Generative AI performance report, Search Engine Land reported. The error covers data from November 9 to November 11, and Google’s note says it “affects data logging only,” meaning the impressions happened and were never recorded.

The November 2026 core update started rolling out on November 10, per Search Engine Roundtable, which drops the three buggy days directly on top of the first days of the rollout. Anyone charting AI Mode or AI Overviews impressions before and after the update is reading a decline that Google has already said is a recording problem rather than a change in how often the site appeared.

Google’s note names one report and stops there. It says nothing about the main Search performance report, where impressions and clicks from AI Overviews already land inside the totals. The safer course is to treat the Generative AI breakout for those three days as unusable and the main totals as intact, and to say which of the two a figure came from whenever a stakeholder asks why the numbers disagree.

Search Console carries an annotation on the Generative AI report for the affected dates, so the warning sits on the chart itself and not only on Google’s data anomalies page. Neither Google’s note nor the coverage says whether the missing impressions will be filled back in. A CSV exported this week is worth re-pulling later rather than filing as the record.

What to do

For the Generative AI report, pick a baseline window that ends on November 8 and compare forward from November 12, which keeps the logging error out of the arithmetic. The main Search performance report carries no note for those dates, so its baseline can stay as it was. The rollout had already made the comparison week awkward before the bug landed, so the clean windows on either side are short and worth choosing deliberately.

In any report that already went out covering those dates, add the correction rather than quietly reissuing the chart. The decline is real in the data and not real in the world, and a client who saw the first version will remember the drop.

Nothing needs fixing on the site. Google scoped this to logging, so there is no AI Overviews visibility to win back and no technical change that would have prevented the dip.