Search Console Lags Are a Weak Core Update Signal

You've probably seen the screenshot by now. Search Console's Performance report says "Last update: 45 hours ago," and someone in the replies is sure a core update is about to land.

Users reported lags of 45 hours and more in an r/SEO thread and on X on October 10 and 11, 2026, and several SEOs on X and Reddit read the freeze as a warning. Google's Search Console data anomalies page gives that reading little support. It lists logging errors on the start dates of two 2026 updates and on other days when no update began.

My read is that the lag is a weak signal at best. Export your data right away anyway.

The rumor traces to an r/SEO thread and a post on X, both from October 10.

On r/SEO, a user asked at 10:54 AM ET whether anyone else saw the "Last update: 45 hours ago" stamp. The replies split. One commenter said, "Same thing. Sounds like an update is rolling out." Another, u/SEOPub, answered, "This has nothing to do with algorithm updates." A third, u/DutchSEOnerd, said the delay "happens more often but not twice in one week," and added that Wednesday had a delay too. I have only that one commenter's word for the Wednesday stall.

At 4:22 PM ET, X user SEOwner posted: "Core update likely around the corner, Google has seemingly frozen the results, nothing moving at all for the past 24 hours or so." In a reply to another user, Metehan Yesilyurt wrote, "Core update is coming." Aleyda Solis's SEOFOMO roundup that day linked a piece predicting that "the next massive Google update is around the corner." Thomas Jepsen answered the mood on X with a joke: "May you never get tired of pre-announcing core updates."

Google's records do not settle the question. The Search Status Dashboard lists the September 2026 spam update as starting September 24 and running 13 days, 16 hours, with no incident after it. The anomalies page lists a Discover logging error for May 21, 2026, and the dashboard shows the May core update starting that same day. The page lists another Discover logging error for June 24, which is the day the dashboard shows the June spam update starting.

If you stopped there, you would call it a pattern. The page also lists a Generative AI report logging error in Search for August 13 to 17. The dashboard shows the August spam update starting on August 18, after the window closed. Google's page says the missing data was restored on August 21.

I read that as a coincidence you can find or lose depending on where you stop. Two of the entries share a start date with an update, one sits just before it, and the page records logging errors in specific reports. It does not record the freshness delay people are posting about, and it lists nothing for October as of October 11. These records give no reason to think this lag predicts an update.

Thomas Jepsen's joke has a point, and so does u/SEOPub's remark that a delay "happens pretty often." Neither tells you what will happen to your traffic. What the anomalies page does show is that Search Console's numbers can change after the fact. A complete export taken before any shift is worth more than a number you read later.

That is why I would export clicks and impressions by page now, including the Generative AI report, and save the export date with the file. If a core update does start, you can see which page types moved instead of guessing from sitewide traffic. Seeing where it moved is not the same as knowing why, and I would not claim the second. I would rather have the export than the prediction.