When search metrics change sharply, first check whether the movement reflects traffic or measurement. This record brings together affected periods, metrics and recovery notices from Google’s official help page.
SEARCH CONSOLE / DATA NOTES
The record behind the numbers
Latest affected start date first. Check overlapping periods together.
Official Google source · Content reviewed
MeasurementSeparate logging anomalies from traffic changes
ChangeInterpret retired search features separately
RecoveryOnly label recovery when officially confirmed
- Logging error
Discover metrics undercounted
A logging error reduced recorded Discover clicks and impressions, including generative AI impressions for eligible properties.
Logging only · recovery not specified in the source
- —Data restored
Generative AI search impressions restored
Generative AI search impressions were undercounted; missing data was restored on August 21.
- Logging error
Discover logging error
Discover clicks and impressions, including generative AI impressions for eligible properties, were undercounted.
Logging only · recovery not specified in the source
- Logging error
Discover clicks and impressions undercounted
A logging error reduced recorded Discover clicks and impressions.
Logging only · recovery not specified in the source
- onwardsFeature change
FAQ rich results discontinued
FAQ rich results stopped appearing in Search, reducing impressions in Performance and FAQ rich result reports.
- —Logging error
Two-day Discover logging error
Discover clicks and impressions were undercounted during this period.
Logging only · recovery not specified in the source
- —Logging error
Job search appearance data missing
Job listing and Job details clicks and impressions were not reported.
Logging only · recovery not specified in the source
- —Unrecoverable
Bulk export data cannot be recovered
Two days of bulk export data are missing for some properties and will not be recovered.
- —Error resolved
Impression logging corrected
The April 3 entry covers this affected period. Impressions, CTR and average position were affected; clicks were unaffected. The error is resolved.
How to interpret a reporting change#
- Match the date and report. Search, Discover, search appearance and bulk exports cover different datasets. Check whether the notice applies to your property.
- Separate measurement from feature changes. A logging anomaly alone does not establish a ranking decline or a site outage. Interpret discontinued search features separately.
- Compare other evidence. Review organic visits, server logs and conversions. Different measurement systems need not produce identical totals.
- Annotate comparisons. Record the affected period and source. Revisit earlier exports when Google announces restored data.
How this record is maintained#
The official page is reviewed every 15 days. Only new issues, corrections or recovery notices change this article’s modification date. A check without substantive changes leaves that date unchanged.
Google retains a limited recent history. This page preserves the entries collected here; removal from the source does not establish resolution. This is not a complete history before the first collection, and recovery is never inferred without a notice.
Timeline dates prioritize the affected data period, rather than publication date. Dates without a source timezone are not converted to Korean time. The interpretation steps above are 247COMPASS editorial suggestions, separate from Google’s official notices.
