Discover's first solo core update, a 9.5 volatility spike, and CSS scroll animations land in Chrome.

The week of 9–15 February 2026 was loud on both sides of the house. On the SEO side, rank trackers hit some of the highest readings ever recorded while Google stayed silent, and the first-ever Discover-only core update kept rolling underneath it all. On the build side, Chrome 146 beta shipped scroll-triggered animations you can write in pure CSS, and the browser vendors agreed on the 20 things they'll all fix this year through Interop 2026. If you run a business website — or you're about to commission one — here's what actually happened, and what each item should change about how you build.

1. Unconfirmed volatility spikes on 10 and 15 February — Semrush Sensor hits 9.5

What happened

Rank-tracking tools recorded a sharp volatility spike around Tuesday 10 February, then another wave over the weekend of 14–15 February. The Semrush Sensor touched 9.5 out of 10 — one of the highest readings that tool has ever produced. Barry Schwartz at Search Engine Roundtable described the volatility as "very heated" and noted it had not cooled through the weekend. Google confirmed nothing for web search.

Context matters here: this isn't a one-week event. Volatility from the December core update never fully settled, bleeding through January into February's fluctuations. The algorithm is effectively moving all the time now, with named updates just marking the loudest moments.

The triage sequence when trackers scream and Google says nothing

• Separate ranks from clicks. In Search Console, check whether positions moved or only click-through did — AI Overview expansion can cut clicks without touching rank.
• Check which query classes moved. Brand terms dropping is alarming; informational terms churning is normal weather in 2026.
• Compare competitors on the same queries. If the whole niche is bouncing, it's the algorithm. If only you moved, audit your last 30 days of changes.
• Rule out the boring causes first — deindexed pages, broken redirects, a slow deploy, an expired certificate.
• Wait seven days before rewriting anything. Volatility this extreme routinely round-trips on sites with sound fundamentals.

2. The February 2026 Discover core update rolls on — Google's first Discover-only update

What happened

Google's February 2026 Discover core update, launched on 5 February, continued rolling out all week. It's a genuine first: Google has never before announced a core update that targets Google Discover only, leaving web search rankings officially untouched. The stated goals: surface more locally relevant content from sites based in the user's country, cut sensational clickbait, and reward in-depth, original, timely content from sites with real topic expertise. The rollout started with English-language users in the US, with other countries and languages to follow.

Why it matters even if you ignore Discover

• Diagnosis discipline: if your web search rankings moved this week, this update is officially not the reason. Don't let a confirmed Discover update become the scapegoat for an unrelated search drop.
• Publishers and content-led brands that lean on Discover traffic should watch referral data through the rollout — Google estimated up to two weeks, so effects will keep landing.
• The criteria are a preview. "Original, in-depth, locally relevant, not clickbait" is where all of Google's surfaces are heading. Content built to that bar is future-proofing, not Discover optimisation.

3. Chrome 146 beta: scroll-triggered animations in pure CSS

What happened

On 11 February, Chrome 146 went to beta with a feature web designers have been simulating with JavaScript for a decade: scroll-triggered animations written declaratively in CSS. Because the browser handles the scroll linkage itself, the animation runs off the main thread — no Intersection Observer polling, no scroll-jank, less CPU burn on mobile.

Also in the release

• Scoped custom element registries — multiple apps or widgets on one page can define custom elements without name collisions.
• Sanitizer API — a built-in, spec-backed way to insert user-generated HTML without opening XSS holes.
• WebGPU compatibility mode — GPU-accelerated graphics reaching older OpenGL and Direct3D11 hardware.
• WebNN — hardware-accelerated machine-learning inference in the browser, no server round-trip.

The pattern across all four: work that used to require heavy JavaScript libraries keeps migrating into the platform itself. That's the strongest argument going for lean html web development — semantic markup, native platform features, and CSS doing jobs that once needed 80KB of scroll library. Sites built that way get faster every browser release without shipping a single new byte.

4. Interop 2026: browser vendors agree on the year's 20 fix-it areas

Apple, Google, Microsoft, Mozilla and Igalia published the Interop 2026 scope — the annual pact on which web platform features every browser engine will make behave consistently. Coverage rolled out across vendor blogs through the week, including Microsoft Edge's post on 12 February. This year: 20 focus areas drawn from 33 proposals, plus four investigation areas.

The highlights for site owners

