Google Search Console Had a Bug That Was Inflating Your Impression Data Since May 2025

If your Google Search Console impression numbers have been looking suspiciously healthy for the past several months, there is a reason for that — and it is not because your SEO got dramatically better.
Google has officially confirmed a logging error inside Search Console that caused impression counts to be over-reported continuously from May 13, 2025 onward. The Search Console bug has been running silently in the background for nearly a year. Google is now deploying fixes, and as those corrections roll out over the coming weeks, you will likely see a noticeable drop in your reported impressions. Your actual search performance has not changed. Your data reporting is just about to get more honest.

What Exactly Happened

A logging error on Google’s side caused Search Console to record more impressions than were actually occurring. Google updated its official Data Anomalies in Search Console page to confirm the issue, noting that the error has been preventing accurate impression reporting since May 13, 2025.
The good news — and this is worth underlining clearly — is that clicks and all other metrics inside Search Console were not affected by this bug. Only impressions were inflated. Your click-through rate data, your average position figures, your click counts — all of those remained accurate throughout the period. It was purely an impression over-counting problem caused by how Google was logging that specific data point.
Google’s own statement confirmed: fixes are being implemented to restore accurate reporting, and the correction will roll out gradually over the next few weeks.

What Will You Actually See in Search Console

Once the fix begins rolling out, impressions in your Performance report will decrease. For some sites this could look like a sharp drop. For others it may be more gradual depending on how the rollout progresses across different accounts and property types.
The critical thing to understand going into this is: a drop in impressions does not mean a drop in rankings or traffic. It means the inflated numbers are being corrected back to what was actually happening in search.
If you manage clients or report to stakeholders who watch Search Console data closely, get ahead of this now. Brief them before the numbers shift, not after. An unexplained impression drop showing up in a monthly report without context is the kind of thing that generates unnecessary alarm and awkward questions.

This is not the first time Google Search Console has had a data reporting issue that caught SEOs off guard. We covered a similar situation earlier when Google Search Console experienced a significant data delay that left professionals with no new data for over 57 hours — another reminder that GSC reporting is not always as reliable as we assume it to be.

How Long Has This Been Going On

The bug started on May 13, 2025 and has been present in reporting ever since — a window of nearly 11 months. That is a long time for a core reporting metric to be silently inaccurate, and it raises a fair question: how many SEO decisions, content strategies, and performance evaluations were made using impression data that was inflated throughout this period?
If you ran any analysis comparing impression trends between early 2025 and the second half of 2025, that comparison is now unreliable. If you set impression-based targets or benchmarks after May 2025, those baselines were built on overstated numbers. This does not necessarily mean the directional insights were wrong — if impressions trended up in your data during this period, they may still have genuinely trended up — but the absolute numbers were higher than reality throughout.
Google has not disclosed exactly how large the inflation was, which makes it harder to quantify what “corrected” data will look like versus what was being reported. The practical advice is to treat the post-fix baseline as your new starting point and avoid making direct comparisons with data from the affected period without flagging the anomaly.

What You Should Do Right Now

1. Note the anomaly in your records

Add a clear annotation in your Search Console data and any reporting dashboards you use. Mark May 13, 2025 as the start of the inflated impression period. This way, anyone looking at historical data six months from now will understand why there is a visible step-change in the numbers.

2. Communicate proactively with clients and stakeholders

If you manage SEO for clients or report upward to a leadership team, send a brief heads-up before the numbers change. Explain that this is a Google-side data correction, not a performance drop. A short, plain-English note saves significant confusion later.

3. Do not adjust your SEO strategy based on the drop

When impressions fall, the instinct is to investigate — to check rankings, audit content, look for crawl issues. In this case, resist that instinct. The drop you are about to see is a data correction. Unless you see corresponding drops in clicks, traffic, or average position, there is nothing to investigate.

4. Recalibrate your impression benchmarks

Once the fix has fully rolled out and your numbers stabilise, use that settled figure as your new baseline for future impression targets and comparisons. Do not try to extrapolate back to pre-May 2025 figures for forward-looking benchmarks.

5. Cross-reference with other data sources

If you use Google Analytics, third-party rank trackers, or any other SEO platforms alongside Search Console, compare how those sources were trending during the same period. They were unaffected by this bug and can help you understand what was actually happening with your organic visibility versus what GSC was reporting.

Data accuracy issues inside Google’s tools have been a recurring concern for the SEO community. Earlier this year, the Google Search Console Links Report was also flagged for showing a decline in visible links—raising broader questions about how much SEOs should rely on GSC as their single source of truth for search performance data.

Why Impressions Matter — And Why This Bug Is More Significant Than It Sounds

Impressions are one of the primary health indicators SEOs use to assess organic visibility. They tell you how often your pages are appearing in search results, even when users are not clicking through. A rising impression trend typically indicates improving rankings or expanded keyword coverage. A falling trend can signal ranking drops, indexing issues, or reduced search demand.
Because impressions sit at the very top of the organic funnel — before clicks, before sessions, before conversions — they influence a wide range of decisions: which content to expand, which pages to consolidate, where keyword gaps exist, and how to prioritise crawl budgets. A nearly year-long inflation of this metric means a meaningful number of those decisions were made with a skewed picture of reality.
It is also worth considering click-through rate (CTR) calculations during this period. CTR is calculated as clicks divided by impressions. If impressions were inflated throughout this period, the CTRs you calculated for individual pages and queries during that window were artificially suppressed — meaning pages may have appeared to have lower CTRs than they actually did. Any CTR optimisation decisions made on the back of that data deserve a second look once corrected numbers are available.

The Broader Pattern Worth Paying Attention To

This is the second significant Search Console data issue within a relatively short period. Between data delays, link report discrepancies, and now a nearly year-long impression over-reporting error, it is becoming increasingly important for SEOs to treat Google Search Console as one data source among several rather than the definitive record of organic performance.
That does not mean GSC is unreliable overall — it remains the most direct window into how Google specifically sees and crawls your site. But for performance reporting and trend analysis, cross-referencing with analytics platforms and third-party tools gives you a more complete and resilient picture.

Opositive’s Take

A Search Console bug quietly inflating impression data for nearly 11 months is a significant issue, and Google deserves credit for acknowledging it transparently and committing to a fix. But for SEOs and marketing teams, this is also a useful moment to step back and reflect on how much decision-making weight gets placed on a single platform’s reported numbers. At Opositive, we have always recommended treating Search Console as an essential but incomplete data source — best used alongside Google Analytics, rank tracking tools, and log file analysis for a full picture of organic performance. This bug reinforces that position firmly. As the corrections roll out, do not panic at the impression drop. Use it as a reset point, document the anomaly clearly, and rebuild your benchmarks on the corrected baseline. Clean data, even if the numbers are lower, is always more useful than inflated data that looks good but points you in the wrong direction.

Stay updated with the latest Google Search Console news and SEO updates at news.opositive.io