DEV Community

Usama Ejaz
Usama Ejaz

Posted on Originally published at justblogged.com

A Blog Style Guide That Fits on One Page (Filled-In Template)

Most style guide advice assumes a company with a content team. The top results for "content style guide" round up Microsoft, Google, Shopify, the BBC and the UK government. Zapier's guide lays out a 10-part outline and says a company with a handful of employees probably shouldn't bother yet.

For the full document, I think that's right. But a small team still needs something the day a second person starts drafting posts... a new hire, a freelancer, or an AI assistant. That something is one page, and you can write it in an afternoon.

It has eight short sections:

  1. Who you write for
  2. How you sound
  3. Words you use and avoid
  4. Claims and numbers
  5. Formatting
  6. Links and endings
  7. Images
  8. A check to run before submitting

Most of the rules come from one place: the corrections your reviewer keeps making.

The page, filled in

This is for a made-up firm, Pike Street Bookkeeping: four people and a freelance writer who drafts two posts a month. The rules are theirs. What's worth copying is the length and how specific each line is.

PIKE STREET BOOKKEEPING: BLOG STYLE GUIDE
Version 3, updated 4 November 2026. Owner: Dana (final say on anything here).

1. WHO WE WRITE FOR
Owners of service businesses with 2 to 20 staff who either do their own
books or have just handed them to someone. They know what an invoice is.
Most don't know what "accrual" means. Many read on a phone between jobs.

2. HOW WE SOUND
Like our best bookkeeper on a call: direct, calm, specific.
  Yes: "Send us last month's bank statements by the 5th and your books
        close by the 15th."
  No:  "We leverage best-in-class processes to streamline your
        financial journey."
"We" is the firm. "You" is the reader. No jokes about the IRS.
Two posts that sound right: "What a bookkeeper actually does each month"
and "Cash or accrual? The question to ask your accountant."

3. WORDS WE USE AND AVOID
  "bookkeeping," not "accounting services" (we are not CPAs)
  "client," not "customer"
  "QuickBooks Online" in full the first time, then "QuickBooks"
  US spelling. Numerals for all numbers. "$40", not "$40.00".
  Cut on sight: leverage, streamline, seamless, robust, journey,
  "in today's fast-paced world".

4. CLAIMS AND NUMBERS
Every number gets a link to its source, or "from our client files, 2025".
Tax dates and limits are checked against the IRS page on the day we
publish, and the post says when they were checked.
We never promise savings. We never name a client without written OK.

5. FORMATTING
Titles in sentence case. One question per post, answered in the first
two sentences. Headings are plain statements, 8 words or fewer.
Paragraphs of 4 sentences or fewer. Lists only for steps, or for
4 or more items of the same kind.

6. LINKS AND ENDINGS
At most one link to a service page, and only where it helps the reader
decide something. Link to our own older posts when they answer the
next question. End with the reader's next step, not "Contact us today!"

7. IMAGES
Cover from the Canva template in the shared drive. Screenshots cropped
to the part that matters, with client names blurred.
Alt text says what the image shows.

8. BEFORE YOU SUBMIT
Read the first two sentences alone: do they answer the title?
Every number has a source. No client named without permission.
Spellcheck set to US English. Submit with a note saying what you're
unsure about.
Enter fullscreen mode Exit fullscreen mode

That's about 380 words. A reviewer can keep it in their head, and a freelancer can reread it before every draft without resenting it.

Where the lines come from

Start from a blank page and you get adjectives: "friendly but professional", "approachable", "authoritative". Nobody can check a draft against an adjective. A useful line is one you can point at in a draft and say "this breaks rule 3".

So build it from what you already have:

  • Your last five posts and the edits made to them. If "customer" got changed to "client" in three of them, that's a line in section 3. If two posts spent a paragraph clearing their throat before the answer, that's the "answered in the first two sentences" rule.
  • What customers say on calls and in email. Describe the reader in their words. "Doesn't know what accrual means" is something a writer can act on. "Financially curious SMB owner" isn't.
  • The one mistake that would actually cost you. For a bookkeeper it's a wrong tax date. For a clinic, anything that reads as medical advice. For a builder, a price that sounds fixed. Write it as a rule about checking, not a warning.
  • Two of your own posts that sound right. Examples teach voice faster than descriptions. Name them in section 2.

The rule that keeps it short: a line goes in only after the same correction has been made twice. Once is a typo. Twice is a pattern, and writing it down saves you the third fix.

What the long outlines have that you can skip

Zapier's outline has 10 parts, four marked essential and six optional. Mapped onto the single page:

Zapier's outline Marked On the one-page guide
1. Company and product details Essential Folded into section 1, one line
2. Voice and tone Essential Section 2
3. Audience information Essential Section 1
4. Grammar, word usage, formatting Essential Sections 3 and 5
5. External or technical style guide Optional One line in section 3 ("US spelling")
6. Competitor information Optional Left out
7. Channel-specific guidelines Optional Left out: it covers one channel, the blog
8. Media, SEO and hashtag guidelines Optional Sections 5 and 7
9. Best-performing content and examples Optional Two post titles in section 2
10. Resources about the company Optional Left out

Three parts drop out. And three sections of the page have no source in the outline at all: claims and numbers, links and endings, and the pre-submit check.

On a small business blog those three are where the expensive mistakes happen. A slightly off tone costs you a little. A wrong price, a client named without permission, or a post that ends in a hard sell costs more, and the reviewer is the last person who can catch it.

Also leave out anything that's really a brand book. Logo spacing, colour codes and typefaces belong to whoever builds the site theme. A writer never touches them.

Getting people to actually use it

A guide sitting in a shared drive gets read once. Three habits keep it alive.

Number the rules and cite them in review. "Rule 4: this tax date needs a source and a checked-on date" is faster to write than a paragraph and easier to accept. It also shows you which rules get broken most, and those are the ones to reword.

Give it to every outside writer before the first draft. Paste it into the brief. "Rule 6" on draft one is much easier than explaining on draft four why every post ends with a sales pitch.

Give it to the AI assistant too. If anyone drafts with ChatGPT, Claude or similar, paste the guide into its instructions or the top of the prompt. One page fits easily. The specific lines (banned words, "answer in the first two sentences", "no client names") do more to stop a draft sounding machine-written than "write in a friendly tone" ever will. The draft still goes through review.

Keeping it to one page

Put a version number, a date and one owner's name at the top. When a new rule goes in, find one nobody has cited in a review for a few months and take it out. A guide that only grows becomes the 20-page document nobody opens.

Change it when the business changes: a new service, a new kind of reader, a mistake that reached the live site. Not when someone has a new opinion. The odd draft that sounds a bit off just needs a review comment.

And if you haven't published anything yet, write two or three posts first. You'll have real edits to pull rules from, which is the only place the good lines come from anyway.

Originally published on the JustBlogged blog.

Top comments (0)