Google's March 2026 core update finished rolling out on April 8. Twelve days. No blog post from Google explaining what changed. Just a one-liner on the Search Status Dashboard: "Released the March 2026 core update."
But the data tells the story. Semrush Sensor hit 9.5 out of 10 on volatility. Over 55% of tracked sites registered measurable ranking changes. Some domains lost half their traffic overnight.
Here's what actually changed and why it matters.
Your Domain Is One Score Now
Google used to evaluate Core Web Vitals page by page. Your homepage could score perfectly while your /about page loaded like it was on dialup, and that was fine. Each page stood on its own.
Not anymore.
The March 2026 update introduced site-wide CWV aggregation. Google now produces a domain-level assessment. Every indexed page on your site contributes to one number. Your fastest page and your slowest page get averaged together.
That forgotten services page you built three years ago with a heavy template and never touched again? It's pulling down your entire domain right now.
Only 47% of sites currently pass the "good" CWV thresholds under this new model. The other 53% are losing somewhere between 8-35% of their traffic, conversions, and revenue.
INP Is Where Everyone Fails
If you haven't been paying attention to Interaction to Next Paint, now's the time. INP replaced First Input Delay last year, and it's a completely different animal.
FID only measured the delay on your first click. INP measures every single interaction across the entire session. Every button tap, every dropdown, every form field. The slowest one counts.
43% of sites fail the 200ms INP threshold. It's the most commonly failed metric by a wide margin.
And here's the thing about INP -- it's not an image problem. You can compress every JPEG on your site and it won't move INP a millimeter. INP is a JavaScript problem. It measures how long the browser's main thread is blocked when a user tries to interact with something.
Every plugin you load. Every third-party script. Every animation library. Every analytics tracker. They all compete for the same main thread. Stack enough of them together and your site becomes unresponsive for 300, 400, 500 milliseconds after each click.
The average site built with a popular template builder runs 20+ plugins. Each one adds JavaScript to the main thread. One popular builder adds 0.18 seconds to load time and 32.4 MB to page weight compared to lighter alternatives. Another one tested at 5.8 seconds LCP out of the box. That's deep in the red zone.
You can check your own INP in Chrome DevTools. Open Performance Insights, click around your site, and watch the INP readings. If you're above 200ms on any interaction, you're failing.
// Quick INP check in the browser console
new PerformanceObserver((list) => {
for (const entry of list.getEntries()) {
console.log('INP candidate:', entry.duration, 'ms', entry.name);
}
}).observe({ type: 'event', buffered: true, durationThreshold: 16 });
Paste that in your console and start clicking around. Anything over 200ms is a problem.
Fix the Template, Not the Page
Here's the part most SEO advice gets wrong. People audit individual URLs. They run PageSpeed Insights on their homepage, fix a few images, and call it done.
Under site-wide scoring, that approach is useless.
Most CWV problems are template-level problems. If your blog post template has a CLS issue, and you've published 3,000 posts using that template, you have 3,000 pages with the same CLS issue. All 3,000 are dragging down your domain score.
Fix the template once and you fix all 3,000 pages. That's the multiplier most people miss.
Go to Google Search Console, look at your Core Web Vitals report, and group by issue type -- not by URL. You'll see patterns. "CLS issue: more than 0.1" affecting 847 URLs. Those 847 URLs almost certainly share a template. Fix the template, not each page individually.
# If you're on WordPress, find which templates your failing URLs use
wp post list --post_type=page --fields=ID,post_title,page_template --format=csv
The Spam-Then-Core Sequence
Something nobody's talking about enough: Google's spam update completed March 25. The core update started March 27. Less than 48 hours apart.
That's not a coincidence. The spam update cleared out manipulative link schemes and scaled content abuse. Then the core update immediately re-evaluated quality rankings with those signals removed.
If your site was propped up by questionable backlinks, you got hit twice in the same week. 71% of affiliate sites saw measurable ranking declines across 600,000 tracked pages. Finance affiliates lost 40-55% of their rankings. AI content farms lost 60-80%.
Sites that gained? Niche publications with original research, first-hand case studies, and real expertise. The winners had actual humans with actual experience writing about things they'd actually done.
The Real Nuance
I should be honest about something. Google's own John Mueller has said Core Web Vitals are "not giant factors in ranking." And he's right -- in isolation.
CWV won't tank a site with genuinely excellent content and strong authority. But CWV are a baseline filter. Think of it like table stakes. You can't win the hand without them, but having them doesn't guarantee you win.
The shift to site-wide scoring amplifies this. It's not that one slow page destroys you. It's that a pattern of neglect across your domain creates a persistent drag. If 30% of your indexed pages fail LCP thresholds, the aggregate pulls everything down. Every page. Including the ones that pass individually.
What This Actually Means
The sites winning after this update share a pattern: clean code, minimal dependencies, semantic HTML, fast on every page. Not just the homepage. Not just the landing pages. Every page.
The sites losing share a different pattern: template bloat, plugin sprawl, JavaScript soup, and a strategy that only optimized the pages they thought mattered.
The recovery window for technical CWV fixes is 4-8 weeks. Content quality improvements won't be recognized until the next core update, likely June or July 2026. If you're going to act, act now.
We automated our own content pipeline specifically to avoid this kind of bloat. Every page we publish passes through a quality gate before it goes live. Clean markup, minimal scripts, fast everywhere. That's not a feature we sell -- it's just how we build things.
If you're staring at a Core Web Vitals report full of red and don't know where to start, that's literally what we do. First conversation is free -- kief.studio/contact.