An unconfirmed February shakeup, Firefox's AI kill switch, and two days Google can't give back.

February refused to go quietly. Between 23 February and 1 March, rank trackers spiked to core-update levels while Google confirmed nothing, the screws tightened on generic content and inflated reviews, Firefox shipped its long-promised AI kill switch, Gutenberg previewed the biggest editing change of the WordPress 7.0 cycle, and Google quietly admitted that two days of Search Console export data are gone for good. If your website is how customers find and choose you, here's what actually happened this week — and what each item should change about how you run your site.

1. Late-February volatility: core-update-level swings, zero confirmation

What happened

The ranking turbulence that has rolled almost continuously since December flared again this week. Site owners reported sudden traffic drops and gains without touching their sites, and tracking tools backed them up: SEMrush Sensor pushed toward scores as high as 9.5 in the late-February window, and Sistrix's Update Radar showed spikes comparable in intensity to confirmed core updates from 2024 and 2025. Google's only confirmed update in the period remains the February 2026 Discover core update — which affects Google Discover exclusively. Everything moving in organic search this week moved unannounced.

Why this window is different

• Duration, not just amplitude. SERPs usually settle two to four weeks after a core update. The December update never really settled — volatility has bled from December through January into late February.
• No confirmation means no finish line. With a named update you at least know when the rollout ends. Unconfirmed turbulence gives you nothing to wait out, which makes disciplined measurement more important, not less.
• The pattern favours fundamentals. Sites that ride out every tremor share the same traits: fast pages, clean information architecture, and content with a detectable point of view.

2. Google tightens the screws on generic content, reviews and Business Profiles

Alongside the volatility, this week's local-search reporting pointed at a coherent theme: Google is pushing back against content that feels mass-produced, and pages that offer no new insight or demonstrable expertise are struggling to hold rankings. At the same time, rules around reviews and Business Profiles tightened while AI search features kept expanding across results — a squeeze on trust signals from both ends.

What this means in practice

• Volume content is now a liability. Ten templated service-area pages that say nothing carry more risk than three pages with real specifics, pricing logic and proof.
• Reviews are infrastructure, not decoration. If your local visibility leans on your Business Profile, keep review generation clean and keep testimonials, case studies and proof on your own site too — the one surface Google can't glitch or repolice overnight.
• Expertise has to be visible in the markup. Authorship, credentials, original data and first-hand detail need to live on the page where machines can parse them — a job for disciplined html web development, not a plugin.

3. Firefox 148 ships with an AI kill switch — and two changes developers should test

On 24 February, Mozilla released Firefox 148, headlined by a new AI Controls section in Settings — the "AI kill switch" users had been promised, letting people disable Firefox's AI-enhanced features in one place. Android got a refreshed toolbar and a copy-link-text option, and screen-reader access to mathematical formulas in PDFs improved.

The developer-facing changes

• CSS anchor positioning: the position-area property now correctly keeps anchored elements within the viewport. If your site uses anchored tooltips, popovers or dropdown menus, give them a regression pass in 148.
• Initial about:blank loads synchronously rather than being replaced by a second, asynchronously loaded document — a subtle change that can affect scripts and embeds that touch the initial document.
• The user signal matters too: a mainstream browser shipping a one-click AI off-switch tells you a real slice of your audience is opting out of AI features. Never make your site's core journey depend on any browser's AI layer.

4. Gutenberg 22.6 lands as WordPress 7.0 takes shape

Gutenberg 22.6 shipped on 25 February with 388 merged pull requests. The headline feature is visual change tracking for post revisions: browsing revisions in the editor now shows a colour-coded diff — added text in green, removed text in red strikethrough, formatting and attribute changes outlined in yellow, and whole blocks flagged when added or removed. For any team where editors, marketers and developers share one WordPress install, this is the single most useful editorial-workflow change in years.

It arrives mid-sprint toward WordPress 7.0, whose beta cycle is previewing an always-iframed post editor, viewport-based block visibility and per-block custom CSS. Translation for site owners: the block editor is about to change more in one release than it has in several — if your theme or custom blocks are fragile, this is your quarter to find out on staging, not in production.

5. Search Console: two days of export data are gone for good

