Probably not. But there are a few things worth checking before you hit update.
A quick guide for site owners, developers, and anyone who just wants to know what’s changed.
WordPress 7.0 is landing on 20 May 2026, and depending on which corner of the internet you’ve been reading, it’s either the most exciting thing to happen to the platform in years or a looming compatibility disaster. The truth, as usual, sits somewhere more sensible in the middle.
The short version: most sites will update without any drama whatsoever. But there are a handful of specific things that could catch you out, and the new features, particularly around AI, are worth understanding rather than ignoring.
The PHP question: do you need to worry?
The change most likely to affect older sites is a minimum PHP version bump. WordPress 7.0 raises the floor from PHP 7.2 to PHP 7.4. If your site is still running PHP 7.2 or 7.3, it will stay on the WordPress 6.9 branch after the update rolls out. You’ll still receive security patches, but new features are off the table until you upgrade your PHP version.
The good news is that PHP 7.2 and 7.3 account for under 4% of monitored WordPress installations. Most hosts have been nudging people off these versions for years.
If you’re unsure what version you’re on, your hosting control panel will show it, or you can check under Tools > Site Health in the WordPress admin. If you are on 7.2 or 7.3, the fix is usually a single dropdown change with your host. Do it in a staging environment first, run through your site, and you’re good to go. PHP 8.2 or 8.3 is what you actually want to be on for the best performance with 7.0’s new features.
Will your plugins and theme survive the jump?
The PHP version bump is the headline compatibility concern with WordPress 7.0, but there’s a subtler issue underneath it: plugins and themes that haven’t been updated recently may simply not be written to run cleanly on PHP 7.4 or above, let alone the 8.2 or 8.3 you should actually be targeting.
This matters more than it sounds. A plugin that technically “works” on a newer PHP version might throw deprecated function warnings, behave inconsistently, or fail silently in ways that are hard to diagnose. And themes built on older frameworks — particularly anything using a classic PHP architecture rather than block-based templates — can develop layout issues or lose functionality when the environment beneath them shifts.
The risk isn't usually a site going completely down. It's things quietly breaking in ways you might not notice for days.
The plugins most likely to struggle are those that haven’t seen an update in a year or more, rely heavily on older PHP functions that were deprecated in 8.x, or are built on top of frameworks that themselves have lagged behind. Page builders, membership plugins, and WooCommerce extensions are historically the categories that cause the most friction during major WordPress updates — not because they’re poorly made, but because they’re complex and the surface area for something to shift is larger.
The plugins and themes most likely to need attention before updating to WordPress 7.0.
Page builders
Elementor, Divi, and similar tools have large codebases and complex hooks. Check their changelogs for explicit 7.0 compatibility notes before updating.
WooCommerce extensions
Third-party WooCommerce add-ons vary wildly in update frequency. Any extension from a smaller developer is worth checking manually.
Membership & LMS plugins
MemberPress, LearnDash, and similar plugins touch a lot of WordPress internals. Verify compatibility before updating any site that relies on them.
Classic / non-block themes
Themes that predate Full Site Editing won't break outright, but some template functions may behave differently. Test in staging regardless.
The AI changes: actually kind of a big deal
The most significant shift in WordPress 7.0 isn’t visible in any single feature, it’s the infrastructure underneath. Until now, every AI plugin for WordPress had to build its own connection to whichever AI service it used, store its own credentials, and handle everything independently. That created a mess of overlapping tools, inconsistent behaviour, and a lot of duplicated effort.
WordPress 7.0 replaces that with a standardised system built into core. There’s a new Connectors screen in the admin where you configure your preferred AI provider once, whether that’s OpenAI, Google Gemini, or Claude. Once it’s set up, any compatible plugin can use that connection without asking you to set things up again.
Think of it like Wi-Fi settings. Previously every app had to handle its own networking. Now there's a shared layer they can all draw from.
The WP AI Client is the PHP library that powers this. It gives developers a single interface for communicating with AI services, so switching provider becomes a settings change rather than a rebuild. Community providers for OpenRouter, Ollama, and Mistral have already appeared alongside the official OpenAI, Google, and Anthropic plugins.
There’s also an Abilities API, which lets plugins declare what they can do in a format that AI assistants can understand and act on. Combined with an MCP adapter, this means automation tools and AI agents can interact with WordPress in a consistent way, without custom code for every combination of plugins.
In practice this means things like generating alt text, creating content drafts, SEO suggestions, and WooCommerce product descriptions can all run through one configured AI connection rather than three separate plugins each with their own subscription. It’s a more robust foundation than anything WordPress has had before on this front.
Other things worth knowing
The editor gets a genuinely useful overhaul of the revisions screen. Previously, reviewing an old version of a post meant wading through raw HTML in a two-column view. The new visual revisions show changes the way they appear in the editor, with colour-coded additions, deletions, and modifications. A small thing that will save a lot of frustration.
Two new blocks ship in core: a Breadcrumbs block that no longer requires a plugin or custom code, and an Icon block for adding SVG icons directly into content. The Grid block, previously experimental, is stabilised. The block editor itself has been upgraded to React 19, which brings performance improvements that should make the editing experience noticeably snappier.
The admin has also had a visual refresh, with animated transitions between screens using the View Transitions API. Navigation no longer triggers a full page reload, which makes the dashboard feel considerably more modern. None of this will break anything, but it’s worth being aware of if you have clients who are used to a specific admin experience.
Before you update
Pre-update checklist
- Check your PHP version in Site Health or your hosting control panel — 7.4 is the minimum, 8.2 or 8.3 is ideal
- Back up your site before touching anything, including database and files
- Run the update on a staging environment first, particularly for WooCommerce stores, membership sites, or anything with significant customisation
- Check your critical plugins for 7.0 compatibility notes, especially anything that already integrates AI features
- Check whether your theme is a classic theme or a block theme — most new design tools in 7.0 are optimised for block themes
- If you want to use the AI features, decide on a provider (OpenAI, Gemini, or Claude) and have an API key ready to configure in the new Connectors screen
- After updating, run through your critical user flows: checkout, forms, login, any custom post types or page builder sections on a provider (OpenAI, Gemini, or Claude) and have an API key ready to configure in the new Connectors screen
- If anything breaks, the update can be rolled back — confirm your host supports rollback before proceeding
WordPress 7.0 is a genuinely interesting release. The AI infrastructure in particular is a meaningful step forward, and the shift from fragmented plugin-by-plugin integrations to something platform-level is the kind of change that doesn’t show up in screenshots but matters a lot over time. For most sites, the update will be straightforward. For older setups, a bit of preparation beforehand will make it go smoothly. Either way, it’s worth doing.
One last thing worth saying plainly
You cannot put off updating forever — old WordPress versions carry real security risk, and 7.0 brings enough under the hood that staying on 6.x indefinitely is not a sensible long-term position.
That said, I never recommend updating on a .0 release. Let someone else find the bugs. The WordPress community is large and the edge cases will surface quickly — within a few weeks you’ll have 7.1 or 7.2 with the worst of it ironed out. Wait for a couple of point releases, keep an eye on the changelog, and update then. You get all the same features with considerably less risk.
