WordPress 7.0 Is Here: What Really Matters for Your Website

Every few weeks, there's another sensational announcement—this time, WordPress 7.0. This post distinguishes between what really matters for day-to-day website management and what's only relevant to developers, and honestly explains when an update is worth it and when patience is the better choice.

Date

24.08.2026

What WordPress 7.0 Actually Is

WordPress 7.0 was released on May 20, 2026, under the code name “Armstrong,” following the tradition of naming each major version after a jazz musician. The release was originally scheduled for April 9. However, at the end of March, the Core Team extended the timeline to thoroughly revise the memory architecture for the planned real-time collaboration feature once again. This delay is, in itself, a small but positive side note: The team postponed a deadline that had already been set rather than going live with a known issue.

WordPress 7.1 “Mary Lou” has since been released (August 19, 2026); the current version is 7.1.4, dated October 28, 2026. The interim releases were by no means limited to bug fixes: 7.0.2, released on July 17, for example, addressed one critical and one severe security vulnerability. So anyone who keeps WordPress up to date is now running a version that has already undergone several bug and security fixes.

The innovations that really make a difference in your everyday life

A redesigned admin interface with a Command Palette. If you regularly manage content yourself, this is probably where you’ll notice the biggest change. You can now open the Command Palette from anywhere in the dashboard—using ⌘K or Ctrl+K, or via a new icon in the top admin bar—and jump directly to settings, posts, or features. For someone who only uses WordPress occasionally, this might seem a bit unfamiliar at first. For anyone who works in the backend regularly, it’s noticeably faster.

A visual revision view right in the editor. Changes to a post can now be tracked using a color-coded preview, similar to the track changes feature in a word processor. This allows team members working on content to see at a glance what has changed since the last version, rather than having to laboriously compare the two versions in their heads.

More flexible mobile navigation menus. So-called navigation overlays make it possible to customize the behavior and appearance of mobile menus much more extensively than was previously possible without additional extensions. For websites that previously had to make do with the limited standard options, this is a tangible improvement that is truly noticeable.

New breadcrumb and icon blocks. These are small but handy additions that let you insert navigation paths and icons directly in the editor without needing an additional plugin. Every plugin you can do without means one less potential security and maintenance risk—even if the individual impact here is small.

Dynamic data views in administration. The data views (DataViews) that underpin the newer administration screens have been given new layouts. However, this does not yet fully replace the classic post and user lists in version 7.0. Users who manage a lot of content can find what they're looking for more quickly without having to scroll through multiple pages.

The new features that are more relevant to developers and agencies

PHP-only blocks. Until now, developing custom blocks for the editor almost always required knowledge of React, a JavaScript library that many traditional WordPress developers have never learned. With WordPress 7.0, simpler blocks can now be built without React. This significantly lowers the barrier to entry for custom development, but primarily affects those who build websites from a technical standpoint, not those who later maintain them editorially.

The new AI infrastructure at the core. With the WP AI Client, a central Abilities API, and a Connectors Hub, WordPress is creating—for the first time—a unified interface through which external AI providers and plugins can be integrated in a standardized way. Previously, each AI plugin had to provide its own, often incompatible, integration method. This standardization is particularly relevant for developers who integrate AI features into websites, rather than for day-to-day use of the site itself.

New developer APIs and performance optimizations in the core. For agencies and developers, this means faster, cleaner code in several parts of the system. For website operators, the impact is indirect at most—for example, because images are now processed directly in the browser, reducing the load on the server.

What Was Cut, and Why That's Good News

Originally, WordPress 7.0 was supposed to include a feature for real-time collaboration in the editor, similar to the simultaneous editing of a document as seen in modern word processing programs. This feature was removed shortly before the release. The decision was made by WordPress co-founder Matt Mullenweg on May 8, just under two weeks before the release. He cited the excessive vulnerability—so-called race conditions, in which two simultaneous changes can overwrite each other—as well as server load, memory consumption, and recurring errors from automated tests.

From a marketing perspective, the scrapped feature is frustrating because it was touted as a major highlight in many advance announcements. From a practical standpoint, however, the decision is absolutely the right one. A half-baked collaboration feature that could lead to data loss or overwritten content would pose a greater risk to any website than a missing—but previously announced—feature. Better to have a feature later that actually works than one now that occasionally messes up content. Real-time collaboration is still missing in WordPress 7.1 as well. According to the Core Team, a new approach is still in its early stages and will first be tested as a standalone plugin.

For companies that rely on multiple editors or external copywriting agencies, an unreliable collaboration feature would have been a double-edged sword anyway. The tried-and-true—albeit slightly less convenient—method of working with individual drafts and clear approvals will remain in place for the time being, which, when in doubt, is more important for the reliability of content than the convenience of simultaneous editing.

Should you update now?

One important technical change concerns the minimum requirements: WordPress 7.0 requires at least PHP 7.4. Anyone still running an older version of PHP must first adjust their hosting package before updating, which in many cases is straightforward but not automatic. Websites running on PHP 7.2 or 7.3 will remain on the 6.9 branch. However, only the current version of WordPress is officially supported; security fixes for older branches are only available if the team voluntarily backports them. In any case, PHP 8.3 or higher is recommended.

For most corporate websites, we don’t recommend updating immediately on the release date; instead, we suggest waiting a few weeks until the most important plugins and themes have been updated to support the new version. WordPress 7.1 is now the latest version. The best way to check if your plugins are compatible is to review the changelog for each plugin. Before any update, however, you should always test it in a staging environment to verify that all active plugins and customizations continue to function properly before applying the update to the live website.

