Content Marketing · November 16, 2026 · 8 min read
How to Write a Blog Style Guide in One Page
A blog style guide works when it fits on one page and records decisions rather than taste. Here are the eight fields worth writing down, and how the same page doubles as an AI instruction.
By FluxWriter
A blog style guide for multiple writers is one page, not twenty, and its job is to record decisions rather than describe taste. Twenty pages gets skimmed once and never opened again. One page gets pasted into a freelancer brief, into a message to an editor, and into the instruction box of whatever AI tool you use. This walks through the eight fields that page needs, what belongs in each, and how to keep it honest once the drafts start arriving.
A Style Guide Records Decisions, Not Taste
Most style guides fail for the same reason. They describe a feeling. "Friendly but professional." "Authoritative yet approachable." Two competent writers read that and hand back very different drafts, and both are defensible, because nothing in the sentence can be checked.
A decision reads differently. "Second person throughout. Use you, never we, except in the final paragraph where the product is mentioned." An editor can mark a sentence wrong against that line in about thirty seconds, without an argument, and the writer knew which way to go before starting.
That gives you a test for every line you are tempted to add. Could an editor point at a specific sentence and say it breaks this rule, with no opinion involved? If not, it is taste, and taste belongs in the hiring decision rather than the document. What is left is narrow: the choices where two good writers would reasonably diverge.
Eight Fields Fit on One Page
The page has eight fields, and each one exists because leaving it out produces a visible inconsistency in the output.
- Reader. One sentence naming who the post is for and what they already know.
- Person and pronoun. You, we or I, and where each is allowed.
- Banned words and phrases. The list, with replacements, and no explanations.
- Claim rules. What may be stated flat, what must be framed as an assumption, what is never said at all.
- Numbers and evidence. Whether you cite sources, and what a writer does when there isn't one.
- Formatting defaults. Heading style, paragraph length, when a table earns its place, sentence case or title case.
- Mechanics. Spelling variant, serial comma, numerals, date format.
- The sample paragraph. Three or four sentences that only your business would have written.
As a rough target, the whole thing lands between 400 and 600 words. That is not a rule anyone can prove, but it is the length at which the page still gets read before someone writes.
The Person Decision Comes First Because Everything Inherits It
Person is the field with the widest blast radius. We pulls a post toward the company: we built, we found, we recommend. You keeps it on the reader's situation: your margins, your restart cost. Both are legitimate, and a blog that has not chosen will switch between them inside a single post, usually where the writer starts talking about the product.
So decide it, then decide the exception. A common shape is second person for the body, with first person permitted only where you describe something you did yourself, and only in the closing paragraph. Write that exception down; an undocumented one gets applied everywhere within about three posts.
The related decision is what you call the business the reader runs. "Your agency" reads differently from "your team", and differently again from "your organisation". Pick the word your customers use about themselves.
A Banned-Words List Is the Fastest-Acting Line on the Page
Two kinds of entry belong here. The first is the filler that every generic blog runs on: unlock, leverage, delve, seamless, game-changing, robust, in today's fast-paced world. The second is specific to you: a competitor's product name used as a generic noun, an industry term your customers do not say, a category label you have decided against.
Keep it short enough to check. As a rough rule, fifteen to twenty-five entries stays searchable; a list of two hundred stops being enforced and starts being ignored, which is worse than no list, because now the page has a section nobody trusts.
Write the replacement next to the ban, because the ban alone leaves a gap the writer fills with something equally vague. "Not utilise: use." "Not solutions: name the thing." That column turns the field from a complaint into an instruction, and it is the part an AI tool follows most reliably.
Claim Rules Decide What a Post Is Allowed to Assert
Sort every claim a writer might make into three buckets, and name them on the page. Assert flat: things well established and checkable in a minute. Frame as an assumption: your own estimates, worked examples, rules of thumb, anything from experience rather than a published figure. Never say: the ground your business is not in a position to speak on.
That third bucket deserves specific wording, because it is where a post creates real exposure. Do not let a writer state what the law requires, what a contract does, who owns a piece of work, or whether a practice is permitted. Recast those as the question the reader should be asking, or as a prompt to check the agreement in front of them and take proper advice. The same applies to anything touching health, financial recommendations or advertising rules, whether the writer is a freelancer or a model.
Two more lines close the field. No invented figures: if a number needs a source you do not have, it goes, or it becomes an example labelled as illustrative. And no promised outcomes. A post can say what usually moves and roughly how long it takes; it cannot say a page will rank.
The quickest way to work out which fields you actually need is to look at what the drafts are already doing wrong. The word budgets below are illustrative rather than measured, and they describe the length at which each field still stays checkable.
| What you keep seeing in drafts | The field that fixes it | Rough word budget |
|---|---|---|
| Posts switch between "we" and "you" halfway through | Person and pronoun | 25 |
| Every introduction opens with the same three filler phrases | Banned words and replacements | 120 |
| A draft states a percentage with nothing behind it | Claim rules | 100 |
| Headings alternate between questions and statements, and the casing drifts | Formatting defaults | 80 |
| The post could have been published by any competitor | Sample paragraph | 90 |
That is 415 words across five fields. The remaining three, taken together, rarely need more than another hundred, which puts a complete page at a little over 500 words.
The Same Page Works as a Model Instruction
The reason to write decisions rather than adjectives is that a model reads the page the same way a freelancer does. "Do not be salesy" changes almost nothing. A list of six exact phrases never to write changes the output immediately, because it names strings rather than a mood.
The sample paragraph does the heaviest lifting here. Register transfers by example far better than by description, so give three or four real sentences from a post you were happy with, then say what is happening in them: sentence length, whether numbers appear, how the first sentence commits to an answer.
Paste the page whole rather than summarising it, and treat what comes back as a draft. Specific rules tend to hold through a short piece and drift in the last third of a long one, so when you check a 2,000-word draft against the guide, read the closing sections first. That is where the pronoun slips and the banned words return.
A Style Guide Only Holds If Something Checks It
The page decays on its own. New writers arrive, phrases creep back, and the field that mattered most in March is settled by June. Give it one named owner and five minutes a month.
The mechanism that keeps it accurate is simpler than a review cycle. Whenever you correct a draft, ask whether the correction belongs on the page. If you have made it twice, it is a missing field, and writing it down costs less than making it a third time. Keep an add-only log at the bottom with dates, so a writer who disagrees can see when the decision was taken.
Keep this page separate from the per-post brief. The brief carries the topic, the keyword, the angle and the internal links. The style guide carries the decisions every post inherits. Repeating site-level rules inside each brief is how a one-page document quietly becomes eight pages spread across twenty files.
FAQ
Should every client or brand get its own style guide?
Yes, one page each, but most of the content will be shared. Keep a house page covering formatting, mechanics and the claim rules you apply everywhere, then a short per-client page that overrides person, banned words and the sample paragraph. Those three fields carry most of the difference between one client's blog and another's.
How long should a style guide be before it is too long?
One page, which in practice means somewhere around 500 words. The failure is not that a long guide is wrong; it is that it stops being opened, and an unopened guide produces exactly the inconsistency it was written to prevent. If a field genuinely needs more room, put the detail in an appendix nobody has to read to write a post.
Does a style guide slow writers down?
For the first post or two, slightly. After that it removes decisions the writer was otherwise making from scratch each time. The clearer saving tends to show up in editing rather than drafting, because fewer drafts come back for changes that were never specified anywhere.
The Practical Takeaway
Open your last five published posts and read only the first paragraph of each, side by side. Every place they contradict one another is a field: one says we and another says you, one opens with a question and another with an answer, one carries a number and three do not. Write those contradictions down as decisions rather than preferences, keep the page to about 500 words, and attach it to the next brief you send. The first action this week is the smallest one: put those five opening paragraphs in one document and mark where they disagree.
The page splits across two FluxWriter settings: the rules go into the site's custom writing instructions, and the post your sample paragraph came from goes in as a Brand Voice sample (on every plan).