A core update at full volatility, WordPress 7.0 hits pause, and masonry finally ships.

The week of 30 March to 5 April 2026 was the eye of the storm. Google's March core update — which started rolling out on 27 March, a day after the March spam update finished — spent the whole week reshuffling results, pushing volatility trackers to some of the highest readings they've ever recorded. Meanwhile WordPress announced that 7.0 would miss its April release date, Safari 26.4's native masonry layout settled into developers' hands, and the March web platform roundup landed with genuinely useful CSS. One caveat before we start: this week contained April Fools' Day, and the news below is strictly the verified, dated kind. Here's what happened, and what each item means if your website has to earn revenue.

1. The March 2026 core update: peak turbulence, and it isn't done

What happened

Google's March 2026 core update began on 27 March and was in full flight all week — it wouldn't be confirmed complete until 8 April. The numbers were dramatic even by core-update standards: Semrush's volatility sensor peaked at 9.5 out of 10, among the highest ever recorded, and SE Ranking's comparison against December's update showed far more churn — 79.5% of top-3 URLs changed positions (versus 66.8% in December), 90.7% movement across the top 10, and roughly a quarter of top-10 pages dropping out of the top 100 entirely.

The early pattern

• Destination sources gained. Official sites, specialist publishers and strong brands — pages that are the answer, not a doorway to it — were the visible early winners.
• Intermediary pages lost. Thin aggregator, affiliate-style and "content about content" pages absorbed the sharpest drops.
• The spam update muddied the water. With the March spam update completing on 26 March and the core update starting on the 27th, sites hit during this week can't yet tell which system moved them — one more reason not to react early.

2. WordPress 7.0 delayed: the biggest release in years hits pause

What happened

On 31 March, the WordPress core team announced that 7.0 would not ship on its planned 9 April date. A follow-up post on 2 April spelled out the mechanics: pre-release versions paused until 17 April, with a new schedule to be announced by 22 April. The sticking point is the database architecture behind real-time collaboration — the flagship feature of the release — which the team wants to get right rather than get out.

Why this is the right call — and what it means for site owners

• A delayed CMS release is cheaper than a broken one. WordPress runs a huge share of the web; a rushed architectural change to how content is stored would ripple through every plugin and host.
• Don't freeze your roadmap. Keep your current install patched and keep shipping. Nothing about the delay changes what a good WordPress site needs this quarter.
• Plan 7.0 as a project, not an auto-update. When it lands, the collaboration architecture makes this a test-on-staging release. Budget for it like a mini-migration.

3. Safari 26.4: masonry layout goes native with CSS Grid Lanes

Safari 26.4 shipped on 24 March — just before this week — and its headline feature dominated developer conversation through early April: CSS Grid Lanes, a native masonry-style layout. Pinterest-style column flows, portfolio grids and image galleries that previously needed a JavaScript library now work in pure CSS in one engine. The release also brought WebTransport (a modern, low-latency alternative to WebSocket), the Keyboard Lock API, and 191 bug fixes across SVG, tables and CSS zoom — 44 features in total.

Why designers should care

Masonry via JavaScript has always been a tax: layout shift while the script boots, broken rendering when it fails, and a payload penalty on exactly the image-heavy pages that can least afford it. A native version removes all three — eventually. For now it's one browser, so the professional move is progressive enhancement: a standard CSS grid every browser renders, upgraded to Grid Lanes where supported. That's a ten-line pattern in careful html web development, and it's the difference between using a new feature and depending on it.

4. The March web platform roundup: what Chrome 146, Firefox 149 and friends shipped

Right on schedule at the start of April, web.dev published its "New to the web platform in March" roundup, confirming the month's stable releases — Chrome 146, Firefox 149 and Safari 26.4 — and previewing the betas. The useful bits for working teams:

• Name-only container queries landed in both Firefox 149 and Safari 26.4 — you can now match against a named container with no size condition, which simplifies component-level responsive design.
• CloseWatcher API in Firefox 149 — dialogs and drawers that close correctly with Esc on desktop and the Back gesture on Android, without hand-rolled listeners.
• Scroll-position-driven animation control in Chrome 146 — more scroll-linked motion moving from JavaScript into CSS.
• contrast-color() in Chrome 147 beta — a CSS function that returns black or white, whichever contrasts better with a given colour. Small feature, big accessibility payoff for badge, tag and button systems. Chrome 147 stable was scheduled for 7 April, days after this week closed.

None of these is a headline on its own. Together they continue 2026's clearest platform trend: capability moving out of JavaScript and into CSS and HTML, where it's faster, more resilient and free.

5. Quick notes: spam update aftermath and an April Fools' filter

• The March spam update completed on 26 March, so this week was also the first clean week of post-spam-update data. If your site dropped in late March but holds steady through the core update, the spam system is the likelier cause — a different diagnosis with a different fix.
• April 1 came and went. The industry's joke-post tradition ran as usual, and it's why this recap cites only dated, verifiable announcements. A good habit for readers too: any "Google announces" story published on 1 April deserves a second source before it reaches your strategy deck.
• AI Mode kept expanding. Google's AI Mode reached general availability for US users during March, part of the backdrop against which this core update's "destinations over intermediaries" pattern makes strategic sense: Google increasingly summarises the middle of the funnel itself.

What this week means for your website strategy

Three threads worth pulling together if you own a business website or are scoping a build this quarter:

• Be the destination. The core update's early pattern rewards sites that are the source — original data, real expertise, genuine product depth — and punishes pages that merely stand between a searcher and the answer. Every page on your site should pass one test: would this still deserve traffic if Google could summarise it?
• Volatility is a build-quality audit. Sites that swing violently with every update usually share fundamentals problems — slow templates, thin templated content, messy information architecture. The fix isn't chasing the algorithm; it's engineering the site properly once.
• Ecommerce isn't exempt. Core updates hit product and collection pages as hard as blog posts, and templated store content is exactly the "intermediary" material this update demoted. It's why we'd put unique product content and structured data on the scope of any store build — and it's a fair test question for Shopify development partners you're evaluating: ask how the build itself, not a plugin, earns search visibility.

Frequently asked questions

Is the March 2026 Google core update finished?

No. It began on 27 March 2026 and was still rolling out through the week of 30 March – 5 April, with volatility trackers at some of their highest readings in years. Rankings will keep moving until Google confirms completion, so judge nothing mid-rollout.

Should I change my website while a Google core update is rolling out?

No structural or content overhauls mid-rollout. Positions swing in both directions before settling, so a panic rewrite responds to data that will look different in two weeks. Keep shipping planned improvements, log your rankings, and assess only after Google confirms the update is complete.

Why was WordPress 7.0 delayed and should I wait for it?

The core team announced on 31 March 2026 that 7.0 would miss its planned 9 April date, mainly to get the real-time collaboration database architecture right, with pre-releases paused until 17 April. Don't wait: keep your current WordPress install updated and plan the 7.0 upgrade as a tested project once a stable release lands.

What is CSS Grid Lanes in Safari 26.4 and can I use masonry layouts now?

CSS Grid Lanes is Safari 26.4's native masonry-style layout, shipped 24 March 2026 — Pinterest-style column flows without JavaScript libraries. It's one engine so far, so ship it as progressive enhancement with a standard grid fallback rather than relying on it cross-browser.

Does the March 2026 core update affect Shopify stores too?

Yes — core updates are platform-agnostic, and this one shifted visibility toward destination sources and away from thin intermediary pages. Ecommerce stores with unique product content, real reviews and clean structured data held up best; templated, thin-content stores were the most exposed. If yours dropped, an audit from a Shopify developer partner should look at content depth and site structure before touching keywords.

The takeaway

A week of enforced patience. Google's biggest core update in years was mid-flight, WordPress deliberately chose slower over sorry, and the platform quietly shipped CSS that replaces JavaScript. The common lesson: the wins go to teams that build deliberately — destination-grade content, properly engineered layouts, staged upgrades — while everyone else reacts to a storm that hasn't finished yet. Hold your nerve, prepare your staging environment, and let the update land before you grade yourself.