WordPress 7.1 Beta 1 dropped on July 15, and buried in the roadmap alongside responsive styling and React 19 prep is a feature that could change how you work with AI on your sites: Guidelines.
It's a new section under Settings → Guidelines in the WordPress admin. Think of it as a digital rulebook that lives inside your site — a place where you write down your editorial standards, brand voice, formatting preferences, and content rules. The twist is that it's not just for humans. It's designed so AI tools can read and follow those rules automatically.
The problem nobody talks about
If you've used AI to draft blog posts, product descriptions, or page copy for a WordPress site, you know the drill. You spend twenty minutes crafting a prompt that explains your brand voice. You paste in three paragraphs of style instructions. You specify tone, sentence length, whether to use Oxford commas, what words to avoid. The AI generates something decent. You tweak it. You close the tab.
Next week, you do it all over again. The context is gone. The AI doesn't remember your rules. Your coworker uses a different prompt entirely and gets copy that sounds like a different brand.
The Guidelines feature is WordPress Core's answer to this. You define the rules once, in your site, and they persist. Any AI tool that connects to your site through the MCP Adapter — Claude, Cursor, whatever comes next — can read them.
How it actually works
The Guidelines system pairs with the MCP Adapter that WordPress's AI team released in February 2026. The Adapter implements the Model Context Protocol, which is the standard that lets AI tools interact with external systems. It was built on top of the Abilities API introduced in WordPress 6.9, which gave WordPress a way to register functionality that's standardized, discoverable, and typed.
Guidelines sits on top of that stack. When an AI tool connects to your WordPress site and asks "what are the rules here?", the MCP Adapter serves up whatever you've written in your Guidelines settings. The AI doesn't need you to repeat yourself in every conversation. The rules travel with the site.
You can define things like:
- Brand voice and tone — formal, casual, somewhere in between
- Formatting preferences — heading structure, paragraph length, list usage
- Content rules — what topics to avoid, how to handle sensitive information
- SEO guidelines — keyword density, meta description style, internal linking patterns
- Audience targeting — who reads this site, what level of technical depth is appropriate
The AI reads these before generating content and treats them as constraints, not suggestions.
Why this matters more than another AI feature
WordPress has been adding AI features at speed since 7.0. The native AI Client with streaming and embeddings shipped in May. The MCP Adapter opened the door to external AI tools in February. But Guidelines is different because it addresses the trust gap.
Most AI integrations in WordPress are fire-and-forget: you prompt, it generates, you publish or don't. There's no institutional memory. Guidelines gives your site a persistent voice that survives across tools, across team members, across sessions.
For agencies managing multiple client sites, this is the feature that makes AI content generation viable at scale. Each site carries its own editorial DNA. You don't need to maintain separate prompt libraries or train your team on per-client style guides. The site itself becomes the source of truth.
For solo site owners, it means you can stop re-explaining your preferences every time you open a new AI tool. Write the Guidelines once, update them as your voice evolves, and let the AI adapt.
The bigger picture
The Guidelines feature is part of a broader shift in how WordPress thinks about AI. It's not bolting on a chatbot and calling it a day. It's building infrastructure — the Abilities API, the MCP Adapter, and now Guidelines — that makes the entire ecosystem AI-ready in a structured way.
The WordPress AI team also proposed adding a Knowledge post type alongside Guidelines, which would give sites a dedicated place to store reference material that AI tools can pull from. Think brand documentation, product specs, FAQ content — the kind of structured knowledge that makes AI responses more accurate.
Anne McCarthy, who's leading the 7.1 release, framed the whole cycle around collaboration. Guidelines fits that narrative: it's collaboration between humans and machines, mediated by the platform itself.
What to do right now
WordPress 7.1 Beta 1 is available for testing. If you want to get ahead of this:
- Test the Guidelines feature on a staging site. The beta is available through the WordPress Playground if you don't want to spin up a test environment.
- Start thinking about your editorial rules. Even if you don't use AI tools yet, writing down your content standards is useful for your team. Guidelines just makes that documentation machine-readable too.
- Install the MCP Adapter if you haven't already. It's been stable since February, and it's the bridge between your site and every AI tool that supports the protocol.
The final release lands August 19, timed with WordCamp US in Phoenix. Between now and then, the Core team is running weekly betas through July 29, followed by release candidates through mid-August.
If you've been waiting for WordPress to take AI seriously — not as a gimmick, but as infrastructure — 7.1 is the release that earns that trust.