WordPress 7.0 Armstrong: Operational Guide for Agencies — Migration Checklist, AI-Ready Plugin Management, and Secure Update Strategies for Live Sites

WordPress 7.0 “Armstrong” was officially released on May 20, 2026, marking the beginning of a new era for the platform. This isn't an incremental update: WordPress 7.0 marks the beginning of a new era, laying the foundation for artificial intelligence throughout the entire WordPress experience. For agencies managing live production sites, this release represents both a significant opportunity and a complex operational challenge.

The most controversial aspect of the release was the real-time collaboration (RTC) withdrawal announced May 8, 2026 due to concerns regarding attack surface, race conditions, server load, and memory efficiency. However, What is being distributed is more significant: native AI integration, a crucial moment in the history of content management systems, being the most consequential change not only in this release, but likely in any previous version of WordPress.

This operational guide offers agencies a structured framework for planning, testing, and implementing WordPress 7.0 on production sites, with a particular focus on managing AI-ready plugins and reducing downtime risks.

The Fundamental Innovations of WordPress 7.0 Armstrong

Understanding the building blocks of this release is essential before planning the migration. The biggest change in 7.0 is that WordPress Core can now natively speak with AI models. There are four components at play: AI Client (Core), a new client integrated into WordPress that manages communication with generative AI models.

Integrated AI Architecture: The Four Pillars

WordPress 7.0 launches four fundamental building blocks to help create its native AI architecture.

• AI Client (Core): A new WordPress client that manages communication with generative AI models. It does not create content itself; it serves as a standardized intermediary.
• Abilities API (Server): A PHP-side API for registering specific AI-powered capabilities (generate, summarize, suggest, etc.) and exposing them to other parts of WordPress.
• Client-Side Abilities (JavaScript): The JS counterpart to the Abilities API, with a built-in UI and command palette so that abilities can be invoked from anywhere in the editor.
• Connectors Screen: A central dashboard hub for managing connections to external AI services. It comes with three presets to get you started and supports your personal connections with a few authentication clicks..

Native AI is now integrated into WordPress core, with OpenAI, Google Gemini, and Anthropic Claude natively supported.. Crucially, The plugin is opt-in, so a default 7.0 installation is no more or less “AI-oriented” than a 6.9 installation until you activate it..

Modernized Dashboard and Command Palette

The admin receives a new color scheme and a visual refresh across all screens. Display transitions animate movement between admin pages. A Command Palette (keyboard shortcut Ctrl+K on Windows or ⌘K on Mac, also accessible via an icon in the top admin bar) gives you quick access to tools from anywhere in the dashboard..

PHP 7.4 as a Minimum Requirement

The minimum PHP version is 7.4. WordPress 7.0 removes support for PHP 7.2 and 7.3. This is a critical point: legacy sites on outdated PHP versions require a mandatory server update before migrating to WordPress 7.0.

Phase 1: Pre-Migration Audit and Risk Assessment

Migrating to WordPress 7.0 should not be rushed. The safest upgrade window is two to four weeks after the final release.. This period allows plugin developers to release compatibility updates and the community to report edge-case issues.

PHP Compatibility Audit and Hosting

The first operational step is documented:

1. Check the current PHP version: Check Site Health or your host's control panel for the current PHP version before updating..
2. Plan PHP update if necessaryIf the site is on PHP 7.2 or 7.3, upgrading to PHP 7.4 (minimum) must happen before WordPress 7.0. Ideally, PHP 8.4 is the best PHP version for most WordPress sites in 2026. The recommended PHP version starting in 2026 is PHP 8.3 or higher..
3. Contact the hosting providerConfirm that the infrastructure supports a minimum of PHP 7.4 and, preferably, PHP 8.3 or higher.

Critical Plugin Inventory

The highest risk areas during an upgrade concern legacy plugins and those that manage critical functionalities:

1. Existing AI plugins: You will still need plugins like Jetpack AI, AI Engine, or Rank Math Content AI for specific AI features, but now these plugins will work through a unified system. Plugins updated for WordPress 7.0 will automatically detect your configured providers and stop asking for separate API keys. As early adopters, initial use cases include AI Engine (which already supported multiple providers), Rank Math, and Jetpack AI..
2. Page Builder Plugin: Check your plugin stack for compatibility, especially any plugins that build their own AI integrations or manage their own admin list tables, as both areas see structural changes in 7.0.
3. WooCommerce and membership plugin: Not all plugins carry the same risk. Simple plugins like Classic Editor or Akismet are almost always safe to update immediately. Page builders, e-commerce plugins like WooCommerce, and membership systems carry a much greater risk because they control key parts of your site's functionality..
4. Custom plugin and custom theme: AI Client, new responsive block controls, and stackable patterns all touch on extension points that third-party plugins might use. If a plugin's readme still says “Tested up to: 6.8” or earlier versions, contact the plugin author or test on staging before updating..

