WordPress 7.0 Armstrong Is Live Is It Safe to Update Your Site?

We updated our own ScitSol website to WordPress 7.0 last night before recommending it to a single client. Within 90 seconds of updating on our staging environment, WP Rocket flagged a caching compatibility notice tied to the new admin colour scheme rendering. Caught it, resolved it, pushed live cleanly this morning. That 90-second catch on staging would have been a broken cache on a live site if we had skipped the test.

That is the pattern every major WordPress release creates. Business owners see the update notification, click it on their live site, and discover the problem the hard way. WordPress 7.0 Armstrong is the biggest release in years; the stakes of updating without checking are higher than usual. This guide tells you exactly what to check, in what order, and what is genuinely worth getting excited about once you are safely on 7.0.

Is WordPress 7.0 Safe to Update?

Yes, but not without preparation. The update itself is stable. The risk comes from the gap between WordPress core and your specific combination of plugins, theme, hosting environment, and PHP version.

The sites that will have problems after updating to WordPress 7.0 fall into predictable categories. They skipped the PHP version check. They updated a live WooCommerce store without testing first. They run a plugin that has not been maintained for 18 months. None of these are WordPress 7.0 problems; they are preparation problems.

Work through the following checks before touching the update button, and the risk drops significantly.

Step :1: Check Your PHP Version First

This is non-negotiable. Do this before anything else.

How to Check Your PHP Version

WordPress Admin → Tools → Site Health → Info tab → Server section → PHP version

WordPress 7.0 raises the minimum supported PHP version to PHP 7.4, as confirmed in official WordPress 7.0 documentation. Sites running PHP 7.2 or 7.3 that update to WordPress 7.0 will run on an unsupported configuration, meaning security vulnerabilities go unpatched, plugin compatibility errors become likely, and some sites will produce immediate errors. In contrast, others develop failures over days or weeks as plugins detect the version mismatch.

The safest path:

PHP 7.2 or 7.3: Update your PHP version before touching WordPress. Contact your hosting provider and request a migration to PHP 8.1 or higher. On SiteGround, this takes two minutes in Site Tools → PHP Manager. Do not update WordPress until this is done.

PHP 7.4 or 8.0 is safe to update WordPress with, but consider upgrading to 8.1 or higher regardless, since 8.x delivers meaningful performance improvements.
If you are on PHP 8.1, 8.2, or 8.3, you are in the best position. PHP 8.3 is the version WordPress 7.0 recommends and the one we run on all client sites we manage.

If you are managing multiple websites and want this handled without navigating your hosting control panels, ScitSol’s website maintenance and support service includes PHP compatibility checks and version upgrades as part of the update process.

Step 2: Back Up Your Site Before Anything Else

A full backup before every WordPress major update is mandatory for both files and the database. If your host runs automatic daily backups, confirm the most recent one completed successfully before you proceed. If you use a backup plugin, run a manual backup now.

This step has no conditional logic. It applies to every site, every time, regardless of how confident you are in your setup.

Step 3: Check Plugin Compatibility

Which Plugins to Prioritise

Scroll through your active plugins list and flag any that have not been updated in the past six months. Check their WordPress.org plugin pages or support forums for any WordPress 7.0 compatibility notes.

The plugins most likely to surface compatibility issues in the first two weeks after a major release are those that interact directly with the WordPress admin interface, the block editor, or caching systems. In our experience managing WordPress sites across a range of industries, the first compatibility notices after a major release almost always come from caching plugins, SEO plugins, and page builders, the tools that sit closest to how WordPress renders pages and manages the admin.

Elementor, WooCommerce, Yoast, WP Rocket, and Gravity Forms are all actively maintained and will have 7.0-compatible versions available quickly if they are not already confirmed. Check each one before updating.

If you run any custom plugin built specifically for your business, have the developer who built it review compatibility before you update. Custom plugins do not have a development team monitoring WordPress releases and pushing updates. Compatibility with 7.0 is not guaranteed without a deliberate review.

Step 4: Use a Staging Environment

If your hosting provider provides a staging environment, use it. Update staging first. Test every function your site performs: contact forms, payment processing, booking systems, login flows, search, filters, anything a visitor or customer uses.

If you do not have a staging environment and your site is business-critical, SiteGround provides staging on all plans. Creating a staging copy of your site, testing the update there, and then pushing live takes longer than clicking the update button directly, but it eliminates the risk of downtime on a live site.

Should You Update Right Now or Wait?

For most business websites: wait 7 to 14 days from today.

Within the first two weeks of any major WordPress release, plugin developers push compatibility updates for their products. Waiting means you benefit from those fixes rather than discovering the incompatibilities yourself. The plugins with issues in the first 48 hours will be patched by day ten. Your site does not need to be the environment where you find out which ones they were.

Update sooner if:

• Your site is brand new and not yet live; there’s no reason to build on 6.9.
• You have a staging environment confirmed working on 7.0, and your plugins are all actively maintained.
• Your PHP is already on 8.1 or higher, and you run no custom code.

Wait longer than 14 days, or get professional help, if:

• You run a WooCommerce store. Wait for WooCommerce to release a confirmed 7.0-compatible version before updating anything. Your ecommerce revenue depends on that site functioning without interruption.
• Your site has custom plugins or custom code; a compatibility review is required before updating
• Your site processes payments or holds customer data; stability takes absolute priority over being on the latest version

What Actually Shipped in WordPress 7.0

AI Built Directly Into WordPress Core

The headline change in 7.0 is structural and will shape WordPress’s development for years to come. A new AI Client built into WordPress core allows your site to connect directly to generative AI models- OpenAI, Google’s Gemini, Anthropic’s Claude, or a custom model without needing a third-party plugin to bridge the connection. You set up your preferred provider once through a central Connectors screen in the dashboard, and those AI capabilities become available across your site.

