The search results page kept mutating this week. Google confirmed a Top Stories carousel is now live inside AI Overviews, Search Console opened up its AI performance reports, WordPress 7.1 hit Beta 1, and a batch of Chrome 150 CSS features quietly became safe to use in real client work. If you run a business website — or you're planning a website design or development project this year — here is what happened in the week of 13–19 July, and exactly what to do about each item.
1. Top Stories is now live inside AI Overviews
What actually changed
The biggest story of the week landed on Friday 17 July, when Google confirmed that a Top Stories news carousel is fully live inside AI Overviews for mobile searchers in the US. Barry Schwartz at Search Engine Roundtable had logged sightings all through the week after Lily Ray first spotted it in testing in late June — now it's official and rolled out. The carousel surfaces developing-topic articles and the user's Preferred Sources directly inside the AI-generated answer, alongside AI-generated images and a redesigned citation display.
Why a news feature matters to non-news websites
Because of what it signals: Google is treating the AI Overview as the page, not a box on the page. Fresh content, publisher links and preferred sources are being pulled up into the AI answer itself. The AI Overview is no longer a static summary that pushes your website down — it's becoming a surface your content can appear inside. For a business website, that changes the job description of every page you publish. Content that is current, specific and structured has a route into the answer; content that is generic and undated does not.
This matters most for anyone competing on commercial-intent queries — "best web design agency", "Shopify developer near me", "website redesign cost" — because those are exactly the queries where AI Overviews are expanding. The businesses that win those placements will be the ones whose sites give Google something fresh and quotable every week.
Freshness now has a doorway into AI answers. If your industry has news cycles — product launches, regulation changes, pricing shifts — publishing timely, well-structured takes gives Google something quotable. Static brochure sites have nothing to surface. A maintained insights section is no longer a nice-to-have; it's how your website design and development investment keeps earning visibility after launch.
2. Search Console's AI reports opened up to more sites
Quietly, in the same stretch, Google expanded access to the AI performance reports in Search Console and published a deep-dive help document on controlling how your content appears inside AI features. Until now, most site owners have been guessing how much of their traffic story was AI Overviews eating clicks — the industry numbers floating around suggest AI Overviews can cut organic clicks by roughly 50% on desktop and 30% on mobile for affected queries.
Why first-party data changes the conversation
You can now start separating "our rankings dropped" from "our rankings held but the clicks went to the AI answer" — two completely different problems with two completely different fixes. A rankings drop is a content and authority problem. A clicks drop with stable rankings is a SERP-real-estate problem, and the fix is getting cited inside the AI answer rather than ranked below it: clearer page structure, direct answers high on the page, schema markup, and authorship signals.
This is also the report that finally lets you defend (or question) your SEO spend with evidence. If a service page's impressions are stable but clicks have halved, no amount of "more keywords" fixes that — the page needs to become the quoted source.
Check Search Console this week for the AI performance report. If it's live for your property, baseline it now: note which pages earn AI citations and which queries trigger AI Overviews in your market. Every redesign and content decision from here should be judged against how your pages perform inside AI surfaces, not just the classic ten blue links.
3. WordPress 7.1 Beta 1 landed — with responsive block styling
On 15 July, WordPress 7.1 Beta 1 shipped, kicking off the release cycle that ends with the final version on 19 August, timed with WordCamp US. The headline for builders: the ongoing responsive styling work, which lets you style blocks per viewport directly in the editor — something WordPress developers have hacked around with custom CSS for a decade. WordPress 7.0.1, a pure bug-fix release, also went out on 9 July.
What to do if your business runs on WordPress
- Don't upgrade to the beta on a live site. Betas are where plugin conflicts show up. The gap between now and 19 August is your testing window, not your upgrade window.
- Spin up a staging copy and run the beta against your actual plugin stack — especially page builders, WooCommerce extensions and custom blocks.
- Audit your custom responsive CSS. Once per-viewport block styling ships, a lot of hand-written media queries become removable technical debt. Less custom CSS means faster pages, and page speed remains a ranking factor.
If your WordPress site has accumulated years of plugin layers and it's slower than your competitors, this release cycle is a natural moment to plan a leaner rebuild rather than another patch.
4. Chrome 150's CSS is now mainstream — and it's good for conversion-focused design
Chrome 150 went stable at the end of June, which means by this week the bulk of Chrome users are on it. Three features are genuinely useful for client work, and each one removes a piece of JavaScript or image weight from the typical marketing site:
- text-fit — headings that automatically resize to fill their container. Hero typography that used to need JavaScript libraries now works in pure CSS. Less JavaScript means better Core Web Vitals, and better Core Web Vitals mean better rankings and conversion rates.
- background-clip: border-area — clean gradient borders without pseudo-element gymnastics. Card UIs get cheaper to build and faster to render.
- AccentColor / AccentColorText — your site can pick up the user's OS accent colour, letting web apps and dashboards feel native without shipping theming code.
None of these are safe as the only implementation yet — progressive enhancement still applies, and Safari and Firefox users need sensible fallbacks — but they're now enhancements most of your visitors will actually see. This is the pattern good HTML web development follows in 2026: lean semantic markup, CSS doing the heavy lifting, and JavaScript reserved for what only JavaScript can do. Ship the modern feature behind an @supports check, keep the fallback clean, and let the browser upgrade the experience.
5. Design corner: scrollytelling wins, and the "revenue infrastructure" framing
DesignRush announced its July design award winners this week, with best website going to a scrollytelling treatment of a corporate sustainability report — long-form content turned into a scroll-driven narrative. It's more evidence that editorial storytelling and product marketing keep converging: the highest-rated web design work right now takes dense information and makes it a journey, not a wall of text.
Meanwhile, a widely-shared industry analysis published on 13 July argued that the best B2B web companies in 2026 treat the website as revenue infrastructure — engineered to convert multi-stakeholder buyers and to be found "in search and AI answers". We'd have put it less corporately, but the thesis is the one we build on: a website is a sales asset with a job description, not a digital business card. If your site can't answer "what revenue does this page produce?", that's a conversion optimization problem before it's a design problem.
What this week means if you're planning a website redesign
Put the four stories together and a clear brief emerges for anyone commissioning website design or development in the second half of 2026:
- Structure for quotability. Question-led headings, direct answers near the top of each section, and schema markup — because the AI answer is now the front page of Google.
- Build a freshness engine. A blog or insights section with a weekly cadence gives Google a reason to keep coming back — and gives AI surfaces something current to cite.
- Measure AI visibility from day one. Baseline the Search Console AI reports before the redesign so you can prove what changed.
- Spend your performance budget on CSS, not JavaScript. Chrome 150's features are another step in the platform absorbing what used to need libraries. Faster sites rank better and convert better.
- Design for the skim and the scroll. The award-winning work this month is scroll-driven storytelling, not static brochures.
- Choose your builder on evidence. Whether you're vetting a website development company for a full build or Shopify development partners for an e-commerce store, ask how they handle the items above — AI visibility, redirects, Core Web Vitals — before you look at a single portfolio piece.
Frequently asked questions
Do AI Overviews reduce website traffic?
For queries where they appear, industry studies point to roughly 50% fewer organic clicks on desktop and 30% fewer on mobile. But the loss isn't uniform — pages cited inside the AI answer can gain qualified visits. The strategic goal has shifted from "rank above the fold" to "be the quoted source".
How do I get my website featured in AI Overviews?
Make your content easy to quote: clear heading hierarchy, factual and specific statements, named authors, structured data, and fast crawlable HTML. Then use Search Console's AI performance report to see which pages are earning citations and double down on those formats.
Should I redesign my website for AI search?
Usually you need structural surgery, not a teardown: semantic HTML, question-led headings, quotable summaries, schema markup, and a maintained content section. If the site is also slow or built on a dated stack, fold that work into one redesign rather than paying twice.
How often should I publish new content?
Weekly, if you can sustain the quality. Consistency beats bursts — and with freshness now feeding AI surfaces directly, a steady cadence keeps your site eligible to be quoted.
How do I choose a website development company in 2026?
Judge them on what this week's news rewards: ask to see Core Web Vitals scores on sites they've shipped, how they structure content for AI search, and how they handle redirects during a migration. A capable website development company treats SEO as part of the build, not a separate line item added later.
What is a Shopify developer partner, and do I need one?
A Shopify developer partner is an agency or developer working within Shopify's partner ecosystem to build and customise stores — themes, apps, checkout, integrations. If your store needs more than a template with your logo on it, working with experienced Shopify development partners gets you custom work that still upgrades cleanly when Shopify ships platform changes.
The takeaway
No core update, no ranking earthquake — but the ground shifted anyway. Google spent the week rebuilding the search results page around AI answers and handing site owners the instruments to measure it. The websites that win the next twelve months are the ones publishing fresh, quotable, well-structured content on fast pages. That's not a trend response; that's just what website design and development means now.
Sources & further reading
- Search Engine Land — Top Stories roll out in Google AI Overviews
- Search Engine Roundtable — Google testing Top Stories carousel in AI Overviews
- Search Engine Roundtable — July 2026 Google Webmaster Report
- WordPress.org — What's new for developers (July 2026)
- Chrome for Developers — Chrome 150
- DesignRush — July 2026 design award winners