A stalled Search Console is not a verdict

A reporting stall is a period when Search Console's performance data stops advancing while Google Search keeps serving results, and one hit right after the September 2026 spam update finished rolling out.

The timing invites a bad reading. A spam update ends, the report goes quiet, and the last few days on the chart look flat or low. Teams that report weekly will be tempted to call that the update's impact. It is not. It is the absence of data, and it has to be labelled that way before anyone writes a recovery plan.

#What happened this week

Google's September 2026 spam update started on September 24 and was complete as of October 8, close to the full two weeks the Search Status Dashboard said it might take.

On October 11, Barry Schwartz reported that the Search Console performance report was more than 64 hours delayed, after lagging for several days following the update. Another site owner on X put it at almost 62 hours. By 11 am ET the same day, Schwartz updated the story to say the delay had dropped to 44 hours. Google had not commented at the time of publication.

The same article notes that third-party tools that scrape Google results have also struggled in recent weeks. We covered that side in your SERP tracker is now a sample. Put together, the two main outside views of Google rankings were both degraded in the same window a spam update landed.

#Normal lag versus a stall

Search Console is never real time, so the first job is to know what normal looks like.

When Google launched the 24 hours view in December 2024, it said that view would appear with a delay of only a few hours. The same post explains that Search Console shows data points before collection is complete and marks them with a dotted line. The performance report help describes the newest data as preliminary and subject to change.

So there are two different things that look alike on a chart:

• Preliminary data. The most recent hours or day are incomplete and will be revised upward. This is expected and flagged in the interface.
• A stall. Whole days are missing, and the report's last date stops moving. Nothing in the chart tells you this happened except the date range itself.

A 44 to 64 hour gap is the second kind. A chart that ends early is easy to miss in a dashboard that pulls the last seven days automatically and plots whatever comes back.

#This has happened before

Stalls are not rare. In December 2025, the performance report fell more than 60 hours behind and the page indexing report stalled for about two weeks. John Mueller confirmed on Bluesky that both reports were delayed past what Google would consider normal, and said earlier that week the issue was only in reporting. Schwartz's view at the time was that such stalls are almost always reporting bugs, not changes to crawling or ranking.

Google also keeps a public record of logging problems. The data anomalies page lists known events that changed what Search Console reports showed. Its 2026 entries include a logging error that reduced Generative AI in Search impressions from August 13 to 17, with the missing data later restored, and several Discover logging errors in May, June and August. A team that had reported an AI visibility drop for that week would have reported a logging bug.

#Why it matters more after an update

A spam update is exactly the moment when people read short windows closely. Google's spam update guidance says a site that fixes problems may improve as automated systems learn over a period of months that it complies, so the useful comparison is never three days. The temptation is still there, because a client or a manager wants an answer the day the rollout ends.

The same pipeline now carries AI visibility data. Since Search Console's AI performance report and controls went global, many teams treat it as their main first-party view of AI Overviews and AI Mode. Google has not said whether that report runs on the same schedule as the web search performance data, and the August 2026 anomaly shows it can have its own logging problems. Any stall or gap there deserves the same caution.

#A short protocol for stalled weeks

1. Record the last data date, not just the report date. Every export or dashboard should store the latest date with data next to the date it was pulled. If the gap grows well beyond what your property normally shows, mark the period as stalled.

2. Mask missing days instead of plotting them as zero. A day with no data should be blank, not a drop to the axis. Week-over-week comparisons that include a stalled day should be suppressed or footnoted.

3. Annotate update windows and stalls separately. Put September 24 to October 8, 2026 on the chart as the spam update window. Put the stall dates on as a reporting gap. Two annotations make it clear which one a change lines up with.

4. Check the anomalies page before reporting a change. If a dip lines up with a listed logging error, say so and wait for any restoration note.

5. Use sources outside Search Console as a cross-check. Server logs and analytics landing page sessions from Google organic do not depend on the Search Console pipeline. They are less detailed, though they will show whether real visits fell or only the report did.

6. Rerun the comparison after the backfill. Once the report catches up, pull the same date range again and compare it with the earlier export. Keep both, so you can see how much the late data changed the picture.

#What to tell people this week

The honest status for most sites on October 12 is simple. The spam update finished on October 8, the first-party report is behind, and the days after the rollout are not yet complete. Any claim about the update's effect on a site, positive or negative, should wait until the performance report has caught up and a few complete days exist after October 8.

Teams that track AI visibility should apply the same rule to AI Overview and AI Mode impressions. A flat line at the end of a chart is a question about the data before it is a question about the site.