TL;DR Summary:
Impressions Inflated Year-Long: Google revealed a GSC logging error since May 2025 artificially boosted impression data in Performance reports for all sites.Data Correction Underway: Fix rolling out now drops impressions to accurate levels while clicks and other metrics stay unchanged.Export Data Immediately: Grab current inflated numbers via API before corrections to compare and reveal true AI Overview traffic impact.Why are my Google Search Console impressions suddenly dropping?
Google announced on April 3rd, 2026 that a GSC logging error has been inflating impression data since May 13, 2025. This means nearly a full year of your Search Console Performance reports showed higher impression numbers than reality.
The company will fix this issue over the next few weeks. You’ll see your impression counts decrease as Google corrects the data. Clicks and other metrics remain unaffected according to Google’s announcement.
What the GSC logging error means for your data
This GSC logging error affected impression tracking across all websites using Google Search Console. The error started on May 13, 2025 and continued until Google discovered it in early April 2026.
Google stated that only impressions were inflated. Click data, average position, and other Performance report metrics supposedly remained accurate during this period. Your actual search rankings and click-through rates weren’t impacted by this data collection problem.
The fix rollout began immediately after Google’s announcement. You should start seeing more realistic impression numbers appear in your Performance reports within the coming weeks.
How this GSC logging error affects the Great Decoupling
SEO professionals have watched a troubling pattern called “The Great Decoupling” since AI Overviews launched. This pattern shows impressions climbing while clicks drop, creating graphs that look like alligator mouths opening wide.
Many attributed this alligator trending to AI Overviews answering user questions directly in search results. Users got their answers without clicking through to websites. This seemed to explain why impressions surged as clicks fell.
Now we know the GSC logging error was inflating those impression numbers. The real question becomes: how much of that alligator trending was genuine user behavior versus inflated data? Were AI Overviews actually hurting click-through rates as severely as the data suggested?
You’ll get answers soon. As Google fixes the logging error, you might see that alligator mouth closing. Impressions should drop closer to realistic levels, showing the true impact of AI Overviews on your traffic.
Why other metrics might be affected despite Google’s claims
Google insists that click-through rate and average position weren’t affected by the logging error. This claim raises questions about how the error actually worked.
Click-through rate calculates using impressions divided by clicks. If impressions were inflated but clicks stayed accurate, your CTR percentages would appear artificially low. When Google corrects the impression data, your CTR should improve automatically.
Average position depends on when your content appeared in search results and received impressions. If the system logged fake impressions, those phantom appearances could have influenced position calculations. The math doesn’t add up for these metrics to remain completely unaffected.
You’ll discover the real impact once Google completes the data correction. Compare your metrics before and after the fix to understand what actually changed.
Export your GSC data before the correction
Every website owner should export their current Google Search Console data immediately. This gives you a complete record of the inflated numbers before Google applies corrections.
The standard GSC interface limits exports to 1000 rows. For complete data extraction, you need to use the Search Console API. Tools like Analytics Edge can bulk export your Performance data without row limitations.
Once you have your pre-correction data exported, you can compare it against the corrected numbers. This comparison will show you exactly how much the GSC logging error inflated your impression counts.
Publytics automatically captures and preserves your GSC data continuously, giving you clean historical baselines without manual exports. This automated preservation becomes essential when major data corrections like this occur, ensuring you maintain accurate records for comparison against post-correction metrics. You can track your analytics data with confidence using Publytics to understand the true impact of this logging error on your website performance.
