WordPress 7.1 "Mary Lou": What It Actually Changes for Your Business Website

WordPress remains the workhorse of the business web, which means a major release is one of the few software updates that quietly touches millions of businesses at once. WordPress 7.1 "Mary Lou" shipped on 19 August 2026, and now that the first wave of plugin-compatibility dust has settled, it's a good moment to ask the only question that matters to a site owner: what does this release actually change for you?

Quite a lot, it turns out — less in flashy features, more in the removal of long-standing frictions that have been costing businesses money in small, recurring ways.

Responsive styling without custom CSS

The headline feature is responsive style states: you can now apply different styles to blocks at different screen sizes, with viewport previews, directly in the editor — no custom CSS required. Hover and focus styling for buttons and navigation come with it.

If that sounds minor, consider what it replaces. Until now, making a section behave differently on mobile — tighter spacing, a different font size, a hidden decorative element — usually meant a developer writing custom CSS, which then lived outside the editor where your marketing team couldn't see or safely change it. Over years, sites accumulate layers of these one-off fixes.

Practical implication: some portion of the custom CSS in your theme is now technical debt that could migrate into native controls — worth doing at your next design refresh, because native controls survive theme changes and staff turnover far better than bespoke code.

The new media workflow: faster pages, lighter servers

Two media changes matter. A new media editor consolidates cropping, flipping, rotating and metadata editing in one place — a small dignity for anyone who updates product images weekly. More consequentially, image compression, resizing and thumbnail generation now run in the browser rather than on your server, with broader format support alongside it.

For a content-heavy business site this is a real performance story. Server-side image processing has long been a source of slow uploads, timeout errors on shared hosting and bloated media libraries. Browser-side processing means smaller files with no visible quality loss — and image weight is typically the single largest contributor to slow pages. We've written before about why performance is a sales problem, not an engineering vanity metric; this release moves the baseline in your favour without you paying for it.

One caution: if your site relies on plugins that hook into the old upload pipeline — watermarking, CDN offloading, custom thumbnail sizes — have a developer verify behaviour before assuming everything transferred cleanly.

Collaboration your content team will actually use

7.1 upgrades Notes to support inline notes with @mentions and rich text at block level. Combined with the admin bar now appearing consistently across editors, review workflows that used to happen in email threads and screenshots ("the second paragraph on the About page — no, the other one") can move into the page itself. There are also new content blocks that reduce the need for third-party plugins in common cases. Every plugin you can retire is one fewer update to manage and one fewer security surface.

Accessibility improvements are compliance improvements

The release includes improved screen reader support and better keyboard navigation. As we argued in our accessibility piece, accessibility has become infrastructure: a growing share of procurement, legal exposure and search visibility depends on it. Core-level improvements raise your floor for free — but they don't audit your theme, your colour contrast or your forms. 7.1 is a tailwind, not a substitute.

The dates to plan around

WordPress 7.2 reaches Beta 1 on 20–22 October 2026, with final release scheduled for 8–10 December (Make WordPress Core). For a business site that suggests a simple rhythm:

• October. If you haven't updated to 7.1, do it on a staging copy first with a plugin-compatibility check — the media pipeline changes make this a release where testing earns its keep.
• November. Use the pre-7.2 window to clear plugin and theme updates, retire anything unmaintained, and migrate quick-fix CSS into native responsive controls.
• December. Don't update to 7.2 on day one unless you have staging and backups; let the first point release land.

A site that follows this rhythm twice a year avoids the two expensive failure modes we see most: sites frozen on old versions until an emergency forces a risky jump, and sites auto-updating everything with no testing and discovering breakage from customer complaints. It's the same argument we made when Chrome moved to a two-week release cycle — the modern web platform ships continuously, and "finished" websites are a fiction.

Do you need to do anything today?

If your site is professionally maintained: confirm you're on 7.1, ask what broke (the honest answer is rarely "nothing"), and ask whether browser-side image processing changed your upload workflow. If you maintain it yourself: back up, update staging, click through your money pages — home, top services, contact, checkout if you have one — and only then update production.

And if nobody currently owns this — if your website was built two years ago by an agency you no longer talk to — that's the actual finding of this article. The platform is improving fast; unowned websites don't get to benefit.