WordPress 7: new features for companies

WordPress 7 was released on May 20, 2026 under the name “Armstrong”. For companies, the release is relevant because it bundles several important developments: AI integrations are given a more structured foundation, the admin experience becomes more modern, the editor receives new design and navigation tools and developers get additional APIs for more demanding projects.

At the same time, WordPress 7 is not an update that should be pushed untested to every business-critical website. Many changes affect the editor, dashboard, block features, external connections and technical foundations. Anyone running a company website, WooCommerce shop or individually developed WordPress system should therefore classify the release, test it and only then roll it out to production.

WordPress 7 is officially released

The official WordPress documentation lists May 20, 2026 as the release date of WordPress 7.0 “Armstrong”. The release page and the announcement on WordPress.org also confirm the update. The originally planned April date had previously been moved because the release team needed more time for architecture and stability questions.

This history matters: WordPress 7 was not just a routine feature update, but a larger development step. The project page on Make WordPress Core describes 7.0 as the first major release of 2026. After the postponement, additional release candidates were planned before the final version was published.

For website operators, this means: the final version is available, but a controlled update process remains essential. Especially websites with custom themes, many plugins or custom block development should test WordPress 7 in a staging environment first.

The most important new features in WordPress 7

WordPress 7 brings many detailed improvements. For companies, the most relevant changes are those that affect editorial work, website design, update risk or technical extensibility.

Area	What is new	Why it matters
AI foundations	AI Client, Connectors and Abilities approaches	Plugins and workflows can use AI integrations in a more structured way.
Dashboard	modernized admin interface and Command Palette	Editors and administrators can reach functions faster.
Design	new blocks and expanded block tools	Pages can be designed more flexibly in the editor.
Navigation	editable Navigation Overlays	Mobile and more complex menus become easier to control.
Revisions	more visual revision view	Content changes can be reviewed more clearly.
Performance	more precise prioritization of image and block resources	Hidden elements should interfere less with critical resources.
Development	PHP-only block registration and new editor foundations	Custom block and plugin development becomes more flexible.

Many of these points will not be visible on every website automatically. A classic theme without heavy use of the block editor benefits differently than a company with full-site editing, custom patterns and active editorial workflows.

AI foundations: important, but not automatically a finished AI website

The official announcement describes WordPress 7 as the start of a new foundation for AI across the WordPress experience. Specifically, this includes an AI Client in Core, a more central way to manage external connections through Connectors and the combination with the Abilities API. An optional AI plugin is also mentioned, extending features such as title generation, excerpts, image generation, image editing or alt text suggestions.

This is strategically relevant, but it should not be misunderstood. WordPress 7 does not make every website automatically AI-powered. Instead, it creates a technical foundation that allows plugins, themes and workflows to connect to AI models more consistently in the future.

For companies, this raises three practical questions:

Which AI features are genuinely useful and not just a novelty?
Which external providers are connected and how are accesses managed?
How are data protection, rights, approvals and editorial quality secured?

For company websites, AI inside the CMS is only helpful when processes remain clear. Automatic text or image suggestions need review. Alt texts need editorial quality. External services must be assessed from a data protection and technical perspective. In more complex setups, custom WordPress development can be useful so that AI features are not scattered across many unrelated plugins.

More modern dashboard, Command Palette and Font Library

WordPress 7 modernizes the admin experience. The release announcement mentions a new color scheme, revised controls, smoother transitions between views and visible access to the Command Palette through the upper admin bar. For editorial teams, this is less spectacular than an entirely new feature, but it matters in everyday work: frequently used functions become easier to reach.

The Font Library for all themes is also important. According to the feature showcase, font management no longer works only in block themes, but also in other theme contexts. This can help brand websites because fonts can be managed more directly within the WordPress environment.

Still, companies should remain cautious here. Font management in the backend does not replace a brand and performance strategy. Too many font weights, external sources or unchecked font files can affect loading times and data protection. Existing company websites should therefore check whether the new font management fits the current theme architecture or whether fonts should continue to be maintained centrally in the theme or build process.

New design and editor tools

For editorial and design work, WordPress 7 brings several noticeable extensions. The official sources mention, among other things, a Breadcrumbs Block, an Icons Block, new design controls, responsive visibility for blocks, visual revisions and improved pattern editing. Patterns can be treated more strongly as one unit, so editors do not always have to navigate deeply nested block structures.