This caution has nothing to do with skepticism toward WordPress itself, but rather with the simple fact that every update runs on thousands of completely different website configurations, none of which exactly matches one’s own. What works smoothly on a test site can still cause problems on another site with a different combination of plugins and custom code. Waiting a bit after the release date costs nothing but a little patience, but it noticeably reduces the risk.

A real-world example

For a client project involving several active plugins, including an older booking system, we first performed the update to WordPress 7.0 on a test copy of the website. We discovered that this particular booking plugin did not initially function properly with the new version—a conflict that would have directly resulted in failed booking requests on the live site.

The plugin developer had already announced an update at that point but had not yet released it. We therefore deliberately postponed the update by two weeks until the compatible plugin version was available, rather than risking a breakdown in the booking functionality. On the live site, the customer didn’t notice anything about this entire process, except that at some point a new backend became available that ran noticeably more smoothly than before. That is precisely the difference between a planned update and a rushed one.

Looking back, the actual value of those two weeks of waiting was hardly measurable, because nothing visible happened. That’s exactly what often happens with a sound technical approach: Success isn’t manifested as a spectacular event, but rather as the absence of a problem that would otherwise have arisen. For the customer, this ultimately meant a seamless transition—without a single missed booking and without a single concerned call to support—even though a potentially serious disruption had indeed been averted behind the scenes.

Why Release Lists Often Set the Wrong Priorities

Almost every announcement of a new WordPress release follows the same pattern: a long list of features, sorted by how technically impressive they are, not by their actual usefulness for a company’s website. The AI infrastructure in the core is hailed in most articles as the biggest highlight of WordPress 7.0, yet in practice it affects almost exclusively developers who want to integrate their own AI features. The revamped revision view, on the other hand—a comparatively unspectacular feature—actually changes the day-to-day workflow for many editorial teams.

This distortion isn't a coincidence. Technical innovations are easier to package into an impressive headline than small but effective improvements to everyday workflows. When deciding whether an update is worth it, the length of the official feature list is less helpful than asking who in your company actually works with WordPress and what that person really needs on a day-to-day basis.

Those who don't let themselves be swayed by this and instead use their own processes as a benchmark will ultimately arrive at a much more accurate assessment than any general list of trends could provide.

What You Should Check Before an Update

Before an update is even considered, it’s worth doing a quick, structured check that can be completed in just a few hours:

Is the website currently running on at least PHP 7.4, or does the hosting package need to be updated first?
Have all actively used plugins already been officially confirmed as compatible with WordPress 7.0?
Are there any customizations to the theme or custom developments that need to be tested separately?
Is there a recent backup of the entire website that can be used in case of doubt?
Is there a staging environment available where the update can be safely tested before it goes live?

If you go through these five points before an update, you’ll significantly reduce the risk of unpleasant surprises, regardless of how extensive the release actually is. Incidentally, this checklist applies not only to WordPress 7.0, but to virtually every major update that follows in the coming years, no matter how big or small the individual changes may be.

The difference between a major release and subsequent patch versions

One point that is often overlooked when deciding whether to update: The first version of a major release—in this case, 7.0.0—is rarely the most stable. In the weeks following every major WordPress release, there are typically several patch versions that fix minor but important bugs that only become apparent once the release is widely deployed across thousands of different websites. That’s exactly what happened with WordPress 7.0: On July 9, version 7.0.1 was released with 31 bug fixes, followed by primarily security updates up through version 7.0.8.

For a corporate website, where downtime or display errors can directly cost the company inquiries, this difference is crucial. Those who wait to apply the update until after one or two patch versions have been released benefit from the experience of all the websites that updated before theirs, without becoming a testing ground themselves. This small amount of patience costs practically nothing and significantly reduces the risk.

Conclusion: A useful update, but no need to rush

WordPress 7.0 brings real improvements, especially for anyone who regularly works in the backend or has custom features developed. For the day-to-day operation of a corporate website, a major version update isn’t a must on release day. The situation is different with security updates like 7.0.2 or 7.1.4: You should install these promptly; WordPress itself recommends updating immediately. Waiting a few weeks, testing in a staging environment, and checking the compatibility of your own plugins will provide significantly more security than rushing the update.

In the end, what matters isn't so much how many features a new release brings, but how smoothly the transition goes for your own website. An update that nobody notices is usually a good update. One that everyone talks about afterward usually isn't.

Not sure if your WordPress website is ready for the update?

We'll check your plugins and customizations for compatibility and give you an honest assessment of whether it's worth updating now or if it makes more sense to wait a little longer. Just send us a quick message using the contact form. We'll respond within 24 hours—personally and without any sales pitch.

Sources

Official WordPress releases, verified on November 4, 2026.

Practical knowledge on web design, SEO, AI, and conversion optimization. Based on real projects, without any marketing spin.

View all articles

03.11.2026

Headless CMS for Businesses: When It's Worth It and When It Isn't

When a headless CMS like Storyblok, Contentful, or Sanity makes sense for businesses, and when a traditional system is a better fit: featuring prices as of October 2026, case studies, a decision tree, and an Excel template for comparing CMS platforms.

Technology & Systems

22.10.2026

PHP2Shell: How to Check If Your Website Is Secure (with Instructions for IONOS, STRATO, ALL-INKL, and Others)

The BSI is warning of two critical vulnerabilities in PHP that are not addressed by any WordPress update. We’ll show you how to find your exact PHP version, how to change it with IONOS, STRATO, ALL-INKL, and six other hosting providers, and what to tell your hosting provider.