Use the WordPress 7.0 Compatibility Checker plugin to identify potential issues.

Pre-Migration Audit Checklist

• ✓ Check the current PHP version and plan an upgrade if necessary
• Document all active plugins and check the “Tested up to” status on WordPress.org
• ✓ Identify legacy plugins (not updated in 6+ months)
• Map AI plugins and check WordPress 7.0 compatibility
• ✓ Test current theme on RC4 in local environment
• Contact commercial plugin vendors for compatibility roadmap
• ✓ Document custom code and custom hooks that interact with the admin

Phase 2: Staging Environment Preparation

Staging must have the same plugins, theme, PHP version, and data as production.. A misconfigured staging environment will not catch real problems.

Production Cloning and Staging Configuration

1. Full backup pre-clone: Before any update, perform a full backup (files + database) and verify that it is restorable. If the update fails, the backup is your immediate rollback plan. Without a verified backup, any update is a gamble..
2. Identical staging clonesUse the host's native tool or a cloning plugin like WP Migrate DB to replicate the structure, data, and configurations exactly as in production.
3. Staging isolation: Ensure that the staging environment is accessible only to internal teams and protected by a robots.txt file to prevent search engine indexing.
4. API Connectivity CheckIf the site uses external APIs (Stripe, Mailchimp, analytics services), verify that the test/sandbox keys work on staging.

PHP Configuration on Staging

If the staging PHP version differs from production, update it to the one planned for production. The good news is that you can update PHP in WordPress without breaking your site, as long as you follow the right process..

Phase 3: Structured Testing Procedures on Staging

Testing is not optional for a major release of this magnitude. WordPress 7.0 is stable, but planning for edge cases is the only professional response.

Test 1: Core Update in Isolation

1. Go to Dashboard > Updates on staging
2. Select only WordPress 7.0 (DO NOT update plugins/theme together)
3. Perform the upgrade and monitor for PHP errors in the debug log
4. Check that the dashboard has loaded correctly
5. Check Site Health (Tools > Site Health) for warnings

Test 2: Critical Plugin Compatibility

Verify plugin and theme compatibility with the target WordPress version using Site Health and the plugins pages. Update WordPress core first, as plugins and themes are tested against the latest core version. Update plugins one at a time, checking the site after each one. This immediately isolates issues if something breaks..

Best practices for plugin testing:

1. Update all plugins to stable (non-beta/RC) versions compatible with WordPress 7.0
2. Enable WP_DEBUG and WP_DEBUG_LOG to log errors to wp-content/debug.log
3. Verify each critical functional section:
   • Homepage and navigation
   • Contact Modules (Sending Test)
   • E-commerce: shopping cart, checkout, payment gateway (test environments)
   • User Management: Login, Registration, Profile
   • AI features if enabled: title generation, alt text, etc.
4. Check the browser console for JavaScript errors

Test 3: New Admin UI Verification

Say goodbye to classic WordPress rendered PHP list tables. DataViews is a new React-based content management interface for posts, pages, media, and users. This redesign fundamentally alters how the backend behaves, not just how it looks. Zero Reloads: filtering, sorting, and bulk editing happen instantly without a full page reload..

1. Check that the post, page, and media lists load quickly
2. Test filters, search, and sorting
3. Verify bulk editing of multiple posts
4. If you use plugins that add custom columns, verify that they are displayed

Test 4: Responsive Blocks and Device Visibility

WordPress 7.0 introduces customizable block visibility based on device type, allowing editors to hide or reveal blocks per device, without affecting other viewports.

1. Create a test page with blocks that use responsive visibility
2. View the page on desktop, tablet, and mobile
3. Verify that hidden/visible blocks behave correctly

Phase 4: AI Integration Planning and Connector Management

WordPress 7.0“s AI infrastructure is ”opt-in," not automatic. However, agencies must establish a consistent procedure for its setup and governance.

AI Connector Structure and Providers

The three predefined providers at launch are OpenAI (GPT-4o, GPT-4 Turbo, etc.), Anthropic (Claude), and Google (Gemini).. The new Connectors screen offers a site owner a place to manage connections to external AI services. Instead of scattering API keys and provider settings across individual plugins, WordPress is creating a central location to manage those services..

