WordPress 7.0, codenamed Armstrong, landed on May 20, 2026, and it is the biggest core release the platform has shipped in years. If a WordPress 7.0 upgrade is sitting on your to-do list, do not click that blue Update button just yet. This release raises the minimum PHP and database versions, ships a native AI framework, rebuilds the admin with DataViews, and quietly postpones a feature a lot of people were waiting for. Get the order of operations wrong and you can knock a live site offline in seconds.

I have run this update across client sites, and the pattern is always the same. The sites that break are the ones that rushed. The sites that sailed through followed a checklist. This guide is that checklist, plus a plain-English breakdown of what actually changed and whether you should update today or wait.

Quick answer: should you upgrade to WordPress 7.0?

For most sites, a WordPress 7.0 upgrade is worth doing because every major release includes security fixes you want anyway. But do not rush it on a live site. Here is the short version:

  • Check your server first. WordPress 7.0 needs PHP 7.4 minimum (8.3 recommended) and MySQL 8.0 or MariaDB 10.6.
  • Back up your full site, files and database, before you touch anything.
  • Test on staging, not on production.
  • Wait for 7.0.1. The first maintenance release is scheduled for July 9, 2026, and it will clean up early bugs.
  • Update plugins and themes first, then update core during a low-traffic window.

Now let us get into the details.

What is WordPress 7.0 “Armstrong”?

WordPress 7.0 is the first major core release of 2026, and it follows the open-source project’s tradition of naming releases after jazz musicians. This one honors Louis Armstrong.

The release did not arrive on schedule. WordPress 7.0 was originally planned for April 9, 2026, then pushed back. The reason was not a small bug. The team hit a structural problem with the real-time collaboration framework, where sync data was being stored in post meta on a special internal post type. That approach disabled WordPress persistent query caches the moment anyone opened the editor, which is a performance problem you do not want shipping to millions of sites. The proper fix needed a dedicated database table, not a last-minute patch, so the team did the responsible thing and slipped the date. Armstrong went live on May 20, 2026.

If you want the official rundown, the WordPress.org release announcement and the developer-focused notes on the WordPress core blog are the primary sources. Bookmark both before you start.

WordPress 7.0 system requirements you must check first

This is the part people skip, and it is the part that decides whether your WordPress 7.0 upgrade is smooth or painful. Armstrong moved the floor on two things at once.

PHP 7.4 is the new minimum

WordPress 7.0 dropped support for PHP 7.2 and 7.3. The new minimum supported version is PHP 7.4, and the team recommends PHP 8.3 or higher for the best security and performance. PHP 8.4 is the fastest supported release if your stack is ready for it.

There is a catch that surprises a lot of site owners. If your server is still running PHP 7.2 or 7.3, WordPress will not offer you the 7.0 auto-update at all. Your site stays parked on the 6.9 security branch, and even the manual update is blocked until you raise your PHP version. The good news is you are not exposed in the meantime, since 6.9.x keeps receiving security patches. The bad news is you slowly fall behind on features and plugin fixes, which is its own kind of risk.

MySQL 8.0 or MariaDB 10.6 is now required

The database bar moved too. WordPress 7.0 requires MySQL 8.0 or MariaDB 10.6 as a minimum, up from the much older floor in previous versions. This is not arbitrary. The new DataViews admin interface relies on database behavior that MySQL 5.7 simply does not have. If you are on a cheap shared plan that has not touched its database engine in years, this is the requirement most likely to trip you up, and most hosts do not announce it.

How to check your versions in 30 seconds

You do not need a developer for this. Log in to your dashboard and go to Tools > Site Health > Info > Server. Expand the Server section and you will see your PHP version, your database type, and your database version listed right there. You can also check and change PHP from your hosting control panel. On most US hosts running cPanel or Plesk, you will find it under PHP Selector, MultiPHP Manager, or PHP Settings, usually without opening a support ticket.

[Screenshot placeholder: Tools > Site Health > Info > Server panel. Suggested alt text: “Checking PHP version before a WordPress 7.0 upgrade”]

What actually changed in WordPress 7.0

Armstrong is not a cosmetic update. It touches nearly every part of the platform. Here are the changes that matter.

A native AI framework built into core

This is the headline. Until now, adding AI to a WordPress site meant installing a separate plugin for each provider. WordPress 7.0 changes that with a built-in framework. The new WP AI Client is a core PHP library that gives you one standardized way to connect to AI services like OpenAI, Anthropic, and Google Gemini. Switching providers becomes a configuration change instead of a code rewrite. The new controls live under Settings > Connectors in your dashboard.

