Google didn't wait for spring to warm up. Between 23 and 29 March it shipped two confirmed updates back to back: a spam update that rolled out and completed in under 20 hours — the fastest on record — and then, on Friday 27 March, the start of the March 2026 core update, which is still rolling as you read this. Meanwhile Safari 26.4 landed with CSS Grid Lanes (native masonry, finally), WordPress 7.0 reached release candidate, and fresh analysis showed exactly what kind of pages AI answers prefer to cite. Here's the full week — and what each item means for a business website that has to earn revenue, not just rankings.
1. The March 2026 core update starts rolling — expect weeks of movement
What happened
On Friday 27 March, Google confirmed the start of the March 2026 core update. Within 48 hours, site owners were reporting significant ranking changes — some gaining visibility, others losing it — and rank-tracking tools showed heavy volatility over the weekend. Core updates reassess overall quality, trust and relevance across the whole index, and they typically take one to three weeks to complete, so nothing you see this week is final.
How to handle a core update in progress
- Annotate the date in your analytics so that whatever happens next has a marker against it. You'll thank yourself in April.
- Don't ship reactive changes mid-rollout. Rankings can swing one way and back before an update completes. A change made on day 3 makes day 14 impossible to diagnose.
- Track queries, not just totals. Losing informational queries to AI-answer expansion is a different problem from losing commercial queries to competitors — and only one of them costs you revenue directly.
- Compare against your niche. If every competitor moved too, this is the index re-sorting, not a verdict on your site.
Core updates reward the boring fundamentals compounding over months: genuine expertise, fast pages, clean structure, content that serves the visitor rather than the crawler. If a site swings hard with every core update, that volatility is a build-quality signal — and fixing it starts with the site itself, which is why we treat resilience as part of the job for any website development company, not a separate SEO retainer.
2. The fastest spam update Google has ever shipped
What happened
Before the core update even started, Google ran the March 2026 spam update — announced on 24 March and confirmed complete on 25 March, a rollout of just under 20 hours. For comparison: the August 2025 spam update took 26 days. Google called it a "normal" spam update — no new spam categories, not targeting link spam, not targeting site reputation abuse — but the speed is the story. Google can now re-score spam signals across the index almost overnight.
Why the speed matters
- Shortcuts now fail faster. Scaled low-value content, doorway pages and cloaking used to enjoy weeks of grace while updates crawled out. That window is closing to hours.
- Diagnosis got cleaner. Because the spam update finished on 25 March and the core update began on 27 March, a traffic drop this week is datable: 24–25 March points to spam signals, 27 March onwards points to core quality reassessment. Check your dates before you check anything else.
- Recovery still isn't fast. A quick rollout doesn't mean a quick way back — spam-related drops generally persist until the underlying pattern is removed and the next update re-evaluates.
If traffic dipped on 24–25 March and stayed down, audit for the patterns Google's spam policies actually name: mass-produced pages with no unique value, thin location-page templates, scraped or spun content. Cut or consolidate them properly — with redirects, not deletions — and rebuild those URLs around pages that earn their place. That's remediation work we'd scope alongside conversion optimization, because the same thin pages that trip spam filters also convert nobody.
3. Safari 26.4: masonry layout goes native with CSS Grid Lanes
What happened
Apple shipped Safari 26.4 on 24 March with 44 new features and 191 fixes. The headline for designers and developers is CSS Grid Lanes — native masonry-style layout, the Pinterest-style packed-column grid the web has been faking with JavaScript libraries for over a decade. The release also brought WebTransport (a modern, low-latency alternative to WebSocket, and an Interop 2026 focus area) and the Keyboard Lock API for web apps that need full keyboard control.
What this changes in real builds
- Masonry without JavaScript means portfolio grids, galleries and card walls that don't shift, jank or block rendering while a library measures heights. Faster paint, better Core Web Vitals, less code to maintain.
- Treat it as progressive enhancement for now. One engine shipping isn't a baseline. Serve Grid Lanes where supported and a clean standard grid everywhere else — layout should degrade gracefully, never break.
- Delete the polyfill on a schedule. Every masonry library in your bundle is now legacy-in-waiting. Note it in the backlog with a browser-support threshold for removal.
This is the kind of week that separates teams who track the platform from teams who npm-install their way around it. Native layout beats a library on speed, stability and accessibility every time it's available — and page speed is a ranking and conversion input, not a nice-to-have. It's a fair test question for any agency pitch: ask how they'd build a masonry grid in 2026 and listen for whether the answer starts with CSS.
4. WordPress 7.0 reaches release candidate
WordPress 7.0 hit Release Candidate 1 on 24 March and RC2 on 26 March, putting the biggest release of the year — headlined by real-time collaboration work — on final approach for spring. Earlier in the month, the 6.9.2/6.9.3 security releases (10 security fixes) and 6.9.4 landed, so there's a clear to-do list for anyone running a WordPress business site:
- Be on 6.9.4 now. The March security fixes are not optional on a revenue-carrying site.
- Test 7.0 RC on staging this week — theme, plugins, custom blocks, checkout flows. An RC is exactly the window in which incompatibilities are cheap to find.
- Don't run an RC in production. Release candidates are for rehearsal, not launch night.
5. What AI answers actually cite — and Google's new citation block
Two related threads from the week. First, Google was spotted testing a citations block directly beneath AI-generated answers, plus a "guided research" flow that walks searchers through related questions — both signs that AI answers are becoming a surface you design for, not just a threat you measure. Google also began labelling AI-generated content on forum and Q&A pages. Second, new analysis of AI citation behaviour found that assistants disproportionately cite Reddit, Wikipedia, and list-style or product-focused pages — structured content with clear sections, bullets and direct answers.
The pattern is consistent with everything else we know: machines quote pages they can parse. Clean heading hierarchy, an answer high in each section, lists where lists belong, schema markup, and fast crawlable markup — every one of those is decided during html web development, when the page is actually built. You can't retrofit quotability with a plugin.
What this week means for your website strategy
If you own a business website — or you're scoping a redesign or replatform right now — three threads are worth pulling together:
- Google's cadence is accelerating. A 20-hour spam update followed within 48 hours by a core update means the gap between "what your site is" and "how it ranks" is shrinking. Build quality, not update-chasing, is the only durable strategy.
- The platform is doing more of the work. Native masonry in Safari, WebTransport, WordPress 7.0's collaboration tooling — the baseline capability of a well-built site keeps rising, and sites built on heavy workarounds fall behind on speed and stability.
- Structure is the common denominator. The same clear, sectioned, answer-first pages that survive core updates are the ones AI systems cite. One build discipline serves both. For ecommerce specifically, that discipline extends to the platform layer — it's why merchants increasingly vet Shopify development partners on site structure and speed, not just visual polish, and why a good shopify developer partner treats collection and product page markup as an SEO surface.
Frequently asked questions
How long will the March 2026 core update take to roll out?
Google core updates typically take one to three weeks to fully roll out. The March 2026 core update started on 27 March, so expect rankings to keep moving into mid-April. Don't judge wins or losses — and don't make reactive content changes — until Google confirms the rollout is complete.
Was my site hit by the March 2026 spam update or the core update?
Check the dates. The spam update ran from 24 to 25 March and finished before the core update began on 27 March. A drop on 24–25 March that held points to spam signals — scaled or low-value content, cloaking, doorway pages. A drop from 27 March onwards is the core update reassessing overall quality and relevance.
What is CSS Grid Lanes in Safari 26.4?
CSS Grid Lanes is native masonry-style layout — Pinterest-style columns where items of different heights pack tightly without gaps. Safari 26.4 shipped it on 24 March 2026. Until other browsers support it, treat it as a progressive enhancement with a standard grid fallback rather than a baseline technique.
Should I update to WordPress 7.0 now that it's at release candidate?
Not on a live business site. Release candidates (RC1 shipped 24 March, RC2 on 26 March) are for testing on staging environments. Do run the RC against a copy of your site now — checking your theme, plugins and any custom code — so the final release is a non-event instead of an emergency.
How do I get my website cited in AI answers?
Analysis this week showed AI systems favour list-style, well-structured, product-focused pages — plus high-trust communities like Reddit and Wikipedia. Practical moves: clear heading hierarchy, direct answers near the top of each section, bullet-point summaries, and structured data. These are build decisions, made during HTML web development, not bolt-ons.
The takeaway
A spam update measured in hours, a core update measured in weeks, and a browser release that just deleted a decade of layout hacks. The direction of travel is the same in every story: the machinery is getting faster and more literal, and it rewards websites that are simply built well — structured, fast, honest, and worth citing. Whether you're searching "web developers near me" or shortlisting a specialist remotely, that's the standard to hire against — and the one we hold our own builds to.