Search Console AI Report Bug Overlaps the November 10 Core Update

Updated November 12, 2026 · first published November 12, 2026

Google's Search Console data anomalies page says a logging error decreased impressions in the Generative AI performance report for data from November 9 to November 11, 2026. The November 2026 core update began rolling out on November 10. If your AI-search impressions fell in that window, do not attribute the dip to the update yet.

What Google has published

Two separate Google notices cover the same three days. They describe different things and should not be merged into one story.

Reporting error. Google's Data anomalies in Search Console page lists "November 9 - November 11 (Generative AI in Search)": a logging error caused a decrease in impressions on the Generative AI performance report in Search for that period. Google says the issue affects data logging only. When we read the page on November 12, the entry did not say whether the issue was resolved or whether data would be restored.
Ranking update. Google's Search Status Dashboard lists the November 2026 core update under Ranking, dated November 10, 2026. Search Engine Journal reports a 10:06 a.m. PT start and a rollout that "may take up to 2 weeks to complete", attributed to the dashboard. The dashboard page we fetched did not itself show a duration, so treat the two-week figure as secondhand.

Why the overlap is a measurement trap

A real ranking change and a logging error both show up as a step down in impressions. The logging error is documented as lowering impressions in one report; the core update can move rankings in the standard Search results report. They can occur on the same days, and a single sitewide AI-impressions chart cannot separate them.

The practical risk is a wrong decision: rewriting pages, pausing content or reporting a loss to finance based on three days of data that Google has already labelled as undercounted.

What to do this week

Mark November 9–11 as suspect in any dashboard or export that uses the Generative AI report. Annotate it with a link to the anomalies page rather than deleting the days.
Do not compare against the core update yet. Google's core update guidance says to wait until the rollout finishes and then at least a full week before comparing Search Console data with an earlier period. For this update the baseline is the week before November 10. These are Google's recommendations for core updates in general, summarised by Search Engine Journal for this rollout.
Check the standard Search results report separately. A fall in clicks there is not explained by an AI-report logging error, so it is the better place to look for ranking effects.
Re-pull the data later. Google's August 2026 anomaly entry for the same report carried a note that data was restored. If the same happens here, numbers exported today will be stale. Record the export date next to every figure you save.
Hold finance-facing conclusions. Report the window as "under-reported by a logged error", not as a loss.

The wider lesson for AI-visibility metrics

This is the second logging error in this report's short life, and AI-search visibility is a young, vendor-reported metric. Treat it the way you would treat a metered cost line: keep the raw export, note the pull date, and reconcile against a second source before acting. Our earlier guide to a Google traffic drop overnight covers separating a reporting issue from a real loss, and Google's October 15 AI Search changes covers what is and is not yet measured about AI link changes.

What we have not verified

We have not seen Google state the size of the undercount, whether it affects every site equally, or whether the data will be restored. We also have no measured impact of the November core update on any site. This article will be updated if Google revises either notice. Some news summaries also mention new Search Console platform-property support and multi-select filters; we could not confirm those on Google's own pages, so we do not cover them here.

Frequently asked questions

Did a bug affect Search Console's Generative AI report in November 2026?

Yes. Google's data anomalies page says a logging error decreased impressions in the Generative AI performance report in Search for data from November 9 to November 11, 2026, and that it affects data logging only. When checked on November 12 it did not say whether data would be restored.

When did the November 2026 core update start?

Google's Search Status Dashboard dates it November 10, 2026. Search Engine Journal reports a 10:06 a.m. PT start and a rollout that may take up to two weeks.

Is my AI impressions drop caused by the core update?

Not provably yet. The three-day window overlaps a documented logging error that lowers impressions in that report. Wait for the rollout to finish, then follow Google's guidance to compare a full week afterwards with the week before November 10, and check the standard Search results report separately.

How should I handle the affected days in reports?

Keep the raw numbers, mark November 9 to 11 as suspect with a link to Google's anomalies page, record the export date, and re-pull the data later in case Google restores it.

Want this applied to your stack? Bring the provider bills, gateway logs, and top workflows; we will map the cost drivers and savings path. Book a free audit →

Back to finopsllm.com