WordPress 7.0: what changed, and should you update?
WordPress 7 gives the dashboard a full makeover and lays the groundwork for AI inside your site. For most business sites the update is safe, as long as it happens in the right order.
Or call or text (502) 387-1142
Websites I have built for Kentucky businesses
The short answer
Yes, update, in the right order. WordPress 7.0 arrived on May 20, 2026, and 7.1 followed on August 19. Together they bring a modernized dashboard, new design tools, the building blocks for AI inside WordPress and a new minimum of PHP 7.4. Security fixes go to the newest version, so a business site should get there.
Back up first, check your PHP version and your plugins, test the update on a copy of the site, then update the live site with a way back.
What changed in WordPress 7.0
WordPress 7.0, named Armstrong, was released on May 20, 2026, according to the WordPress 7.0 release post. It was first scheduled for April and was given extra time before launch. The WordPress project calls it the foundation for AI across WordPress. For a business owner, the changes fall into four groups.
AI building blocks
A new AI Client in the core software lets WordPress talk to generative AI models. A new Connectors screen keeps your site’s connections to outside services in one place. The Abilities API gives plugins a standard way to offer actions that automation and AI tools can use. The AI features people picture, like generating images, writing titles or excerpts and suggesting alt text, come from a separate AI plugin that you choose whether to install.
A modernized dashboard
The admin has a fresh look and a Command Palette that opens with Cmd+K or Ctrl+K and jumps straight to any tool. There is a font management page that works with block, hybrid and classic themes, and a revisions view that lets you scrub back through versions of a page and restore one.
Design tools
New Breadcrumbs and Icons blocks, a gallery with a lightbox slideshow, controls to show or hide a block by device, menu overlays built from blocks, patterns you can detach and edit on their own, and custom CSS on a single block.
A higher PHP minimum
WordPress 7.0 needs PHP 7.4 or newer. Sites still on PHP 7.2 or 7.3 stay on the 6.9 branch. The recommended version is PHP 8.3. All three points are in the core team’s PHP support notice.
What did not make it: real-time collaboration
For most of the development cycle, the headline feature was real-time collaboration: several people editing the same page at once, the way they would in a shared document. On May 8, 2026, twelve days before release, it was pulled. The core team’s announcement said the approach was not yet robust enough to ship, pointing to server load, memory use and bugs found in testing.
It did not arrive in 7.1 either. What 7.1 did improve is Notes, the comments you leave on a draft. They can now sit on specific words, carry formatting and mention a colleague with an @. If you were holding off for live co-editing, there is no reason to keep waiting.
What WordPress 7.1 added
WordPress 7.1, named Mary Lou, was released on August 19, 2026, according to the WordPress 7.1 release post. It is the version to aim for today. It added:
- Notes on specific text, with formatting and @mentions
- Responsive styling controls in the Site Editor, with previews at different screen sizes
- A new media editor for cropping, flipping and rotating images
- Image compression and resizing in the browser, with AVIF and HEIC support
- Playlist and Tabs blocks, and button styles for hover and focus
Maintenance and security releases have followed on the 7.1 branch since then. The latest as of mid-October 2026 is WordPress 7.1.3, released on October 6, 2026.
Should a business site update to WordPress 7?
Yes. WordPress’s security page says only the latest version is officially supported. Older branches sometimes get a fix as a courtesy, and a business should not plan around a courtesy. Staying on 6.9 means running a version the project has already moved past.
There are two good reasons to wait a short while, and neither is a reason to wait for months:
- A plugin you depend on has not confirmed support. Page builders, booking plugins and store extensions are the ones to check. Read each changelog for WordPress 7 support, and update once it is there.
- Your server runs PHP older than 7.4. The PHP upgrade comes first, and it deserves its own test before WordPress changes too.
If neither applies, there is nothing to wait for.
Check these five things before you update
- Your PHP version. In the dashboard, go to Tools, then Site Health, then Info, and open the Server section. Anything below 7.4 needs your host to upgrade PHP first. Aim for 8.3 or newer.
- A backup you have restored. A backup only counts once someone has restored it somewhere. Keep a full copy of the files and the database off the server. Here is why backups need testing.
- Plugin and theme support. Update anything that is behind, and read the changelogs of the plugins that run your business: forms, checkout, bookings and memberships.
- Custom code. Code snippets, a child theme, or a plugin someone wrote for you years ago. These are the pieces nobody else has tested.
- Who has admin access. Connections to outside services are managed from the dashboard now, so remove old logins and decide who may connect one.
A safe update path, step by step
This order works for any major WordPress update, and it is the one to follow for 7.0 and 7.1.
- Take a fresh backup of the files and database, stored away from the server.
- Make a staging copy: a private duplicate of the site where mistakes cost nothing.
- On staging, upgrade PHP if needed, then update plugins and the theme, then WordPress itself.
- Test what earns money: send a form and confirm the email arrives, place a test order, make a test booking, log in as a customer, and check the main pages on a phone.
- Pick a quiet hour, take a snapshot, and repeat the same updates on the live site.
- Run the same tests on the live site straight away.
- Watch for a few days: error logs, form notifications and uptime. Keep the snapshot until you are sure.
If something breaks, the snapshot from step 5 is your way back. If an update has already gone wrong, start with what to do when a plugin update breaks your site.
The AI features: what to decide
The AI parts of WordPress 7 are mostly plumbing. They give plugins and AI tools a standard way to work with your site, and one Connectors screen where those connections live. The visible AI features come from a plugin you add on purpose.
A few decisions are worth making deliberately:
- Whether to connect an AI service at all, and which one. Read what it does with the content you send it.
- Who may set up connections. Keep that to the people who manage the site.
- What gets reviewed. If you use the optional AI plugin to suggest alt text or titles, read every suggestion before it goes live. It does not know your products, your town or your customers.
If you want help deciding where AI earns its keep in your business, that is a conversation for AI consulting.
How I handle WordPress 7 on the sites I maintain
Updates on the sites I maintain run with a snapshot first and automatic checks afterward, so a bad update can be rolled back instead of being left for a customer to find. Which version a given site runs depends on its plugins and server, so I check each one rather than assume. Every site I host is also checked from outside every 60 seconds, so a problem after an update alerts my phone before a customer notices.
If you would rather not do any of this yourself, that is what WordPress maintenance and managed WordPress hosting are for. If your site is already broken after an update, WordPress repair comes first.
Frequently asked questions
When was WordPress 7.0 released?
May 20, 2026. WordPress 7.1 followed on August 19, 2026, and the 7.1 branch is where maintenance and security releases are landing now. WordPress’s release archive lists every version and date.
What PHP version does WordPress 7 need?
PHP 7.4 at minimum, with 8.3 recommended. Sites on PHP 7.2 or 7.3 stay on WordPress 6.9 until the server is upgraded.
Will updating to WordPress 7 break my site?
Usually not, but any major update can expose a plugin, theme or piece of custom code that has not kept up. Test the update on a staging copy first and keep a snapshot so you can roll back.
Does WordPress 7 send my content to AI?
WordPress 7 adds the parts that let a site work with AI services, and those connections are managed on the new Connectors screen. Check that screen and your plugins to see what your site is connected to, and decide who may add a connection.
Can I go straight from 6.9 to 7.1?
Yes. The update screen offers the newest release, so a site on 6.9 can move directly to the current 7.1 version. The same checks apply.
Did WordPress 7 add real-time collaboration?
No. It was removed twelve days before the 7.0 release and did not arrive in 7.1. Notes, the comments you leave on drafts, did get better in 7.1.
A thousand products, and updates that cannot quietly break checkout.
Heimerdinger Cutlery has served Louisville since the 1800s. Its WooCommerce store carries roughly a thousand products with live UPS shipping rates on every order, so an update that breaks shipping costs real sales.
That is why every update on the store is tested against checkout before it goes live, with a snapshot taken first so it can be rolled back.
Want a second opinion before you update?
Send me your site address. I will check its PHP version, plugins and backups and tell you whether it is ready for WordPress 7, whether or not you hire me.
