What’s New in WordPress 7.0: Native AI for Marketing

The short version. Here’s what’s new in WordPress 7.0 ‘Armstrong’, which went live on 20 May 2026. The headline change: native AI is now built into the platform itself. WordPress core handles the connections to AI services, so you bring OpenAI, Anthropic, Google, or whichever provider you fancy, and the same connection layer routes everything. A separate, optional plugin adds the bits content teams will actually use day-to-day. Image generation, alt text, draft titles and excerpts, that sort of thing. Real-time co-editing was meant to headline the launch but didn’t make the cut and will turn up in a later release. PHP 7.4 is now the minimum; 8.3 is what the project recommends running. What follows is the version of all this that marketing directors and brand owners need.

AI in WordPress has, for the past three years, meant one plugin per feature: each vendor with its own provider, its own settings page, and (usually) its own invoice arriving every month. 7.0 is the release that dismantles that pattern. The platform now ships with the connection layer, the shared vocabulary plugins use to expose their capabilities, and a single admin screen for managing AI providers. For UK marketing teams already paying for half a dozen AI subscriptions on top of WordPress, the consolidation has started. Worth understanding now rather than at renewal time.

Matias Ventura led the release, with more than 875 contributors and over 200 first-timers landing 420 enhancements across Core and Gutenberg. WordPress itself describes 7.0 as marking ‘the start of a new era, laying the foundation for AI across the WordPress experience’. The direction couldn’t be clearer.

Below: what’s new in WordPress 7.0 through a marketing operations lens, what’s been held back, and what to put on the agenda with your agency or in-house developer this week.

What’s New in WordPress 7.0: The AI Changes at a Glance

A scan of the AI changes, before we get into the detail:

• AI provider connections (OpenAI, Anthropic, Google, or custom) are now managed from one admin screen at Settings > Connectors.
• The WP AI Client is a built-in connection layer plugins use to talk to AI services without each having to carry its own credentials.
• The Abilities API: a shared way for plugins to publish what they’re capable of, so AI tools can call on those capabilities instead of each one duplicating the same work.
• A separate optional AI plugin (manual install) layers on the visible features: image generation and editing, suggested titles and excerpts, drafted alt text.
• Nothing AI-related runs until an administrator switches it on. A stock 7.0 install is no more AI-active than a stock 6.9 install.

What Counts as ‘Native AI’ in WordPress 7.0?

Three pieces of core code, working together. The WP AI Client does the actual talking to AI services. The Abilities API gives plugins a common way to publish what they’re capable of. And the Connectors hub is the single admin screen where providers get configured, keys get pasted in, and features get switched on. Anything you read about ‘native AI in WordPress 7.0’ refers to one or more of those three. Together, they retire the old approach of one plugin per AI feature, each with its own vendor relationship.

Why Does AI in WordPress Matter for My Business?

Because AI control is now centralised. Before 7.0, AI policy on a WordPress site was distributed across plugin settings pages, each with its own credentials and commercial terms. After 7.0, you make one decision about provider and policy. That decision then propagates to every compatible plugin. For marketing teams that have been quietly adding AI features one at a time, the consolidation makes audit, governance, and cost control practically possible for the first time.

How Does the WP AI Client Work?

Easiest way to picture it: a translator. The WP AI Client introduced in ‘Armstrong’ takes whatever’s coming from your installed plugins and converts it into the right shape for whichever AI service you’ve connected. Anthropic, Google, OpenAI, your own custom endpoint, it doesn’t matter; from the dashboard’s perspective, they all look identical. Plugins talk to the AI Client. The AI Client handles the routing.

For a marketing team, the practical consequence is provider portability. The agency can switch the AI provider behind any feature without rebuilding it, and individual plugins no longer need their own credentials, settings, or subscriptions. If your team has been signing AI vendor contracts with one eye on a future where the market moves faster than you can keep up, the AI Client makes that future a lot less painful.

What Is the Abilities API?

The Abilities API is a shared vocabulary plugins use to declare what they’re good at, so AI tools and other plugins can act on those declarations in a coordinated way. A booking plugin can announce ‘I can check availability for these dates’. An SEO plugin can announce ‘I can suggest a meta description for this page’. AI features built on top can then call those abilities, rather than each plugin reinventing the same logic from scratch.