• Cross-document view transitions — smooth animated transitions between separate pages, natively. The single biggest reason teams reached for single-page-app architectures is becoming a browser feature on plain multi-page sites.
• Dialog, popover and the :open pseudo-class — modals and popovers with native behaviour, focus handling and accessibility, no library required.
• WebRTC and WebTransport continue from 2025 for real-time features.
• Investigation areas include accessibility testing, JPEG XL and mobile testing.

The practical read: anything on the Interop list is a safe bet to build on this year. That changes architecture maths — a fast multi-page HTML site with view transitions can now feel as polished as an app, at a fraction of the complexity and with none of the SEO risk JavaScript-heavy rendering carries.

5. Platform notes: AI Overview overlay cards, Bing's AI reports, and WordPress 7.0's roadmap

• Google AI Overviews were spotted testing new overlay cards this week — another iteration in how cited sources get displayed. Meanwhile Seer Interactive's ongoing CTR research would soon show AI Overview click-through recovering from its 1.3% December low toward 2.4% by February — leveling off, not collapse. Citations remain the prize: cited brands earn dramatically more clicks per impression than uncited ones.
• Bing Webmaster Tools rolled out redesigned AI Performance reports, giving site owners visibility into how their content shows up in Microsoft's AI experiences. If Copilot traffic matters to your funnel, you can finally measure it properly.
• Search Console lag: the week's forum chatter confirmed that features Google announced in November and December still hadn't reached most accounts — a reminder to verify feature availability before building reporting workflows around announcements.
• WordPress entered the week with 7.0 planning underway and a return to three major releases in 2026 confirmed — the fastest cadence in years. Gutenberg 22.5 (4 February) brought per-block custom CSS. If your site runs WordPress, this year will bring more change than the last two combined; budget maintenance accordingly.

What this week means for your website strategy

Three threads worth pulling together if you're scoping a build or redesign this quarter:

• Volatility resilience is a build spec. A 9.5 Sensor week separates sites with fundamentals from sites with luck. Speed, structure and expertise are decided when the site is built — which is why the sharpest question for any development partner is "show me how the build itself earns rankings."
• The platform is eating your JavaScript budget. Scroll animations, view transitions, dialogs, sanitisation — all going native. Teams still defaulting to heavyweight frameworks for marketing sites are paying complexity tax on features the browser now ships free.
• Ecommerce isn't exempt. Storefront themes carry the same scroll libraries and modal scripts this week made obsolete. It's the kind of platform-level housekeeping good Shopify development partners fold into theme work by default — and a fair test when you're comparing a shopify developer partner against a generalist: ask which native browser features their themes already use.

Frequently asked questions

Why did Google rankings fluctuate during the week of 9–15 February 2026?

Unconfirmed volatility spiked around 10 February and again on 15 February, with the Semrush Sensor hitting 9.5 out of 10 — one of its highest readings ever. Google confirmed nothing for web search; the only confirmed rollout was the Discover-only core update from 5 February. Diagnose before acting, and give it a full week of data before changing content.

What is the February 2026 Google Discover core update?

The first update Google has ever announced that targets Google Discover only, not web search rankings. Launched 5 February, it promotes locally relevant, original, in-depth content and demotes clickbait, starting with English-language users in the US. If your search rankings moved this week, this update is not the official explanation.

What did Chrome 146 beta ship for web developers?

Beta landed on 11 February with scroll-triggered animations in pure CSS (running off the main thread), scoped custom element registries, the Sanitizer API, WebGPU compatibility mode, and WebNN for in-browser machine learning.

What is Interop 2026 and why does it matter for my website?

The annual agreement between Apple, Google, Microsoft, Mozilla and Igalia on 20 web platform areas every browser will make consistent this year — including cross-document view transitions and native dialog/popover behaviour. Features on the list are safe to build on without JavaScript workarounds.

Should I make big site changes while the Discover update and volatility play out?

Freeze reactive content rewrites until the data settles — but don't freeze fundamentals. Technical work on speed, redirects, structured data and page structure is safe in any algorithm weather and pays off regardless of where rankings land. Many businesses searching "web developers near me" mid-panic this week would be better served fixing fundamentals than finding a new agency to blame.

The takeaway

One half of this week was noise — a 9.5 volatility spike Google won't explain, an update that only touches Discover. The other half was signal: the browser platform absorbing another layer of JavaScript's job, and every major vendor agreeing on what to fix next. The websites that win 2026 will be the ones that hold their nerve through the noise and rebuild on the signal — leaner, faster, and native-first.