Google disclosed a data anomaly that lands squarely in this week: due to a technical issue, 28 February and 1 March 2026 are missing from Search Console bulk data exports for some properties — and Google says the data will not be recovered. It caps a scrappy week for measurement generally, which opened with Barry Schwartz flagging a Google reporting issue affecting seemingly everyone on 23 February.

• Annotate the gap now. Add 28 Feb – 1 Mar notes to your dashboards so nobody misreads a two-day hole as a traffic crash during the next quarterly review.
• Don't let one tool own your truth. Cross-reference Search Console against your analytics and server logs; when a first-party tool drops data silently, redundancy is the only defence.
• Be careful with week-over-week comparisons that span the gap — automated reports will show phantom declines.

6. Interop 2026: the browsers publish their shared to-do list

Launched mid-February and dominating web-platform conversation through this week, Interop 2026 is the annual pact between Apple, Google, Microsoft, Mozilla and Igalia to fix the platform's worst cross-browser inconsistencies. This year's focus areas read like a modern design-system wishlist: cross-document view transitions (smooth animated navigation between pages, no SPA required), more stable container queries and subgrid, and JavaScript Promise Integration for WebAssembly. For agencies, the signal is that native, framework-free techniques keep absorbing work that used to require heavy JavaScript — which means lighter, faster sites are getting easier to build well.

What this week means for your website strategy

Pull the threads together and a clear brief emerges for anyone scoping web work this quarter:

• Build for turbulence. Unconfirmed volatility is the permanent weather. Resilience — speed, structure, genuine expertise on the page — is a build-quality feature you should demand from any website development company you evaluate, and it's the difference between sites that wobble and sites that hold.
• Generic is the new penalty. The content crackdown and the review tightening point the same way: differentiation and proof, on your own domain, in crawlable markup.
• Platform churn is accelerating. Firefox 148, Gutenberg 22.6, WordPress 7.0 on the runway, Interop 2026 — the platforms underneath your site are moving fast. Ecommerce teams feel this hardest; it's why working with Shopify development partners who track platform releases beats retrofitting after something breaks, and why a good shopify developer partner treats upgrade testing as routine, not billable drama.
• Measurement needs redundancy. Two days of unrecoverable data is a small loss with a big lesson: never let a single tool be your only record of how the site performs.

Frequently asked questions

Was there a confirmed Google update in late February 2026?

No. The only confirmed update in the period was the February 2026 Discover core update, which affects Google Discover only. The organic ranking volatility of 23 February – 1 March was unconfirmed, with tracking tools like SEMrush Sensor spiking to core-update-level scores without any announcement from Google.

Why is Search Console data missing for 28 February and 1 March 2026?

A technical issue on Google's side left 28 February and 1 March 2026 missing from Search Console bulk data exports for some properties, and Google has said the data will not be recovered. Annotate those dates in your reporting so a two-day gap isn't misread as a traffic drop.

Does Firefox 148's AI kill switch affect my website?

Not directly. Firefox 148's new AI Controls let users disable Firefox's own AI-enhanced browser features, not features on your site. The relevant developer changes in the release are a CSS anchor positioning fix and a synchronously loading initial about:blank document — worth a regression pass if your site uses anchored popovers or tooltips.

What's new in Gutenberg 22.6 and should I update?

Gutenberg 22.6, released 25 February 2026, merged 388 pull requests and adds visual change tracking to post revisions — colour-coded diffs showing added, removed and reformatted content. It's a preview of what's landing in WordPress 7.0, so update on a staging site first and test your custom blocks against it.

Should the late-February volatility change my website plans?

It shouldn't trigger a panic redesign, but it should sharpen your standards. The pattern across the week — volatility plus a crackdown on generic content and inflated reviews — rewards sites with real expertise, clean structure and fast HTML. Whether you search for web developers near me or hire remotely, evaluate builders on those fundamentals, not proximity.

The takeaway

The week of 23 February – 1 March was a stress test with no announcement: rankings moved without confirmation, measurement tools dropped data without warning, and the platforms under every website kept shipping. The sites that came through unbothered weren't lucky — they were built with the fundamentals Google keeps rewarding and the redundancy this week proved you need. Turbulence is the environment now. Build for it.