The server-side foundations arrived in WordPress 6.9 in December. As the WordPress 7.0 Field Guide details, 7.0 adds the JavaScript counterpart, with a built-in UI and command palette of its own, allowing AI features to actually understand the specific site they’re running on. For business websites, the long-term consequence is groundwork for AI features that operate on real site data, not generic text generation with no context.

The Connectors Hub: One Screen for AI Policy

It lives under Settings > Connectors in the WordPress admin. As laid out in the WordPress 7.0 Field Guide, three providers come pre-registered out of the box: OpenAI, Anthropic, and Google. Each has its own official provider plugin on WordPress.org, maintained by the core team: AI Provider for Anthropic, AI Provider for Google, and AI Provider for OpenAI. You paste an API key once, and every compatible plugin on the site uses that connection through the AI Client. One credential, one provider choice, everywhere.

For agencies running multiple sites, and for marketing teams setting AI policy across a brand, the Connectors hub is the screen where policy gets enforced. One set of decisions, in one place, instead of thirty plugin settings pages scattered across the admin.

Is WordPress 7.0 AI on by Default?

No. The infrastructure is in the codebase, but it stays dormant until someone with admin rights switches it on. Think pipes laid down without the water turned on. Upgrade a site and walk away, and nothing AI-related fires: no copy gets drafted, no data gets pushed to a provider. Someone with admin access has to add credentials, set up a connection in the Connectors screen, and toggle features on individually. A stock 7.0 install with no extras behaves the way 6.9 did.

A separate, optional AI plugin extends the experience further, with image generation and editing, title and excerpt generation, and alt-text suggestions. That plugin is a manual install. It is not bundled with WordPress.

Commercially, the opt-in posture matters. For UK businesses bound by UK GDPR and a stack of client data protection agreements, the infrastructure is there when the organisation is ready to use it, and absent until then. Analysis: marketing teams can plan AI adoption on their own timeline, rather than reacting to features that have been activated without consultation.

What the Optional AI Plugin Actually Does

The optional AI plugin adds practical content-team features, all of which rely on a Connectors hub provider being configured first. It does the user-facing AI work: generating and editing images inside the media library, suggesting titles and excerpts while you draft a post, drafting alt text for images. None of which is new in itself. Third-party plugins have offered the same features for years now. What’s new is the wiring. Everything runs through the platform’s own connection layer, so swapping the provider (from OpenAI to Anthropic, say) is a settings change rather than a project.

What Else Shipped in 7.0

The rest of the release is supporting cast for the AI story, but it deserves a quick tour because some of it lands the same week as the AI changes:

• ‘Modern’ admin dashboard: a new colour scheme officially named ‘Modern’, with smoother view transitions between screens.
• Command Palette: a keyboard shortcut (⌘K on Mac, Ctrl+K on Windows or Linux) that pops up a search bar at the top of the screen. Type roughly what you’re after; fuzzy matching forgives typos and gets you to any admin page, draft post, or registered command. An icon sits in the upper admin bar for users who forget the shortcut.
• Font Library: a dedicated font management page that works across block, classic, and hybrid themes.
• Visual revisions: a slider-based, side-by-side comparison of post versions, with summaries and clickable change markers.
• Four new blocks: a dedicated Headings block, native Breadcrumbs, built-in Icons, and an upgraded Gallery block with lightbox slideshow support. The Cover block also gains video background embeds.
• Block-level custom CSS, customisable mobile navigation overlays, and block visibility by device.
• DataViews and DataForms: new Activity and Details layouts, an improved modal appearance, and the ability to register third-party types in the Field API. This is gradual modernisation of the admin layer, and it changes underlying components that some plugins customise.

The Plugin Compatibility Question You Need to Ask Your Agency

Plugins that customise the admin list and form screens (Posts, Pages, Users) face the highest compatibility risk in 7.0, because of the underlying DataViews and component changes. Anything that adds columns, custom filters, or bulk actions to those screens needs testing on staging before you go anywhere near the production update. That’s the one to put at the top of the agency conversation this month.

Real-time co-editing, the Google Docs-style feature most editorial teams were watching for, didn’t survive the final fortnight. The release squad pulled it on 8 May, twelve days before launch, after stability problems they couldn’t fix in time. The team chose to rebuild it rather than ship something half-baked. Block-level comments and presence indicators, both introduced in 6.9, remain in place. Over on Make WordPress Core, 7.1 is now flagged as ‘the current release in progress’. The project usually ships three majors a year, which would put the next one somewhere later in 2026, though there’s no firm date yet.

