WordPress 7.0 brings core performance improvements, block editor refinements, and tighter PHP requirements. For most small business owners, the update is worth doing, but not urgently. The real work is checking plugin and theme compatibility before you click update, not after.
01WordPress 7.0 Is Out. Here’s the Honest Version.
WordPress 7.0 officially releases May 20, 2026. If your first instinct was mild dread followed by a vague plan to deal with it later, the dread is probably disproportionate. The ignoring-it plan still isn’t.
WordPress powers 43.5% of all websites globally and 61.7% of sites running a known CMS. For your specific five-page service site or WooCommerce store, the update is mostly a maintenance task wearing a press release.
Here’s what you actually need to know.
02The Parts That Sound Big But Probably Don’t Affect You
Every major WordPress release comes with a changelog that reads like a developer wrote it for other developers. Because they did.
The 7.0 release focuses heavily on database performance improvements, cleaner code architecture, and changes to how WordPress handles background processes. These are real improvements. They will make things faster and more stable at a technical level. You will not notice them in any perceptible way while editing a page or checking your contact form.
What the Engine Changes Actually Mean
The database query optimizations matter most for sites with large content libraries, heavy traffic, or complex background queries. A blog with 800 posts or a WooCommerce store with 500+ SKUs might actually feel the difference. A 12-page brochure site will not. It’s the same principle as replacing the fuel injectors on a car you drive exclusively to the grocery store and back: technically improved, imperceptibly identical. The car does not know you’re impressed.
The code architecture changes are primarily relevant to theme and plugin developers who need to update their products to stay compatible. Which brings us to the part that actually is your problem.
The PHP Requirement Nobody Warned You About
WordPress 7.0 raises the minimum PHP version requirement. If your hosting environment is running an old PHP version, and a surprising number of small business sites are, because nobody ever checked, you need to update that first. Log into your hosting control panel, find the PHP version setting, and compare it against the 7.0 requirements. Most modern hosts make this a one-click change. Some older setups make it a small headache. Either way, worth knowing before you’re staring at a broken site wondering what happened.
03Where You’ll Actually Notice Something Different
The WordPress admin dashboard is getting a visible refresh in 7.0. Not a complete redesign, but enough that if you’ve been logging into the same interface for four years, it’ll feel slightly rearranged. Like someone cleaned up your desk without telling you. Everything’s still there, just in slightly different spots.
Block Editor Improvements That Actually Help
The block editor gets meaningful improvements in 7.0. Pattern management is cleaner, the interface for reusable blocks is less confusing, and performance inside the editor is noticeably faster on larger pages. If you’ve been editing pages and occasionally watching the editor grind through a complex layout, this will improve. The block editor has been the most complained-about part of WordPress for years. The 7.0 version isn’t perfect, but it’s materially better to work in.
If you’re still on the Classic Editor plugin because someone told you the block editor was too complicated, 7.0 is a reasonable moment to try switching. The gap has narrowed considerably.
Plugin Compatibility Is Where the Work Lives
WordPress 7.0 includes API changes that affect how some plugins communicate with core. Most actively maintained plugins will have already pushed compatibility updates by release day. The ones that haven’t are the problem.
A small B2B site running three key plugins, say a CRM connector, a form builder, and a backup tool, needs all three to be 7.0-compatible before updating. One incompatible plugin in that stack and you’ve got a broken contact form, a failed backup, or a CRM that’s silently not logging anything. None of those problems announce themselves loudly. You find out weeks later, usually when it matters.
04This Isn’t a Security Emergency. You Can Stop Treating It Like One.
Major version releases like 7.0 are not primarily security patches. They’re feature and architecture releases. Security fixes come in minor versions: 7.0.1, 7.0.2. That’s where the “update immediately” urgency actually applies. Treating every major version bump as a critical security emergency is how you make rushed decisions that break things.
That said, staying on an unsupported version long-term creates real exposure. WordPress 6.x will continue receiving security patches for a while after 7.0 launches, but that window isn’t unlimited. Eighteen months from now, being on 6.x is a real security conversation. Right now, in the first few weeks after 7.0 launches, it isn’t.
The businesses that should feel actual urgency are the ones deferring updates for a year or more, now sitting multiple versions behind. At that point you’re not dealing with one update, you’re dealing with accumulated debt, and some of your plugins may have stopped receiving updates entirely. If your current “maintenance plan” is someone manually spot-checking plugin versions in the dashboard once a year, you’ve built a process around hoping nothing catches fire before the annual inspection. It will eventually catch fire. There will not be a warning.
05Your Actual To-Do List (Three Things, Done in Order)
Three things. Do them in order.
- Back up your site before touching anything. Full backup: database and files. If you’re automating your backup routine, confirm the most recent backup completed successfully and download a local copy. If you’re not automating backups, do this manually right now and then set up automation. This is the only step that protects you if something goes wrong, and something occasionally does.
- Audit your plugins before updating WordPress. Go to your plugins list and look at the “Tested up to” column for each active plugin. Any plugin that hasn’t been updated in 12+ months and isn’t showing 7.0 compatibility is a compatibility risk. Check the plugin’s page in the WordPress repository for recent updates or a note about 7.0 support. Contact the developer if it’s a premium plugin you’re paying for. If the plugin is abandoned, replace it now, not after you’ve already updated WordPress and it’s broken.
- Check your PHP version. Log into your hosting control panel and confirm you’re running a PHP version that meets 7.0’s requirements. Most managed WordPress hosts handle this automatically. Shared hosting on older infrastructure sometimes doesn’t. This takes five minutes and saves you a confusing support ticket later.
That’s it. No theme audit required unless your theme is older than three years and hasn’t been updated recently. No hosting migration needed unless your host is genuinely ancient. The rest of the checklist advice floating around is theater.
06Wait 6 Weeks or Wait 6 Months: Only One of These Is a Strategy
Deliberately deferring for 4–8 weeks after a major release is defensible and sometimes smart. Indefinitely is not a strategy. It’s a to-do item that learned to hide.
Wait if any of the following apply:
- You’re running WooCommerce and you’re within 6 weeks of peak season. Do not update your e-commerce stack during your highest-revenue period. A checkout breaking during Black Friday because of a plugin conflict costs more than any performance improvement is worth. Update after the season closes.
- You have a heavily customized theme that hasn’t been touched in years. A service firm with a custom theme built in 2019 and untouched since is a real compatibility risk. Test on a staging environment first, or wait until you can get an hour with a developer to check it properly.
- One or more critical plugins isn’t showing 7.0 compatibility yet. Give it 4–6 weeks. The developer may just be behind on the declaration even though the plugin works fine, or they may push an update in that window. If it’s still not updated after 6 weeks, the plugin is probably abandoned and you need a replacement regardless of which WordPress version you’re running.
- You’re in the middle of a site redesign or major content push. Don’t add an unknown variable to an already complicated project. Finish the work, then update.
What you shouldn’t do is wait 12+ months. Hosting providers and plugin developers eventually drop support for old versions. The longer you wait, the more likely you are to hit a scenario where updating WordPress also requires updating PHP, rebuilding your theme, and replacing two plugins simultaneously. That’s a day of work and several hundred dollars of developer time. The same update done within a reasonable window after release is a couple of hours.
If you’re trying to think through whether your overall setup is worth maintaining or due for a broader overhaul, the criteria for when to upgrade your tech stack applies here too. Sometimes the update question surfaces a bigger conversation about whether the platform still fits.
07The Verdict: It’s a Checkbox
WordPress 7.0 is not a crisis. It’s not the update that breaks everything, and it’s not the one you can safely ignore forever. It’s a normal, significant version release that requires about 45 minutes of attention, most of which is backup and plugin audit, not the actual update itself.
Update within the next 2–3 months. Back up first. Check your plugins. Confirm your PHP version. Then click update and go do something that actually moves your business forward.
If you’ve got critical incompatible plugins or you’re in peak season, wait 6–8 weeks and revisit. If your stack looks clean, update when you have 30 minutes and a recent backup. Either way, put a calendar reminder for 90 days out so this doesn’t quietly age into a problem.
It’s a checkbox. Treat it like one.
Jon Skalski has been working in business operations since 2019 and consulting for small businesses for the last 4 years. He works in HubSpot, Zapier, Make, Monday.com, Notion, Airtable, and an expanding stack of AI tools. He runs PulseOps. linkedin.com/in/jon-skalski
