Core update is the main storm
Google's March 2026 core update is still rolling out on April 1, now on day 5 after starting on March 27. Google said the rollout may take up to two weeks, so unstable rankings right now are not a mystery, they are the forecast. The separate March 2026 spam update already finished on March 25 after a very short rollout, so today's bigger story is clearly the live core update, not spam.
The volatility data fits that picture. Rankings were extremely hot through most of March, cooled from the peak, but never really settled. Over the last week, movement stayed elevated, with March 29 at 7.1, March 31 at 6.6, and today's partial score at 7/10 so far. Because today's score is incomplete, the safer read is that Google is still shaking the results hard enough for many sites to feel it. That is thunderstorm territory.
What the industry is seeing
Across the SEO press, the common thread is uncertainty, not a clean pattern. Search Engine Journal has framed the spam update as relatively muted, while also noting that site owners were hoping for stronger action against low-value and AI-rewritten content. At the same time, Google's own Search Central surfaces no major new blog post for today, which usually means site owners should focus less on chasing a fresh announcement and more on watching real performance data while the core rollout runs.
Another useful reality check: misinformation is still easy to rank. SEJ recently showed that a fake Google update could gain visibility in Search and AI Overviews, which is a good reminder not to trust every hot take flying around during volatile days.
What to do
- Do not panic-edit pages during the rollout.
- Check Search Console for drops starting March 27, 2026.
- Look for patterns by page type, not one-off keyword losses.
- If weak pages are thin, repetitive, or made mainly for SEO, fix those first.
- Wait for rollout completion before declaring winners and losers.
Bottom line
Today looks like a real Google weather event, not background noise. If traffic moved, the active core update is the most likely reason, and the smart play is calm monitoring, not random surgery.
