WordPress.com Guidelines: A Practical SMB Review

Business Intelligence · Business Technology | September 8, 2026

WordPress Intelligence: Platform strategy, CMS market dynamics, AI features, and the business behind the web's most widely used CMS.

Affiliate 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.

Executive Brief

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 verdict: Worth turning on for any site with more than one writer, more than one AI tool, or more than one platform. Writing guidelines by hand is free on every plan. The AI-drafting shortcut requires a paid plan, starting at $4/month (Personal, annual billing).

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 Is WordPress.com Guidelines?

Guidelines is a settings page — Settings → Guidelines — where you define your site's content standards in five sections. Those standards become a persistent memory that compatible AI tools on WordPress.com read from automatically.

It is not the same as the WordPress Agent. Guidelines is the memory. The WordPress Agent is one consumer of that memory. They're related products, not the same product — and more tools are likely to plug into that same memory over time.

Guidelines are stored in site settings and require administrator access to view and edit. When editors, authors, and contributors use AI-powered tools, those tools automatically apply the site's guidelines.

Guidelines vs. WordPress Agent: What's the Difference?

Feature	Guidelines	WordPress Agent
What it is	A settings page storing site standards	An AI assistant that reads and acts on those standards
Function	Memory — stores the rules	Consumer — applies the rules when drafting, editing, publishing
Where it lives	Settings → Guidelines	Editor, Telegram, email, Slack
Plan gating	Free to write by hand; AI generation requires a paid plan	Requires paid plan
Can work without the other?	Yes — human writers get value	Yes — but without Guidelines, it re-learns context every time

What You Actually Fill In

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

Site

What this website is for and who it's for, in a paragraph.

Example: "This is a photography portfolio for a freelance photographer based in Seattle. All content should be professional but approachable. Avoid jargon and write for a general audience."

Copy

Tone, voice, formatting rules. Active voice, second person, sentence-case headings, whatever your house style actually is.

Example: "Use active voice and short sentences. Address readers directly as 'you.' All headings should use sentence case. Avoid idioms and cultural references that may not translate well."

Images

Visual style, mood, alt-text requirements, the difference between "on brand" and "technically a photo."

Example: "Use bright, natural photography with people as the primary subject. Avoid stock photos that look staged. All images must include descriptive alt text under 125 characters."

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.

Example: Heading block — use sentence case, keep headings under 8 words. Buttons block — use action verbs (Get, Start, Learn), limit to 3 words. Image block — always include alt text, prefer landscape orientation.

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 — and more tools are likely to plug into that same memory over time.

The AI-Drafting Shortcut

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. Nothing is saved until you choose to.

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.

Plan Gating and Pricing

Plan	Monthly	Annual (per month)	Generate Guidelines?
Free	$0	$0	✗ (upgrade prompt)
Personal	$9	$4	✓
Premium	$18	$8	✓
Business	$40	$25	✓
Commerce	$70	$45	✓

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.

Pricing verified as of September 2026. Verify current pricing on WordPress.com before purchasing.

Export, Import, and Revisions

There's an Actions section at the bottom of the settings page that turns this from a single-site setting into something reusable:

Export — download the whole set as a guidelines.json file
Import — upload a previous export to replace what's there now
Revision history — browse past versions and 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.

How Guidelines Fits the WordPress.com AI Stack

Guidelines didn't show up in isolation — WordPress.com has spent the past year giving its AI tools more autonomy:

October 2025: MCP (Model Context Protocol) support launched, giving AI agents like Claude, ChatGPT, OpenClaw, and Cursor read-only access to site content, analytics, and settings.
March 2026: Write access added — agents can now draft and publish blog posts, update image descriptions, organize tags, and reply to comments directly.
August 2026: Guidelines launched, giving agents a persistent memory of brand voice, editorial standards, and visual direction.

Guidelines is the piece that extends the 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.

The trajectory is clear: WordPress.com is building toward AI agents that operate on your site with the full context of your standards, not just your content. Guidelines is the memory layer that makes that possible.

What Guidelines Doesn't Do

Editorial honesty matters more than enthusiasm here. Guidelines is a genuinely useful feature, but it is not a complete content-governance solution:

It doesn't enforce anything. Guidelines steer AI output. They don't prevent a human writer from ignoring them, and they don't guarantee the AI will follow them perfectly every time.
Not every AI tool reads from it yet. The WordPress Agent, the writing assistant, and the image generator do. Third-party plugins and external AI tools may not — support is being added over time.
It's a settings page, not a workflow. There's no approval chain, no editor enforcement, no automatic rejection of off-brand content. You still need editorial review.
It's WordPress.com-specific. If you publish on multiple platforms — say, WordPress.com and Substack, or WordPress.com and a Medium publication — Guidelines only governs the WordPress.com side.
The AI generation is a draft, not a final answer. The "Generate guidelines" output reflects what the AI infers from your published content. If your published content is inconsistent, the draft will be too.

Bottom line: Guidelines is a strong first step toward platform-level content standards. It is not a replacement for editorial judgment or a human review process.

SEO and the AI Slop Problem

In February 2026, WordPress published official AI guidelines for its plugin and theme ecosystem, explicitly targeting what it called "AI slop" — hallucinated references, untested code, fabricated APIs, and mass-produced low-value content. The guidance gave maintainers authority to reject submissions that lacked apparent human oversight.

That same quality-over-volume principle applies to site content. Google's position has been consistent: AI-generated content is not penalized if it is high-quality, original, and helpful to users. What gets penalized is content that provides no value — the kind produced by prompting an AI to "write me a 2,000-word article about [keyword]" with no editorial direction.

