Your AI Search Numbers Dropped This Week? Google Says It Was a Reporting Bug, Not Your Rankings
If you checked how often your business appears in Google’s AI answers this week and the numbers fell off a cliff — stop. Google has confirmed it was a bug in its own reporting, not a drop in your rankings.
Google has added a note to its Search Console data anomalies page confirming that a logging error reduced the impressions shown in the Generative AI performance report for three days: November 9, 10 and 11, 2026.
What exactly happened?
Google’s own words: “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.”
In plain terms: Google’s system stopped counting some of your appearances properly. Your business was still being shown in AI answers — the counter was broken, not your visibility.
Search Console now shows an annotation on the report marking the error, so anyone looking at those dates can see the dip was a known fault.
Why this one is so easy to misread
The timing could hardly be worse. Google’s November 2026 core update started rolling out on November 10 — right in the middle of the three buggy days.
So an owner checking their numbers this week sees two things at once: a big update rolling out, and their AI-search impressions falling. The natural conclusion is “the update hit me.” For the November 9–11 window in the Generative AI report, that conclusion is wrong. The dip there is the logging error.
Real core-update effects are a separate question, and the update is still rolling out — Google said it may take up to two weeks, so it is too early to judge its real impact on any business.
What should you do?
- Ignore the November 9–11 dip in the Generative AI report. Do not make decisions from those three days of data. They are faulty, and Google has said so itself.
- Do not change your website because of it. No rewrites, no panicked edits, no new pages built to “fix” a drop that never happened. Changing a site mid-update because of a reporting bug creates real problems out of an imaginary one.
- Wait for the core update to finish before judging anything. Compare your numbers after the rollout completes against the period before it started — skipping the faulty November 9–11 window entirely.
- Judge by enquiries, not one report. Calls, messages and bookings are real. A three-day dip in one AI report, during a confirmed logging error, is not.
The honest summary
Your rankings did not drop on November 9–11. Google’s counting did. The annotation is now on the report, the error is acknowledged, and the only sensible move is to leave those three days out of any decision and let the core update finish rolling out before you read anything into your numbers.
Questions people ask
Did my business lose visibility in Google’s AI answers this week?
No. Google confirmed the drop was a logging error in the report itself. It affected the data shown for November 9–11, 2026 — not your actual appearances in AI answers.
Is this the November core update hurting my site?
Not this dip. The core update started on November 10, in the same window, which is why the two are easy to confuse. Any real update effect can only be judged after the rollout finishes, using data outside the faulty window.
Will Google fix the missing data?
Google’s note says the issue affected data logging only, and it has placed an annotation on the report. It has not said the missing impressions will be backfilled, so treat November 9–11 in that report as a gap, not a true reading.
Should I report this to Google or change anything in Search Console?
No action is needed. There is nothing to fix on your side — the fault was in Google’s logging, and it is already recorded on the report.
