Most Google ranking updates go unannounced now. Track your own.
Google's docs now admit most core updates ship with no announcement, and the July 18 volatility proves it. Here is how to tell a real shift from your own noise.
Most Google ranking updates now ship with no announcement at all. Google's own documentation says so, and the traffic move you saw last week probably came from one of them. That changes how you read a ranking drop: waiting for Google to confirm a core update before you react no longer works, because the confirmed updates are a small slice of what's actually moving.
Google's docs admit ranking updates go unannounced
Google's core updates guidance spells it out: "These updates are not announced because they aren't widely noticeable, but they are another way that your content can see a rise in position." Read that again. The named updates on the Search Status Dashboard, March 2026 and May 2026, are the ones big enough to warn people about. Underneath them, smaller core updates run all the time, and Google has decided they aren't worth a post.
So the public timeline of updates is not the timeline of changes. It's the timeline of the changes Google felt like naming.
The July weekend Google never confirmed
On July 18 and 19, more than a dozen volatility trackers lit up at once. DataForSEO, Semrush Sensor, Sistrix, AccuRanker, Mozcast, Algoroo, and others all registered movement over the same window. Google confirmed nothing. The Search Status Dashboard stayed clean. If you lost rankings that weekend and went looking for the update to blame, you found silence.
This is the normal state now, not the exception. The rankings shift, the trackers twitch, and no post explains it.
Why waiting for the announcement stopped working
The old routine was simple. Traffic dropped, you checked whether Google had confirmed a core update, and if it had, you told your boss to wait for the rollout to finish before touching anything. That routine assumed the important changes came with a label. They don't anymore. Much of the movement you'll see this quarter will have no name and no dashboard entry, which turns "wait for confirmation" into "wait forever."
Don't panic-edit every time a tracker turns orange. Build enough of your own record that you can tell three things apart: a real Google shift, normal week-to-week noise, and a change you made yourself.
Keep a dated change log
Start with the cheapest habit in SEO. Every time you publish, retitle, redirect, change a template, or ship a speed fix, write the date and the change in one shared doc. Thirty seconds each time. When traffic moves three weeks later, the first question is always "what did we change?", and without a log you're guessing. With one, you can line up the drop against your own edits before you ever blame Google. Most "algorithm hits" we get asked about turn out to be a botched migration or a canonical that changed and nobody logged. If you're staring at a ranking loss right now, this is the same discipline behind refreshing posts that lost their rankings: fix what you can attribute first.
Baseline your normal volatility
Trackers like Semrush Sensor show volatility for the whole web. That's not your site. Your rankings bounce a little every week even when nothing happened, and you can't spot an abnormal move until you know what a normal week looks like. Pull your Search Console position data for your top 20 queries, week over week, across the last three months. Now you have a range. A query that swings two positions is breathing. A query that drops eleven is a signal. When five of your twenty move the same direction in the same week, that's your algorithm alarm, and it fires without waiting for Google. Set it up once inside the analytics you actually check, and you stop reacting to headlines about other people's traffic. When the alarm goes off, work in order: read the change log, rule out tracking bugs and seasonality, then look at which pages and query types moved rather than the site total, because a real core update hits patterns, not everything at once. A confirmed update never told you what to fix. Your own data does that.
If you want help turning your Search Console data into an early-warning system you can trust, that's the kind of work we do at vibhe.
