WordPress 7.0 'Armstrong' Released With Core AI

Version 7.0 is the largest core release WordPress has shipped in several years. It treats generative AI as a first-class capability rather than a plugin afterthought, and it pairs that with a modernised admin theme, a Command Palette, font management, and an extensible Site Editor. The release squad credits more than 875 contributors and over 200 first-time contributors with the work that went into it.

For UK site owners and agencies, the practical question is not whether to upgrade, but how soon, and which plugin and theme combinations need re-testing before pushing 7.0 to production. The headline features carry implications for editorial workflow, performance, accessibility, and security review cycles.

How it works

The centrepiece of 7.0 is the new AI Client in core, paired with an Abilities API. The AI Client provides a standard way for WordPress to communicate with generative AI models, while the Abilities API exposes a server-side contract that plugins, themes, and core features can register against. Connections to external providers are managed from a single hub on the Connectors screen, which ships with three presets and supports custom additions.

A separate Client-Side Abilities package brings the same surface to JavaScript. It includes a built-in UI and a Command Palette, accessible via Ctrl+K (Windows) or ⌘K (Mac), that lets editors trigger AI abilities and admin actions from anywhere in the dashboard. The optional AI plugin extends the default ability set with image generation, image editing, title and excerpt drafting, and alt-text suggestions, all driven by the connected model.

Around the AI layer, 7.0 introduces a refreshed admin theme with a new colour scheme and smoother transitions, a dedicated font management screen that works across block, hybrid, and classic themes, and a visual revision browser that lets editors scrub through versions before restoring. The block editor gains a Heading block refresh, a new Breadcrumbs block, an Icons block, a Gallery lightbox slideshow, and responsive controls that hide or reveal blocks per device breakpoint, with breakpoints themselves now customisable.

Use cases for agencies and merchants

The AI Client and Abilities API change what is possible inside the WordPress admin without leaving the dashboard. An editorial team can generate a draft excerpt or alt text against a model the agency has connected and audited, instead of pasting content into a separate tool. A site builder can register a custom ability that calls an internal product-knowledge model, then surface it via the Command Palette so editors trigger it the same way they would any other admin action.

The new Breadcrumbs block fills a long-running gap: site owners no longer need a third-party plugin or theme-level template work to get a configurable breadcrumb trail. For UK retailers running large product or service hierarchies, that removes a small but persistent piece of plugin debt. The Icons block reduces dependence on custom SVG includes for the same reason.

Responsive visibility controls inside the block editor mean a campaign landing page can show a heavier promotional layout on desktop while serving a leaner mobile variant, without spinning up a separate mobile template. Combined with custom block-level CSS, in-place pattern detachment, and the styled menu overlay, the practical effect is that designers can ship more polished pages with less reliance on bespoke theme code.

What this means for UK site owners

The most consequential change for UK businesses running WordPress is not visual: it is the AI Client itself. From a governance perspective, having an authenticated, managed connection layer inside core is a significant improvement over plugins that bolt on AI features with their own credential handling. It also raises questions that UK businesses will need to answer before flipping the feature on, particularly around data residency, model selection, and what prompts may be logged by the provider. The ICO's published guidance on AI and data protection is the right reference point when defining an internal policy.

For agencies, 7.0 is an opportunity to move clients off ageing plugin stacks. Several of the features now in core (breadcrumbs, icons, font management, gallery slideshow, responsive visibility) have historically required a paid plugin, a page builder, or theme customisation. Auditing client sites against the new core feature set after the upgrade often reduces the maintenance surface and improves performance, because each removed plugin is one fewer database query and one fewer attack vector to monitor. For PPC-led businesses, the responsive controls and styled menu overlay also make A/B testing of landing-page layouts noticeably easier, which feeds into how we structure Google Ads campaigns and conversion tracking.

The redesigned dashboard and Command Palette will be visible to every editor and contributor on the team. For multi-author UK publishers, this is worth communicating ahead of the upgrade, with a short internal note covering the keyboard shortcut, the new font screen, and the revision-browser change so editorial workflows are not disrupted on the morning of the update.

Practical considerations

WordPress 7.0 is a major version bump, not a maintenance release. Plugin and theme compatibility should be confirmed in a staging environment before pushing to production, particularly for sites running page builders, ecommerce plugins such as WooCommerce, or membership platforms with their own admin extensions. Backwards-incompatible changes are documented in the Field Guide, and any plugin that has not been updated in the last twelve months is worth flagging for review.

The AI Client is opt-in: it does not start communicating with external providers until a connection is configured on the Connectors screen. That said, the AI plugin and any third-party plugin that registers abilities will need explicit permission scoping, and the credentials used to authenticate connections should be treated with the same care as any other API key. For sites that handle personal data, the choice of provider and the contract that sits behind it matters as much as the technical setup. The data-protection guidance from the Information Commissioner's Office is the right starting point for that policy work.

Caching and performance are the other practical hurdles. Object caches, full-page caches, and CDNs should be flushed after the upgrade to avoid stale admin assets being served to logged-in editors, and the staging-to-production cutover is a good moment to revisit cache lifetimes if they have not been reviewed in the last twelve months. Sites running custom server-side caches or reverse proxies should test the Command Palette and the Connectors screen specifically, since both load assets that previous versions did not request. The Field Guide includes performance-oriented notes that are worth a read before scheduling the upgrade window.

Finally, agencies running multiple client sites should stagger the rollout. Upgrading every client estate in the same week creates a single point of failure if a plugin author has not yet shipped a 7.0-compatible build. A two-phase rollout (low-traffic sites first, then higher-traffic estates a week later) gives the plugin ecosystem time to catch up and reduces the support load on the team during the upgrade window.

FAQ