Summarize This Article With AI
Try with ChatGPT
Try with Claude
Try with AI Mode
There are certain phrases that make every SEO’s shoulders move closer to their ears.
“Core update.”
“Unexpected traffic drop.”
“Can we make the logo bigger?”
And now, apparently:
“Search Console impression data may have been wrong for almost a year.”
Lovely.
Google has fixed a Search Console logging error that affected impression reporting from May 13, 2025, through April 27, 2026. The issue affected impressions and related metrics, including CTR and average position, but Google said clicks were not affected.
So, the good news is that clicks were fine.
The less good news is that impressions, CTR, and average position may have been reporting through a funhouse mirror for nearly 50 weeks.
Which is exactly what every marketer wants to hear after building quarterly reports, annual comparisons, forecasting models, client decks, board updates, and probably at least one “great visibility growth” slide based on the affected data.
Article Summary
- Google has resolved a Search Console logging error that affected impression reporting from May 13, 2025, through April 27, 2026.
- The issue affected impressions and related metrics, including CTR and average position.
- Google said clicks were not affected and that the issue was related to data logging only.
- Search Engine Land previously reported that the bug caused Search Console to over-report impressions starting May 13, 2025.
- As the fix rolled out, some sites were expected to see impression decreases in the Performance report.
- Old data will not be fixed, according to John Mueller’s clarification reported by Search Engine Roundtable.
- This is why SEO reporting needs annotations, context, and more than one data source.
- Basically, your graph may be technically correct, emotionally misleading, and in need of a footnote.
What Happened?
Google confirmed a Search Console logging issue that affected impression data for almost 50 weeks.
Search Engine Land reported in April 2026 that Google was fixing a long-running Search Console bug that inflated impression counts. The issue began on May 13, 2025, and affected impressions in the Performance report. Google said clicks and other metrics were not affected, and that the issue was related to data logging only.
Search Engine Roundtable later reported that Google updated its notice to say the issue had been resolved. The affected period ran from May 13, 2025, until April 27, 2026. The update said only impressions and related metrics, such as CTR and average position, were affected. Clicks were not affected.
That matters because impressions sit inside so much SEO analysis.
They influence CTR calculations. They shape visibility trends. They affect how teams interpret demand. They influence whether a page looks like it is growing, declining, or underperforming. They can make a strategy look stronger or weaker than it really is.
So, when impressions are wrong for nearly a year, that is not a small footnote.
That is a reporting pothole big enough to lose a dashboard in.
Free Proposal HTML:
Why Clicks Being Unaffected Is the Small Mercy Here
Let’s start with the good news.
Clicks were not affected.
That means the most direct Search Console measure of traffic from Google Search should still be reliable. If your click data showed growth, decline, or stability, this bug does not appear to have changed that.
That is important.
Clicks are often the metric clients and leadership care about most because they connect more directly to traffic, leads, and revenue.
But impressions still matter.
A lot.
Impressions show how often your site appeared in search results. They help teams understand visibility, query expansion, topic reach, and whether content is being surfaced more often across relevant searches.
When impressions are inflated, several things can happen.
CTR may look lower than it really is. Average position may be harder to interpret. Visibility trends may look healthier than they were. Pages may appear to have broad reach without corresponding clicks.
Teams may spend time “fixing” low CTR pages that were not actually performing as poorly as the data suggested.
Or, my personal favorite, someone may build an entire strategic narrative around impression growth that later turns out to have been partly powered by a logging issue.
Delightful.
Absolutely nobody needed that.
The Historical Data Problem
Here is the really annoying part.
The issue has been resolved, but old data will not be fixed.
Search Engine Roundtable reported that Google’s John Mueller clarified the fix applies going forward and that the old data will not be corrected.
That means historical Search Console data from the affected period needs context.
Not panic. Not deletion.
Context.
If you are comparing May 2025 through April 2026 against future periods, impressions may not behave the way you expect. A drop after the fix may not mean visibility has suddenly collapsed. It may simply mean the inflated reporting has stopped.
Similarly, CTR may appear to improve after the fix because the denominator changed. If impressions decrease while clicks remain stable, CTR goes up.
That does not necessarily mean your title tags suddenly became irresistible.
This is exactly why SEO reporting should never be just screenshots and arrows. Data needs explanation. Especially when the platform producing the data admits the data had a 50-week wobble.
Why This Matters for Monthly Reporting
For any SEO team producing monthly reports, this issue needs to be annotated.
Not hidden.
Not over-explained into oblivion.
Annotated clearly.
If your dashboard includes GSC impression trends from May 2025 through April 2026, add a note explaining that Google confirmed a logging issue affected impressions during that period. Also note that clicks were not affected.
If your reports compare YoY impressions, include a caveat.
If your leadership team asks why impressions declined after April 27, explain that Google resolved the logging issue and that reported impressions may now be lower as a result.
If your CTR improves suddenly, check whether it is tied to the impression correction before celebrating too hard.
This is not about undermining the report. It is about making the report more trustworthy. A good SEO report does not pretend data is perfect. It explains what the data can and cannot tell us.
That is the difference between reporting and screenshot decorating.
And yes, screenshot decorating is a real marketing crime.
Possibly not legally, but spiritually.
The Bigger Lesson: Single-Source Reporting Is Risky
This bug is a lovely little reminder that no single platform should carry your entire SEO narrative.
Google Search Console is essential. It is also not perfect.
GA4 is essential. It is also an emotional obstacle course wearing an analytics costume.
Rank trackers are useful. They also show sampled, localized, personalized, and sometimes deeply confusing views of reality.
CRM data matters. It also depends on whether forms, UTMs, attribution rules, and sales processes are set up properly.
That is why SEO reporting should combine multiple sources.
- Use GSC for search visibility and clicks.
- Use GA4 for on-site behavior and channel performance.
- Use CRM data for leads and sales quality.
- Use rank tracking for keyword movement.
- Use server logs or crawl data where needed.
- Use annotations for algorithm updates, tracking issues, site changes, migrations, launches, and known reporting anomalies.
The goal is not to find one perfect data source because there is no perfect data source. The goal is to build a reliable enough picture from several imperfect ones.
Like SEO detective work, but with fewer trench coats.
What SEOs Should Do Now
First, annotate the affected period in your dashboards and reports.
The affected window ran from May 13, 2025, through April 27, 2026. Google said impressions and related metrics were affected, while clicks were not.
Second, review any reports that relied heavily on impression growth during that period.
Do not rewrite history dramatically.
Just add the proper context.
Third, be careful with YoY comparisons over the next year.
If you compare future clean impression data against affected historical data, the trend may look worse than it really is.
Fourth, shift more weight toward clicks, conversions, and business outcomes when explaining performance.
Impressions are useful, but they should not be treated as the whole story.
Finally, use this as a chance to tighten your reporting process.
Add data anomaly notes.
Track Google documentation updates.
Keep a changelog of major reporting issues.
Make sure everyone reviewing the dashboard understands what changed and why.
Because nothing builds confidence like saying, “Here is the data, here is the caveat, and here is what we can still confidently conclude.”
That is grown-up reporting.
Less glamorous than a green arrow, but much more useful.
The Search Everywhere Optimization™ Lesson
This issue also connects to a much bigger trend.
Search performance is becoming harder to measure.
Not easier.
Google Search Console can have logging issues.
GA4 can misclassify traffic.
AI assistant traffic may show up in new channels.
AI visibility may happen without a click.
Reddit, YouTube, TikTok, LinkedIn, reviews, and AI answers may influence the user before they ever visit your site.
Direct traffic may include people who first discovered you somewhere else.
Branded search may increase because users saw you in an AI answer, podcast, newsletter, or social post.
Attribution is getting messier.
Search Everywhere Optimization™ means brands need to understand visibility across the full journey, not just one report.
That includes classic organic search, AI search, social search, local visibility, third-party mentions, community conversations, and brand demand.
GSC is still a core part of that.
But it is not the entire truth.
This bug is a useful reminder that reporting should tell a strategic story, not worship one metric.
Final Thought
Google fixing the Search Console impression bug is good news.
But it does not magically repair nearly 50 weeks of historical reporting.
For SEOs, the right response is not panic.
It is documentation. Annotate the affected period. Explain what changed. Reframe impression trends carefully. Lean on clicks, conversions, and multi-source analysis. And please, for the love of all things canonical, stop presenting SEO reports without commentary.
Because data without context is how perfectly normal stakeholders end up spiraling over a graph that is actually just a platform issue wearing a scary hat.
Search Console remains one of the most important tools in SEO.
But it is still a tool. Not an oracle. Not a truth machine. Not a tiny dashboard deity.
Use it. Trust it where appropriate. Question it when needed. And always add the human layer that turns data into insight.
Want to understand what your search data is really saying across Google, AI search, and the wider Search Everywhere Optimization™ landscape?
Book a free strategy call with SEO Sherpa, and let’s find out where your visibility is growing, where reporting needs context, and where your competitors may be winning the search journey outside the dashboard.
Leave a Reply