Google Confirms 11-Month Bug in GSC Impression Data

Data integrity is the bedrock of search engine marketing, yet even the most established tools are susceptible to technical failure.

On April 3, 2026, Google disclosed a significant logging error within Google Search Console (GSC) that caused the platform to over-report impression data for nearly a year.

Starting on May 13, 2025, and persisting until the fix began its rollout in April 2026, this anomaly inflated visibility metrics for millions of domains globally. While click data remained accurate, the artificial inflation of impressions fundamentally skewed historical performance baselines and conversion rate calculations.

This revelation requires an immediate audit of organic performance reports from the last year. 

This guide deconstructs the logging anomaly in GSC impression data and outlines the necessary steps to recalibrate your search reporting.

What is the 11-Month Logging Anomaly in Google Search Console?

The GSC logging error represents one of the longest-running data discrepancies in the platform’s history.

For 325 days, Google Search Console recorded search impressions at an elevated rate that did not reflect actual user behaviour. An impression occurs whenever a URL appears in a search result for a user, regardless of whether they scroll it into view (except for specific cases like image search).

The bug specifically impacted the internal logging mechanism that counts these occurrences. Because the error only affected the “Impression” metric, core interaction data, such as total clicks and average position, remained valid.

However, the sheer duration of the bug means that year-on-year (YoY) and month-on-month (MoM) comparisons are now technically compromised.

As Google deploys the fix, many site owners will observe a sharp decline in reported impressions. This drop is not a loss of visibility; it’s a correction to reality.

How Overreporting GSC Impressions Data Impacts CTR and Visibility Benchmarks

The primary casualty of the impression bug is the click-through rate (CTR).

Since CTR is a derived metric calculated by dividing clicks by impressions (CTR = clicks ÷  impressions), any inflation in the denominator causes an artificial deflation of the final percentage.

1. Deflated CTR Performance

Throughout the 11-month anomaly, your reported CTR was likely lower than the actual performance of your content. If you optimised meta titles or descriptions based on these deflated figures, you may have been reacting to skewed data.

As the fix takes hold and impression counts normalise (decrease), your CTR will likely improve overnight, even if your search presence remains static.

According to CXL, a good CTR is when the average is over 6.64% for search and 0.57% for display across all industries. This can be calculated by multiplying the CTR by 100 (CTR = (clicks ÷  impressions) x 100).

2. Skewed Share of Voice (SoV) Calculations

Many agencies use GSC impressions as a proxy for organic share of voice within a specific niche.

Because the overreporting likely varied depending on the type of search feature (e.g., Knowledge Panels, AI Overviews, or standard blue links), your competitive benchmarks from May 2025 onwards are likely unreliable. 

This makes historical competitive analysis difficult to validate without third-party sanity checks.

3. Inaccurate SEO Forecasting

Forecasting future traffic based on historical impression volume is standard practice for enterprise SEO teams. Models built during the anomaly period now contain a 325-day bubble of phantom data.

Continuing to use these figures for 2026-2027 planning will result in over-ambitious visibility targets that are impossible to hit under the corrected logging standards.

How to Explain the Correction Drop to Stakeholders

Communicating a sudden drop in performance to clients or board members is a delicate task. Clarity and documentation are your best tools for maintaining trust.

• Annotate Every Dashboard. Immediately place a permanent annotation in Google Analytics, Data Studio, and any internal reporting tool. Mark May 13, 2025, as the “Anomaly Start” and April 3, 2026, as the “Logging Correction.”
• Decouple Clicks from Impressions. Pivot the focus of your reporting toward clicks and conversions. Emphasise that while the “eyes on page” metric was wrong, the actual traffic and revenue figures remain 100% accurate.
• Calculate the Correction Factor. Compare the average daily impressions in the two weeks following the fix against the same period in the previous month. Use this ratio to provide a rough estimate of how much the data was inflated.
• Proactive Notification. Don’t wait for stakeholders to ask about the drop. Send a brief memo explaining that Google has improved its measurement accuracy, which has resulted in a one-time adjustment to impression counts.
• Focus on Business Outcomes. Remind stakeholders that impressions are a top-of-funnel vanity metric. Revenue, leads, and actual site visits remained unaffected by this reporting change.