Connector Configuration Procedure for Agencies

1. Define AI provider policy for clientsStandardize on one or two providers to simplify support and auditing. The centralized Connector system is a major quality of life improvement for agencies managing many sites. Instead of tracking which API keys are configured in which plugins across dozens of client sites, you’ll have a standard location. This also makes it easier to control AI usage and costs across your portfolio..
2. Generate and store credentials securelyCreate dedicated API keys for each client site (not shared master keys) at your chosen provider. Store them in a company password manager (1Password, LastPass, Dashlane).
3. Configure Connectors after WordPress 7.0 upgradeGo to Settings > Connectors, select provider, enter API key, verify connection.
4. Document client configurationProvide the client with a guide on where to find the Connectors area, which AI features are enabled, and the usage policy (costs, data privacy).
5. Implement access controlLimit access to the Connectors screen to admin roles. Centralizing AI connections makes it easier to scale AI usage but also increases the risk of inadvertently broadening AI data sharing. Policies must be explicit, and role-based access must be verified..

API Capabilities for AI-Ready Plugins

Paired with the AI Client is the Abilities API. This is one of the most technically significant additions in WordPress 7. The Abilities API allows plugins, themes, and WordPress core itself to register their capabilities in formats that are readable by both humans and AI agents. In practical terms, this means that an AI assistant within WordPress can understand what your installed plugins can do and use them..

For agencies: when selecting AI-ready plugins for installation on WordPress 7.0, verify that they natively use the Abilities API rather than their own legacy AI frameworks. This reduces the technical support burden.

Phase 5: Final Pre-Production Checklist

Once testing on staging is complete and results are documented, run this checklist before moving to production.

Backup and Rollback Preparation

1. Full production backup: Verify that a full backup exists and confirm that both files and the database have successfully completed. A corrupt or partial backup is not a safety net.. Use UpdraftPlus, BackWPup, or the host's native tool.
2. Backup restore test: Restore the backup to a test environment to verify it works. Ideally, for major updates (PHP version change or WordPress core major version), keep the backup for at least 7 days in case delayed problems appear.
3. Document rollback procedure: If an update breaks something in production, you need a documented and tested rollback plan. The rollback should be executable in minutes, not hours. Document rollback steps for each type of update and ensure at least two team members can perform them..

Operational Window and Client Communication

1. Select low-traffic time slots: A safe routine remains simple and practical. Check that backups are actually working, then perform updates during slower traffic periods. After that, test the things that visitors use most, like forms or checkouts, and confirm that everything functions as expected..
2. Notify the client in advanceCommunicate the maintenance window, estimated duration (30 min – 2 hours depending on complexity), and post-upgrade steps.
3. Have team availableEnsure a senior developer is available for 2-4 hours after the update to monitor and address issues.

Final Checklist (12-24 hours before upgrade)

• ✓ Full production backup + restore test completed
• ✓ Staging updated to WordPress 7.0 and all tests passed (no critical PHP/JS errors)
• ✓ PHP updated on production if necessary and verified with phpinfo()
• ✓ All critical plugins tested on staging and updated if new versions were needed
• ✓ Theme tested on staging, no CSS/layout issues
• ✓ Documented AI connectors and provider credentials (if used)
• ✓ Documented rollback procedure and trained team
• ✓ Client notified of maintenance window
• ✓ Analytics tag verification (Google Tag Manager, pixel tracking) for post-update QA

Phase 6: Production Execution and Post-Update Monitoring

During the Update

Update WordPress core first, as plugins and themes are tested against the latest core version. Update plugins one at a time, checking the site after each one. This isolates issues immediately if something breaks.

1. Access Dashboard > Updates
2. Click “Update WordPress core” (7.0 Armstrong)
3. Wait for completion (2-5 minutes normally)
4. Check the dashboard is loaded, no white errors
5. Proceed with plugin updates one at a time (wait 30-60 seconds between updates)
6. Update the latest theme

Post-Update: First Contact (first 5 minutes)

1. Verify the homepage has loaded and the layout is correct
2. Log in to wp-admin, verify the new dashboard is loaded
3. Check the browser console (F12) for critical JavaScript errors
4. Test a page with a form: send a test email
5. If e-commerce: test cart, add test item, verify payment gateway in test mode

Post-Update: Full Check (1-2 hours later)

Perform a post-update verification checklist covering homepage, admin, modules, checkout, and browser console errors..

