What Does the WordPress 7.1 Roadmap Mean for Site Owners in 2026?

What is the WordPress 7.1 roadmap, and why should I care?

The WordPress 7.1 roadmap is the core team's public plan for the next major release after WordPress 7.0. Published in June 2026, it lists the features the project intends to ship, from new blocks to deeper AI tooling. If you run a site or advise people who do, it tells you where the largest CMS on the web is heading.

I do not build on WordPress myself. I run an SEO, AEO, and GEO practice with Webflow as my build platform. But I watch WordPress closely because most of my clients either came from it or still compare against it. When the biggest player publishes a roadmap, it shapes the whole conversation about where to build.

This piece breaks down what WordPress 7.0 already delivered in 2026, what the 7.1 roadmap promises, when it is targeted, and what the whole direction means if you are weighing your options. I am reading from the WordPress core team's own release notes and roadmap, not rumor, so you can act on it with confidence.

What did WordPress 7.0 already change in 2026?

WordPress 7.0 shipped on May 20, 2026, and it was a large block editor release. According to the WordPress core team's release notes, it added Visual Revisions for clearer edit history, two new core blocks called Breadcrumbs and Icons, a responsive Grid block, and an expanded Font Library with a dedicated management page. It also introduced a unified AI interface in core.

The headline for me is that AI moved into the core itself. WordPress 7.0 added what the project calls the AI Client, a single interface for connecting external AI models and plugins rather than leaving every plugin to bolt on its own. That is a real signal about where the platform sees its future, and it matters beyond WordPress users.

The editor changes are practical too. Breadcrumbs as a native block helps site structure, and Visual Revisions makes editing history something a normal person can read. These are the kinds of quiet improvements that make a mature platform easier to live with, even if they do not grab headlines the way an AI feature does.

What is WordPress 7.1 planning to add?

The 7.1 roadmap, published by the core team in June 2026, spans AI, admin experience, media, performance, and collaboration. Planned additions include new blocks such as Playlist, Table of Contents, and Tabs, an expanded Icon API, and richer Notes features like suggestion mode and emoji reactions for asynchronous feedback between editors.

The collaboration thread is the one I find most telling. WordPress is trying to make working together inside the editor feel modern, with comments, suggestions, and reactions that teams expect from tools like Google Docs. Notes with suggestion mode is a concrete step toward that, and it aims squarely at how content teams actually operate day to day.

On the AI side, the roadmap proposes further work on the AI Client introduced in 7.0, plus improvements to connectors and AI-powered content guidelines. In plain terms, WordPress wants AI to be a native part of the writing and building flow, not a plugin afterthought. That is the same direction the rest of the web tooling world is moving.

When is WordPress 7.1 coming out?

The release team is targeting August 19, 2026, for WordPress 7.1, according to its published roadmap. That is a plan, not a promise. WordPress dates have moved before, and features get cut late when they are not ready. Treat the date as a direction of travel rather than something to build a launch around.

I say this from watching how these releases actually land. A target date on a roadmap is the team's best intention at the moment it was written. Scope gets trimmed, testing surfaces problems, and priorities shift. The honest read is that 7.1 is coming in the second half of 2026, with the exact day subject to change.

For planning purposes, that is enough. If you run a WordPress site, you can expect another major update this year with meaningful editor and AI changes. If you are deciding whether to stay or move, you do not need the exact date. You need to know the platform is still investing heavily, which it clearly is.

Why does real-time collaboration keep slipping?

Real-time collaboration is genuinely hard, and WordPress has been honest about that. The feature was pulled from 7.0 shortly before release because of bugs and performance problems, and the 7.1 roadmap still lists it with open questions, including what to ship and which storage method to use. It is not confirmed for 7.1.

This is worth respecting rather than mocking. Live multi-user editing, the kind where two people type in the same document at once, is one of the toughest problems in software. Pulling it late instead of shipping something broken is the right call. I would rather a platform delay a hard feature than dump an unstable version on millions of sites.

It also sets realistic expectations. If collaboration is a core need for your team today, WordPress is not there yet, and the roadmap does not promise it will be in 7.1. That gap is exactly the kind of thing I weigh when a client asks whether to stay on WordPress or move to a platform where the workflow already fits.

What does the AI Client in WordPress mean for site owners?

It means WordPress is treating AI as core infrastructure, not a plugin. The AI Client introduced in 7.0, and extended in the 7.1 roadmap, gives the platform one standard way to connect external AI models. For site owners, that promises more consistent AI features and fewer competing plugins each doing their own thing.

I think this is a smart move, and it mirrors what I do on the Webflow side. The whole point of my work is making sure a site is understood and cited by AI systems, so a CMS building AI connection into its core is aligned with where traffic is going. The platform that makes AI native gives its users a head start.

The caution is that native AI features are only as good as how you use them. A built-in AI Client does not write accurate copy or earn citations by itself. It is plumbing. The judgment about what to publish, and how to make it trustworthy to both readers and machines, still sits with you. Tools help, but they do not replace the work.

Should this change how I choose between WordPress and Webflow?

It should inform the choice, not decide it. WordPress 7.1 shows a platform investing hard in AI and editing, which is reassuring if you are already there. But the roadmap does not fix WordPress's core tradeoffs around plugins, maintenance, and security. Those are still the reasons many of my clients move to Webflow.

My honest position is that the right platform depends on the team, not the feature list. WordPress rewards teams that can manage plugins, updates, and hosting, and its flexibility is real. Webflow rewards teams that want a visual, hosted, lower maintenance build. A strong 7.1 does not erase that difference. It just makes WordPress a stronger version of what it already is.

I have written about why studios keep making this move in my piece on why Webflow studios are dropping WordPress migration work, and about the SEO side in my WordPress to Webflow migration guide. The 7.1 roadmap is a reason to reassess, not a reason to panic or to switch on impulse.

How does the 7.1 roadmap affect my SEO and AI visibility?

Directly, very little. Your search and AI visibility come from content quality, clean structure, and technical health, and those are platform independent. WordPress 7.1 adds helpful blocks like Table of Contents, but a native block does not lift you into AI answers on its own. The fundamentals still decide who gets cited.

Where the roadmap matters is in making good practice easier. A native Table of Contents block and Breadcrumbs help structure, which both readers and answer engines like. But these are conveniences, not magic. I have seen sites on every platform rank and get cited well, and others fail, based entirely on the substance and structure of their pages.

This is the point I make to worried clients. A CMS update does not move your AI visibility. The market-share story, which I cover in my piece on WordPress losing market share to Webflow, is about workflow and maintenance, not about who ranks. Pick the platform that fits your team, then do the actual optimization work on top of it.

What should you do about the WordPress 7.1 roadmap now?

If you are on WordPress, read the roadmap and plan a test of 7.1 in a staging site before you update production. If you are weighing platforms, use it as a checkpoint to reassess your fit honestly. Either way, do not let a feature list pull you into a rushed migration or a rushed upgrade.

The bigger takeaway is that the whole web-building world is converging on AI-native tooling, WordPress included. That is good news, because it means your platform will keep gaining capabilities. It also raises the bar, because when everyone has AI features, the winners will be the ones who use them with judgment and honesty rather than hype.

If you want a clear-eyed read on whether WordPress or Webflow fits your business, and how to set either one up to actually get found by Google and AI answer engines, I am happy to talk it through. I do this assessment for clients often, without pushing anyone toward a platform they do not need. Reach out and let's chat.