WordPress 7.0: What We Have Learned Since Launch

WordPress 7.0 has now been out in the wild for a little while, which means we are starting to get a clearer picture of what the update means for real websites, rather than just release notes.

When WordPress 7.0 “Armstrong” launched on 20 May 2026, it was described as the start of a new era for WordPress, with a refreshed admin experience, new design tools, improved editing controls and the foundations for future AI features.

At the time, the sensible advice for most small business website owners was not to rush the update straight onto a live website, especially where the site relies on a custom theme, important plugins, forms, ecommerce tools or bespoke functionality.

That advice still stands.

Since launch, the news around WordPress 7.0 has not suggested that business owners need to panic. It has, however, reinforced the importance of testing properly, checking theme compatibility and making sure any move to WordPress 7.0 is handled as a planned update rather than a quick click of the “update now” button.

WordPress 7.0 has not been a disaster, but it has not been a “do nothing” update either

Major WordPress releases nearly always need a bedding-in period. WordPress itself is only one part of a working website. Your site may also depend on a theme, a child theme, plugins, page templates, forms, SEO tools, security tools, hosting settings, analytics scripts, caching, WooCommerce, booking systems or other custom development.

That is why the question is not simply “does WordPress 7.0 work?”

The better question is “does WordPress 7.0 work properly with this particular website?”

For a simple website using well-maintained plugins and a modern theme, the answer may be yes with only routine checks. For older sites, heavily customised sites, or websites that rely on themes which have not yet been updated for WordPress 7.0, the answer may be that some compatibility work is needed first.

A Classic Editor hotfix was released shortly after launch

One of the more useful post-launch developments was a hotfix related to the Classic Editor. WordPress contributors reported that an issue affected users of the classic editor who had extended the post publishing panel to add extra action buttons. A hotfix was made available on 28 May 2026, with a permanent fix targeted for WordPress 7.0.1.

This is a good example of why we prefer a careful update process. Not every issue affects every website, and not every issue is dramatic, but small admin or editing problems can still matter if they affect the way a business manages its content.

At O’Brien Media, we still use and support plenty of WordPress websites where the Classic Editor, custom fields, bespoke templates or older editing workflows are part of the way the website works. Those sites need to be checked properly before being moved to a major new version of WordPress.

WordPress 7.0.1 is now scheduled

WordPress contributors have now scheduled WordPress 7.0.1 as a bug-fix maintenance release, with the general release planned for 9 July 2026.

This does not mean WordPress 7.0 is unsafe or that all sites should avoid it. It means the normal post-release process is taking place. Once a major version is used by millions of websites, smaller issues are found, reviewed and grouped into a maintenance release.

For business websites, this is another reason to avoid rushing. If your website is stable, taking a little time to check the theme, plugins and custom functionality before moving to WordPress 7.0 is usually the better route. It gives plugin and theme authors time to publish compatibility updates, and it gives website support teams time to identify anything that may need adjusting.

Theme compatibility is one of the biggest areas to check

One of the key messages since launch is that theme and plugin testing still matters. The WordPress Developer Blog has encouraged developers to test plugins and themes against WordPress 7.0, particularly where their work touches AI APIs, block registration, editor screens, design tools or accessibility.

For small business owners, that technical list can sound a bit distant, but the practical point is simple: your website theme controls a lot of what your visitors see and how your pages are structured.

If WordPress changes the way editing tools, blocks, patterns, styles or admin screens behave, the theme may need updating so it remains fully compatible. In some cases, that may simply mean applying an update from the theme developer. In other cases, especially where a site has been customised, it may mean a developer needs to make small changes to bring the theme up to date.

A useful way to think about it is like updating the operating system on a phone. The phone may be working perfectly well, but after a major system update, some apps also need updating so they continue working properly. WordPress is the system, while your theme and plugins are the apps that need to keep up with it.

WordPress 7.0 is also laying the groundwork for what comes next

WordPress 7.0 introduced foundations for AI and more advanced editing workflows, but it is clear from the WordPress 7.1 roadmap that this is part of a longer direction of travel rather than a one-off update.

WordPress 7.1 is currently planned for 19 August 2026 and is expected to continue work around collaboration, notes, responsive styling, media improvements, editor refinements and AI-related features.

That matters because it shows WordPress is moving quickly. The platform is becoming more powerful, more flexible and more complex. That is good news for businesses that want a website they can continue to grow with, but it also means website maintenance cannot be treated as something that only happens when something breaks.

Keeping a WordPress website healthy now means keeping the theme, plugins, hosting environment and custom code aligned with the direction WordPress is moving in.

What should small business website owners do now?

If your website is already managed and supported, the best approach is to let your website support team handle the update properly. That should include checking the theme, reviewing key plugins, making sure backups are in place, testing important features and only then applying WordPress 7.0 to the live site.

If you manage your own WordPress website, avoid updating your live site without preparation. At the very least, take a full backup first, check whether your theme and plugins mention WordPress 7.0 compatibility, and test the parts of the site that matter most to your business. That could include contact forms, checkout pages, booking forms, galleries, page layouts, menus, login areas and any custom features.

For WooCommerce websites, membership websites, booking websites or sites with custom integrations, testing is even more important. A broken contact form or checkout issue can quickly cost more than the time saved by rushing the update.

Our approach at O’Brien Media

For O’Brien Media customers, we are treating WordPress 7.0 as a proper compatibility update rather than a routine minor update.

The checks and subsequent installation of WordPress 7.0 are being offered as a fixed price service at £150. That covers the compatibility checks, any updates needed as part of the move to WordPress 7.0, and the installation of WordPress 7.0 itself.

We have chosen to offer this as a fixed price service rather than simply using up monthly support time, because we do not want other important work, such as SEO updates, security updates, plugin updates or general website maintenance, to be delayed or skipped.

Where there is another small update a customer would like us to look at while we are already working on the site, we will include it within the fixed price where it can be sensibly handled as part of the same work.

Our view: update, but update properly

WordPress 7.0 is an important release, and the post-launch news has not changed our view that WordPress remains a strong, flexible and future-facing platform for small business websites.

What it has confirmed is that major updates need care.

WordPress 7.0 brings useful improvements and sets the stage for where the platform is heading next. But because every business website is different, the safest route is to check compatibility before making the move.

If your website is important to your business, updating WordPress should not be a gamble. It should be a planned piece of maintenance that protects your site, keeps it secure and makes sure it is ready for what comes next.

Need help with WordPress 7.0?

If you are an O’Brien Media customer and would like us to go ahead with the WordPress 7.0 compatibility checks and update, just get in touch and we can arrange the work for your site.

If you are not currently supported by us but would like help with your WordPress website, we provide WordPress support, website maintenance, hosting and website development for small businesses across Swindon, Wiltshire and the wider UK.

WordPress 7.0 is a positive step forward. The important thing is making sure your website is ready to move forward with it.