Your Search Console chart falls overnight. The page still loads, and no one has changed it. Should you rewrite the content? First, check Google's data anomalies page. It records known reporting changes and errors that can make a chart dip or rise. Match the report and dates, then decide whether the page itself needs attention.
Here is a recent example. Google's notice for 9–11 November 2026 says a logging error reduced impressions in the Generative AI performance report for Search. Google labels this a data logging only issue. If your chart falls in that window, record the overlap before treating the change as a page problem. A dip alone is not a verdict on the page.
Check the report, not just the shape of the line
Open the anomalies page and find the section for the report you are reading. On 15 November 2026, its Performance reports section held 10 dated notes for 2026. They included issues involving Search results, Discover and Generative AI reporting, as well as one bulk data export gap. Some entries describe changes to what is reported rather than a temporary error. A note for one report does not apply automatically to every Search Console chart.
Write down the property, report name, search type, date range and filters. Then copy the notice's affected dates and metric. For the November example, the metric is impressions in the Generative AI Search report. Google's report help page says this report covers impressions for links shown in AI Overviews and AI Mode. Discover has a separate Generative AI report. Keep those surfaces separate in your notes.
Use complete days where possible. Google's AI report may mark the newest data as preliminary with a dotted line. Its dates use Pacific Time, so a daily view in another tool may have different boundaries. If you filter to one page or device, preserve those filters in your investigation note. An apparent change in the property chart and a page row can also differ because the chart and table group data differently.
What happened to the November data?
Google's 9–11 November entry reports fewer logged impressions. As checked on 15 November 2026, it had no restoration note. Google gives no correction factor for any property or page. Do not fill the gap with an estimate or present it as a measured loss of visibility.
The same page offers two useful precedents. A similar Generative AI Search logging error affected 13–17 August 2026. Google added a 21 August update saying the missing data for that period had been restored and the report showed complete metrics. A different issue left 28 February and 1 March 2026 missing from bulk data exports for some properties; Google says those two days will not be recovered. Restoration is possible, but not automatic. Recheck the notice and the affected report after a few days, then decide what comparison is still valid.
Add a short annotation, then keep a fuller record
Google's Search Console annotations guide says you can open a Performance report, right-click the chart on the affected date, select a date, enter a note of up to 120 characters and click Add. A note for 10 November could read: “Google logging error 9–11 Nov (anomalies page); do not read as page change.” Everyone with access to the property can see annotations, so keep personal or sensitive details out. Only property owners and full users can add or delete annotations; restricted users can view them. Annotations do not appear in comparison mode or 24-hour views.
Google documents this workflow for Performance reports, including the regular Search results Performance chart, but its help text does not explicitly confirm that the Generative AI Search report supports custom annotations. If Add annotation is absent there, keep the report-specific record in your team notes.
| Record | Example for the November issue |
|---|---|
| Report and filters | Generative AI performance report (Search); property, dates, search type, page and device filters recorded |
| Known issue | 9–11 November 2026: Google reports reduced logged impressions; notice checked 15 November |
| Page checks | Live URL, canonical URL and last crawl date from URL Inspection, if a page change is suspected |
| Decision | Hold a chart-driven rewrite; fix a separately observed reader problem if one exists |
| Recheck | Reopen Google's notice and the same report after a few days; retain the original filters |
This table is the longer team record. A chart annotation is a quick pointer to it, not a replacement for report names, filters and source dates.
Use the regular Web report for context, not proof
Google's November notice names the Generative AI performance report in Search. It makes no statement about whether regular Web Search data for those dates was affected. The Generative AI report help page says its data is included in the Web search type in the Performance report (Search results). That does not make the regular Search results chart an independent measurement of AI-feature impressions.
You may still inspect regular Search results performance for wider page context, with the same dates and filters where available. Keep its metrics labelled as Web Search data. If a page also has a live technical problem or fails to answer its promised question, investigate that on its own evidence. Our guide to choosing which SEO page to update helps weigh that work; the Generative AI report walkthrough explains the AI report's scope.
Illustrative example, not site data: A guide's AI impressions appear lower on 10 November than on nearby days. Its reviewer logs the matching Google notice, checks the live URL and canonical, and records the URL Inspection last crawl date. No content issue is found. The decision is to wait for an updated notice and later complete report periods, rather than rewrite the guide because of that single point. If the reviewer later finds a missing answer on the page, that is a separate reason to edit it.
Make this a habit: when a Search Console chart changes, check the data anomalies page before writing a diagnosis. Match the report, date and metric; note whether Google later restored the data; then decide what evidence remains. If you want a place to keep observations, proposed edits and later results separate, use the AI search content audit planner.
When no notice matches your report and dates, the Search Console diagnosis guide offers other checks to try.
Google Search Console Help: data anomalies, Generative AI performance report (Search), Search Console annotations; Google Search Central custom annotations announcement. Reviewed 15 November 2026.
