WordPress 7.0 Is a Platform Shift, Not a Point Release

Please Keep Your Hands Inside the Car at All Times

WordPress 7.0 is scheduled for April 9, 2026. That matters because the smartest response is not hype or panic. It is planning. 7.0 is shaping up to be one of those releases that changes what WordPress can be, especially as the project keeps building a more formal foundation for AI capabilities and modern editing workflows.

This is an opinionated take from a working agency and integration shop. We like progress. We also like predictable rollouts. The goal is to understand what 7.0 is trying to enable, what is likely to be “Gutenberg-first,” and how to protect client sites while the ecosystem catches up.

1) The real story: WordPress is becoming a more capable application platform

Every major release has a list of features. The bigger question is, in what direction those features point.

WordPress 7.0 continues a pattern we have been watching for a while:

• WordPress is formalizing interfaces that used to live in plugin land.
• WordPress is making the editor and admin experience more application-like.
• WordPress is laying groundwork for AI-assisted workflows, but in a way that can be controlled, audited, and opted into.

If you build custom sites, maintain plugins, or run a portfolio of client installs, this is not abstract. It affects how you test, how you set expectations, and how you decide when a “major update” is safe enough to roll out.

2) AI in core: exciting, but the important part is the architecture

The most interesting AI-related work around 7.0 is not “WordPress ships with AI.” It is that WordPress is moving toward a standardized way for plugins and themes to request AI capabilities.

The direction here has been increasingly clear: AI in WordPress should be opt-in infrastructure. In other words:

• Core provides the plumbing and common interfaces.
• Nothing runs without explicit configuration.
• Providers and credentials are not assumed.

That is the right posture for client work. It reduces the risk of surprise costs, surprise data exposure, and surprise behavior changes.

From an agency perspective, the near-term value is not that every client site suddenly needs AI. The value is that when AI does make sense, the ecosystem can converge on fewer patterns instead of every plugin inventing its own.

3) Collaboration: likely valuable, but expect it to be Gutenberg-first

WordPress collaboration features are the kind of thing that sounds obviously useful. Real-time editing, comments, suggested changes, and better multi-author workflows can be a big deal for teams.

But here is the practical nuance: collaboration is an editor capability, and the editor in core is Gutenberg.

If you build primarily in the Block Editor, you are likely to see the earliest and most complete version of collaboration improvements.

If you build primarily with a page builder like Divi, do not assume you get the same collaboration experience automatically. Unless a builder is built on top of Gutenberg’s editing surface or explicitly integrates with the new collaboration APIs, those features will not show up in the builder UI by default.

This is not a knock on Divi or other builders. It is just a reminder to set expectations correctly. “Gutenberg-first” features tend to land in the Block Editor first, then spread outward as the ecosystem adopts the underlying APIs.

4) Stability and performance: the part that can hurt you even if you ignore new features

Most client sites are not waiting for AI features or collaboration to ship so they can immediately change their workflow. They are waiting so their site keeps working.

That is why our biggest concern with a major release is rarely the headline feature list. It is:

• plugin and theme compatibility,
• performance regressions,
• new defaults that change behavior,
• and edge cases that only show up at scale.

Even if you do not plan to use new features right away, new constraints can affect existing hosting configurations. That is where you can get “nothing changed, but everything feels slower,” or worse, “the site is broken and we do not know why yet.”

5) What we will test (and how) before recommending 7.0 broadly

If you maintain a portfolio of sites, you need a repeatable test plan. Here is a practical list that tends to catch the issues that matter.

Compatibility

• PHP version and extensions on each hosting plan
• Theme compatibility (especially custom themes)
• Page Builder compatibility (our own focus is Divi 4 and Divi 5)
• Critical plugins: security, caching, forms, page builder, SEO, backups
• Editor workflows: Block Editor, Classic Editor (if used), and any custom blocks

Performance

• Baseline page speed and TTFB before the update
• Cache behavior after the update (object cache, page cache, CDN)
• Admin performance for content-heavy sites
• Database load for sites with large post tables or heavy meta usage

Operational safety

• Confirm backups and restore procedures
• Confirm staging workflow and deployment steps
• Confirm monitoring and alerting for uptime and error spikes

This is not glamorous, but it is how you avoid spending release week doing emergency support.

6) A practical rollout posture for agencies

If you are a plugin author or you have a product that must be compatible on day one, you should be testing betas and RCs. That is part of the job.

If you are an agency responsible for client outcomes, it is reasonable to be more conservative. Your clients are not paying for you to be first. They are paying for you to be right.

A good posture looks like this:

• Disable automatic major updates across client sites.
• Test 7.0 on staging for a representative set of sites.
• Roll out in waves, starting with lower-risk sites.
• Keep a rollback plan that is actually tested.

Closing recommendation (agency POV)

WordPress 7.0 is scheduled for April 9, 2026. Yes, there’s value in testing betas and release candidates if you have a time-sensitive launch, a complex plugin stack, or you maintain products that need day-one compatibility. But for most client sites, our recommendation is simpler: wait until after the release, then test and roll out on your schedule. We’ve already disabled automatic major updates across our client portfolio so we can give 7.0 proper due diligence and protect client interests.