• ✓ Homepage: loading, images, mobile/desktop layout
• ✓ Navigation menu: all links work, submenus expand
• ✓ Search: test a search, check results
• ✓ Modules: send test, verify received email
• ✓ E-commerce (if applicable): add to cart, proceed to checkout, cancel (do not process real payment)
• ✓ Admin page: access with different roles (admin, editor, author), check permissions
• ✓ Media Library: Upload a test image and check that it displays correctly
• 5xx Error Rate: Monitor server logs for error spikes
• ✓ Performance: Compare Pagespeed Insights/GTmetrix with pre-upgrade baseline

Continuous Monitoring (24-72 hours post-upgrade)

If troubleshooting is taking longer than 15-30 minutes on a live production site, roll back to backup. It's faster and less risky than debugging under pressure. Fix the issue on a staging copy, then try the update again once you understand what went wrong..

• Monitors Sentry/Rollbar for unhandled errors
• Check PHP error logs for deprecation notices.
• ✓ Review Google Search Console for new crawl errors/404s
• ✓ Check INP metric (Interaction to Next Paint) in CrUX: After an update, you need to test your INP score. A healthy update keeps your interaction latency under 200ms. If an update makes menus or buttons feel sluggish, it's technically a “broken” update that harms your SEO and conversions..

Safe Update Strategies for Multi-Client Sites (Agencies)

Agencies that manage dozens or hundreds of websites cannot afford to update each installation manually. Tools like ManageWP, MainWP, or InfiniteWP allow you to manage updates across multiple WordPress sites from a centralized dashboard, with automatic pre-update backups, rollbacks, and status reports. For agencies managing dozens of sites, this automation is essential..

Recommended Automated Workflow

1. Automatic stagingClone the site to an isolated virtual staging environment for each client
2. Automated testRun test suite (page load, link verification, HTML validation)
3. Visual Regression Testing: Site backup, running updates in a staging environment, performing Visual Regression Testing, and deploying to production only if everything passes.
4. Notify and roll backIf tests fail, contact the DevOps team for manual investigation. If they pass, deploy to production automatically.
5. Post-deployment monitoring: Monitor uptime, 5xx errors, and performance for 24–48 hours

FAQ

Should I immediately update to WordPress 7.0 on May 20, 2026?

No. The safest update window is 2-4 weeks after the final release.. This period allows plugins to update compatibility and edge-case bugs to emerge. For critical production sites, wait at least 3-5 days for initial hotfixes. For agencies, plan client updates on a rolling basis over 2-3 weeks.

You should use PHP 7.0 or higher with WordPress 7.0.

PHP 7.4 is the absolute minimum. WordPress 7.0 is dropping support for PHP 7.2 and 7.3. However, PHP 8.4 is the best PHP version for most WordPress sites in 2026. The recommended PHP version as of 2026 is PHP 8.3 or higher.. If you are still on PHP 7.x, update before migrating to WordPress 7.0.

Will my current AI plugins work with WordPress 7.0?

It depends on the plugin. Most won't break, but some might need updates. The most significant compatibility issues are React 19 and the iframe editor, not the AI features specifically. Check with each plugin developer for WordPress 7.0 compatibility before upgrading.. Plugins like Jetpack AI, AI Engine, and Rank Math are already updating to support the native AI Client.

What happens to real-time collaboration (RTC) in WordPress 7.0?

Real-time collaboration and co-editing, previewed during beta and release candidate cycles, were not provided in the final 7.0 release. The official announcement, release notes, and Field Guide do not include the functionality. Watch for WordPress 7.x releases for a possible reintroduction.. It will likely return in WordPress 7.1 or later.

How can I disable AI in WordPress 7.0 if I don't want to use it?

The plugin is opt-in, so a default 7.0 installation is no more or less “AI-oriented” than a 6.9 installation until you activate it.. The Client AI is integrated but inactive until you configure Connectors and enable an AI skill. No data leaves your site until you explicitly allow it. For agencies that want to completely avoid AI, simply do not configure the Connectors.

Conclusion

WordPress 7.0 marks the beginning of a new era, laying the foundation for artificial intelligence throughout the entire WordPress experience. For agencies managing production sites, this release represents a significant architectural change that requires planning, rigorous testing, and communication with clients.

By following this operational checklist—from pre-migration audit, to structured testing on staging, to AI-ready management and secure update strategies—agencies can implement WordPress 7.0 Armstrong with confidence. The key is to avoid rushing and to treat the release as an orchestrated project, not as a quick update push.

For specific questions about plugin compatibility or hosting requirements, please refer to the Complete Operational Guide for WordPress 7.0 Armstrong and the WordPress AI Client Connector: Step-by-Step Technical Guide for detailed procedures on AI integration.