WordPress 7.1 gives your brand voice guidelines an API

WordPress 7.1, releasing August 19, sneaks in a small feature that matters more than the block additions getting the headlines: a new post type called wp_knowledge, built to hold a site's editorial and brand guidelines as actual content, readable by AI tools through the REST API and WP-CLI.

Right now, if you use ChatGPT, Claude, or an automation pipeline to draft anything for your business, your brand voice lives wherever you last typed it out: a Google Doc, a Notion page, or the top of a prompt you keep pasting in. Every tool starts from zero. Every writer on your team re-explains the rules. WordPress 7.1 is the first version of core software that treats those rules as something a machine should be able to fetch on its own.

What actually shipped in WordPress 7.1

wp_knowledge is a custom post type proposed for WordPress core by committer Greg Ziolkowski. Site owners write down their voice, tone, and content rules as entries. Writers see those rules as a checklist inside the block editor. Outside the editor, the same entries are exposed through the REST API and WP-CLI, so anything that can make an API call, including a script, a plugin, or an n8n workflow, can pull the current rules before generating text.

Why brand voice guidelines finally have a home

The point isn't the post type itself, it's where it lives. A style guide in a shared drive is something a person has to remember to open and copy from. A style guide exposed through an API is something software can check automatically, every time, without anyone pasting it into a prompt again. That's the actual gap this closes: telling an AI tool your voice once, instead of telling it once per tool, per week.

What to actually do about it

1. 1

   Write the rules down now

   Don't wait for 7.1 to land on your install. List your actual voice rules: sentence length, words you avoid, how you handle pricing language, what a good headline looks like for you. Ten bullet points is plenty.

2. 2

   Put them somewhere fetchable

   When 7.1 ships, migrate those bullets into wp_knowledge entries, or in the meantime keep them on one page with a stable URL you can point automations at.

3. 3

   Point your pipeline at that one source

   Update your ChatGPT custom instructions, your Claude project, and any n8n or Zapier step that drafts content so it pulls from that page or endpoint instead of a rule someone half-remembers.

4. 4

   Check the output before you trust it

   Generate the same piece two ways, once with the guidelines pulled in and once without. If you can't tell the difference, your rules are too vague to be worth automating.

If your business already runs on WordPress and you're feeding a chatbot the same three paragraphs of brand voice every week, that's worth fixing before the next feature ships. Tell me how your content actually gets written and I'll show you where the guidelines belong.