WordPress 7.0 is here. Should you update your site today?

WordPress 7.0 is here. Should you update your site today?

Update, July 2026: WordPress has since issued an emergency security release. If you updated to 7.0 after reading this, you’ll want to be on 7.0.2 — here’s what happened and how to check you’re patched.

WordPress 7.0 lands today — one of the most significant core releases since the Block Editor arrived in 2018. New admin interface, native AI hooks for plugins, a stricter PHP baseline, and a long list of under-the-bonnet changes.

Your dashboard might already be nudging you to hit “Update Now.”

Our advice: Don’t. Not yet. Here’s what’s in 7.0, what it actually means for your site, and why the smart move this week is to wait.

What’s new in WordPress 7.0

A few headline changes worth knowing about:

A new admin interface (DataViews)

The familiar list tables for Posts, Pages and Media are being replaced with a more modern, React-based interface. Filtering and sorting feel closer to a SaaS dashboard than the old WordPress admin. Once you’re used to it, it’s a genuine improvement, but if you log in this week and things look unfamiliar, you’ll know why.

A native AI framework

WordPress 7.0 introduces an AI Client and an Abilities API, plus a new Settings → Connectors screen. In plain English: WordPress core now has a standardised way for plugins to talk to AI providers (OpenAI, Anthropic, Google), and a single place for site owners to manage their API keys. Nothing happens automatically. No AI is active on your site unless you install a provider plugin and add an API key. But expect plugin developers to start shipping AI features through this framework over the coming months.

A higher PHP baseline

The minimum supported PHP version moves to 7.4, with 8.3+ recommended for best performance. If your site is still on PHP 7.2 or 7.3 (a surprising number of budget hosts still default to these), WordPress won’t break, but it also won’t offer you the 7.0 update. You’ll be held back on the 6.9 branch until you upgrade PHP with your host.

Real-time co-editing didn’t make the cut

It was the most hyped feature in the run-up to 7.0 — Google Docs-style live editing inside WordPress — but the core team pulled it from the final release on May 8, citing stability concerns. It’s expected to return in a future release, but no version has been confirmed. If you read the hype articles expecting Google Docs-style editing today, it isn’t there.

There’s plenty more under the hood: block registration changes for developers, performance improvements, accessibility tweaks, but those are the ones that affect day-to-day site owners.

Why we’re telling our clients to hold off

Updating WordPress is rarely the problem. Plugins are.

A modern WordPress site is usually running 15–30 plugins from different developers, each on their own release schedule. When a major core update lands, every one of those plugins has to be tested against it. Some developers are ready on day one. Some aren’t. A few will quietly break things and only patch the issue a week or two later, once enough sites have reported the bug.

Major version jumps (especially ones that change admin internals like DataViews) are the most likely to expose plugin incompatibilities. A plugin that worked perfectly under 6.x might throw errors, conflict with the new admin, or stop loading altogether under 7.0.

If you hit “Update Now” on launch day:

  • Best case: nothing breaks, everything works, you got lucky.
  • Likely case: one or two plugins behave oddly until they’re patched.
  • Worst case: white screen of death, broken checkout, broken forms, or an admin you can’t log into. (Which, as it happens, is today.)

That’s not a risk worth taking for the sake of being a couple of weeks early.

What we’re doing at WP Care Pros

Right now, WordPress 7.0 is running in our internal test environments. We’re checking it against the page builders and plugins our clients actually run — Elementor, Divi, Beaver Builder, Avada, WPBakery, ACF, WooCommerce, Gravity Forms, and the SEO and security plugins that turn up on most sites — and watching the wider community for compatibility reports.

When we’re confident it’s safe, we’ll roll it out across client sites in a staged way, as part of our WordPress maintenance service: staging environment first, full backup, deploy, smoke-test, then move on to the next. If something does misbehave, we roll back. Clients don’t have to think about any of it, and if anything does go sideways under our watch, we fix it without sending another invoice.

That’s the whole point of a care plan. Updates aren’t a checkbox; they’re a process.

Agencies running this for end clients: same applies. We handle the 7.0 rollout under your brand, your clients never need to hear the words “WordPress 7.0,” and we’ll send you a white-labelled report once it’s done. More on how that works →

If you’re managing your site yourself

A few sensible steps if you don’t have a care plan:

  1. Take a full backup first — files and database. Not a “the host probably has one” backup. An actual one you’ve tested.
  2. Update everything else first. Plugins and theme to their latest versions before you touch core.
  3. Check your PHP version. If you’re on PHP 7.3 or lower, sort that with your host before updating to WordPress 7.0.
  4. Wait a week or two. Let other people find the bugs. Watch your plugin developers’ changelogs for “WordPress 7.0 compatibility” notes.
  5. Update on a staging site first if you have one. If you don’t, at least do it during quiet hours, not while customers are checking out.

The honest summary

WordPress 7.0 is a good release. The new admin is a real improvement, the AI groundwork is sensible, and the codebase is healthier for it.

But “good release” and “safe to install on your live site today” are two different things. The sites that get burned by major WordPress updates are almost always the ones that updated the moment the notification appeared.

If your site matters to your business (bookings, leads, sales, reputation, etc) let the dust settle.

If you’d rather not think about it at all, that’s what we’re here for. Apply for a care plan, or if you’re not sure which tier fits, our 60-second plan quiz will point you in the right direction. If something’s already gone wrong with a 7.0 update on your site, our emergency support team is available 24/7 — or call 0208 0505 999.


WP Care Pros manages WordPress sites for SMEs and agencies across the UK. Major version updates are tested in staging, deployed with backups, and rolled back if anything misbehaves. See our care plans →

Jason Hubbard
Jason Hubbard
Founder

Jason has been working in WordPress for over 15 years. He founded JMJ Digital to build sites for businesses across the UK, and later launched WP Care Pros as a dedicated branch — bringing that same depth of experience to ongoing care and maintenance at scale.

Related reading

More from the blog

WordPress Maintenance Mode – WP Care Pros guide thumbnail
Maintenance
WordPress Maintenance Mode: How to Turn It On (And Fix It When It’s Stuck)
20 Jul 2026
WordPress update failed? What to do next
Maintenance
WordPress Update Failed? Here’s What It Means and What to Do
9 Jun 2026
In this article
What’s new in WordPress 7.0 Why we’re telling our clients to hold off What we’re doing at WP Care Pros If you’re managing your site yourself The honest summary
Need help with your site?

Stop managing WordPress yourself. Let us handle it.

Apply for a care plan and we'll handle updates, security, backups, and everything in between.

No contracts · UK support team · Cancel anytime