Search Console Impressions Dropped? Google Fixed an 11-Month Logging Error

A client opens their monthly report, sees Search Console impressions down sharply against last year, and asks what broke. In many cases nothing broke on the site. Google found and fixed a logging error that had misreported impressions for almost a year, and the corrected numbers are lower. Any agency that reports impressions, CTR or average position year over year is now comparing against a period Google itself says was wrong.

This guide covers what Google has confirmed, which metrics you can still trust, and how to explain a Search Console impressions drop to a client without sounding like you are making excuses.

Why did Search Console impressions drop?

Search Console impressions dropped for many sites because Google fixed a logging error that kept it from accurately reporting impressions from 13 May 2025 until 27 April 2026. That is the entry on Google's Search Console data anomalies page. Google says the issue has been resolved and that, as a result, you may notice a decrease in impressions in the Performance report.

Read that carefully. Google says impressions may decrease now the error is fixed, which suggests more impressions were logged than were real. Google has not said how large the effect was, which sites or search features it touched most, or whether every day in the affected period has been reprocessed. So the honest position is: Google expects a decrease, the size is not stated, and it will vary by site.

Google is also clear that the error affected data logging only. Rankings and real visibility did not change because of it. What changed is the record of that visibility.

Which metrics changed, and which did not?

Clicks were not affected by the logging error; impressions, CTR and average position were. Google's note says only impressions and the metrics that depend on them changed, which makes sense once you remember how they are calculated:

• Impressions were misreported directly, and for most sites the fix brings them down.
• CTR is clicks divided by impressions. With accurate clicks and misreported impressions, CTR during the affected period was off too. If impressions fall after the fix, CTR will look higher.
• Average position is averaged across impressions, so misreported impressions moved it too. Google has not said in which direction, so do not promise a client that it improved or worsened because of the fix.
• Clicks are untouched. They are the one Search Console number you can compare straight across the whole period.

A Search Console impressions drop paired with flat or rising clicks is the signature of this correction, not of a site problem. If clicks fell as well, look for a real cause such as lost pages, seasonality or an algorithm update, and run the September spam update checks before you blame the fix.

Why did FAQ impressions fall to zero in May?

FAQ impressions fell to zero because, as of 7 May 2026, FAQ rich results no longer appear in Google Search. Google lists this on the same anomalies page, for both the Performance report and the FAQ rich result report, and says reported FAQ impressions will drop. In the search appearance reference, FAQ rich results now sit in the deprecated list, and the matching bulk export field is empty for recent dates.

This is not part of the logging fix, and it does not come back. Separate it in the report. If a client's site leaned on FAQ markup, show FAQ search appearance impressions as their own line ending on 7 May, then show whether the pages behind them kept their clicks as ordinary results. That turns "we lost a feature" into "here is what the pages still earn".

What other Search Console data dips should you know about?

Google's anomalies page lists several shorter 2026 dips that can distort a month-to-month chart, and each one is a logging issue rather than a ranking change:

• Generative AI report in Search, 13 to 17 August: a logging error reduced reported impressions. An update on 21 August says the missing data has been restored.
• Discover: clicks and impressions dipped on 7 to 8 May, 21 May, 24 June and 13 August.
• Job listing and Job details: impressions and clicks for these search appearances were not reported from 16 to 27 April.
• Bulk data export: 28 February and 1 March are missing for some properties, and Google says that data will not be recovered.

If you pulled the Generative AI report during that August window, pull it again: the restored numbers will be higher than your saved copy. If you track how AI Overviews affect clicks, check those dates before drawing a trend line.

How should you report year over year after the fix?

Report year over year by leading with clicks, because clicks are the only Search Console metric that was accurate on both sides of the comparison. For any month between May 2025 and April 2026, the impressions, CTR and average position you saved last year were based on misreported impressions. Comparing a corrected 2026 month against one of those months exaggerates the decline in impressions and distorts the change in CTR.

A practical layout for the next twelve monthly reports:

