WordPress 7.0: What’s New, What Got Cut, and Should You Update?

WordPress 7.0: what’s new and should you update?

WordPress 7.0, codenamed “Armstrong”, shipped on May 20, 2026. It is the biggest release in years: AI is built into core for the first time, the admin has had its first major visual refresh in over a decade, and the minimum PHP version has moved up. It also lost its most talked-about feature twelve days before launch.

If you run a business site on WordPress, here is what actually changed, what it means day to day, and a safe way to update if you have not already.

The headline: AI is now part of WordPress core

WordPress 7.0 does not add a chatbot to your dashboard. It adds the plumbing that lets plugins use AI in a consistent, provider-neutral way. According to the official WordPress 7.0 Field Guide, there are three pieces:

  • WP AI Client. A single interface plugins can use to talk to generative AI models, without each plugin building its own integration.
  • Connectors. A new Settings → Connectors screen where you connect an AI provider once. Anthropic, Google and OpenAI are supported by default, and other providers can be added.
  • Abilities API. A standard way for plugins to describe what they can do, so AI tools can chain those actions together into workflows.

For site owners, the practical benefit is fewer API keys scattered across plugins and more control over which AI provider touches your content. For now, most of the value arrives as plugins adopt it, so expect this to matter more over the next year than on day one.

A redesigned admin

The dashboard looks different the moment you log in. The main changes:

  • A modern colour scheme and smoother view transitions between admin screens.
  • Command palette everywhere. Press ⌘K on a Mac or Ctrl+K on Windows from the admin bar to jump to any screen, post or setting.
  • A dedicated Fonts screen for managing typography across the site.

Nothing moves so far that you will not find it, but it is worth warning anyone else who edits the site before they log in.

Editing and collaboration changes

Visual revisions

Revisions are now visual. You can compare versions side by side, with changes colour-coded and a slider to move through the history. Restoring an older version of a page is much less of a guess.

Notes and suggestions

Notes on blocks now send email notifications when someone is @mentioned, and there is a Suggestions mode for proposing edits without changing the published text. Useful if a client or colleague reviews your drafts.

New blocks and design tools

  • Breadcrumbs and Icon blocks.
  • Lightbox for galleries.
  • Video backgrounds.
  • Block visibility by device, so you can hide a block on mobile without custom CSS.

The editor is also iframed for better stability, and core is built to WCAG 2.2 level AA accessibility standards.

What got cut

Real-time collaboration, the Google Docs-style simultaneous editing that was the most anticipated feature, was removed on May 8, 2026. As DreamHost’s release summary notes, the team cited concerns about surface area, race conditions, server load, memory use and recurring bugs. It can still be tested in the Gutenberg plugin, but do not install that on a live business site to get it.

The Playlist block was also dropped from this release.

The change that can break sites: PHP 7.4 minimum

WordPress 7.0 requires PHP 7.4 or higher. Support for PHP 7.2 and 7.3 has been dropped. Sites still running those versions will stay on WordPress 6.9 and receive security updates only.

In practice, you should be on PHP 8.2 or newer anyway, both for security and speed. You can check your version under Tools → Site Health → Info → Server. If it is old, most hosts let you switch it in the control panel in a few clicks, but test first, because very old plugins may not support newer PHP.

Should you update to WordPress 7.0?

Yes, for almost every site. Point releases since launch have fixed early bugs, and staying on an old major version means missing security hardening over time. The question is how, not whether.

A safe update routine

  1. Take a full backup of files and database, and confirm you can restore it. Our WordPress security and backup checklist covers what a usable backup looks like.
  2. Check your PHP version is 7.4 or higher, ideally 8.2+.
  3. Update plugins and themes first, one at a time, and check the site after each.
  4. Test on a staging copy if your host offers one. Click through forms, checkout and booking pages.
  5. Update core, then clear your caching plugin and CDN cache.
  6. Re-test the money pages: contact forms, lead forms, checkout and any tracking tags.

After you update: three quick wins

  • Use block visibility by device to hide heavy desktop-only sections on mobile. That can help mobile load times, which is where our Core Web Vitals guide for WordPress says most sites lose points.
  • Add the Breadcrumbs block to posts and pages. It helps visitors navigate, and pairs well with breadcrumb structured data. See our guide to blog schema markup.
  • Review Settings → Connectors before any AI plugin does it for you, so you decide which provider has access to your content.

Common questions

When was WordPress 7.0 released?

May 20, 2026. Several point releases have followed with bug and security fixes.

Does WordPress 7.0 include real-time collaboration?

No. It was removed shortly before release and remains experimental in the Gutenberg plugin.

What PHP version does WordPress 7.0 need?

PHP 7.4 or higher. PHP 8.2 or newer is recommended.

Do I need an AI subscription to use WordPress 7.0?

No. The AI features are optional. You only connect a provider if you want plugins to use AI.

The short version

WordPress 7.0 is a solid, worthwhile update: AI plumbing in core, a cleaner admin, visual revisions and useful new blocks. The one thing that can catch you out is the PHP 7.4 minimum. Back up, check PHP, update plugins first, then update core and re-test the pages that bring in leads.

Written by

Prem

Guest contributor on GuestPosts.

Leave a Reply

Your email address will not be published. Required fields are marked *