Your client saw a ranking drop the same week SEO Twitter posted about a "Google update." They want to know whether Core Web Vitals thresholds changed, whether their PageSpeed report is now obsolete, and whether you should drop everything to chase a new green score.
Short answer: the recent core updates did not reset how Google measures LCP, INP, or CLS. Google re-evaluated which pages best satisfy search intent across the whole index. Page experience, including Core Web Vitals, still matters. It is not the headline of these updates, and it is not a separate "CWV algorithm" you can fix in isolation.
Below: which official updates matter for page experience work, what stayed the same for Google page experience and CWV, and what to do when traffic moves after a core update.
Google core updates in 2025–2026: official timeline
When someone says "Google's latest algorithm update," they might mean different releases. For page experience and CWV work, these are the ones that matter:
Update | Official timing | What it affects | Relation to CWV |
|---|
December 2025 core update | Rolled out from 11 Dec 2025 (~18 days) | Broad search quality and relevance | Indirect: competitive pages may shift; CWV thresholds unchanged |
March 2026 core update | Rolled out from 27 Mar 2026 (~12 days) | Broad search quality and relevance | Same as above |
March 2026 spam update | From 24 Mar 2026 | Spam policy enforcement | Not a CWV or page experience change |
February 2026 Discover core update | From 5 Feb 2026 | Google Discover feed | Separate surface; do not confuse with web ranking CWV |
Google lists confirmed ranking updates on the Search Status Dashboard. Check there before you rewrite a performance roadmap.
Core updates are broad. Google's own guidance compares them to refreshing a list of restaurant recommendations: some move up, some move down, and a drop does not automatically mean the site is "bad." The systems are reassessing helpful, reliable content at scale, not announcing new LCP cut-offs.
Did Google change Core Web Vitals or page experience thresholds?
If your brief is only "react to the algorithm update," start here. Google's published guidance for page experience in 2026 still says the same thing on thresholds and signals.
CWV "Good" bands are unchanged: LCP at or below 2.5 seconds, INP below 200 ms, CLS below 0.1 (Understanding Core Web Vitals). There is no single page experience score used for ranking; the page experience FAQ states that core ranking systems look at a variety of signals, and CWV are among them.
Field data from CrUX is what matters for ranking context, not a one-off Lighthouse run. Lab scores help you debug; real-user data is what Search Console's CWV report reflects. INP is the interaction metric (FID was replaced in March 2024). If a stakeholder still asks about First Input Delay, point them to LCP, INP, CLS explained.
None of the December 2025 or March 2026 core updates on the status dashboard were labelled as page experience updates. The last named page experience rollout in the dashboard history is the June 2021 mobile page experience update. Since then, CWV have remained part of ongoing ranking systems without a repeat of that launch-style announcement.
So when a client asks "Did Google change the Core Web Vitals rules?" the honest answer is: not in these core updates. The rules in Search Central are the same. What changed is which pages Google prefers for a given query after a broad quality reassessment.
What changed in core updates that still affects your CWV work
Core updates do not rewrite CWV maths. They can still change how much CWV matter for a specific site in practice.
Competitive context shifted
A core update can promote pages that were already fast and demote pages that were borderline on content quality and slow. When many competitors in a niche improve experience, your "Good" CWV stop being a differentiator and become baseline. That feels like "Google got stricter on CWV" even when the thresholds did not move.
For how CWV interact with rankings in general (tiebreaker, not trump card), see How Core Web Vitals Impact SEO Rankings.
Google clarified how often rankings refresh
In December 2025, Google updated core update documentation to explain that smaller core updates happen continually, not only during named releases. Improvements to helpful content can show up between major updates; recovery also may not wait for the next named event.
For performance teams, that means measuring CWV on a schedule, not only when a core update hits the news cycle.
Documentation and crawling guidance moved (not CWV thresholds)
Search Central's changelog in late 2025 added JavaScript canonicalisation notes, noindex handling clarifications, and migrated crawling docs to Google's crawling infrastructure site. Those changes affect how you ship and index fixes, not the 2.5s / 200ms / 0.1 thresholds.
For a full map of which Search Central pages mean what for delivery, use Google Search Central Core Web Vitals and Page Experience Docs (2026). That post is the doc companion; this one is the update-timeline companion.
Discover is a different product surface
The February 2026 Discover update changed what surfaces in Discover, not how web Search scores LCP on a product page. Agencies reporting "traffic is down" should split Discover vs Web in Search Console before blaming CWV.
Does Google page experience still affect rankings after a core update?
Yes, but not as a separate "page experience update" headline. Google still uses CWV and related signals as part of broader page quality. Content relevance and helpfulness carry more weight when Google is choosing between pages.
A useful mental model has three layers:
Relevance and helpful content: does the page answer the query better than alternatives?
Trust and experience signals: CWV, mobile usability, HTTPS, intrusive interstitial avoidance.
Competitive set: who Google compares you to for that query after the update.
Google states that it still aims to show the most relevant result even when page experience is weak. In crowded SERPs, experience often tips close calls. That is why page experience is worth maintaining even when a core update headline is about content quality or E-E-A-T, not performance.
It also explains a pattern agencies see after every core update: a client with red CWV in Search Console and thin or outdated content loses twice. Fixing only scripts without content review rarely recovers large drops. Fixing only blog posts while LCP sits at 5s leaves money on the table for competitive queries.
Why rankings can drop when Core Web Vitals still look fine
Three mechanics create false blame:
Template deploys move CWV and rankings together
If your blog template regressed (new ad slot, heavier hero image), CWV and rankings can fall in the same week. The update did not change CLS limits; the deploy changed CLS.
CrUX field data lags behind your lab fixes
CrUX updates on a rolling 28-day window. You might analyse a core update in week one while Search Console still shows pre-fix field data. Lab scores improved Tuesday; Google's field view has not caught up yet.
Third-party visibility reports are not new CWV rules
Industry analyses (for example visibility studies after the March 2026 core update) describe who won or lost visibility, not new CWV thresholds. Use them for competitive context, not as proof that Google raised LCP requirements.
Before you promise "we will recover rankings by fixing INP," separate:
URLs with large position loss on high-value queries
Whether those URLs are Poor vs Good in the CWV report
Whether content quality, not performance, is the more likely driver
What to do after a Google core update (agency checklist)
Confirm timing on the Search Status Dashboard
Match the traffic change to the Search Status Dashboard window. Wait until the update is finished before deep analysis. Google recommends comparing at least a full week after rollout ends.
Split Discover, Web, and spam in Search Console
Use search types and filters. A Discover drop is not fixed by CLS work on checkout.
Triage dropped URLs, not the whole site
For URLs with large drops:
Run the helpful content self-assessment honestly.
Check CWV status for those URL groups (mobile first).
Check recent deploys, tag managers, and third-party scripts on those templates.
If a template-wide regression is suspected, read third-party scripts and performance.
Keep PageSpeed monitoring on a schedule
Manual PageSpeed runs after bad news produce screenshots, not a trend. PageSpeed Insights vs automated monitoring covers why one-off tests fail agencies at portfolio scale.
Use the agency CWV monitoring checklist to keep lab and field views on a schedule, not tied to SEO news cycles. For setup detail, see automated PageSpeed monitoring for multiple sites.
Report what you can prove to clients
Client updates should separate:
Google ran a broad core update; thresholds for CWV did not change.
These URLs lost visibility; here is content vs performance evidence.
Here is what we are fixing first and when field data should reflect it.
That framing reduces the weekly "did Google change the algorithm again?" loop.
Mistakes to avoid after a Google core update
Do not renegotiate CWV targets because of a core update headline unless Search Central actually changes thresholds (rare).
Do not delete useful content because rankings dipped. Google warns that mass deletion often signals search-first pages, not user-first pages.
Do not chase a perfect Lighthouse score for SEO alone. Google explicitly notes that perfect lab scores are not the goal of page experience work.
Do not treat AI Overviews traffic loss as a CWV problem by default. Click mix is changing for other reasons; see AI Overviews and CTR for that parallel track. Fast, crawlable pages still help both traditional and AI-mediated discovery.
FAQ
Did Google's March 2026 core update change Core Web Vitals thresholds?
No. Google did not announce new LCP, INP, or CLS "Good" thresholds with that update. It was a broad core update listed on the Search Status Dashboard, not a page experience launch.
Is Google page experience still a ranking factor in 2026?
Yes. CWV remain part of page experience signals Google uses. They work alongside content quality and relevance; they do not replace them.
Should we pause content projects and only fix CWV after a core update?
Usually no. Assess whether the drop is content-led, experience-led, or both. Strong teams continue content improvements while keeping CWV from regressing on important templates.
How long until CWV fixes show in rankings?
Field data needs roughly a 28-day CrUX window, then Google needs time to incorporate changes. Many teams see meaningful movement over weeks to a few months, not overnight. See the timelines in How Core Web Vitals Impact SEO Rankings.
Where does Apogee Watcher fit?
Watcher does not replace Search Console or Search Central docs. It helps agencies run scheduled PSI/Lighthouse checks and track lab plus CrUX field data across many client sites, so you spot regressions between core updates instead of discovering them when a client forwards an SEO newsletter.
What you can do next
Google's latest core updates reshuffle which pages win on quality and relevance. They do not redefine Core Web Vitals. Confirm the update on the official dashboard, triage dropped URLs by content and CWV evidence, keep monitoring on a schedule, and tell clients that page experience is still baseline work in competitive SERPs even when the news cycle is about something else.
If you manage multiple client sites, pair this timeline with the Search Central documentation guide and implement monitoring from the agency checklist. Start with a free Apogee Watcher account to automate tests and catch regressions before the next core update fills your inbox.