Responsive block visibility is especially interesting. Content can be shown or hidden depending on screen size. This can simplify mobile layouts, but it also brings risks: when teams maintain desktop and mobile content separately, duplicate content, inconsistent messaging or forgotten updates can quickly appear.

For companies, these functions should therefore not be treated as permission for arbitrary layout variants. They are useful when clear component rules exist:

Which content may differ by device?
Which blocks are editorially flexible and which belong to the design system?
How are accessibility, heading structure and SEO checked?
Who reviews mobile states before publication?

If a relaunch is being planned, these new editor features should be considered early in website conception. That way, design system, editorial logic and technical implementation can be planned together.

One notable point in WordPress 7 is stronger editing of Navigation Overlays. The feature showcase describes a dedicated area where menus can be built with blocks and patterns. Instead of maintaining only lists of links, teams can design more complex mobile or visual menus.

For simple websites, this can be helpful. Larger company websites need clear limits. Navigation is not a decorative area, but a central element of user guidance. Too many columns, effects or editorial exceptions can make orientation worse.

Before using the feature, companies should check:

Is the main navigation still understandable?
Does the menu work with keyboard and screen readers?
Is mobile use still fast and clear?
Are important pages internally linked well enough?
Does the overlay fit the existing information architecture?

Especially for larger websites, it is worth looking at existing content, search intent and internal links. A new menu feature does not replace structural planning.

Illustration of a WordPress update checklist with staging, backup, plugin check and live approval

Performance, accessibility and update checks

According to the feature showcase, WordPress 7 also brings performance and accessibility improvements. On the performance side, this includes more precise image loading prioritization, more reliable on-demand loading of block stylesheets in classic themes and new possibilities for script dependencies. For operators, this does not automatically mean that every website becomes faster. It does improve the technical basis on which themes and plugins work.

For accessibility, the official overview names improvements in media management, Voice Control usability, contrast in the new admin color scheme as well as editor navigation and interaction. This is positive, but it does not replace checking the actual website. Accessibility still depends heavily on theme, content, forms, contrasts, focus states and components.

After the update, business-critical websites should at least check:

central page types in the frontend
mobile navigation and menus
forms, error messages and consent banners
Core Web Vitals and visible layout shifts
backend workflows for editors and administrators

If performance fluctuates after an update, targeted performance optimization is more useful than generic plugin tuning. The important question is the cause: theme, images, caching, scripts, database, external services or plugin conflicts.

What is not included in WordPress 7: real-time collaboration

One important point for classification: Real-Time Collaboration was a major topic during development, but it was removed from WordPress 7 before the final release. The WordPress Developer Blog names concerns around interface, race conditions, server load and memory efficiency as well as recurring errors from tests.

This is not a failure of the whole release, but a deliberate stability decision. For companies, this information matters because some early beta reports still referred to shared live editing. In the final scope of WordPress 7.0, this feature is not included; companies that need collaborative live editing must continue to use separate workflows or watch later WordPress versions.

Update plan for company websites

WordPress 7 is a major release. Even if many websites can install the update without major problems, the process should be controlled. For company websites, Bajorat Media recommends a pragmatic workflow:

Document current WordPress, PHP, theme and plugin versions.
Create a complete backup and clarify the restore path.
Test the update first in WordPress staging.
Check backend workflows, editor, navigation and central templates.
Test forms, search, login, cart or checkout.
Compare performance and visible layout changes.
Fix issues or postpone the update.
Run the live update in a suitable maintenance window.
Follow up with WordPress monitoring and a visual check.

For individually developed themes, many custom blocks, WooCommerce, multisite or complex integrations, a WordPress inspection is also useful. It shows whether technical debt, plugin dependencies or editor customizations should be cleaned up before the update.

Conclusion: WordPress 7 shows direction, but updates need process

WordPress 7 is an important release because it clearly shows the direction of the CMS: more structured AI integration, a more modern admin experience, more design control in the editor and additional foundations for developers. For companies, this is useful when these possibilities are embedded into clear website processes.

The most important recommendation is therefore not “click update immediately”, but controlled testing. Anyone operating WordPress professionally should combine major releases with backup, staging, functional testing, performance review and follow-up checks. Then WordPress 7 does not become a risk, but a useful reason to bring the website forward technically and editorially.

Solutions

Web Design & General

WordPress & WooCommerce

Online Marketing

WordPress 7: new features and what companies should check now