Google Confirms Search Console Generative AI Report Bug Nov 9-11
Google confirmed a logging bug that cut impression counts in the Search Console Generative AI report for November 9-11, 2026, overlapping the November core update rollout.

- Google confirmed a logging bug affecting the Generative AI performance report from November 9-11, 2026.
- The bug caused a decrease in impressions but affected data logging only, with no impact on search performance.
- The November 2026 core update began rolling out November 10, 2026, inside the bug window.
- An annotation marking the error is visible inside the Generative AI performance report in Search Console.
Google has confirmed a data logging bug that depressed impression counts in the Search Console Generative AI performance report for November 9 through November 11, 2026. The company posted the issue on its official data anomalies page and stated plainly: "A logging error caused a decrease in impressions on the Generative AI performance report in Search for data from November 9 - November 11, 2026. This issue affects data logging only."
That sentence carries two facts site owners need. First, the scope is narrow: three days, one report, one metric family. Second, the impact is cosmetic. Impressions logged during the window will read lower than reality. Actual rankings, traffic and visibility in Google Search were untouched.
What does the bug actually affect?
Only the Generative AI performance report inside Search Console. This report tracks how sites appear in Google's generative AI surfaces, including AI-driven experiences within Search results. The bug undercounted impressions logged between November 9 and November 11, 2026.
Google has not promised a backfill. The anomaly note does not state whether corrected data will replace the faulty figures, so analysts should treat those three days as unreliable in any month-over-month comparison.
If you log in to Search Console and open the Generative AI performance report now, you will see an annotation marking the error directly on the affected date range. That in-product annotation is the confirmed, Google-authored record of the issue.
How do you separate this from the core update?
Here is the complicating factor. The November 2026 core update began rolling out on November 10, 2026 — squarely inside the bug window. Two events hit the same 72-hour stretch.
This overlap creates a real analytical trap:
- A drop in Generative AI report impressions between November 9 and November 11 is most likely the logging bug, not a ranking change.
- A change in positions, clicks or query-level performance in other Search Console reports during the same window could reflect the core update.
- Comparing the Generative AI report against the standard Performance report for the same dates is the fastest way to isolate cause: the bug affects only the former.
Google's own statement draws the line clearly. "This issue affects data logging only" means the bug changed what was recorded, not what searchers saw. Any genuine ranking movement in that period belongs to the core update, which is a separate and legitimate ranking event.
What should site owners do now?
Three practical steps follow from the confirmed facts. Check the annotation in the Generative AI performance report to confirm your property falls inside the flagged window. Exclude or footnote November 9-11, 2026 impression data from any reporting that uses the Generative AI report as a source. Track the core update independently through the standard Performance report and rank tracking tools, since that rollout began November 10 and operates on its own timeline.
Publishers and SEO teams that build dashboards off Search Console exports should also check whether their pipelines ingested the depressed figures. A three-day dip in an automated alert system could trigger a false alarm about AI-surface visibility.
The forum discussion on X that followed the anomaly posting reflects the same read: site owners noticed the impression decrease, cross-referenced the anomaly page, and confirmed it was reporting-side.
What to monitor next
Watch Google's data anomalies page for any follow-up note on data correction or backfill for the November 9-11 window, and track the November 2026 core update through its full rollout, since ranking effects from a core update typically stabilize over one to two weeks after launch.
via support.google.com (Original)
More from Nathan Brooks
Show full bio
Senior reporter covering companies, deals and strategy in Search rankings and algorithm updates, generative engine optimization at SERP Journal.
211 articles