How to Identify Genuine Ranking Shifts vs. Data Fixes

Distinguishing between a technical data correction and a real algorithm update is vital for SEO health. Use these five diagnostic steps to isolate the cause of any volatility:

1. Compare Impressions with Average Position

If your impression count drops but your “Average Position” remains stable or improves, you’re likely seeing the effects of the GSC fix.

A genuine ranking loss would almost always be accompanied by a decline in average position. If the rank stays the same but the views drop, the views were never there to begin with.

2. Monitor Click Stability across Correction Dates

Because the bug didn’t affect clicks, a genuine SEO problem will show a simultaneous drop in both clicks and impressions. If your clicks remain steady while impressions fall, your search visibility is physically unchanged; only the reporting has been corrected.

This is the most reliable litmus test for the logging fix.

3. Analyse Specific Query Buckets for Uniformity

The logging error was a systemic infrastructure bug. Segment your data by “Query” and “Page” in GSC. If the drop is uniform across all categories and query types, it’s a global logging fix.

If the drop is isolated to specific terms or single pages, you are likely experiencing a standard search ranking shift or a topical content issue.

4. Cross-Reference with Third-Party Visibility Indexes

Tools like Semrush, Ahrefs, or Sistrix use their own crawlers to estimate visibility. Compare the GSC drop date with these third-party trackers.

Since these tools do not rely on Google’s internal logging, their data remained unaffected by the bug. If GSC shows a drop while third-party visibility stays flat, you have confirmed the logging correction.

5. Review Search Feature Presence

Sometimes, a drop in impressions occurs because Google removed a specific search feature (like an AI Overview or a Featured Snippet) from a keyword.

Check your “Search Appearance” report in GSC. If “Product Results” or “Review Snippets” impressions dropped specifically, it might be a rich result eligibility issue rather than the global logging fix.

Future-Proof Your SEO Reporting Strategy

Relying on a single source of truth for visibility metrics is a high-risk strategy. Diversifying your data sources provides a safety net when primary tools fail.

• Export GSC Data to BigQuery. Standard GSC reports are limited to 1,000 rows in the UI. By using the BigQuery Bulk Data Export, you gain access to granular, row-level logging data. This allows for more sophisticated cleaning and filtering when Google announces historical errors.
• Implement Multi-Source Dashboards. Build reporting environments that pull data from GSC, GA4, and independent rank trackers simultaneously. This triangulation allows you to spot anomalies within 24 hours rather than 11 months.
• Shift to Value-Based KPIs. Move your primary reporting focus away from impressions and toward “Actionable Visibility,” which are clicks that lead to specific high-value behaviours. This reduces your exposure to fluctuations in top-of-funnel reporting bugs.
• Regular Data Audits. Schedule a quarterly review of all tracking configurations. Check for tracking padding, duplicate triggers, and known vendor anomalies to catch errors before they become long-term problems.

Get Expert Help to Improve Search Integrity

The 11-month GSC impression bug is a reminder that even the largest data platforms make mistakes.

For marketing leaders, the goal is not to have perfect data, but to have verified data. By understanding the relationship between clicks, impressions, and positions, you can explain the current visibility drop as a necessary correction rather than a failure of your SEO strategy. 

Ensure you annotate your reports, adjust your CTR expectations, and focus on the metrics that actually drive revenue.

Don’t let an 11-month logging error skew your 2026 performance reviews. Tell No Lies provides the technical audits and data engineering expertise needed to clean your historical search data and set accurate benchmarks for the future.

Contact us today to help you with Google Search Console and data integrity needs. Let us help you tell the real story behind your search performance.