Google's first Discover-only core update, another volatility spike, and anchor positioning goes Baseline.

Google did something it has never done before this week: it announced a core update that touches Discover and only Discover. That landed on 5 February, three days after rank trackers lit up with yet another unconfirmed volatility spike on 2 February. Meanwhile WordPress shipped a 49-bug maintenance release, the browser makers launched Interop 2026, and CSS anchor positioning quietly became something you can actually use in production. Between 2 and 8 February 2026, the ground moved for search and for the build layer underneath it. Here's what happened — and what each item means if your website is supposed to move revenue, not just exist.

1. The February 2026 Discover core update — Google's first Discover-only update

What happened

On Thursday 5 February, Google announced the February 2026 Discover core update — the first time it has ever shipped a core update scoped to Discover alone, rather than Search and Discover together. The rollout started with English-language users in the US, with other countries and languages to follow, and Google estimated up to two weeks to complete. Per Google's own documentation, the update does three things:

• More locally relevant content — surfacing articles from websites based in the user's own country.
• Less sensational content and clickbait — an explicit demotion target, named in the announcement.
• More in-depth, original, timely content from sites with demonstrated expertise in a given area, based on Google's understanding of the site's content as a whole.

Why it matters beyond publishers

Discover has become a serious traffic channel for many content-led businesses — and a volatile one. A Discover-only update means Google now tunes that feed independently of blue-link rankings, so a Discover traffic swing this month is not evidence your search rankings moved. Segment the two in analytics before you diagnose anything.

2. Another unconfirmed volatility spike, starting 2 February

What happened

Rank-tracking tools recorded a strong volatility spike around Monday 2 February, continuing the unconfirmed turbulence that has been running since January. Google confirmed nothing — and notably, this wave is separate from the Discover update that began on the 5th. That's the 2026 pattern in miniature: confirmed updates and unconfirmed tremors now run in parallel, and site owners have to tell them apart on their own.

The triage sequence, again

• Separate rank changes from click changes in Search Console — they have different causes and different fixes.
• Separate Search from Discover. This week especially: a Discover drop after 5 February is the confirmed update; a Search drop from the 2nd is the unconfirmed wave.
• Compare competitors. If your whole niche moved, it's the algorithm breathing. If only you moved, audit your last 30 days of changes.
• Rule out the boring causes — broken redirects, deindexed pages, a slow deploy, an expired plugin.
• Wait a full week before rewriting anything. Panic edits during volatility routinely turn temporary dips into permanent losses.

3. WordPress 6.9.1: 49 bug fixes, zero drama

WordPress 6.9.1 shipped on Tuesday 3 February — a pure maintenance release fixing 49 bugs across Core and the Block Editor, including issues in the block editor, mail handling and classic themes. No feature changes, no breaking changes: back up, update, move on. The same week, WP Engine launched Newsroom, a platform aimed at editorial teams running structured content workflows at scale — another signal that the WordPress ecosystem keeps consolidating around publishing operations, not just hosting.

The unglamorous point: an enormous share of "SEO emergencies" we get called into trace back to unpatched CMS installs and abandoned plugins, not algorithms. A maintenance release like 6.9.1 is the cheapest insurance in this entire recap. If nobody owns updates for your site, that's the first gap to close.

4. Interop 2026 launches — and anchor positioning goes Baseline

What happened

Two related pieces of web-platform news landed at the start of February. First, web.dev's January platform roundup (published as February opened) confirmed that with Chrome 144 and Firefox 147 now stable, CSS anchor positioning and the Navigation API have reached Baseline Newly available — meaning they work across the modern browsers. Chrome 144 also introduced the declarative <geolocation> element and the Temporal API for sane date-and-time handling. Second, the browser vendors launched Interop 2026: twenty agreed focus areas — fifteen of them new — where Chrome, Firefox, Safari and Edge will converge this year, including container style queries, CSS scroll snap, the shape() function and an upgraded attr().

