On May 20, 2026, WordPress shipped the biggest core release in eight years. Version 7.0, named after Louis Armstrong, put AI infrastructure directly into the software that runs over 40% of the web. More than 875 contributors, over 200 of them first-timers, packed in 420-plus enhancements and fixes. And a loud chunk of the community immediately said: we didn’t ask for this.
If you run a business site on WordPress, the debate matters less than the practical question. What actually changed, and what should you do about it? Here’s the short version.
What WordPress 7.0 Actually Added
Three pieces of AI plumbing now live in core. An AI Client handles communication with AI providers. An Abilities API lets plugins expose what they can do in a standard way. And a Connectors hub lets you authenticate external AI providers from your admin screen in a few clicks.
Note what’s missing from that list: AI features. Core itself doesn’t write your posts or generate your images. The AI tools live in an optional official plugin that can generate images, titles, excerpts, and alt text. Don’t install it, and your dashboard works mostly the way it did before.
That distinction got lost in the launch noise. One developer who tested the betas put it well: WordPress didn’t really ship an AI feature, it shipped a PHP AI SDK that any plugin can use. The practical effect is that the AI plugins you already run, and there’s a good chance something in our roundup of the top 20 most popular WordPress plugins qualifies, will stop each bolting on their own API handling and start sharing one standard layer.
The MCP Adapter Is the Sleeper Feature
Buried below the headlines is the piece most likely to change how you work: an official MCP Adapter. It lets AI agents like Claude Code, Cursor, and Codex read and write to your site directly. Tell an agent to update a product description, fix a broken link, or draft five posts, and it can do it on the live site.
This lands at the right moment. AI agents already handle shopping on the other side of the counter, as we covered when AI agents started buying direct in ChatGPT. Now the same pattern reaches site management. Sites that are easy for agents to read and edit will get maintained faster and cheaper than sites that aren’t.
It also lands with real risk. Write access for an AI agent means an agent can break things, and developers on Reddit flagged exactly that concern at launch. Treat agent access like you’d treat a new contractor: its own account, minimum necessary permissions, and a fresh backup before it touches anything. Our rundown of the security threats targeting small stores in 2026 applies double once software can log in and make changes on its own.
The Non-AI Wins Nobody Is Talking About
Strip out the AI debate and 7.0 is still a strong release. The Command Palette now works everywhere in the admin: press Ctrl+K (Cmd+K on Mac) and jump straight to any screen or action. GoDaddy called it “the kind of quietly useful improvement that compounds,” and for anyone managing multiple client sites, it is.
Content-only pattern editing is the one to show your clients. They can now edit text and swap images inside a pattern without being able to wreck the layout. Fewer Monday morning “the homepage looks weird” emails.
You also get a revisions panel for templates and patterns, a font library that works across all themes, and a new grid package for building layouts. None of it is flashy. All of it removes friction.
What Got Cut, and What It Costs to Upgrade
Real-time collaboration, the headline feature everyone expected, was pulled before release over performance and server load concerns. It’s now expected in a later release. If you were waiting for Google Docs-style editing in WordPress, keep waiting.
The upgrade itself has two known costs. The minimum PHP version rises to 7.4, so sites on ancient hosting will need a hosting-side update first. And a handful of users reported styling breakage after updating, so test on a staging copy before you push it live. While you’re in there, it’s a good moment to re-check performance, because our Core Web Vitals optimization guide still decides how Google treats you, new admin or not.
The upside: for a release this size, 7.0 has been remarkably stable. Reviewers noted strong plugin compatibility and smooth upgrades for most sites.
Your 30-Minute Action Plan
First, check your PHP version in Site Health. If it’s below 7.4, email your host today.
Second, clone your site to staging and run the update there. Click through your key pages and your checkout if you sell online.
Third, decide your AI posture on purpose instead of by default. If you want the features, install the official AI plugin and try it on alt text first, the lowest-risk, highest-tedium job it solves. If you don’t, skip the plugin and you’ve lost nothing. If integrated AI is a dealbreaker on principle, the ClassicPress fork exists and some users are migrating to it, but that’s a big move to make over an optional plugin.
Fourth, if you experiment with agent access through the MCP Adapter, do it on staging with a limited account and daily backups.
The Takeaway
WordPress 7.1 is already in beta, with the final release timed for WordCamp US on August 19. It adds streaming AI responses and embeddings support for semantic search, which tells you where this train is headed.
You don’t have to love AI in your CMS. You do have to make a deliberate choice about it, because the default is no longer neutral. The site owners who win with 7.0 won’t be the ones arguing about it. They’ll be the ones who upgraded on staging, turned on exactly the features they need, and got back to work.