What This Means for Marketing and Business Owners

Brand Voice and AI Content Governance

The new AI infrastructure doesn’t produce content on its own. What it does is make life much easier for plugins and tools that want to draft copy, write alt text, suggest titles, or knock out excerpts in your brand’s voice. Which puts a fairly pointed question in front of marketing directors: who’s allowed to use it, who reads what it produces, and who signs the thing off before it appears on a page your customers actually see.

Treat this as policy work, not technology work. Pick the provider. Define the channels where AI assistance is permitted. Name the reviewer. Write the off-limits list for pages where human authorship is the rule. A short document is enough. That work is now overdue.

Vendor and AI Subscription Consolidation

Most marketing teams already pay for AI tools on top of WordPress: copywriting subscriptions, image generators, SEO suggestion plugins, alt-text tools. The Connectors hub and the Abilities API will, over the next twelve to eighteen months, fold many of those tools into the WordPress install itself. Some will remain useful, some will overlap. Analysis: an audit by the end of 2026, of which AI tools are still earning their place, is the work most marketing teams aren’t yet thinking about. Worth scheduling now.

Data Handling and UK GDPR

The Connectors hub raises live data protection questions. Which provider holds the credentials. Where the content gets sent for processing. What gets logged, and who has access. If you’re a UK organisation working under UK GDPR and the Data Protection Act, those answers sit firmly with your DPO or in-house counsel, not whoever happens to be installing plugins on a Wednesday afternoon. The AI Client also gives you the architectural option of routing AI traffic through a UK-region provider where that’s a client or compliance requirement, which the previous plugin-based approaches couldn’t always offer.

Hosting and PHP

7.0 raises the PHP floor to 7.4 (up from 7.2.24 in 6.9), with 8.3 the recommended version, per the WordPress core team’s announcement that PHP 7.2 and 7.3 are being dropped. Sites still running 7.2 or 7.3 simply won’t be offered the 7.0 update; they’ll sit on 6.9 and lose security patches in due course. Anything below 8.2 in 2026 is either end-of-life or about to be.

If you’re not the one logging into the server yourself, the question to put to whoever does is: ‘What PHP version are we on, and is the site ready for 7.0?’. If the answer involves an upgrade first, that’s a piece of work in its own right. Put it in the diary and the budget, rather than letting it land mid-project as a nasty surprise.

The Next Twelve Months

The first-year cost picture reads as follows: a one-off staging and upgrade exercise, possible PHP upgrades on older sites, modest initial AI provider costs once the optional plugin is installed, and, set against those, the gradual saving as overlapping AI subscriptions are retired. Commentary: for most mid-sized UK businesses, the net cost in year one will be broadly flat. Real savings appear from year two onwards as plugins consolidate around the core APIs and standalone AI subscriptions can be reviewed for redundancy.

WordPress Before and After 7.0

Is WordPress 7.0 Safe to Install Yet?

For the most part, yes, with the usual caveats. Run it on a staging copy first, work through your regression checks, and don’t push to live until the team’s seen it behave. Confirm plugin and theme compatibility, paying particular attention to anything that customises the admin list and form screens. Check that backups are current. Worth flagging: the squad’s willingness to delay the headline feature rather than ship something half-baked is a fair signal about the scrutiny the rest of 7.0 got.

Should You Be Upgrading to WordPress 7.0?

For most business sites, yes, on a sensible timeline. The AI infrastructure alone is worth having in place before the rest of the plugin market builds around it. The admin and editor improvements are a useful bonus, mind you. The real question is when to upgrade and in what order across your sites, not whether to upgrade at all.

Three Things Worth Sorting This Month

1. Decide your AI provider policy before anyone installs the optional AI plugin anywhere. Pick a provider. Agree which parts of content production are fair game for AI help. Decide who signs things off. Write down what happens to the data along the way. Two pages of plain English is enough. Just write it down.
2. Talk to whoever runs your sites about the upgrade. Find out which are good to go, which need PHP work first, and which carry plugins that might break against the new admin layouts. Get the answer in writing, with dates. A nod over a Slack call doesn’t count as a plan.
3. Audit your existing AI subscriptions. List every AI tool the marketing team currently pays for. Mark which ones now overlap with what WordPress can do natively. Set a review date for the end of 2026, by which point the plugin market will have shifted enough to make sensible consolidation decisions.