WordPress.com Guidelines: A Practical SMB Review

The CODEW Business Intelligence | September 8, 2026

Disclosure: The CODEW participates in affiliate and partner programs, including with Automattic/WordPress.com. Some links in this article may earn us a commission at no additional cost to you. This does not influence our independent assessment — see our verdict below.

Photo by Markus Winkler from Pexels

I've lost count of how many times I've had to re-explain a publication's voice to an AI tool. Every new writer session, every fresh chat window, every tool swap — the same paragraph, typed out again: who we're writing for, how formal to be, which words we never use. It's a small tax, but it's a tax you pay constantly, and it never once occurred to the software that it should remember.

Automattic's new Guidelines feature, quietly added to WordPress.com, is the first real attempt from a major CMS to fix that at the platform level. It's not flashy. It's a settings page. But a settings page that gives every AI tool on a site a shared, permanent memory of what that site actually is turns out to matter more than most of the louder AI launches this year.

The problem nobody bothered to solve until now

Here's the pattern if you've run content across more than one person or more than one tool: someone explains the brand voice to the AI on Monday. Someone else explains a slightly different version of it on Tuesday. The AI image generator nails the aesthetic once, then misses it completely the next time, because "our aesthetic" was never written down anywhere the tool could actually reach. If a style guide exists at all, it's buried in a shared drive or a Notion page — everywhere except the one place generating the content.

Automattic's own team put it plainly in the feature's development notes: content standards today live scattered across documents, wikis, and institutional memory, which makes them hard to find while writing and even harder for any tool — human or automated — to apply consistently. Guidelines gives those standards one home inside WordPress itself, present at the exact moment someone's writing, not something you dig up afterward to check your work against.

Worth noting: Automattic is explicit that Guidelines isn't an AI feature dressed up as infrastructure. It works fine without AI in the picture at all — human writers get the same shared reference point. AI is just the part that benefits most, because AI is the part with zero memory between sessions otherwise.

One honest caveat: this is still an early-release feature. It's live across WordPress.com sites now, but not every AI surface on the platform reads from it yet, and Automattic hasn't pretended otherwise. Worth knowing before you build a workflow around it.

What you actually fill in

You'll find it under Settings → Guidelines, split into five sections:

Site — what this website is for and who it's for, in a paragraph.
Copy — tone, voice, formatting rules. Active voice, second person, sentence-case headings, whatever your house style actually is.
Images — visual style, mood, alt-text requirements, the difference between "on brand" and "technically a photo."
Blocks — rules scoped to individual Gutenberg blocks. A Heading can carry different instructions than a Button, which can carry different instructions than an Image block.
Additional — everything else. Accessibility requirements, legal language, banned terms, the stuff that should never appear on your site, period.

Fill these in once, and you're not scoped to a single AI tool or a single chat session. Right now that means the writing assistant, the image generator, and WordPress Agent — Automattic's newest AI feature, which is worth distinguishing from Guidelines itself. Guidelines is the memory; WordPress Agent is one thing that reads from it. They're related, not the same product, and more tools are likely to plug into that same memory over time.

Letting the AI draft its own leash

The detail worth calling out: if a site doesn't have guidelines written yet, Automattic doesn't leave that as homework. There's a "Generate guidelines" option that reads your existing published content and drafts a first pass — for whichever section you pick. It shows up as a suggestion you can accept, edit line by line, or dismiss outright. If you've already got AI-drafted guidelines in place, an "Improve guidelines" option lets it take another pass rather than starting from scratch.

Most brand-voice tooling makes you sit down and document standards you never wrote down in the first place — genuinely hard if you're a small team or an agency inheriting a client's years of unstructured archive. This flips it: the AI reverse-engineers a plausible starting point from what you've already published, and you edit it down to what's actually true instead of staring at a blank page.

That generation feature is gated to paid plans — Personal, Premium, Business, and Commerce, with free sites pointed toward an upgrade. Writing guidelines by hand, though, isn't behind any paywall. That's the right place to charge: the convenience of AI drafting it for you, not the ability to have standards documented at all.

