The June spam update wraps in 48 hours, Figma rewrites its canvas, and Chrome 150 lands.

A dense week. Between 22 and 28 June, Google pushed a confirmed spam update through search in barely two days, Figma used Config 2026 to move code, motion and shaders onto the design canvas, Chrome 150 reached early stable with CSS that kills a whole category of JavaScript hacks, and Search Console's new AI controls kept expanding. Each story sounds like industry inside-baseball until you translate it into the only question that matters: does this change how a business website earns and converts traffic? Here's the week, translated.

1. Google's June 2026 spam update: done rolling out in two days

What happened

Google announced the June 2026 spam update on Wednesday 24 June and confirmed it finished on Friday 26 June — roughly 48 hours, one of the fastest rollouts on record for an update of this type. It's the second spam update of 2026, it applies globally in all languages, and early community readings suggest it hit harder than March's. Google told Search Engine Roundtable it's a "normal" spam update: it does not target link spam and does not enforce the site reputation abuse policy. It's the automated spam-detection systems getting better at what they already do.

What a spam update actually punishes

• Scaled content abuse — mass-produced pages (increasingly AI-generated) that add no original value.
• Doorway pages — near-duplicate location or keyword pages built to funnel, not inform. "Web design in [town]" times forty is the classic pattern.
• Thin affiliate and copied content — republishing what already ranks with nothing added.
• Sneaky redirects and cloaking — showing Google one thing and users another.
• Expired domain abuse — old domains repurposed to host unrelated content for rankings.

If your traffic moved between 24 and 26 June, check the timing against Search Console before assuming anything else. If the window matches and you've been running programmatic pages or bulk AI content, you have your answer. And note the sobering part: recovery from an algorithmic spam update isn't a form you file — you fix the violations and typically wait for the systems to reprocess your site, often not until the next update.

2. Figma Config 2026: code, motion and shaders move onto the canvas

What happened

Figma's Config conference ran 23–25 June in San Francisco, and the announcements amounted to a thesis: everything that used to happen after design — code, animation, effects — should happen on the canvas. The headliners: Code Layers, which turn any design layer into working, interactive code with a click or a prompt; Figma Motion, a keyframe timeline that exports animation as CSS, JSON, React, MP4, WebM, animated SVG or GIF; WebGPU-powered shader fills on paid plans; and an upgraded Figma AI agent alongside generative plugins.

What it means for how websites get built

• The handoff gap narrows. Motion specs that used to be a Loom video and a shrug now export as CSS or React. Fewer interpretation errors, faster builds.
• Prototypes get more honest. Code Layers means stakeholders review something that behaves like the real product, not a picture of it. Better decisions, earlier.
• Generated code still isn't shipped code. Nothing announced at Config guarantees semantic HTML, accessibility, performance budgets or crawlable markup. The craft of html web development — heading hierarchy, clean structure, fast render paths — is still what separates a site that ranks and converts from a beautiful demo.

3. Chrome 150: CSS that replaces JavaScript, and a browser facelift

Chrome 150 hit early stable on 17 June, with the full stable rollout landing 30 June — so this was the week developers got their hands on it. The visible change is a WebUI refresh: cleaner icons, simplified context menus, updated internal pages. The changes that matter for your website are in the engine:

• CSS text-fit — headlines and dynamic text that automatically size to fit their container, in pure CSS. Every hero section with a JavaScript "fit text" library just got lighter.
• AccentColor and AccentColorText — CSS access to the user's operating-system accent colour, for web apps that want to feel native.
• WebGPU immediates — setImmediateData() passes small, frequently updated values to shaders without buffer overhead, useful for the growing wave of GPU-driven page effects.
• Security default — users on Enhanced Safe Browsing now get "Always use secure connections" switched on automatically. If any corner of your site still serves HTTP, more visitors will now see friction.

Elsewhere in browsers: Firefox 152 shipped field-sizing, letting textareas and inputs grow with their content natively, and the Safari 27 beta previewed transform-aware anchor positioning, the :heading pseudo-class and stretch-based box sizing. There was no stable Safari release in June — the usual reminder to treat Safari as your compatibility floor and ship new CSS behind progressive enhancement.

4. Search Console's AI controls keep spreading

The Search Console story that started mid-June kept developing through this week: Google's new "Search generative AI" settings — which let a site opt out of AI Overviews, AI Mode and AI Overviews in Discover while staying fully indexed in classic results — took effect from 17 June, UK-first under a CMA mandate, with documentation and the AI performance reports expanding to more properties since. It's the first time publishers have had a lever over AI answer inclusion that doesn't also nuke their organic rankings.

