WordPress 7.0 lands on 20 May 2026, and it’s the biggest change to the platform in years. If your architecture or property website runs on WordPress — and there’s a good chance it does, because most do — this is the update worth paying attention to. Not because you need to panic, but because the firms that get caught out by a major release are almost always the ones who didn’t know it was coming.
Here’s the honest version: most sites will update without any drama at all. But there are a handful of specific things that can catch you out, and a little preparation makes the difference between a non-event and a bad week. Below is what’s changing, what to check, and the one decision that actually matters for your site.
What’s new in WordPress 7.0
This isn’t a routine security patch. WordPress 7.0 is being described as the most significant shift since the block editor arrived in 2018, and a few things stand out.
The headline change is a built-in AI client. WordPress now has a native, provider-agnostic way for plugins to connect to AI tools — there’s a single Connectors screen where you configure your preferred provider once, and any compatible plugin uses that connection. For most practice websites this runs quietly in the background for now, but it’s the kind of foundational change that matters more over the next few years than it does on day one.
There’s also a redesigned admin dashboard — the part you log into to edit pages — getting its first serious modernisation in over a decade. It’s faster and cleaner, with smoother transitions and no full page reload every time you click. Behind the scenes there are real performance improvements and a more modern editor.
One thing worth clearing up, because a lot of coverage online still gets it wrong: the much-hyped real-time collaboration feature — Google Docs-style editing where several people work on the same page at once — has been pulled from this release. It was the reason the launch slipped from April to May, and the WordPress team decided it wasn’t stable enough to ship. It’s coming in a future version, not this one. If you’ve read elsewhere that 7.0 brings live co-editing, that’s out of date.
The part that actually matters for your firm
Here’s the honest version most “what’s new” articles skip.
Core WordPress updates are generally well tested and reliable. The thing that breaks websites during a major release is almost never WordPress itself — it’s the plugins and themes layered on top of it. Contact forms, SEO tools, booking and enquiry systems, image galleries, the page builder your site was designed in: these are the components that can misbehave when the platform underneath them changes this much.
And the risk usually isn’t the whole site going down. It’s things quietly breaking in ways nobody notices for days — an enquiry form that still looks fine but stops sending emails, a portfolio page that loads slightly wrong on mobile. For a professional services firm, where your website is often the first impression a prospective client gets before they ever call you, that’s not a technical inconvenience. It’s lost work.
These are the categories most likely to need attention before you update:
| Component | Risk level | Why it matters |
|---|---|---|
| Page builders (Elementor, Divi, etc.) | Higher risk | Large, complex codebases with deep hooks into WordPress. Check the builder’s changelog for explicit 7.0 compatibility before updating. |
| Booking / enquiry & WooCommerce add-ons | Higher risk | Third-party extensions vary wildly in how often they’re maintained. Anything from a smaller developer is worth checking by hand. |
| Membership or client-portal plugins | Worth checking | These touch a lot of WordPress internals. Verify compatibility before updating any site that relies on them. |
| Classic (non-block) themes | Worth checking | Older themes won’t break outright, but some template functions can behave differently. Test on staging regardless. |
| Anything not updated in 12+ months | Worth checking | Stale plugins are the single most common source of friction in a major release. Outdated code and a changed platform don’t always mix. |
There’s also a quieter technical point. WordPress 7.0 performs and stays secure best on a recent version of PHP — the language your site’s server runs on — with 8.3 or higher recommended. Plenty of sites are running older versions without their owners ever being aware of it. It’s the kind of thing that doesn’t matter until it suddenly does, and it’s usually a single change with your host to fix.
Before you update: the checklist
If you (or whoever looks after your site) are handling this, this is the order to do it in:
- Check your PHP version — find it under Tools → Site Health in the WordPress admin, or in your hosting control panel. Aim for 8.3 or higher.
- Take a full backup first — database and files, before touching anything. Confirm your host supports a rollback if needed.
- Update on a staging copy first — a private duplicate the public never sees. Essential for any site with a shop, client area, or significant custom design.
- Check your critical plugins — look for explicit WordPress 7.0 compatibility notes, especially page builders and anything handling forms or payments.
- Confirm your theme type — classic or block. Most of 7.0’s new design tools are built for block themes; classic themes still work but behave differently in places.
- Test the journeys that earn you money — submit the enquiry form and confirm it actually arrives, check the portfolio displays correctly, click through key pages on mobile.
- Only then go live — with the backup in hand, so anything unexpected is a five-minute rollback, not a lost week.
A note on timing: there’s no prize for updating on launch day. A major .0 release is where edge cases surface, and the WordPress community is large enough that they surface fast. Waiting for a point release or two — keeping an eye on the changelog and updating once the worst is ironed out — gets you all the same features with considerably less risk. The one thing you can’t do is put it off indefinitely; old WordPress versions carry real security risk, so “later” needs to mean weeks, not never.
So who’s actually doing this for your site?
That checklist assumes someone owns the process. For a lot of firms, “whoever looks after the site” is no one in particular — it was built a few years ago, the developer moved on, and nobody’s quite sure who handles updates now. A major release is exactly when that gap becomes expensive.
This is precisely the kind of moment our WordPress care plans are built for. Updates like 7.0 don’t land on our clients’ live sites until they’ve been tested on a staging copy and confirmed working. Backups are automatic, the PHP environment is kept current, and if a plugin throws a wobble, it’s our job to catch and fix it — usually before the client even knows there was a question. The point of a care plan isn’t the monthly maintenance log. It’s that a release like WordPress 7.0 arrives and you don’t have to think about it at all.
If you’re not sure how your site would handle this update — or who’s responsible for it in the first place — that’s worth knowing before 20 May, not after. We’re offering free website audits for architecture and property firms: a short, personalised walkthrough of your current setup, where the risks are, and what we’d recommend. No pitch, no obligation.
Get in touch and we’ll take a look before the update lands.