Guidelines directly address the root cause of most AI slop: lack of context. When an AI tool knows the site's audience, voice, and standards, it produces content that reads like it was written by someone who understood the brief. When it doesn't, the output defaults to generic filler.

The SEO implication: Guidelines is not an SEO tool. But for SMBs using AI to produce content at volume, it is a practical defense against the content-quality problem that damages search performance — not through a penalty, but through irrelevance.

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.

It makes sense for:

Agencies — 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.
Multi-author sites — 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 applies at the point someone's actually writing.
Publishers and creators — keep first-person, conversational voice intact while letting the Agent handle polish and reviews. The words and voice stay yours; the AI handles the rest.
Ecommerce sites — product photography style and copy rules can be set once and applied consistently across every generated image and refined product description.
Developers building client sites — gives the WordPress Agent a durable, reviewable spec to work from instead of going rogue.

It's not necessary for:

Solo operators with small, recent archives — you'll get more accurate results typing your own rules in by hand than having the AI guess from a handful of posts.
Sites with existing style guides — if your standards are already documented and your team follows them, Guidelines adds a second place to maintain the same rules.
Sites with minimal AI use — if your only AI use 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.

The timing rule: Set it up when you add a second writer, a second site, or your first AI publishing tool — not before.

How Guidelines Compare

Approach	What It Does	Where It Falls Short
WordPress.com Guidelines	Platform-level memory read automatically by compatible AI tools; export/import for multi-site use	WordPress.com only; not every AI tool reads from it yet; no enforcement
Manual style guide (Notion, Google Doc)	Comprehensive, customizable, platform-agnostic	Not connected to any writing tool; requires manual paste-in for every AI session
Prompt libraries/custom instructions	Portable across tools (ChatGPT, Claude); customizable per session	Still requires manual application; no shared team memory; no version history
Specialized brand-voice tools	Deep analysis of brand voice from existing content; dedicated dashboards	Separate subscription; not integrated with the CMS; output still needs manual application
Human editorial review	Catches what no automation can; final quality gate	Doesn't scale; depends on the reviewer's availability and judgment

What makes Guidelines different: It's the first approach where the standards live inside the tool that's generating the content, rather than beside it. That's a small architectural difference with a large practical consequence — no copying, no pasting, no remembering to apply the guide. The rules are just there.

The CODEW Verdict: Should You Actually Turn This On?

Category	Rating	Why
Concept	★★★★★	Solves a real, recurring problem — AI tools with no memory of brand context
Execution	★★★★☆	Clean settings UI, export/import, revision history; limited tool support at launch
Value for SMBs	★★★★★	Free to write by hand; the highest-leverage part costs nothing
Value for Agencies	★★★★★	Export/import turns client onboarding into a template; versioning protects against bad AI revisions
AI-Drafting Shortcut	★★★☆☆	Useful for sites with real publishing history; less useful for new sites or solo writers
Maturity	★★★☆☆	Early-release feature; not every AI surface reads from it yet; no enforcement mechanism

The CODEW verdict: Yes, turn it on — 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.

The smart play: Set it up when you add a second writer, a second site, or your first AI publishing tool — not before. If you're a solo operator with a small, recent archive, or you already have a style guide written down somewhere, skip the AI drafting; you'll get more accurate results typing your own rules in by hand.

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 a paid plan 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; they don't guarantee it.

☐ Enable the WordPress Agent on your site if you want the Guidelines to actually be applied in the editor, via Telegram, or via email.

Frequently Asked Questions

Is WordPress.com Guidelines free?

Writing guidelines by hand is free on every plan, including the Free plan. The "Generate guidelines" AI-drafting shortcut requires a paid plan (Personal, Premium, Business, or Commerce).

Where do I find Guidelines on WordPress.com?

Go to your site's dashboard, then Settings → Guidelines. You'll need administrator access to view and edit them.

Do Guidelines work with AI tools other than the WordPress Agent?

Currently, the writing assistant, the image generator, and the WordPress Agent read from Guidelines. Support across plugins and third-party AI tools is being added over time. MCP-connected agents like Claude and ChatGPT may also read from Guidelines depending on the tool's implementation.

Can I export my Guidelines and use them on another site?

Yes. There's an Actions section at the bottom of the Guidelines settings page where you can export as a guidelines.json file, import a previous export, and browse revision history. This is particularly useful for agencies managing multiple client sites.

Do Guidelines enforce content standards automatically?

No. Guidelines steer AI output and give human writers a shared reference point. They do not prevent a human writer from ignoring them, and they don't guarantee the AI will follow them perfectly every time. Human review remains essential.

Will using Guidelines help my SEO?

Indirectly. Google does not penalize AI-generated content that is high-quality and helpful. Guidelines helps AI tools produce more original, on-brand content by giving them context — reducing the risk of generic, low-value output that damages search performance through irrelevance rather than penalty.

Is Guidelines available on self-hosted WordPress?

Guidelines is a WordPress.com feature. Self-hosted WordPress sites do not have access to it, though the underlying concept may be integrated into Jetpack or the Gutenberg plugin in the future.

What's the difference between Guidelines and the WordPress Agent?

Guidelines is the memory — a settings page where you define your site's standards. The WordPress Agent is one AI tool that reads from that memory and applies it when drafting, editing, or publishing content. They're related products, not the same product.

The CODEW Stat

Guidelines is free to set up by hand on every WordPress.com plan. The AI-drafting shortcut starts at $4/month (Personal, annual billing). For agencies managing multiple client sites, the export/import feature means a single style guide template can be reused across every onboarding — turning a recurring coordination cost into a one-time setup.

The CODEW