The optional AI plugin extends this further: generating and editing images, creating post titles and excerpts, suggesting alt text for images, and automating content production tasks that currently require separate paid tools.

What this means for your business in plain terms:

If you publish regular blog content, drafting and editing get faster. If you run a WooCommerce store, writing product descriptions and generating image alt text becomes accessible without adding another paid subscription. If you have multiple people contributing to your site’s content. Workflow automation through the new Abilities API becomes a practical option rather than a developer-only capability.

The more significant strategic question this answers is whether businesses should stay on WordPress or migrate to newer platforms with native AI built in. For most Australian small and medium businesses, the answer is now clearly to stay on WordPress. You retain your existing site, SEO history, plugin stack, and content, and add AI capabilities on top rather than rebuilding from scratch on an unfamiliar platform.

Google’s helpful content system, now a permanent part of its core ranking algorithm, evaluates whether content demonstrates genuine expertise and first-hand experience. AI-drafted content that does not meet that bar does not rank, regardless of which platform produced it. If you want to understand how to use AI in your content production without creating ranking risk, our SEO content strategy guide covers this specifically.

The Modernised Dashboard

Command Palette: The Change You Will Notice Most

Press Cmd+K or Ctrl+K from anywhere in the WordPress admin, and a command palette appears with a search bar that lets you jump instantly to any page, post, plugin, setting, or admin action without navigating through menus. For anyone who spends meaningful time inside WordPress, this single feature changes how the dashboard feels to use day-to-day more than any visual redesign.

Visual Revision Scrubbing

You can now slide through previous versions of a post or page and see precisely what changed between versions rather than toggling between two static snapshots. For teams with multiple content contributors or editorial approval workflows, this removes one of the genuinely frustrating parts of managing version history in WordPress.

Refreshed Interface

WordPress 7.0 ships a fully updated admin interface with a new colour scheme and smooth transitions between screens. The visual change is noticeable but not disruptive; the layout and navigation structure remain familiar.

Dedicated Font Management

A single font management page now works across block, hybrid, and classic themes. Previously, font management was fragmented across theme settings and separate plugins. If your site was built with Elementor, your current font setup is unaffected. This becomes relevant when planning a future redesign or theme migration.

Four New Blocks

WordPress 7.0 adds four new blocks to the native block editor. If your site runs Elementor, these do not affect your day-to-day editing. They are most relevant for sites built entirely in the native block editor.

The Feature That Did Not Ship

Real-time collaborative editing was the headline feature of this release: the ability for two or more people to edit the same post simultaneously, each seeing the other’s changes in real time, like Google Docs inside WordPress. It was removed from the release on May 8, 2026, twelve days before launch.

The WordPress core team publicly confirmed the reasons: race conditions under concurrent editing, excessive server load, memory efficiency issues, and recurring bugs discovered during fuzz testing. The team chose not to ship a broken feature rather than delay the entire release—the right call.

It will be rebuilt for a future release. No confirmed date has been given for 7.1, 7.2, or beyond.

If your team needs multiple people editing content simultaneously right now, a well-structured WordPress development setup with clear role permissions and editorial workflows is the practical solution in the meantime. It is not native real-time collaboration, but it significantly reduces the friction of multi-contributor content management.

Pre-Update Checklist

WordPress 7.0 is worth updating to. If your time is better spent running your business than working through this checklist and managing staging environments, that is exactly what ScitSol’s website maintenance and support service exists for. We handle the process end-to-end: compatibility checks, PHP upgrades, staged updates, live deployment, and post-update monitoring. Your site stays current, and your time stays on your business.

Final Thoughts

WordPress 7.0 Armstrong is the most significant WordPress release in years. The AI infrastructure it establishes will compound through versions 7.1 and 7.2 as the Abilities API matures and more providers integrate with the Connectors hub. The Command Palette alone is worth updating once your setup is confirmed as compatible. The real-time collaboration delay is the right call. A stable release without one feature is better than a broken release that shipped it.

Update your site only after you have run through the checklist above.

Contact ScitSol to handle your WordPress 7.0 update.

FAQs

Is WordPress 7.0 safe to update to?

Yes, the core release is stable. The risk comes from your specific plugin stack, PHP version, and theme, not from WordPress itself. Check your PHP version first, back up your site, audit your plugins, and test on staging before going live. Sites that follow this process have very few problems.

What happened to real-time collaboration in WordPress 7.0?

Real-time collaborative editing was the most anticipated feature of this release and was removed on May 8, 2026, twelve days before launch. The WordPress core team cited race conditions, excessive server load, and memory efficiency problems discovered during testing. It will be rebuilt for a future release, with no confirmed timeline.

Should I update my WooCommerce store now?

No, not yet. Wait for WooCommerce to release a confirmed WordPress 7.0-compatible version. Updating your store before that confirmation risks breaking checkout, payment processing, or product management. The cost of downtime on an e-commerce site justifies waiting.

Will my Elementor site work after updating to WordPress 7.0?

In most cases, yes, provided Elementor has released a 7.0-compatible update. Check the Elementor changelog before updating WordPress. Your existing page designs and layouts are not affected by the WordPress update itself. The new AI features and blocks in 7.0 sit alongside your existing Elementor setup, not on top of it.

Is the AI in WordPress 7.0 free?

The AI Client and Abilities API are built into WordPress core at no cost. The AI capabilities themselves come from whichever provider you connect to, OpenAI, Google, Anthropic, or others- and those providers charge based on usage. The cost is your AI provider subscription, not WordPress.