Sitting underneath this is the Abilities API, which first arrived in 6.9 and now extends to the browser. In plain terms, it lets WordPress describe what your site can do in a structured, permission-aware format that AI tools can read and act on. WordPress 7.0 adds a client-side Abilities API that brings that permission system into JavaScript, laying the groundwork for browser agents. This is the foundation for a lot of what comes next, and I cover the practical SEO angle further down.

DataViews replaces the old admin list screens

The classic WordPress List Tables, the screens you use to manage posts, pages, and media, are being replaced by a modern React-based system called DataViews. Armstrong expands it with a new Activity layout for timeline-style views and a compact view mode for dense lists. It is faster, more filterable, and it is the reason the MySQL requirement went up.

Browser-side media processing

WordPress 7.0 moves image work into the browser. Instead of your server decoding, resizing, and encoding every upload, the platform now offloads that to the visitor’s browser using WebAssembly. For content-heavy sites, this takes load off your hosting and speeds up the media workflow.

New and improved blocks

The block editor got real additions, not just polish:

  • Breadcrumbs block. Highly customizable and schema-ready out of the box, which is a quiet win for SEO.
  • Icon block. Supports scalable SVGs and ships with 88 preloaded icons.
  • Playlist block. Adds audio playback with waveform visualization.
  • Responsive Grid block. Multi-column layouts that reflow cleanly across devices, no custom CSS required.
  • Viewport-based block visibility. Hide any block on specific device types without touching code or installing a plugin.

There is also a developer-friendly change worth flagging. You can now register blocks using PHP alone, and WordPress generates the inspector controls for you. For teams that never moved to React, that lowers the barrier to building custom blocks.

Editor and design upgrades

Modern blocks now render inside an iframe in the editor, which isolates their styles so admin CSS and front-end CSS stop fighting each other. You also get live previews of block style variations, the ability to add navigation links straight from the List View sidebar, customizable navigation overlays, and stronger guardrails that protect complex patterns from accidental edits. Under the hood, the team hardened the codebase with static analysis tooling and brought the command palette to mobile.

What did not make the final release

Honesty matters here, because one headline feature is not in the box yet.

Real-time collaborative editing is postponed. This was the big one people expected, and it is exactly the feature that caused the release delay. The framework was tabled for 7.0 and is expected to ship in a future release once the database architecture is sorted out. There is a related developer note: if your plugins or themes still use classic meta boxes through add_meta_box(), plan to migrate to register_post_meta() and the PluginSidebar component, because classic meta boxes disable collaboration mode for a post once that feature lands.

Looking ahead, WordPress 7.1 is expected in August and 7.2 in December. During the 7.1 cycle, the team briefly shipped a React 19 upgrade in Gutenberg, then reverted it after plugins built for React 18 started crashing. They are now taking a more incremental approach with a compatibility layer. The takeaway for you is simple: the React 18 to 19 transition is still in motion, so keep an eye on plugin compatibility through the rest of 2026.

Should you upgrade to WordPress 7.0 right now?

Here is my honest take. Yes, you should plan a WordPress 7.0 upgrade, because major releases carry security fixes and you do not want to drift onto an aging branch. But timing matters.

If you run a simple site with mainstream plugins and you have a staging environment, you can move now after testing. If you run a revenue-critical site, an e-commerce store, or a setup with older or custom plugins, wait for the 7.0.1 maintenance release scheduled for July 9, 2026. The “wait for x.0.1” rule exists for a reason. It gives plugin and theme developers a few weeks to push compatibility updates and lets the first round of bugs surface on other people’s sites instead of yours.

The one thing nobody should do is hit Update on a live production site the day a major version drops. That is how a quiet Tuesday turns into an emergency.

The pre-upgrade checklist

Run through this before you start. Skipping steps is where WordPress 7.0 upgrades go wrong.

  1. Take a full backup. Files and database, stored somewhere off the server. If your host offers one-click backups, use that and download a copy too.
  2. Confirm PHP is 7.4 or higher. Aim for 8.3. Check under Tools > Site Health > Info > Server.
  3. Confirm your database meets MySQL 8.0 or MariaDB 10.6. If it does not, contact your host before going further.
  4. Update every plugin and theme to its latest version. Outdated extensions are the number one cause of post-update breakage.
  5. Check plugin and theme compatibility with WordPress 7.0, especially anything that touches the block editor.
  6. Note any custom code. If a developer built custom functionality, especially anything using classic meta boxes, flag it for review.
  7. Spin up a staging copy and run the full update there first.
  8. Test the important stuff on staging: contact forms, checkout, login, and any membership or booking flows.