Export, import, and not starting from zero every time

There's an Actions section at the bottom of the settings page that turns this from a single-site setting into something reusable: export the whole set as a guidelines.json file, import a previous export to replace what's there now, and browse revision history to roll back if a change didn't work out.

If you run more than one WordPress.com site — an agency with a client roster, a publisher with a network of properties, or just someone running a flagship site and a side project — that export path means you build a style guide once and carry it with you. It also means guidelines can be versioned the same way a post can, which matters the day an AI-suggested revision turns out worse than what it replaced.

Where this fits with the rest of what WordPress.com AI can do

Guidelines didn't show up in isolation — WordPress.com has spent the past year giving its AI tools more autonomy, from read-only access to a site's content, to write access that lets an agent draft and publish posts or fix alt text across a media library, to design-aware generation that already pulls your theme's colors and fonts automatically. Guidelines is the piece that extends that same "already knows your setup" logic from visual design to editorial standards — an agent that knows your color palette can now also know your house style and your banned words, without you repeating either in the prompt.

Who actually needs this

A one-person blog can get by without it — the brand voice already lives in one person's head, and every draft passes through the same filter before it goes live. Guidelines are for anyone managing more people, more sites, or more AI tools than they can personally proofread.

If you're an agency, this is a way to encode a client's rules once and hand editorial work to a junior writer or an AI assistant without either one needing a full rewrite. The export function turns that into a template: build a solid structure for one client, adjust the language, reuse the skeleton for the next onboarding. If you run a multi-author site, it replaces the Slack message that says "remember, we use sentence case for headlines" — the one you've now sent five times this quarter — with a rule the software enforces at the point someone's actually writing.

Should you actually turn this on?

My advice: yes, and it costs you nothing to try. Writing guidelines by hand is free on every plan, so there's no reason not to fill in at least the Site and Copy sections today, even if you never touch the AI-drafting shortcut.

The paid-plan "Generate guidelines" feature is worth the upgrade specifically if you're sitting on a site with real publishing history and no documented style guide — it turns hours of writing one from scratch into minutes of editing a draft. If you're a solo operator with a small, recent archive, or you already have a style guide written down somewhere, skip it; you'll get more accurate results typing your own rules in by hand than having the AI guess from a handful of posts.

Where it doesn't help: if your only AI use on the site is occasional one-off image generation, or a single writer who already keeps voice consistent, Guidelines solves a coordination problem you don't have yet. Set it up when you add a second writer, a second site, or your first AI publishing tool — not before.

Do this first

ACTION ITEMS

Go to Settings → Guidelines and fill in Site and Copy by hand — five minutes, free on any plan, and the highest-leverage part of the feature.
If you're on Personal/Premium/Business/Commerce with a publishing archive, try Generate guidelines on the Copy section and edit the draft down rather than writing from scratch.
Before relying on it for a client site, export the set as guidelines.json and keep a copy outside WordPress — treat it as a backup, not just a setting.
Don't skip the human review step on anything AI drafts against these rules. Guidelines steer output; it doesn't guarantee it.

Source Attribution

WordPress.com Support — "Set up content guidelines for AI tools"
Make WordPress AI Team — "Content Guidelines: A Gutenberg Experiment," make.wordpress.org
The Next Web — "WordPress.com lets AI agents write, publish, and manage your site"
CMSWire — "WordPress.com Enables AI Agents to Write, Manage Content"
ppc.land — "WordPress.com Write Capabilities Let AI Agents Edit Your Live Site"
TechCrunch — "WordPress.com Now Lets AI Agents Write and Publish Posts, and More"
WordPress.com Partner Brief — "Guidelines," August 2026

THE CODEW · BUSINESS INTELLIGENCE

Editorial Note

This piece is part of The CODEW Business Intelligence — practical technology and business guidance for SMBs, entrepreneurs, and operators deciding what tools are actually worth adopting.

Coverage is based on Automattic's public documentation and reporting cited above, current as of publication. Feature availability and plan requirements are subject to change; readers should confirm current details on WordPress.com before making purchasing decisions.

The CODEW