Gutenberg 22.7 Introduces Content Guidelines: WordPress Wants AI to Know Your Brand Voice

Gutenberg 22.7, released on March 11, 2026, is a quiet release with loud implications. Alongside the usual bug fixes and polish, it ships two experimental features that reveal where WordPress is heading: Content Guidelines and the Connectors credential manager. Both are building blocks for AI-powered publishing in WordPress 7.0 and beyond.

What Happened

The headline addition is Content Guidelines — described officially as “a single place in WordPress to capture site-wide content standards and context, so publishing tools can manage content that stays on-brand and consistent.” In practical terms, it’s a new system where you define your site’s voice and tone rules, structural requirements, image guidance, and accessibility standards. These guidelines are stored as a custom post type with full REST API access, revision tracking, and import/export support.

The idea is straightforward: if AI tools are going to help write and edit content in WordPress, they need to know what “good” looks like for your site. Content Guidelines gives them that context. A corporate site with formal tone requirements and a personal blog with casual voice both get a structured way to communicate those standards to any AI-powered plugin that integrates with the system.

Alongside Content Guidelines, the Connectors system (which we covered last week) gets its admin interface in this release. Navigate to Settings → Connectors to manage API credentials for AI providers like OpenAI, Anthropic, and Google in one centralized location. Both features are marked experimental for now.

Real-Time Collaboration Gets 14 Bug Fixes

The other major focus of Gutenberg 22.7 is stability for Real-Time Collaboration (RTC), which is now enabled by default to match WordPress 7.0’s planned behavior. Fourteen separate bug fixes address issues including CRDT document persistence on save, emoji and surrogate pair synchronization, disconnect dialog behavior, and stale awareness state on browser refresh.

Global Styles also got an upgrade: block developers can now define custom CSS selectors in block.json that Global Styles will honor, allowing styles to target specific elements within a block rather than only the block’s root wrapper.

Why It Matters

Content Guidelines is WordPress’s answer to a real problem with AI content tools: they don’t know your brand. Every AI plugin currently has to solve this independently — asking users to paste style guides into settings fields, or just guessing. A standardized system means any AI tool can read the same guidelines, and site owners define their standards once instead of configuring every plugin separately.

Combined with the Connectors API for credential management and the official AI provider plugins, WordPress is assembling a complete AI publishing stack: credentials (Connectors) + context (Content Guidelines) + capability (provider plugins). Whether this becomes transformative or just another unused settings page depends entirely on how plugin developers adopt it.

What You Should Do

Both features are experimental and shipping in the Gutenberg plugin, not WordPress core yet. If you’re running the Gutenberg plugin, update to 22.7 and explore Content Guidelines under a test environment. If you’re waiting for WordPress 7.0 (April 9), these features will land as part of that release.

Developers building AI-powered WordPress tools should start designing against the Content Guidelines REST API now — it’s the signal WordPress is sending about how AI integrations should work going forward.

Sources

• What’s New in Gutenberg 22.7? — Make WordPress Core
• WordPress Gutenberg 22.7 Lays Groundwork For AI Publishing — Search Engine Journal
• WordPress Gutenberg 22.7: AI Connectors, Content Guidelines — ALM Corp