WordPress 7.0 shipped on May 20, 2026, and I have now run it across enough client sites to tell you what actually matters and what is just release-note noise. Here is the short version: this update does not put AI on your website. It puts in the plumbing that lets other things put AI on your website. That distinction is the whole story, and it changes what you should be doing over the next few months.
If you have been quietly ignoring the update prompt in your dashboard, this one is worth ten minutes.
What actually shipped in WordPress 7.0
The release, codenamed Armstrong, was originally targeted for April to line up with WordCamp Asia. Leadership pushed it back roughly six weeks to stabilize the AI infrastructure and finish the admin redesign. What landed on May 20:
- The AI Client, a provider-agnostic PHP interface built into core
- The Abilities API, a central registry of named actions your site can expose
- A Connectors hub in wp-admin where you authenticate outside AI providers
- An optional official AI plugin for generating titles, excerpts, alt text, and images
- The first real visual refresh of wp-admin in over a decade, including a Command Palette
- PHP-only blocks, so developers can ship blocks without touching React
- A minimum PHP bump to 7.4, dropping support for 7.2 and 7.3
Notice what is not on that list: a chatbot, an AI writer in your editor, or anything that starts generating content the moment you hit update. Core shipped the wiring, not the appliance.
The AI Client, explained without the jargon
Before 7.0, every AI plugin rolled its own connection to OpenAI or Claude or whoever else. Each one wanted its own API key, stored it in its own settings page, and broke in its own creative fashion when a provider changed an endpoint. Three AI plugins meant three integrations to maintain and three places for a key to leak.
The AI Client replaces that with one standardized interface in core. A plugin sends a prompt through it and gets a response back in a predictable format, regardless of which model is on the other end. You authenticate providers once in the Connectors hub, and plugins request access through core rather than hoarding credentials.
For you as a site owner, the wins are simple. Fewer places to store API keys, fewer plugins doing sketchy things with your credentials, and the ability to swap model providers without rebuilding every AI feature on the site. That last one matters more than people realize, because AI pricing keeps moving and vendor lock-in is how you end up overpaying.
The Abilities API is the part that actually matters
If the AI Client is the wire, the Abilities API is the outlet. It is a registry where plugins, themes, and core itself declare named actions along with input rules, output rules, and permission checks. Things like create_order, list_products, get_inventory, or schedule_post.
Here is why that beats the AI writing features everyone is talking about. Once your site publishes a structured list of what it can do and who is allowed to do it, an AI tool can operate your website instead of just writing text for it. A support assistant that genuinely looks up an order status. A tool that checks live inventory before answering.
WordPress.com has already expanded its AI agent from read-only access to actual write actions, and the guardrails they built are the model everyone should follow: changes need explicit approval, new posts default to drafts, deletions stay reversible where possible, activity shows in the site log, permissions follow existing WordPress user roles, and every operation can be switched on or off individually.
Take that list and treat it as your checklist. Any AI plugin that wants write access to your site and does not offer approval gates, role-based permissions, and an audit log has no business being installed on a site that makes you money.
The admin redesign you will notice on day one
The dashboard got its first serious visual overhaul in more than ten years. The static list tables you have stared at since WordPress 3.x are replaced by React-based DataViews. There is a proper font management page, visual revision scrubbing, and a Command Palette you open with Cmd+K.
The Command Palette is the sleeper feature. Instead of hunting through menus to reach a settings page or jump to a specific post, you hit Cmd+K and type. If you manage a lot of sites, it changes how fast you move.
Fair warning though. A redesigned admin means your staff and your clients open the dashboard and find things moved. If you hand off site access to anyone, plan a short walkthrough before you update, not after the panicked phone call.
What got pulled from the release
Real-time collaboration, the feature most people were actually waiting on, was cut twelve days before launch over performance and server load concerns, and postponed to a future version. If your plan this year involved multiple people editing the same post at once in WordPress, keep whatever workaround you have. I would rather they pull a feature than ship one that hammers shared hosting, but it does mean the update is less transformative on day one than the buildup suggested.
Check your PHP version before you do anything else
This is where I see small business sites break, every single release cycle. WordPress 7.0 requires PHP 7.4 minimum. Support for 7.2 and 7.3 is gone.
If you are on budget shared hosting that has not touched its PHP defaults in years, you may be sitting on an older version and not know it. Check under Tools then Site Health then Info in your dashboard. If you are below 7.4, do not update WordPress until your PHP is current. And honestly, 7.4 is the floor, not the target. Run PHP 8.2 or higher if your plugins support it, because the performance difference is significant and older versions stopped getting security patches a long time ago.
There is a second hosting consideration nobody put in the release notes. AI features mean outbound API calls, and the React-based admin is heavier than the old list tables. On cheap hosting, both show up as a sluggish dashboard. If your admin already felt slow, it will feel worse after this update, and that is a hosting problem rather than a WordPress problem. I broke down the usual culprits in my guide on how to speed up a slow WordPress site.
If your current host cannot give you a modern PHP version without an upsell call, that is your answer about whether to stay. I keep client sites on hosts that stay current without being asked. Hostinger is where I put budget-conscious sites that still need real performance, and SiteGround is my pick when a client needs stronger support and staging built in. I compared the options I actually use in my best WordPress hosting guide.
What I am telling clients to do right now
Five steps, in this order.
1. Confirm your PHP version first. Site Health tells you in about fifteen seconds. Fix it before updating core, not after.
2. Update on staging, not production. This is a major version with a redesigned admin and new APIs, and every plugin you run interacts with that. Test it somewhere that does not cost you customers if it breaks. If your host does not offer staging, that is another reason to move.
3. Audit your existing AI plugins. If you picked up AI tools over the last two years, several of them are now doing redundantly what core does natively. Every plugin you remove is one less security surface, one less update to babysit, and one less thing slowing your admin down. I keep a running list of the tools that survive my own audits in my post on the AI tools I actually use for small business clients.
4. Do not connect a provider until you know what it can touch. The Connectors hub makes authentication easy, which also makes it easy to hand broad access to something you have not vetted. Check what abilities a plugin registers and what permissions it wants before you authorize it.
5. Leave real-time collaboration out of your plans. It is not shipping in this version. Plan around the tools you have.
The part most small business owners are missing
The Abilities API is quietly the most important thing in this release, and it has almost nothing to do with writing blog posts.
What it sets up is a future where AI tools interact with your website as a system rather than as a page of text. That means the structure of your site, your product data, your inventory, your service descriptions, and your schema all start mattering in a new way. A site with clean, structured, well-labeled data becomes usable by AI agents. A site with everything crammed into unstructured page builder content does not.
That is the same lesson showing up in search right now, where clear structure and direct answers are what get a business quoted in AI results. I covered that side of it in my post on how small businesses get cited in Google AI Overviews. Different surface, same underlying requirement. Structure your content properly and machines can use it. Leave it messy and you get skipped.
So the real takeaway from WordPress 7.0 is not “install the AI plugin.” It is “get your site data and structure in order, because the tools that read it are about to get a lot more capable.”
Where this leaves you
WordPress 7.0 is a foundation release. It is not going to redesign your homepage or write your service pages. What it does is make WordPress a platform AI tools can plug into properly, with permissions and audit trails instead of a pile of competing plugins each holding their own API key.
The sites that benefit are the ones that are technically current: modern PHP, a host that keeps up, a lean plugin stack, and content that is actually structured. The sites that suffer are the ones on old PHP with fifteen overlapping plugins and everything locked inside a page builder. Getting from the second group to the first is most of the work, and it is the part people put off.
If you would rather not spend your weekend checking PHP versions and testing a major update on staging, that is what I do. I handle WordPress updates, hosting migrations, performance work, and site recovery for small businesses, and I have been doing it since long before anybody put AI in a release note. Head over to webguynick.com and tell me what your site is doing. I will tell you straight whether it needs work or whether you are fine to sit tight.
Share this:
