WordPress follows a continuous release cycle, publishing major versions several times per year. As the WordPress 6.x series matures through its final minor releases, attention in the community is turning toward what WordPress 7 will bring. While no official announcement has fixed the release date, the WordPress roadmap and the ongoing Gutenberg development cycle give us a clear picture of what is coming.
This article summarises the anticipated changes in WordPress 7, what they mean for site owners, developers, and the wider ecosystem — and how AI tooling fits into the evolving WordPress landscape.
The Gutenberg Roadmap: Where We Are Now
The Gutenberg project — WordPress's block editor initiative — has been the central thread of WordPress development since version 5.0. The roadmap for Gutenberg identifies four phases:
- Phase 1 (complete): The block editor for post and page content
- Phase 2 (complete in WordPress 6.x): Full Site Editing — block-based templates, global styles, site editor
- Phase 3 (in progress): Collaborative editing — multiple users editing simultaneously, real-time cursors, comment threads in the editor
- Phase 4 (future): Multilingual — native WordPress translation tools at the block level
WordPress 7 is expected to be the release where Phase 3 (collaborative editing) reaches production maturity, along with significant improvements to Phase 2 (FSE) that address the rough edges still present in WordPress 6.x.
Anticipated Feature: Collaborative Editing
Collaborative editing is the feature that will most visibly distinguish WordPress 7 from its predecessors. Similar to how Google Docs shows multiple cursors and real-time edits from different users, WordPress 7 is expected to allow multiple administrators or editors to work on the same page or post simultaneously.
For teams managing content collaboratively — editorial teams, agencies working with clients, marketing departments — this removes one of WordPress's most significant pain points: the need to coordinate who is editing what to avoid conflicts and overwritten changes.
The technical foundation for this is already being built into the Gutenberg editor through Yjs, a conflict-free replicated data type (CRDT) library. The shift from a sequential edit model to a real-time concurrent model is architecturally significant and explains why Phase 3 has been in development for an extended period.
Full-Site Editing Maturity
WordPress 6.x introduced Full Site Editing — the ability to use block-based templates for every part of a theme, not just post content. Headers, footers, sidebars, archive pages, and 404 pages all became editable through the site editor.
However, the FSE experience in 6.x has felt unfinished for many users. The interface has multiple overlapping concepts (templates, template parts, patterns, global styles), and the navigation between them is not always intuitive. WordPress 7 is expected to bring a substantially refined FSE interface:
- A more unified site editor that reduces the cognitive load of understanding the template hierarchy
- Improved block pattern management — easier discovery, saving, and reuse of patterns across the site
- Better style variation handling — switching between theme style variations without breaking custom overrides
- Drag-and-drop template part repositioning in the site editor canvas
Performance: Speculative Loading and INP
WordPress 7 will continue the performance trajectory established in WordPress 6.x, which introduced image lazy loading, fetchpriority hints, and improved script loading strategies. Two areas are likely to see advances:
Speculative Loading
The Chrome team's Speculation Rules API allows browsers to pre-render or pre-fetch pages that users are likely to navigate to next. WordPress 7 is expected to implement native support for speculative loading, potentially through the Speculation Rules plugin being merged into core. For high-traffic sites, this can dramatically improve perceived navigation speed for users.
Interaction to Next Paint (INP) Optimisation
Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) as a Core Web Vital in 2024. INP measures responsiveness to all interactions on a page, not just the first one. WordPress 7 is expected to include editor and theme optimisations specifically targeting INP improvements, helping sites maintain good Core Web Vitals scores as Google's metrics evolve.
Data Views: A New Admin Interface Paradigm
One of the most exciting developments in recent Gutenberg releases is Data Views — a new, more powerful way of displaying and managing lists of content in the WordPress admin. Data Views provides a flexible grid/list toggle, inline editing, bulk selection, and filtering that goes far beyond the classic WP_List_Table interface.
In WordPress 6.5–6.7, Data Views was introduced for managing pages in the site editor. WordPress 7 is expected to roll out Data Views more broadly — potentially to the main Posts list, the Media Library, and plugin management interfaces. This would represent the most significant redesign of the WordPress admin list experience in over a decade.
Native AI Integration
The WordPress project is beginning to explore AI integration at the core level. While WordPress has historically been conservative about adopting external dependencies, the block editor's extensibility means AI features are appearing as block plugins and editor extensions in advance of any core integration.
WordPress 7 may introduce official extension points or APIs that make it easier for AI-powered plugins to integrate with the editor in a standardised way — rather than each plugin implementing its own workarounds. This would benefit tools like WP AI Agent by providing stable, official hooks for AI actions that currently rely on REST API calls and WP-CLI.
What Site Owners Should Prepare For
Each major WordPress release brings compatibility considerations. Here is what to keep in mind ahead of WordPress 7:
Review Your Theme
If your site still runs a classic (non-block) theme, WordPress 7's FSE improvements will not directly benefit you. Consider evaluating block themes — many are now mature and offer better long-term compatibility with where WordPress is heading.
Audit Plugin Compatibility
Plugins that interact with the editor — page builders, custom block plugins, SEO tools — may require updates when WordPress 7 ships. Subscribe to update notifications from your plugin vendors and check compatibility before upgrading your live site.
Test in Staging
As with any major WordPress release, always test WordPress 7 in a staging environment before applying it to a production site. AI-powered site management tools like WP AI Agent can simplify this process — you can ask the agent to clone your settings, run compatibility checks, and report on any issues found.
Embrace the Block Editor
WordPress's direction is unambiguously toward a fully block-based editing experience. Developers and site owners who invest now in understanding the block editor, FSE, and block patterns will be better positioned to take advantage of WordPress 7's improvements when they arrive.
The Bottom Line
WordPress 7 is not a revolution — WordPress rarely is. It is the continuation of a long-term project to modernise the platform while maintaining backward compatibility. The move toward collaborative editing, a more polished FSE experience, and better performance tooling all point in the right direction.
For site owners and developers, the best preparation is to stay current with WordPress 6.x releases, which are already rolling out many of the building blocks for WordPress 7's headline features. When WordPress 7 arrives, those who have kept pace with 6.x will find the upgrade straightforward.