WordPress 7.0 ships on 20 May 2026, the biggest core release in years and the headline event at WordCamp Asia. Plenty of coverage will treat that as if it changes everything for every site running WordPress. It does not, and pretending it does is how business owners end up worrying about the wrong thing.

WordPress powers around 43% of the world's internet, give or take, as W3Techs reported earlier this month. If you run a small business site on WordPress, you sit inside that statistic somewhere. So a major release matters. But the questions that matter for your site are not the ones being asked in the launch coverage.

First check: whether your site will even be offered the update

WordPress 7.0 needs PHP 7.4 as a minimum and recommends PHP 8.2 or 8.3. If your host has not moved you onto a current PHP version, the WordPress Core team has already confirmed your site will simply not be offered the 7.0 update. You stay on the 6.9 security branch until your hosting catches up.

This sounds dry. The street-level consequence is not.

Roughly half of WordPress sites are still running PHP versions that have hit end of life, according to figures from a recent infrastructure analysis published by WPM. That is a remarkable number for a platform handling a third of online commerce. If you are on cheap shared hosting that quietly kept you on PHP 7.4 or earlier because upgrading takes work, you may not even know. The first sign of a problem is usually a security advisory and a plugin that suddenly will not install.

So before reading another word about real-time collaboration or AI blocks, open your WordPress dashboard, go to Tools, then Site Health, and verify what PHP version you are running. If it is 7.4 or below, ring your host and ask why.

What you will actually notice as a business owner

Two of the changes in 7.0 will genuinely make your day easier.

The first is visual revisions. Instead of the old plain-text diff that nobody could read, the editor now shows colour-coded changes inline in the document. Yellow marks a changed block, red shows what was deleted, green shows what was added, as the WordPress Core team documented in the 7.0 source of truth. If you have ever asked your VA to update a product description and then spent ten minutes squinting at a wall of code to see what changed, you will appreciate this immediately.

The second is the admin refresh. WordPress is replacing its old List Tables, the screens you see on Posts, Pages, and Users, with a new system called DataViews. The visual gap between the modern block editor and the slightly tired classic admin closes. Faster filtering, no full page reloads, layouts that match what the rest of the dashboard looks like. Nothing dramatic on day one. But every time you manage your content, you save a couple of seconds.

These are quality-of-life wins. They will earn their place quietly, the way any good tool does.

Visual revisions are the most useful day-to-day change in 7.0 for owner-operators.

The headline features mostly are not for you

Real-time collaboration is the most-talked-about feature. Multiple editors on the same post or page at the same time, in the same way Google Docs handles concurrent edits. The team at DreamHost called it a fundamental shift in how teams work in WordPress, which is fair if you have a team.

If you are running 50 WooCommerce stores with a dedicated DevOps function and three editors pushing campaign pages every week, that workload genuinely benefits from real-time collaboration. It is the right feature for that workload. But that is not most Irish businesses. The owner of a Killarney gift shop editing her own product copy at half past ten in the evening does not need her page to be co-edited live. She needs it to save reliably.

The native AI Client and Abilities API, also drawing a lot of attention, is plumbing. WordPress now ships with a provider-agnostic interface that lets plugins talk to AI models in a standard way, as the Make WordPress Core team explained in March. That matters enormously for the plugin ecosystem. It does not give you any AI capability directly. You will see the benefit only when plugins start using it, which will take months and quite a bit of testing.

The bigger question is who pushes the button

Back in March, the WordPress team shipped three releases of 6.9 inside 24 hours. As Ben Ryan documented in his post-mortem, 6.9.2 fixed ten vulnerabilities and crashed an unknown number of sites. 6.9.3 fixed the crash but left three patches incomplete. 6.9.4 finished the job. Anyone running an unmanaged site through that window had a real job to do. Anyone on properly managed hosting did not notice.

A solicitor's firm in Sligo I spoke to last month moved off a cheap shared host for exactly that reason. Nobody had ever told them when their site was being updated, or whether anyone had verified it afterwards. The bill was small. The risk was not.

WordPress 7.0 is a bigger release than 6.9. It moves more pieces. The PHP floor is higher, the new admin design touches every screen, and the collaboration layer adds a new database table. The right question for any business owner this week is not what is in the release. It is who is responsible for testing it, applying it, and rolling it back if something breaks.

If the answer to that question is "me, eventually", that is not a managed WordPress setup. That is a WordPress site sitting on hosting that happens to allow WordPress. Web60's approach to managed WordPress upgrades on enterprise infrastructure starts from the opposite assumption: the customer should never be the one deciding when, or whether, a major release lands. Backups run first. A rollback path exists if needed. The upgrade happens to the site, not by the owner.

The practical upshot

WordPress 7.0 launching tomorrow does not change your to-do list today. Two things are worth doing this week. Confirm your hosting is on PHP 8.2 or higher. Confirm somebody other than you is responsible for testing the upgrade before it reaches your production site. If both answers are yes, the launch is a non-event for you, which is what a stable platform should feel like. If either answer is no, the launch has just made that gap more expensive.

For the wider context on where this AI-and-collaboration version of WordPress fits in the bigger shift, AI-Powered WordPress: What Every Business Owner Needs to Know in 2026 covers the strategic ground. For more on the AI features specifically, the earlier write-up on what the WordPress 7.0 RC1 release means for business sites explains what plugin authors are building on top of the new API.

WordPress is not the part of your business that should make news in your week. It is the part that should be quietly working.