The briefing
Our thesis: Two Google events now sit on top of each other in your reporting window, and treating them as one signal will lead to the wrong decision. Google has confirmed a logging defect that undercounted impressions in the Generative AI performance report for November 9 to 11, and its November core update began rolling out on November 10 and was still in progress at the November 13 snapshot. A dip in your AI Search impressions during those days may be a recording artifact, a genuine ranking shift, or both at once. The disciplined move is to annotate the interval, keep logged impressions separate from actual traffic and ranking, and resist the urge to diagnose a cause neither source has established.
Quick summary of what is verified:
- Google documents an impressions logging error in the Generative AI performance report for November 9 to 11, 2026. It says this affects data logging only.
- Google has not quantified the undercount and has not said the missing impressions were restored.
- The November 2026 core update began November 10 at 10:06 a.m. US/Pacific and may take up to two weeks to complete.
- The two incidents overlap in time. Neither one alone explains why any dashboard moved.
Google confirms a November 9 to 11 AI Search impressions logging defect
What the sources show: Google's Search Console data anomalies documentation identifies a logging error that reduced reported impressions in the Generative AI performance report in Search for November 9 to 11, 2026, per Google's anomaly documentation. Google states the incident affects data logging only. Search Engine Roundtable reported the issue on November 12 and linked the official document, per Search Engine Roundtable.
The documentation does not quantify how large the undercount was. It does not say the missing November impressions have been restored. An August restoration note appears on the same page, but that note belongs to a separate incident and should not be applied to November.
The confirmed scope is narrow. The cited evidence does not establish an effect on clicks, conversions, revenue, other Search Console reports, or a broad service outage. It concerns reported impressions in one report for three days.
Our read: This is a measurement defect, not a demand signal. If your AI Search impressions look soft across November 9 to 11, the first explanation on the table is that Google recorded fewer than actually occurred. Acting on that number as if it reflected real visibility would compound a recording error into a strategy error.
Two habits matter here. First, keep impressions distinct from clicks and from downstream outcomes. A logging error on impressions tells you nothing, on its own, about whether clicks or conversions changed. Second, mark the affected window in any dashboard a stakeholder reads, so a three-day artifact is not mistaken for a trend. We covered what this report can and cannot measure when it launched in The Search Console Generative AI Report Is Live.
One caution on the restoration question. Because Google has not said the November impressions were restored, you should treat those three days as possibly incomplete until Google updates the document. Do not borrow the August restoration language to assume a fix. That is our interpretation of an undated document, and it should be labeled as such in any internal note.
Google's November core update began November 10 and was still rolling out at the checked snapshot
What the sources show: Google's Search Status Dashboard records the November 2026 core update beginning November 10 at 10:06 a.m. US/Pacific, with the release entry posted at 10:07 a.m., per Google's Search Status Dashboard. The entry states the change applies globally and to all languages and may take up to two weeks to complete. Search Engine Journal reported the launch on November 10, per Search Engine Journal.
The November 13 snapshot contains the launch entry and no completion notice. That supports treating the rollout as ongoing at that point.
The dashboard page does not carry a publisher publication dateline, so it is checked documentation with an explicit event timestamp but no stated publication date. The cited source does not name winners or losers, content targets, rules about AI-generated content, or an effect size.
Our read: A core update that is still rolling out is not a finished measurement. Ranking and traffic can move in both directions during the window, and early movement can reverse before the rollout completes. Reading a mid-rollout position as a settled verdict is a common and expensive mistake.
Because Google gives a possible two-week window, plan your assessment around rollout completion, not around the first days of volatility. Hold major content or technical reactions until you can see a stable post-rollout baseline. Our guidance on reading a turbulent reporting period without overreacting is in Measuring SEO When the Clicks Fall, and the playbook for working a core or spam update window is in The August 2026 Spam Update Just Closed.
The most important point is the overlap itself. The impressions logging defect and the core update share the same calendar. If your AI Search impressions dropped on November 10, you cannot tell from the cited evidence whether the logging error, the core update, both, or neither caused it. The responsible position is to name both possibilities and avoid asserting one.
How the two incidents interact in your reporting
What the sources show: The logging defect covers November 9 to 11, per Google's anomaly documentation. The core update began November 10 and was ongoing at the November 13 snapshot, per Google's Search Status Dashboard. The two windows overlap on November 10 and 11.
Our read: Overlapping incidents create a confounded reporting window. When two plausible causes affect the same days, any single-cause explanation is a guess dressed as a finding.
Practical separation looks like this:
- Treat November 9 to 11 AI Search impressions as potentially understated by the logging defect. Do not read them as demand.
- Treat ranking and traffic movement from November 10 onward as possibly core-update related, but unconfirmed until the rollout completes.
- Cross-check clicks, sessions, and conversions using sources outside the Generative AI report, rather than treating its logged impressions as a proxy for those outcomes. Checking those measures is our recommended diagnostic step, not a claim about how they behaved. The cited evidence says nothing about clicks or conversions.
If you report across channels, this is also a moment to lean on your broader analytics discipline rather than a single Google surface.
Counterarguments and limitations
The strongest objection to our thesis is that careful separation may be overcaution. A traffic change that began well before November 9 needs an explanation outside this overlap. Once the rollout is complete, stable post-rollout data may support a clearer assessment of subsequent changes, though timing alone would not establish the core update as their cause. Our thesis does not forbid conclusions; it forbids premature ones.
The evidence also cannot show several things. It cannot show the size of the impressions undercount, because Google has not quantified it. It cannot show whether the November impressions were restored, because the documentation does not say so, and the August restoration note is a separate incident. It cannot show which sites the core update helped or hurt, because the cited sources name no winners, losers, or effect size. And it cannot show that the logging defect touched clicks, conversions, or any report beyond the Generative AI performance report.
What would change the view: a Google update quantifying the undercount or confirming restoration, a completion notice on the core update, or stable post-rollout data that isolates one cause. Until then, the confounded-window reading stands.
What to do next
- Annotate November 9 to 11 in every dashboard that shows AI Search impressions, with a note that Google confirmed a logging defect for those days.
- Stop reading the Generative AI report impressions for that window as demand. Keep impressions distinct from clicks and conversions.
- Do not assume the November impressions were restored. Recheck Google's anomaly page for a quantified figure or a restoration statement before adjusting any number.
- Mark the core update as ongoing from November 10 and schedule your assessment for after Google posts a completion notice, allowing for the stated two-week window.
- Cross-check clicks, sessions, and conversions from sources outside the Generative AI report to see whether real outcomes moved. Label this as diagnosis, not a finding.
- Hold major content or technical changes until you have a stable post-rollout baseline, so you are not reacting to mid-rollout volatility.
- When you brief leadership, distinguish the affected dates from the rest of November and explain both incidents where their windows overlap. Attribute a change only when the evidence supports it.
Sources and dates
- Data anomalies in Search Console Publication date not shown; checked 2026-11-13
- Google Search Console Generative AI Performance Report Data Bug Nov 9 - 11 2026-11-12
- November 2026 core update - Google Search Status Dashboard Publication date not shown; checked 2026-11-13
- Google's November 2026 Core Update Starts Rolling Out 2026-11-10
