WordPress 7.0, codenamed "Armstrong," landed on May 20, 2026, and the numbers tell the story faster than any feature list. Seven days after release, 46 percent of all WordPress installations had auto-updated to version 7.0 across hosting environments worldwide — with no reported breakage. That is not cautious adoption. That is the ecosystem saying it trusts the release.
For context, WordPress powers roughly 43 percent of the web. When almost half of those sites move to a new major version in a week without things catching fire, it says something about the maturity of the release process and the confidence hosting providers have in the platform. Matias Ventura led the release, and the team ran four release candidates between March and May before giving the final green light. The extended RC phase was deliberate — they pushed back the schedule in April to shore up database stability rather than ship on time with known issues. That kind of restraint is why the upgrade went smoothly.
What actually changed
The headline feature is the WP AI Client, a unified interface baked directly into WordPress core for connecting external AI models and plugins. This is not a gimmick add-on. It is a standardized API layer that lets theme and plugin developers integrate AI capabilities without each one building its own connection logic. If you have been watching the WordPress AI plugin space — dozens of competing integrations, each with its own settings page and authentication flow — you can see why a core-level abstraction matters. It gives the ecosystem a common foundation instead of a fragmented mess.
The Site Editor got a serious round of improvements. Template management is tighter — you can now edit nested blocks, synchronized patterns, and templates directly in the editor without bouncing to a separate template area. New core blocks include icons and breadcrumbs, the paragraph block supports native multi-column layouts without a plugin, and you can now indent paragraphs (with the first paragraph excluded by default, which is a nice typographic touch). Image blocks respect aspect ratios across wide and full alignment, and dimension presets let you define reusable width, height, and spacing values. None of these are flashy individually, but together they mean you need fewer plugins to build a polished layout.
The admin dashboard is getting a gradual visual overhaul to match the Site Editor's look and feel. This is not a sudden redesign that forces everyone to relearn the interface. It is incremental, moving the admin screens toward the same design language as the block editor over time.
One of the more interesting developer additions is PHP-only blocks. Previously, creating a custom block meant writing React and dealing with the JavaScript build pipeline. Now you can register a block entirely in PHP, which lowers the barrier for developers who are comfortable with WordPress's traditional stack but have not adopted the React workflow. This matters for the long tail of agencies and freelancers who maintain hundreds of sites and need to add custom blocks without spinning up a Node environment for each one.
CERN moved to WordPress
The timing was perfect for WordCamp Europe 2026 in Kraków, which ran June 4-6. The event drew 2,458 attendees from 81 countries, and the biggest announcement from the stage was that CERN — the European Organization for Nuclear Research, the place where the World Wide Web was invented — has gone live on WordPress. When the organization that literally created the web decides your CMS is good enough for their public-facing site, that is a signal that carries weight beyond the WordPress community.
The security play: Protect The Shire
WordPress.org also launched a security initiative called "Protect The Shire" aimed at securing all 78,000 plugins and themes in the repository. The approach is practical rather than dramatic: a temporary 24-hour cooldown period for plugin and theme releases before auto-updates kick in. The idea is to give defenders more time to spot vulnerabilities before they propagate to millions of sites automatically. The initiative uses AI tools to assist with vulnerability detection across the repository, which is a smart use of automation at a scale that manual review cannot match.
The React 19 stumble
Not everything went perfectly. Gutenberg 23.3.0 shipped with a React 19 upgrade that broke compatibility with plugins built for React 18. The team reverted it quickly and is working on a smoother migration path. This is worth noting not because it is a disaster — it was caught and rolled back before most sites noticed — but because it shows that even a well-run release process can hit friction at the dependency layer. Plugin developers should keep an eye on the core development blog for the updated timeline.
What to do right now
If you are still on 6.9 or earlier, update. The 46-percent-in-a-week adoption rate with no breakage should take the anxiety out of that decision. Back up first, test on staging if you have a complex setup, then push it live. The AI Client alone is worth the move if you are building anything that touches content generation, translation, or automated moderation.
If you are a plugin developer, start looking at the WP AI Client API and the PHP-only block registration. Both represent where the platform is heading, and getting familiar now means you are not scrambling when clients start asking about them.
WordPress 7.0 is not a revolution. It is a release that quietly makes the platform more capable, more secure, and easier to build on. The quiet part is the point. The best infrastructure upgrades are the ones you barely notice because they just work.