Should a business site pull out of AI answers?

Almost certainly not. For publishers whose product is the content itself, the calculus is genuinely hard. For a business website, being cited in an AI answer is a recommendation at the moment of decision — the modern equivalent of ranking #1. The right move is the opposite of opting out: get your AI visibility measured. If the AI performance report is available on your property, baseline it now, and make sure the pages AI systems cite have a clear next step on them — this is where conversion optimization and SEO stop being separate disciplines.

5. Platform notes: WordPress 7.1 gets a date, Shopify builds keep compounding

• WordPress 7.1 is targeted for 19 August 2026 — discussed across community coverage this week with a packed backlog, and core committers debating whether real-time collaboration belongs in core at all. If you run WordPress, the practical takeaway is calendar math: plugin-compatibility testing in early August beats firefighting in late August.
• Quiet weeks are for maintenance. No major CMS shipped a release this week, which makes it the right week for the unglamorous work: core and plugin updates, redirect audits, Core Web Vitals checks.
• Commerce stacks feel every search story. The spam update's distaste for templated, thin pages applies double to ecommerce — collection pages with boilerplate descriptions are exactly the pattern that gets classified as low-value. Good Shopify development partners earn their fee here: unique collection copy, structured data on every product, and fast templates that survive whatever Google ships next.
• One to watch as we publish: today, 29 June, SEO analyst Lily Ray spotted Google testing a Top Stories carousel inside AI Overviews — fresh news links embedded directly in AI answers. If it rolls out, it's the strongest signal yet that AI Overviews will cite timely content, not just evergreen pages. More next week.

What this week means for your website strategy

Pull the threads together and the week has one shape: the floor is rising at both ends of the craft.

• On the search end, Google is running spam classification fast enough to complete a global rollout in 48 hours. Shortcut content — scaled, templated, thin — is a depreciating asset with an enforcement date. Original content on a technically clean site is the only durable position.
• On the build end, Figma is generating code, Chrome is absorbing JavaScript patterns into CSS, and browsers ship monthly. The differentiator is no longer "can you build it" — it's judgment: what to generate, what to hand-craft, what to ship. When you evaluate a website development company or a web design and development team, ask how they use these tools and where they refuse to.
• In between sits measurement. AI visibility reports, AI referral traffic, spam-update windows — the businesses that win the next year are baselining all of it now, while the numbers are small enough to learn from cheaply.

Frequently asked questions

What does the June 2026 Google spam update target?

It's what Google calls a normal spam update — improved automated detection of spam-policy violations like scaled content, doorway pages, cloaking and expired-domain abuse — applied globally in all languages. Google confirmed it does not target link spam or site reputation abuse. It rolled out 24–26 June.

My site dropped after 24–26 June — how do I recover?

Confirm the timing in Search Console first, then audit honestly against Google's spam policies: bulk AI content, templated location pages, thin affiliate pages, sneaky redirects. Fix or remove what matches, improve what remains, and be patient — algorithmic spam recoveries usually surface only after Google reprocesses the site, often at the next spam update. There's no reconsideration request for this.

My rankings didn't move — do I need to do anything?

Nothing urgent. Take the free health check: sites that pass spam updates untouched generally have original content and clean foundations. Log your rollout-window baseline in Search Console so you can compare cleanly when the next tremor arrives.

Should my team adopt Figma's Code Layers and Motion now?

Pilot them for prototyping and motion specs — the handoff speed is real. But keep human developers as the quality gate for anything that ships, because generated code doesn't guarantee accessibility, performance or SEO-clean markup. Speed in, judgment out.

Do new CSS features like text-fit actually matter for a business site?

Yes — each one retires a JavaScript workaround, which means lighter pages, fewer layout bugs and better Core Web Vitals, all of which feed rankings and conversion. Adopt progressively with fallbacks; Safari had no stable release this month and remains the compatibility floor. If you're comparing agencies or searching "web developers near me", ask candidates which of this month's CSS features they've already shipped — it's a fast test of who keeps current.

The takeaway

A 48-hour spam update and a design tool that writes code are the same story told from opposite ends: production is getting easier, and getting away with mediocre production is getting harder. Google is automating the demotion of low-effort pages at the exact moment the tools automate the creation of them. The websites that compound from here are the ones where every generated shortcut passes through human judgment before it ships — and where structure, speed and originality are build decisions, not afterthoughts.