How to upgrade to WordPress 7.0 safely, step by step

Once your checklist is clean, the WordPress 7.0 upgrade itself is straightforward.

  1. Pick a low-traffic window. Late evening or early morning in your main timezone.
  2. Put the site in maintenance mode if you have a plugin for it, so visitors do not catch a half-updated page.
  3. Run the update on staging one more time and click through the key pages.
  4. Update core on production from Dashboard > Updates, or let your managed host run it.
  5. Clear every cache: your caching plugin, your host’s server cache, and your CDN.
  6. Walk the site like a visitor. Homepage, a few posts, a service page, the contact form, and checkout if you sell anything.
  7. Recheck Site Health for any new warnings.
  8. Watch your error logs for 24 to 48 hours. Most problems show up fast.

If anything looks wrong, this is exactly why you took that backup. Roll back, fix the issue on staging, and try again.

Common WordPress 7.0 upgrade problems and how to fix them

Even a careful WordPress 7.0 upgrade can hit a snag. Here are the usual suspects.

The update is not being offered. This almost always means your PHP version is below 7.4 or your database is below MySQL 8.0. Raise the PHP version in your hosting panel, confirm the database, then retry.

White screen or critical error after updating. Usually a plugin or theme conflict. Restore your backup, then on staging deactivate plugins, update core, and reactivate one by one to find the culprit.

A form, checkout, or login stopped working. Test these specifically after every update. The fix is normally an updated version of the relevant plugin, or a compatibility patch from its developer.

Collaboration mode acting strangely on a post. If you have started testing collaborative features, classic meta boxes can disable them. Migrate that custom code to the modern APIs.

A site stuck on 6.9. If you cannot meet the new requirements right now, you are not in danger, since 6.9.x still gets security patches. But treat it as a hosting upgrade you need to schedule, not ignore.

This is the part most upgrade guides miss, and it is the most important shift in the whole release.

With the Abilities API and the WP AI Client baked into core, a WordPress site in 2026 is no longer just a place humans read. It is a structured system that AI agents can understand and act on. As more plugins describe their capabilities through the Abilities API, assistants like Claude and ChatGPT can discover what your site can do and even take action through proper permissions.

For anyone who cares about visibility, that has a direct consequence. Answer Engine Optimization, the practice of getting your content cited by AI answers, is becoming as important as classic SEO. The good news is the basics are not complicated. Publish clear, well-structured content. Use schema, and Armstrong’s new schema-ready Breadcrumbs block helps here. Keep an llms.txt file. And add a visible “Last updated” date to your cornerstone pages, because AI engines weight recency and that single line measurably improves how often your content gets cited.

If you want help getting a site ready for both human search and AI answers, that is exactly the kind of work our team does at Kavcom Expert. A clean WordPress 7.0 upgrade is the foundation. Structured, AI-readable content is what gets you found.

Frequently asked questions

Is WordPress 7.0 safe to upgrade to?

Yes, for most sites. Major releases include security fixes, so staying current is the safer long-term choice. The smart move is to back up, test on staging, and wait for the 7.0.1 maintenance release on July 9, 2026, before updating a revenue-critical production site.

What PHP version does WordPress 7.0 require?

WordPress 7.0 requires PHP 7.4 as the minimum. PHP 8.3 or higher is recommended for the best security and performance. Sites running PHP 7.2 or 7.3 will not be offered the update until they upgrade PHP.

Will my plugins break after the WordPress 7.0 upgrade?

Most well-maintained plugins are fine, but outdated or abandoned plugins are the most common cause of problems. Update everything to its latest version first, test on staging, and check that any plugin touching the block editor lists WordPress 7.0 compatibility.

What happened to real-time collaboration in WordPress 7.0?

It was postponed. The collaborative editing framework needed a database architecture change that could not be rushed, which is why the release was delayed. It is expected to ship in a future version.

How long does a WordPress 7.0 upgrade take?

The core update itself usually takes a few minutes. The real time goes into preparation: backing up, testing on staging, updating plugins and themes, and verifying key features afterward. Budget an hour or two to do it properly on a typical small business site.

Do I have to upgrade to WordPress 7.0 right away?

No. If you cannot meet the PHP or database requirements yet, your site stays on the 6.9 branch and continues to receive security patches. Plan the upgrade rather than forcing it, but do not put it off indefinitely, or you will fall behind on features and fixes.

Tags: