On April 3, 2026, Google updated its Data Anomalies in Search Console page with a disclosure that should stop every marketing team mid-report:

"A logging error is preventing Search Console from accurately reporting impressions from May 13, 2025 onward. This issue will be resolved over the next few weeks; as a result, you may notice a decrease in impressions in the Search Console Performance report. Clicks and other metrics were not affected by the error, and this issue affected data logging only."

A Google spokesperson added in a statement to Search Engine Land: "We identified a reporting error in Search Console that temporarily led to an over-reporting of impressions from May 13, 2025 onward. Bug fixes are being implemented to ensure accurate reporting" (Danny Goodwin, Search Engine Land, April 3, 2026).

That is eleven months of inflated impression data in the most widely used organic search measurement tool in the world.

Every impression-based KPI, every CTR calculation, every visibility trend line, and every board report built on Search Console impressions during this period was built on a number that was too high. Google confirmed clicks were unaffected, which means your traffic data is fine, but every metric derived from impressions (CTR, impression-based share of voice, visibility scores, year-over-year impression comparisons) is now suspect.

Google did not say how inflated the numbers were, did not explain the technical mechanism behind the error, and did not address whether this bug interacted with two other known data quality issues that affected Search Console during the same period.

That is not enough information for a marketing leader who needs to explain to their board why the dashboard is about to show a drop.

How SEO practitioners spotted the Search Console impression bug before Google disclosed it

Google's disclosure did not come out of nowhere. The practitioner community had been raising alarms for days before the official acknowledgment.

Brodie Clark, an independent SEO consultant, published a LinkedIn post on March 30, 2026 flagging bizarre impression spikes across desktop, particularly within merchant listings and Google Images search appearance filters. His post included screenshots and a direct call for the Google Search Console team to investigate. Practitioners in the thread confirmed they were seeing identical patterns across their own properties (Brodie Clark, March 30, 2026, via Search Engine Roundtable).

Google's official acknowledgment arrived four days later on April 3.

PPC.land published a detailed timeline documenting that the logging error had run for nearly a year without detection, noting it affects "one of the most widely consulted data sources among SEO professionals and marketing teams for measuring organic search visibility" (PPC.land, April 4, 2026). Their reporting connected the April disclosure to a chain of earlier data quality events that had been treated as separate incidents.

Glenn Gabe, an independent SEO consultant, pointed to a compounding problem that Google's announcement did not address: the merging of AI Mode data into Search Console totals without any filter to separate it. His assessment captured what many practitioners were feeling: "We now have the 10-blue links, featured snippets, AIOs, and now AI Mode all grouped together in the performance reporting under Web Search. Good luck trying to figure this out in GSC."

In the comment threads across LinkedIn and X, secondary theories emerged about what might be contributing to the impression inflation beyond Google's internal logging error. Technical SEO consultant Razvan Antonescu attributed at least some of the late-March spikes to renewed SERP scraping: "Scraping. Is called scraping. Apparently, they managed to bypass filters again." Separately, Clement Prayal connected the timing of the most visible recent spikes to OpenAI's launch of an agentic product discovery feature in ChatGPT on March 24, 2026, suggesting AI-powered commerce crawlers may be adding a further layer of phantom impressions.

The common thread across every reaction is a single question: how many decisions were made on data that turned out to be wrong?

How inflated Search Console impressions affect CTR, reporting, and the AI click narrative

It is tempting to treat this as a technical footnote. Google says the bug inflated impressions, the fix is rolling out, and things will normalize in a few weeks.

But impression data is not a cosmetic metric. It is the denominator in CTR calculations, the basis for visibility trend reporting, and one of the most commonly presented SEO KPIs at the board level. When the denominator is wrong for eleven months, the damage is not limited to one number on one chart. It cascades.

Every CTR figure from the past year was calculated with an inflated denominator. CTR equals clicks divided by impressions. If impressions were overstated, every CTR number came out lower than reality. Pages that appeared to be underperforming on click-through rate may have been performing normally. Content that was deprioritized, rewritten, or defunded because of "declining CTR" may have been penalized for a measurement error rather than genuine underperformance.

Every board-level impression report from the past year is suspect. Impression growth is one of the most commonly presented SEO KPIs to leadership. A chart showing impressions up 40% year over year looks like organic momentum. If a meaningful portion of that growth was the bug, the real trajectory was different, and the narrative presented to leadership was wrong.

The "AI Overviews are eating our clicks" narrative was measured with a broken ruler. From mid-2025 onward, the SEO industry observed a pattern: impressions rising while clicks stayed flat. The dominant interpretation was that AI Overviews were satisfying queries directly on the SERP and suppressing click-through rates. Studies were published, strategies were revised, and budgets were reallocated based on that interpretation. But the impression denominator that produced those "declining CTR" numbers was inflated for the entire period. The real magnitude of AI Overviews' impact on click behavior may be different from what the industry concluded.

This does not mean AI Overviews have zero impact on clicks. They likely do. But the measurement was contaminated, and separating the genuine behavioral shift from the measurement artifact is now impossible without clean data. For how AI Overviews actually affect organic visibility, see our GEO guide.

Three overlapping Search Console data problems from May 2025 to April 2026

Google's disclosure addressed a logging bug. But the logging bug is not the only thing that has been distorting Search Console impression data over the past year.

Based on our initial review across client properties and the timeline documented by PPC.land, Brodie Clark, and other practitioners, there appear to be three overlapping data integrity issues affecting the same impression numbers during the same period.

The logging bug (May 2025 to present): This is what Google confirmed on April 3. Impressions inflated across the Performance report since May 13, 2025. Clicks unaffected. Fix rolling out over several weeks.

The scraper inflation and its removal (September 2025): On September 12, 2025, Google deprecated the &num=100 parameter that allowed search queries to return 100 results per page. Rank-tracking tools relied heavily on this parameter, and every scraper load registered impressions for every URL on the page in Search Console, even though no human saw them. When Google killed the parameter, practitioners reported impression drops of 20-40% overnight, and the "Alligator Effect" (the widening gap between rising impressions and flat clicks) snapped shut immediately (Search Engine Land, October 2025).

The critical question is whether the September drop brought impressions back to a clean baseline or whether the logging bug was still inflating numbers underneath. If both problems were running simultaneously from May through September, the September correction only peeled away one layer of inflation while the other continued undetected.

AI Mode data merged without segmentation (June 2025): On June 17, 2025, Google began counting AI Mode clicks, impressions, and position data toward totals in the Search Console Performance report, merged into the existing "Web" search type with no dedicated filter. As of April 2026, there is still no native way to separate AI Mode data from traditional organic, featured snippet, or AI Overview data. AI Mode now reaches 75 million daily users, which means this is a significant data stream being blended in with no way to isolate it.

Any impression trend line spanning mid-2025 to mid-2026 contains at least five documented discontinuities. Year-over-year comparisons using impression data from this period are unreliable.

How we are measuring the Search Console impression bug across 17 properties

Google's announcement was 47 words. It confirmed the bug existed and said the fix was coming. It did not quantify the damage, acknowledge the compound effect of three simultaneous data issues, or provide any framework for how marketing teams should interpret their data during and after the correction.

We are publishing a research study to fill those gaps.

What we are analyzing: 12 months of Search Console performance data (April 2025 through March 2026) across 17 properties spanning B2B SaaS, ecommerce, media, and professional services. Properties range from 17,000 to 5.55 million annual clicks and from 2.52 million to 292 million annual impressions. We captured the data in early April 2026, before the fix had fully propagated.

What we are looking for: The property-level inflation magnitude by comparing post-fix impression levels against the pre-May 2025 baseline. Whether the impression-click divergence pattern (impressions growing while clicks stay flat) appears universally or only in certain property types. Whether the &num=100 scraper signature is distinguishable from the logging bug signature. Whether some properties are barely affected while others show near-total artificial data. And whether the corrected CTR figures change which content looks like it is underperforming.

What we plan to publish: The full property-level data tables with anonymized property profiles. The estimated inflation magnitude across the portfolio. Corrected CTR calculations for the bug period. An annotated timeline with all five documented data discontinuities. And a measurement framework showing which Search Console metrics are trustworthy, which are compromised, and what to use instead during the correction period.

Why this matters beyond our own clients: Every marketing team that has reported impression-based SEO metrics to leadership over the past year needs to understand what portion of their reported growth was real and what portion was the bug. Every team that made content prioritization decisions based on CTR analysis needs to know whether those decisions were based on clean data. And every team that concluded "AI Overviews are suppressing our click-through rates" needs to revisit that conclusion with a corrected denominator.

This research is the second in a series from Passionfruit Labs on the measurement crisis affecting organic and AI search:

Study 1: The AI Visibility Measurement Crisis documented that AI citation metrics from platforms like ChatGPT and Perplexity are unreliable. The AI side of the measurement stack is broken.

Study 2 (this research, forthcoming) examines whether the traditional SEO side of the measurement stack was also corrupted during the same period.

Study 3: The Post-Fix Baseline will follow once Google's correction has fully propagated, showing the actual before-and-after comparison across the same 17 properties.

How to audit your Search Console data during the impression fix

You do not need to wait for our research to take immediate action on your own properties.

Run the 5-minute health check: Open each Search Console property, set the date range to 12 months, and compare the impression line against the click line. If impressions grew significantly while clicks stayed flat, your data was affected. The wider the gap, the larger the likely inflation.

Switch your primary KPI to clicks: Until the fix is complete and you have a clean baseline, report on total organic clicks and click growth rate. Google confirmed clicks were not affected by the error. Impressions and CTR are unreliable until the correction stabilizes.

Communicate proactively: Tell your leadership team, board, and clients about the bug before they see the impression drop in their dashboards and interpret it as a performance decline. Use Google's Data Anomalies page as the primary source. The drop is a data correction, not a ranking loss.

Export your data now: Capture daily data from every GSC property before the fix fully propagates. You need the pre-fix numbers to calculate property-specific inflation once the correction stabilizes. This data will not be available again after impressions normalize.

Annotate your dashboards: Mark May 13, 2025 (bug begins), June 17, 2025 (AI Mode merged), September 12, 2025 (&num=100 killed), and April 3, 2026 (fix begins) in every reporting dashboard that uses Search Console data. This prevents anyone from interpreting the forthcoming impression drop as a performance change.

When we publish the full Search Console impression analysis

We will publish the full research study once we have completed the analysis across all 17 properties. If you want to receive it the day it goes live, follow Passionfruit Labs.

If your dashboards are about to show an impression drop and you need help explaining it to leadership or recalibrating your measurement framework, talk to our team. We are offering complimentary GSC data integrity audits during the correction period.

The impressions are about to go down. That is a good thing. It means the data is getting more accurate. The question is what your data actually said underneath the noise, and that is what we intend to find out.

FAQs

What is the Google Search Console impression logging bug?

On April 3, 2026, Google confirmed that a logging error in Search Console has been inflating impression counts in the Performance report since May 13, 2025. The bug caused Search Console to over-report how many times pages appeared in search results. Clicks and other engagement metrics were not affected. Google is rolling out a fix over several weeks, and impression numbers will decrease as the correction takes effect. The decrease reflects more accurate data, not a drop in actual search visibility.

How long were Google Search Console impressions inflated?

The logging error ran for approximately eleven months, from May 13, 2025 through the start of the fix rollout in early April 2026. Google did not disclose the magnitude of the inflation or explain why the error went undetected for that long. This makes it one of the longest-running data quality issues in Search Console's history, and it overlapped with two other events that separately distorted impression data: the &num=100 scraper parameter removal in September 2025 and the merging of AI Mode data into Performance report totals in June 2025.

Were clicks affected by the Search Console impression bug?

No. Google explicitly confirmed that clicks and other metrics were not affected by the logging error. Click data in Search Console from the past year remains reliable. However, every metric that uses impressions as an input was distorted. CTR (clicks divided by impressions) was artificially depressed because the denominator was inflated. Impression-based share of voice, visibility scores, and year-over-year impression comparisons from this period are all unreliable until the fix stabilizes and new baselines are established.

Why are my Search Console impressions dropping in April 2026?

If you are seeing a decrease in reported impressions in April 2026, it is almost certainly the result of Google's fix for the logging bug, not a decline in your actual search performance. Google stated that users "may notice a decrease in impressions" as the correction rolls out. Your organic traffic, rankings, and click volume have not changed. The impression number is simply becoming more accurate. Check your click data to confirm that actual traffic is stable, and communicate this context to leadership before they interpret the dashboard change as a performance problem.

Should I still use Google Search Console for SEO reporting?

Yes, but with an important adjustment. Click data remains the most trustworthy metric in Search Console and should serve as your primary reporting KPI during and immediately after the correction period. Impression data and CTR will become reliable again once the fix has fully propagated and a new clean baseline is established, likely by May or June 2026. Until then, treat impression-derived metrics (CTR, visibility scores, impression growth rates) as directional signals rather than precise measurements. Cross-reference Search Console click trends against GA4 organic session data to confirm your actual performance trajectory.

How do I explain the Search Console impression drop to my leadership team?

Lead with Google's own statement from the Data Anomalies page, which confirms the logging error and states that clicks were unaffected. Then show your click data alongside the impression data to demonstrate that actual traffic remained stable while impressions were inflated. Frame the correction as a data quality improvement: the numbers are going down because they are becoming more accurate, not because performance declined. If your click data shows steady or growing organic traffic during the period, that is your real performance story and it was strong the entire time.

Passionfruit Labs | April 2026