How to Read the Generative AI Report During a Core Update

Publishers reading the Generative AI report this week can separate a confirmed Search Console logging error from the November 2026 core update and a test of where AI Overview sources sit. You will learn which impression dip to ignore, what still belongs in the main Performance report, and how to spot bottom-of-overview source icons before you brief leadership. The bug window sits inside the update, so the two can look like one event.

Updated November 13, 2026

What should you ignore in the Generative AI report?

Google’s data anomalies page says a logging error caused a decrease in impressions on the Generative AI performance report in Search for 9–11 November 2026. The notice states, “This issue affects data logging only.” Search Engine Roundtable reported an annotation on the report and wrote that this “is just a reporting bug and had no impact on your performance in Google Search.”

Before you brief, set aside:

• Impression totals for 9, 10, and 11 November 2026 in that report.
• Comparisons that treat those three days as complete generative data.
• Any line that calls the dip lost AI visibility.

The core update started on 10 November, inside that window. The annotation is not evidence the update cut generative impressions. Google restored missing data for an earlier Generative AI logging error, 13–17 August 2026. It has not said the November impressions are back.

What should you compare in the main Performance report?

Judge whether Search visibility moved in the Search Console Performance report. This anomaly is a logging error on Generative AI impressions. Search Engine Roundtable said it had no impact on your performance in Google Search. The November 2026 core update began on 10 November 2026 at around 1:07 pm ET. Google wrote that the rollout “may take up to 2 weeks to complete.”

Google called it “a regular update designed to better surface relevant, satisfying content for searchers from all types of sites.” Search Engine Roundtable adds that it is global, not a penalty, and that core updates also affect Discover and feature snippets. Across 23 confirmed updates, it put the median rollout at 14 days; March 2024 ran 45.

A Performance-report move that continues after 11 November fits the update. A dip only in the Generative AI report on those dates is not a visibility loss.

How do you spot bottom-of-overview source icons?

Search Engine Roundtable reported a test that places source icons at the bottom of AI Overviews, not the top. That may make sources harder to find and could reduce clicks further. Brodie Clark wrote that referenced sites sit “at the bottom of the response” and that “hovering displays the full list of citations.”

• Check the bottom of an AI Overview, not only the top.
• Hover the site count; this test shows the full citation list.

Search Engine Roundtable asked why Google would move these source links to the bottom when it will result in even fewer clicks. Keep that question in a citation-to-click audit. The layout is a test, not a confirmed switch.

What should you check before you brief leadership?

1. Confirm the annotation, then exclude 9–11 November impressions from any visibility-fell claim.
2. State the 10 November start, up to two weeks, all site types, and the regular-update wording.
3. Read the Performance report outside that window. Core updates can also move Discover and feature snippets.
4. Flag bottom source icons as a spotted test, not a global switch.
5. Do not promise a data restore or a recovery date.

If the Performance report is still down after 11 November, review content against Google’s core-update advice. Search Engine Roundtable notes later refreshes may not be announced. Keep longer referral questions, such as Reddit search referrals after Google’s AI shift, outside this chart.