WordPress 7.1 Is Live: The Guidelines Feature Puts Your Editorial Rules Inside AI Workflows
WordPress 7.1 dropped.
The release went live on August 19, 2026, timed to the final day of WordCamp US in Phoenix. No fanfare required. What shipped is operationally significant for any content team using AI inside WordPress: a native system for storing editorial rules that AI tools can read before generating a single word, a more capable AI Client with streaming and vector embeddings, and an Abilities API that plugin developers can finally build production-grade automation against.
Real-time collaboration is still behind feature flags. React 19 is still coming. Those delays are fine, because what shipped is more immediately useful to editorial teams right now.
The Guidelines Feature: What It Actually Is
Find it at Settings → Guidelines once you update. Under the hood, WordPress 7.1 introduces a wp_knowledge custom post type with its own REST routes at /wp/v2/knowledge and dedicated *_knowledge_item capabilities. This is not a free-text notes field. It is a version-controlled, permissioned content store for three knowledge types: guideline, memory, and note.
The intent from the WordPress Core roadmap is explicit: Guidelines brings “a persistent, structured system for encoding editorial rules, brand voice, and content standards directly into WordPress for humans and AI alike.”
That distinction from “for humans and AI alike” is the operative phrase. When an AI plugin connects via the WordPress AI Client, it can query the Guidelines store before generating content. Your banned phrases, citation requirements, topic restrictions, and tone mandates live there. They are not embedded in a single prompt. They are site-level configuration that persists across every AI-assisted draft.
Guidelines can be exported from one WordPress property and imported into another. For teams managing multiple sites under a shared brand, that portability closes a real consistency problem.
AI Client: Streaming and Embeddings
Two new capabilities land in the PHP AI Client in 7.1.
Generation streaming renders AI output in real time inside the editor, no loading bar, no waiting for a complete response before the text appears. For editors sitting in review workflows, that is a meaningful reduction in friction per session. Multiply that across a daily publishing schedule and the time savings become material.
Embeddings are the bigger structural addition. The AI Client can now represent site content as vectors, enabling semantic search based on meaning rather than keyword matching. Stop thinking of this as a conversational feature. Think of it as coverage-gap detection. An AI tool with embeddings access can understand what your site has already said about a topic, identify what is missing, and generate content that extends rather than repeats your existing library.
No AI model ships with WordPress itself. No provider is pre-configured. You connect your own through Settings → Connectors. New in 7.1: Connectors accept username and application password authentication in addition to API keys, which removes a friction point for teams managing credentials through standard WordPress user accounts rather than third-party key stores.
Abilities API: Why Plugin Developers Care Now
The Abilities API, introduced as infrastructure in WordPress 6.9, picks up the execution capability it needs to build against in 7.1: a filterable execution lifecycle, custom validation, and enhanced querying and filtering. The WordPress Developer Blog describes it directly: “nearly everything you’d need to actually build against it.”
For content automation workflows, the practical effect is AI agents that can interrogate site capabilities before acting. An agent checks what the site can do, what the current user role permits, and what Guidelines say before executing. That architecture is auditable. It respects existing access controls. An agent inheriting Editor-level permissions cannot change site settings regardless of what it is prompted to do.
This is the permission model that makes scaled AI-assisted publishing defensible to editorial leadership. The checks are built into the platform layer, not enforced through prompt engineering alone.
One Block Change Worth Noting for Content Teams
The HTML block now supports editable nested core blocks. The Raidboxes release guide notes this is “a major advantage for AI-generated websites, as LLMs often output layouts in raw HTML.” If your team is ingesting AI-generated content that arrives as raw HTML and then cleaning it manually in the editor, that step gets shorter in 7.1.
What to Test Before You Update Production
The enforced iframe mode for block themes is the highest-risk change in this release. Any block built against Block API version 2 or lower will not render correctly in block-theme editors after the upgrade. Check your custom blocks and your essential third-party plugins. In block.json, the version field needs to read "apiVersion": 3.
The staging path is straightforward: install the WordPress Beta Tester plugin on a staging environment that mirrors your production plugin stack, confirm compatibility, then schedule the production update when you have a clean run. The August 19 release date held through four release candidates without slipping, which is a reasonable signal of build stability.
Speculative loading also moves from conservative to moderate in 7.1 when page and object caching are detected. On lower-powered hosting environments, background prerendering of pages will consume more server resources than before. Watch request rates in the first week post-update.
Configure Guidelines Before You Push AI Further
The Google August 2026 search volatility hit thin, AI-generated content hard. Pages with structured, human-reviewed content held rankings. The Guidelines feature is the WordPress-native mechanism for putting that human editorial judgment inside the AI workflow at the point of draft generation, not just at the review stage.
Set up your Guidelines store this week. Document your banned phrases, your citation standards, your topic scope, and your tone requirements as structured knowledge items. That configuration is now infrastructure. It is version-controlled, importable across sites, and accessible to AI tools that integrate with WordPress core.
That is a materially different operating model than prompting your way to brand consistency on every individual content request.
Frequently Asked Questions
What is the WordPress 7.1 Guidelines feature and where do I find it?
Guidelines is a native WordPress content system that stores editorial rules, brand voice standards, and content mandates in a wp_knowledge custom post type. Access it at Settings → Guidelines after updating to 7.1. AI tools that connect via the WordPress AI Client can read these guidelines before generating content. The guidelines can also be exported and imported between WordPress sites, which matters for teams managing multiple properties under a shared brand.
Does WordPress 7.1 include a built-in AI model or provider?
No. WordPress 7.1 ships the infrastructure: the AI Client, Connectors for authentication, the Abilities API, and Guidelines. You connect your own AI provider through Settings → Connectors using an API key or, new in 7.1, username and application password authentication.
How do vector embeddings in the AI Client affect content strategy?
Embeddings allow the AI Client to represent your site’s existing content as vectors, enabling meaning-based semantic search across your library. In practice, this gives AI tools the context to understand what topics your site has covered, identify coverage gaps, and generate content that extends your existing corpus rather than duplicating it. It is a foundation for topical authority workflows inside WordPress, not just a conversational search feature.
What is the biggest technical risk when updating to WordPress 7.1?
The enforced iframe mode for block themes. Any custom or third-party block built against Block API version 2 or lower will not render correctly in block-theme editors after the update. Check block.json for "apiVersion": 3 on all custom blocks and test on a staging environment before updating production sites.