WordPress 7.0 dropped today, 20 May 2026, and it’s the biggest release the platform has seen in years. If you’re running a WordPress site, there are a few things worth knowing before you hit update.
What’s actually new in WordPress 7.0
A refreshed admin dashboard
The WordPress admin gets its first proper visual overhaul in a long time. The new DataViews interface replaces the old list tables across posts, pages, and media. You get faster filtering, sorting, and grouping without full page reloads. If you spend a lot of time in the backend, you’ll notice the difference quickly.
A new Omnibar also ships in 7.0, giving you one-click access to the Command Palette from anywhere in the admin using Ctrl+K (or ⌘K on Mac). It’s a small thing, but it changes how you move around the site.
Built-in AI connections
WordPress 7.0 introduces a native AI Client API and a new Connectors screen in Settings. You can now connect your site to OpenAI, Google Gemini, or Anthropic’s Claude directly through the dashboard. Once you set your API key, every compatible plugin on your site uses those credentials. You no longer need to manage separate AI keys for each tool.
The API itself doesn’t do anything on its own. It’s the plumbing that plugin and theme developers build on top of, so the practical benefits will grow as more plugins adopt it.
Block editor improvements
A new Icon block ships in core, letting you add icons from a built-in collection without a plugin. Patterns also get a cleaner editing experience, where synced and partially synced patterns behave more predictably across the site editor. PHP-only block registration is now supported, which matters mostly to developers, but the practical result is that blocks are lighter and faster to build.
Responsive block visibility controls also make it into 7.0, so you can show or hide blocks at different screen sizes natively, without CSS hacks or third-party plugins.
Real-time collaboration: still coming, but not today
This was the headline feature for 7.0, and it got pulled at the last minute. The team built simultaneous editing (like Google Docs, inside WordPress) but ran into a performance problem that affected the whole site when the editor was open. Rather than ship something broken, they pulled it.
It’s coming in a later release. The rest of the update is solid without it.
PHP version changes
WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum is PHP 7.4. If your site is running one of those older versions, it won’t get the 7.0 update at all and will stay on the 6.9 security branch until you upgrade PHP.
PHP 8.2 or higher is the recommended version. If you’re not sure what your site is running, your hosting control panel will tell you.
What this means for your site
A major version bump in WordPress carries more risk than a minor update. The admin has changed, the block editor has changed, and there’s a new AI API touching areas that many plugins extend. Plugin compatibility is the main thing to watch.
The plugins most likely to have issues are page builders (like Elementor, Divi, or Beaver Builder), SEO plugins with editor integrations, any plugin that adds its own AI features, and WooCommerce extensions that touch the editor or admin screens. Most of the major plugins will have released compatibility updates by now, but not all of them will have.
The other thing to watch is your theme. If you’re using a classic theme with heavy customisations, the admin changes are mostly cosmetic. If you’re on a block theme and using the site editor, test before you update.
What you should do before updating
1. Back up your site first. A full backup, including the database and all files. If your host doesn’t do this automatically, do it manually before touching anything. If the update causes a conflict, you want to be able to restore to exactly where you were.
2. Check your PHP version. If you’re on PHP 7.2 or 7.3, the update won’t run anyway. If you’re on 7.4, it’ll work but you should plan to move to PHP 8.2 soon. If you’re already on 8.0 or above, you’re fine.
3. Check your plugins are updated. Go through your plugin list before updating WordPress. Most plugin authors will have pushed compatibility updates in the lead-up to today’s release. Any plugin showing “not tested with 7.0” or running an outdated version is a potential problem.
4. Test on staging first. If your site is business-critical, don’t update live. Clone it to a staging environment, run the update there, and check that everything works. Your hosting provider should offer this.
5. Wait a few days if you’re cautious. Major releases often get a small patch in the first week as post-launch bugs get reported. If you can wait until late May, you’ll be on a slightly more settled version.
Want someone to handle this for you?
If you’re not sure where to start, or you’d rather not risk your live site on a major update, we can take care of it. PrimaryRush handles WordPress updates, plugin compatibility checks, site backups, and staging environment testing for clients across Ireland and the US.
Get in touch and book a quick call and we’ll sort it out.