Why a business owner should care about CSS news

• Anchor positioning replaces JavaScript. Tooltips, dropdown menus and popovers — components most sites bolt on with heavy JS libraries — can now be positioned natively in CSS. Less JavaScript means faster pages and better Core Web Vitals, which feed straight back into the search picture above.
• Interop reduces cross-browser bugs at the source. Every focus area that converges is a class of "looks broken in Safari" ticket that stops existing.
• These are html web development decisions, made at build time. A site built this year on native platform features will be lighter and cheaper to maintain than one built on 2022's library stack.

5. Quick hits from the week

• Discover, Search and preference signals. Google's Discover update documentation leans on its understanding of site-level expertise — and Google has been building user-choice features like Preferred Sources that let readers up-rank publishers they trust. Direction of travel: being a source people would choose is becoming a measurable input, not a nicety.
• The February Google Webmaster Report (published 30 January, digested by everyone this week) rounded up a busy month: core search signals flowing into Google's AI experiences and continued January volatility — useful context for why the 2 February spike surprised nobody.
• Ecommerce angle: the Discover update's clickbait demotion applies to store blogs too. Thin, sensational content attached to a storefront is now a liability twice over. Stores that invest in genuinely useful buying guides — the standard we hold as Shopify development partners — are on the right side of every change in this recap.

What this week means for your website strategy

Three threads worth pulling together if you own a business website or are scoping a redesign:

• Channels are fragmenting; fundamentals aren't. Search, Discover and AI answers are now tuned separately — but all three reward the same build: fast, structured, original, expert. One good site beats three channel hacks.
• The platform is doing more of the work. Anchor positioning, the Navigation API and Temporal landing cross-browser means modern sites need less JavaScript than the ones they replace. If a proposal for your rebuild reads like a 2022 dependency list, ask why.
• Maintenance is strategy. A 49-bug CMS patch and a deleted JS library will do more for most sites this month than any content sprint. Whether you find help by searching "web developers near me" or hire a specialist remotely, judge them on exactly this: update discipline, dependency hygiene, and evidence of fast Core Web Vitals on shipped work.

Frequently asked questions

What is the February 2026 Google Discover core update?

The first update Google has ever announced for Discover alone. Rolling out from 5 February to US English users first, it promotes locally relevant, in-depth, original content from sites with real topical expertise, and demotes sensational clickbait. Google estimated up to two weeks for the rollout.

Why did my rankings move around 2 February if no update was announced?

An unconfirmed volatility spike hit on 2 February, continuing January's turbulence — and it's separate from the Discover update. Diagnose before acting: split rank drops from click drops, compare competitors, rule out technical causes, and wait a week of data before changing content.

Should I install WordPress 6.9.1 straight away?

Yes. Released 3 February, it's a pure maintenance release fixing 49 bugs across Core and the Block Editor with no feature changes. Back up and update promptly — unpatched installs cause more real-world SEO damage than algorithm updates do.

What does CSS anchor positioning becoming Baseline mean for my site?

With Firefox 147 joining the other engines, tooltips, dropdowns and popovers can be positioned natively in CSS across modern browsers. That lets developers delete heavy JavaScript positioning libraries, making pages lighter and faster — a direct Core Web Vitals win.

Does the Discover update matter for ecommerce and Shopify stores?

Indirectly, yes. If your store publishes content, Discover now holds it to a higher bar: original, useful, expert material earns visibility, while clickbait-styled posts get demoted. Thin content bolted onto a storefront is a liability; genuinely helpful buying guides are an asset in Discover, Search and AI answers alike.

The takeaway

This week drew the map for 2026 in one frame: Google tuning its surfaces independently and rewarding demonstrated expertise, the algorithm moving whether or not anyone announces it, and the web platform absorbing work that JavaScript used to do. None of it favours tricks. All of it favours websites that are well built, well maintained and worth choosing — which has quietly become the entire job description.