WordPress 7.0 & 7.1 in 2026: What Business Owners Need to Know Before Updating

2026 has been the busiest year for WordPress in a long time. WordPress 7.0 “Armstrong” shipped on May 20, 2026, bringing AI infrastructure into core and a rebuilt admin experience. Three months later, WordPress 7.1 “Mary Lou” followed on August 19 with responsive design controls and better collaboration tools. A third major release, 7.2, is planned for December.

If you run a business website on WordPress, you do not need to follow every developer note. You do need to know what changed, what could break, and how to update safely. This guide covers exactly that.

What’s new in WordPress 7.0 “Armstrong”

AI built into WordPress core

WordPress 7.0 introduced a shared AI foundation instead of leaving every plugin to reinvent it. The new AI Client gives plugins one standard way to talk to AI models, and the Connectors screen (Settings → Connectors) lets you add your AI provider credentials once. At launch, OpenAI, Anthropic (Claude) and Google (Gemini) were supported. The Abilities API lets plugins describe what they can do so AI assistants can use those features safely.

What it means for you: fewer duplicate API keys scattered across plugins, and a cleaner path to AI-assisted content, translation and support tools. As always, review what data each AI feature sends to third-party providers before enabling it.

A modernized admin

Classic admin list tables are being replaced by faster, filterable DataViews, and a Command Palette makes it quicker to jump between screens and actions. For teams managing lots of pages, posts or products, day-to-day admin work is noticeably smoother.

New blocks and design tools

The block and site editors received new blocks, stronger design controls and visual revisions, continuing WordPress’s move toward a full design system. If your site is built with Elementor or another page builder, these editor changes matter less day to day, but they still affect compatibility, which is why testing is important.

What didn’t ship

Google-Docs-style real-time collaboration was the most anticipated 7.0 feature and delayed the release from its original April date. Several release reviews report it was ultimately held back for a later version. Check the official WordPress 7.0 project page for its current status before planning a workflow around it.

What’s new in WordPress 7.1 “Mary Lou”

• Responsive styles without CSS: you can now set how blocks look at different screen sizes directly in the editor, for global styles and individual blocks.
• Better collaboration with Notes: formatted notes, @mentions with email notifications, inline notes on selected text and multiple conversations per block.
• New blocks: including a Playlist block for podcasts and audio.
• Connectors API for plugins: plugins can now register their own connectors on the Connectors screen introduced in 7.0.
• Accessibility improvements: a new accessible tooltips API, better screen-reader predictability and clearer admin labels.

The official WordPress 7.1 release page has the full feature tour.

Will WordPress 7.x break my website?

WordPress core updates themselves are heavily tested. Problems almost always come from the surrounding stack:

• Page builders (Elementor, Divi, Bricks, WPBakery) and their add-on packs.
• SEO, multilingual and caching plugins that hook deeply into the editor or admin.
• WooCommerce extensions and custom checkout code.
• Old PHP versions. WordPress recommends PHP 8.3 or newer. Sites stuck on old PHP are slower and more exposed to security issues.
• Abandoned plugins that have not been updated in a year or more.

A safe WordPress update checklist

1. Back up everything: files and database, stored off the server.
2. Check PHP: go to Tools → Site Health and confirm you are on a supported, modern PHP version.
3. Audit plugins and themes: remove unused ones, replace abandoned ones and confirm “tested up to” versions.
4. Update on staging first: clone the site, update core, theme and plugins, then test.
5. Test what makes money: contact forms, checkout, booking tools, logins, key landing pages and mobile layouts.
6. Check performance: re-run PageSpeed or Lighthouse to ensure nothing regressed.
7. Deploy during low traffic and keep your backup ready for a fast rollback.
8. Monitor for 48 hours: error logs, form submissions and analytics.

Updates are also a security task. Outdated plugins remain one of the most common ways small-business sites are compromised. Our guide to essential security measures for small businesses covers the rest of the basics.

How to take advantage of WordPress 7.x

• Tighten your editorial workflow with Notes and @mentions for reviews and approvals.
• Use responsive styles to fix mobile layouts without extra CSS. This matters for conversions, as we explain in our 2026 web design trends article.
• Consolidate AI tools through Connectors, with clear rules on what content is sent to AI providers.
• Pair updates with a performance review: see our speed optimization guide.
• Use the accessibility improvements as a reason to audit your whole site. Read our 2026 website accessibility guide.

Frequently asked questions

Should I update to WordPress 7.1 right away?

For most sites, update after testing on staging and waiting a few days for the first maintenance release. Keeping WordPress current is important for security, but a tested update beats a rushed one.

Do I have to use the new AI features?

No. The AI infrastructure is there for plugins to use. Nothing is sent to an AI provider unless you configure a connector and enable a feature that uses it.

Does WordPress 7.x work with Elementor?

Current versions of Elementor and Elementor Pro support the 7.x line, but add-on packs and older builder versions may not. Update the builder and its add-ons together, and test on staging first.