A blog approval workflow for small teams: who drafts, edits, checks and publishes

6 min read·16 October 2026

When two or three people share a blog, posts tend to fail in one of two ways: they sit in "nearly done" for weeks, or they go live without anyone checking them. A blog approval workflow fixes both by giving four jobs (draft, edit, fact-check, publish) a named owner each, with a handoff and a deadline between them. One person can hold more than one job, but nobody should be the only person who has checked their own post.

This isn't a problem only small firms have. In the Content Marketing Institute's 2025 research, 33% of B2B marketers named workflow and content approvals as a challenge, down from 41% the year before. Here's the checklist we'd use for a team of two or three.

Key takeaways

• A blog approval workflow gives four jobs a named owner each: drafting, editing, fact-checking and publishing.
• One person can hold more than one job, but nobody should be the only person who has checked their own post.
• Fact-checking is a separate pass from editing: open every source and find the number on the page, or take it out.
• Give every handoff a deadline, or posts sit in "nearly done" for weeks.
• In WordPress, giving drafters the Contributor role means every post needs someone else to publish it.

Before you start: name an owner for each job

• Name the drafter. The person who writes, or who prompts and shapes an AI draft. They own the post until they hand it over.
• Name the editor. Someone other than the drafter who reads for sense, voice and whether the post answers the question. In a team of two, you swap.
• Name the fact-checker. This can be the editor, but it has to be a separate pass. Reading for flow and reading for accuracy are different jobs, and doing both at once means one gets skipped.
• Name the publisher. One person who presses the button. If everyone can publish, nobody is sure whether a post was approved.
• Set a turnaround for each handoff. For example, two working days to edit and one to check. Without a deadline, "I'll look at it" becomes the place posts go to die.

Stage 1: the brief

• Agree the search query and the reader in one line. A post that targets something people already search for is easier to judge. Our guide to finding blog topics in Search Console shows where those queries come from.
• Write down what the post must include. Your own prices, examples or experience. These are the parts an outside writer or AI tool can't supply.
• Get a yes on the brief before anyone drafts. Most rewrites happen because the angle was never agreed, not because the writing was poor.

Stage 2: the draft

• Link every number to its source as you write. Fixing missing sources later costs the fact-checker far more time than adding them now.
• Mark anything you're unsure of. A comment like "check this" is better than a confident guess.
• Hand over with a short note. What it targets, what you're unsure of, and when you need it back.

If you draft with AI, our AI blogging workflow covers the steps from topic to draft in more detail.

Stage 3: the edit

• Check it answers the question in the first few sentences. If a reader has to scroll to find the point, move the point up.
• Read it aloud for voice. Does it sound like your business, or like every other post on the topic?
• Add the experience only you have. Google's own guidance asks whether content is "written or reviewed by an expert or enthusiast who demonstrably knows the topic well". A real job, a real customer question or a real mistake does that.
• Send it back with specific changes, not "make it better". One round of clear notes beats three rounds of vague ones.

Our checklist for editing AI content goes through accuracy, experience and voice line by line.

Stage 4: the fact-check

• Open every source link and find the number on the page. Not on a page that quotes the page. If you can't find it, the number comes out.
• Check dates. A statistic from an old survey may be true but out of date. Say the year or replace it.
• Check names, prices and product details. Google's self-assessment questions include whether content has "any easily-verified factual errors". Those are exactly the errors a careful reader spots.
• Check claims about your own business with whoever owns them. Prices and turnaround times change. The person who sets them signs them off.

Stage 5: sign-off and publishing

• Confirm the post has passed both the edit and the fact-check. A simple status (Draft, Editing, Checking, Ready) on your content tracker or CMS is enough.
• Add a byline. Google suggests asking whether "pages carry a byline, where one might be expected" and whether it leads to more about the author.
• Check the search title, meta description and slug. The search title is the blue link people see on Google, so it needs the main keyword near the front.
• Add two to five internal links. These are links to your own related posts, which help readers and help Google find the new page.
• Preview it on your phone, then publish. Broken images and odd line breaks are easier to spot on a small screen.

Stage 6: after it goes live

• Request indexing in Search Console. This asks Google to look at the new page rather than waiting for it to be found.
• Put a date in the diary to review it. The publisher or drafter checks clicks and impressions after a few weeks. Our guide to measuring blog performance in Search Console explains what to look at and when.
• Write down what slowed this post down. If the same handoff stalls every time, change the owner or the deadline, not the people.

Make your CMS enforce the blog approval workflow

A written process helps, but software that won't let a post skip a step helps more.

In WordPress, the built-in roles already split the work. The WordPress documentation describes a Contributor as "somebody who can write and manage their own posts but cannot publish them", while an Editor "can publish and manage posts including the posts of other users". Give drafters the Contributor role and the publisher the Editor role, and every post has to pass through someone else before it goes live.

Strapi offers review workflows with stages you define, such as Draft, Editing and Final Review, with roles controlling who manages each stage. Check whether your plan includes the feature before you build your process around it.

What no CMS can do is check facts or judge voice. A status of "Ready" only means someone clicked a button. The checks are only as good as the person doing them.

A good blog approval workflow comes down to a named person and a deadline for every handoff. Today, write the four jobs on a shared document, put a name next to each, and agree the turnaround times before the next post starts.

Frequently asked questions

Can one person run a blog approval workflow alone?

Partly. You can separate the passes by drafting one day and editing and fact-checking the next, but a second reader catches things you won't. Even a colleague outside marketing reading for accuracy is worth asking.

Should the fact-checker and the editor be different people?

Not necessarily, but they should be separate passes. Reading for flow and reading for accuracy pull your attention in different directions, so do them one after the other rather than at the same time.

Which WordPress role should a drafter have?

Contributor. WordPress lets Contributors write and manage their own posts but not publish them, so someone with the Editor role has to approve each one.

Do AI-drafted posts need a different approval process?

The stages are the same, but the fact-check matters more, because AI drafts can state wrong figures confidently. Open every source and confirm each number before the post moves on.

Researched and drafted with Blog AI, checked against its sources, and edited before publishing. How the checks work