1. Clicks, year over year, as the headline SEO number, split into branded and non-branded with Search Console's branded queries filter where it is available.
2. Impressions, CTR and position, month over month only, using months after 27 April 2026, until a full year of corrected data exists.
3. A footnote on any year-over-year impressions figure pointing to Google's anomaly note.
4. Conversions from GA4 next to clicks, so the client sees outcomes, not only visibility.

The branded filter has limits worth stating. Google says it is not available for sites with a low number of impressions, its history starts from when it was introduced in March 2025, and some queries may be classed as branded or non-branded incorrectly. Treat the split as a guide, not an audit.

How do you annotate the dates in Search Console?

You annotate a date in Search Console by right-clicking the Performance chart on that day, entering a note of up to 120 characters and clicking Add. Google's annotations help page says each property can hold up to 200 custom annotations, they are shared with every owner and full user, and annotations older than 500 days are deleted automatically.

Add these to every client property you manage:

• 27 April 2026: impressions logging error ends, impressions corrected.
• 7 May 2026: FAQ rich results removed from Google Search.
• 13 to 17 August 2026: Generative AI report dip, since restored.

The start date, 13 May 2025, is already more than 500 days old, so an annotation there would fall outside what Search Console keeps. Record it in your report instead. Two more cautions. Annotations do not appear in comparison mode, which is exactly the view many people use for year-over-year checks, so put the same dates in the client report too. And annotations are visible to everyone on the property, so keep client names and personal details out of them.

Why export Search Console data every month?

Export Search Console data every month because the Performance report only goes back 16 months, and the period you need to explain will age out of it. Google's guide to debugging traffic drops recommends the Last 16 months view for context and says that to go beyond it you can use the Search Analytics API or bulk data exports to store data in your own systems.

The first months of the affected period have already aged out of that window, and the rest follows month by month until April 2026 drops off in late summer 2027. If you have not saved those months, you will be unable to show a client the before and after. A monthly export of clicks, impressions, CTR and position by page and query, filed per client, is cheap insurance. If the client already uses bulk data export to BigQuery, note the two missing days in February and March 2026 in your data dictionary so nobody mistakes them for an outage.

A good SEO reporting tool pulls the same Search Console metrics into each monthly report, so every report you send becomes part of that record. Pair it with SEO rank tracking tool data, which is measured independently of Search Console and gives you a second view of position that the logging error never touched.

What should you tell a client about the Search Console impressions drop?

Tell the client that Google corrected an error in how it counted impressions, that clicks were never affected, and that the report now compares clicks year over year for that reason. Keep it short, lead with the number that did not change, and link Google's own note. A script that works on a call or in a report comment:

"Google confirmed an error in how Search Console logged impressions between May 2025 and April 2026, fixed it, and says impressions may look lower as a result. So a lower figure against last year is largely that correction, not lost visibility. Clicks were not affected, and your clicks are [up / flat / down] by [X]% year over year. Until we have a full year of corrected data, we will compare impressions month to month and lead with clicks and leads."

Then move on to what the client cares about. A report that spends one paragraph on the correction and the rest on clicks, leads and next steps reads as competent. One that spends the whole meeting on a Google bug reads as defensive. Our guide to reports clients actually read covers that balance in more detail.

Search Console impressions FAQ

Why did my Search Console impressions drop in 2026?

For many sites, because Google fixed a logging error. Its data anomalies page says the error kept Search Console from accurately reporting impressions from 13 May 2025 until 27 April 2026, and that impressions may decrease now that it is resolved.

Were Search Console clicks affected by the logging error?

No. Google says clicks were not affected. Only impressions and the metrics built on them, CTR and average position, were affected, and the error affected data logging only, not rankings.

Why are my FAQ rich result impressions at zero?

As of 7 May 2026, FAQ rich results no longer appear in Google Search, so Search Console reports a drop in FAQ impressions. FAQ rich results now sit in the deprecated search appearance list.

How should I compare this year to last year in Search Console?

Lead with clicks, which were not affected, and treat impressions, CTR and average position between 13 May 2025 and 27 April 2026 as unreliable for comparison. Annotate the dates so anyone reading the chart sees why.

How long does Search Console keep performance data?

The Performance report goes back 16 months. Google suggests using the Search Analytics API or bulk data exports to store data in your own systems if you need a longer history.