Content Brief

← Back to glossary · Category: Content

A content brief is the short plan handed to a writer before drafting begins. It states, in one place, the keyword or question the article must answer, the reader it is written for, the angle it will take, the outline it will follow, and the facts or examples it must include. A good brief is short enough to read in a few minutes and specific enough that two different writers, given the same brief, would produce recognisably similar articles. Without one, a writer is left to guess at the reader, the intent, and the standard of completeness, and the draft that comes back usually needs heavy reworking.

What a content brief is, and what it is not

In plain language, a brief is a promise about the article before the article exists. It answers the questions a writer would otherwise have to invent answers to: who is this for, what do they need, what must the article cover, what should it deliberately leave out, and how will we know it has done its job? When those decisions are made up front, drafting becomes execution rather than exploration, and editing becomes checking the draft against the brief rather than debating what the article should have been.

A brief is not a draft, and it is not a list of keywords to stuff into the text. A draft written in the brief defeats the purpose, because the writer then has nothing left to decide except how to reword what is already there. A keyword list without intent is worse than useless, because it pushes the writer toward repeating phrases rather than answering a question. The brief should name the primary question and the search intent behind it, and let the writer use natural language around it, including related terms only where they genuinely help explain the subject.

It is also not a straitjacket. A writer who discovers, while researching, that the planned angle misses the reader's real question should be able to raise that and have the brief revised. The brief exists to prevent aimless drafting, not to prevent thinking. The best briefs are treated as a working agreement: firm on the reader and the question, flexible on the exact wording and examples, and revisited when the research shows the plan was wrong.

Finally, a brief is not the same as a content gap analysis, though the two are often confused. Gap analysis finds the unanswered question; the brief turns that question into a plan for one article. One gap can produce several briefs, if the question breaks into distinct articles for distinct readers, and one brief should never try to cover several gaps at once. Keeping the two steps separate is what keeps each article focused on a single job.

How a content brief works: the key mechanics

A working brief has a small set of parts, and each part does a different job. The first is the reader: a sentence describing who the article is for and what situation they are in. "Small-business owners planning their first blog" leads to a very different article from "experienced marketers refreshing an old post", even on the same topic, because the two readers need different depth, different examples, and different next steps. A brief that skips the reader leaves the writer writing for everyone, which usually means writing for no one.

The second part is the question and intent. State the main question in the reader's own words, then state what kind of answer they want: a definition, a comparison, a step-by-step process, or a recommendation. This is where intent does its quiet work. A reader asking how to do something needs steps in order, not a discussion of why the thing matters; a reader comparing options needs honest differences, not a sales pitch dressed as a guide. Our glossary entry on title tags and meta descriptions covers how that promise is carried into the search result itself, where the title and description must match what the article actually delivers.

The third part is the outline: the headings the article will follow, in order, each tied to a sub-question the reader has. A good outline is a test of completeness before any drafting happens. Read the headings alone and ask whether a reader following them would reach a complete answer, and whether any heading answers a question nobody asked. If the outline fails that test, fix the outline, which takes minutes, rather than fixing a finished draft, which takes hours.

The fourth part is the evidence and examples the article must contain: the facts to check, the worked example to include, the common objection to address, and the internal links to use. This is also where the brief states what the article must not do: which claims to avoid, which neighbouring topics belong in their own articles, and where the article should hand the reader onward rather than trying to cover everything itself. A brief that names its boundaries saves the writer from the most common form of bloat, the article that tries to be a whole library.

The fifth part is the practical frame: the approximate length, the tone, the call to action, and the deadline. Length should be set by the question, not by a quota: a simple definition needs fewer words than a process with many steps, and padding a simple answer to hit a word count helps nobody. Tone should match the reader, plain and direct for busy owners, more technical only where the reader is technical. The call to action should follow naturally from the article, such as reading a related guide or trying a tool, rather than interrupting it.

Why it matters for a blog post and for search

For a single blog post, a brief is the difference between one draft and three. Writers who start from a brief produce drafts that need lighter editing, because the structure, the reader, and the scope were settled before the first paragraph. That matters most for small businesses, where the person writing is often also the person running the business, and rework is time taken directly from customers. A brief also makes it possible to hand writing to someone else, a freelancer or a colleague, without losing consistency, because the decisions that define the house style and standard are written down rather than held in one person's head.

For search, the honest scope is modest but real. A brief does not, by itself, improve how a page performs in results. What it does is make the conditions for a useful page more likely: a clear match between the question and the answer, a structure that follows the reader's sub-questions, and coverage that is complete without drifting into neighbouring topics. Search engines and readers both reward that kind of clarity, but neither is owed by the brief alone. The brief is a planning discipline, and its value shows up in the quality of the finished page, not as a direct lever on any result.

Common mistakes

The most common mistake is writing a brief that is really a keyword list. A page of phrases with target counts tells the writer what to repeat, not what to answer, and the resulting article reads like it was assembled around phrases rather than written for a person. If the brief's keyword section is longer than its reader and question sections combined, the brief has its priorities backwards.

The second mistake is the brief that tries to cover everything. When a brief lists every related question, every angle, and every possible subtopic, the writer faces an impossible article and usually produces a long, shallow one. A brief should be brave about exclusion: name the questions this article will not answer, and note which article will answer them instead. Exclusion is what gives an article its shape.

The third mistake is skipping the reader. Briefs written for "everyone" or "our audience" in general produce articles pitched at no particular level, with examples that fit nobody's situation. One sentence about who is reading, and what they are trying to do, changes nearly every decision that follows, from the opening example to the final recommendation.

The fourth mistake is never checking the draft against the brief. A brief that is filed away once drafting starts is decoration. The review step should be literal: read the draft beside the brief, heading by heading, and mark every promised sub-question that went unanswered and every section that drifted outside the brief's scope. That check is quick, and it catches most of the problems that otherwise surface only after publication.

How to apply it step by step to a small-business blog

Start with the reader's question, written as they would ask it. If you cannot write the question in one sentence, you do not yet have a brief; you have a topic area, and you need to narrow it. Ask what the reader will do with the answer, because that tells you the intent and the format. Someone who will act today needs steps; someone still deciding needs a comparison.

Next, look at what already answers this question well, including your own pages. Note the sub-questions those pages answer, and the ones they leave open. Your outline should cover the open ones and handle the familiar ones efficiently, not repeat everything from scratch. If your own site already has a page on part of the question, the brief should name it as the place to link, rather than asking the writer to cover that ground again. Our guide to the blog post outline template that ranks gives a ready-made structure for turning this research into headings.

Then write the brief itself, on one page: reader, question, intent, outline, evidence and examples, boundaries, length, tone, and next step. Share it with the writer before drafting, and invite one round of challenge: is the question right, is the outline complete, is anything missing? That conversation is cheap before drafting and expensive after it.

When the draft arrives, review it against the brief first and against style second. Check each heading against its promised sub-question, check the boundaries, and check that the title and description match the article's actual promise. Then, and only then, polish the prose. Our SEO blog writing checklist for beginners is a useful companion for that review pass, and how to write blog posts that rank on Google shows how the brief's decisions play out in a finished article.

Finally, keep your briefs. A folder of past briefs becomes a record of what your blog has promised and covered, which makes the next brief easier and prevents accidental duplication. When you revisit a topic, the old brief tells you what the earlier article was for, so the new one can be written as a genuine follow-up rather than a rewrite. A free metadata generator can help draft the title and description the brief promises, so the search result and the article stay consistent.

Chart: from brief to published article

The diagram below shows the brief's journey in four stages. Each stage has one job, and the arrow matters: work flows forward, but the review at the end can send a draft back for revision, which is a normal part of the process, not a failure of it.

Source note: qualitative process diagram. The sequence reflects the planning discipline described in Google's SEO Starter Guide, which covers titles, descriptions, and site structure as part of making pages understandable. See Sources below.

How this looks on Rankenza

Rankenza's own articles demonstrate the brief in action. Take the blog post outline template article: its reader is clear, its promise is in its title, and its headings follow the reader's sub-questions in order. The comparison below sets a typical brief-free workflow against Rankenza's method, as method against method, with no claim about traffic or results.

That review step is the brief's final check, applied to someone else's writing: does the finished article answer the question the research set out? Your first article is free, then $3.60 per article or $89 for 50 credits.

What the research says

According to Google's Search Central documentation on creating helpful, reliable, people-first content, a reader should leave a page feeling they have learned enough to achieve their goal, and content should show original information or analysis rather than restating what is already available. A brief is how a small team turns that standard into a working habit: by writing down the reader, the question, and the outline before drafting, the team gives itself something to check the finished page against. Google's SEO Starter Guide supports the same discipline from the structural side, covering how titles, descriptions, and internal links should reflect what a page actually contains, so the promise made in search matches the article delivered.

Sources

• Google Search Central, Creating helpful, reliable, people-first content: developers.google.com/search/docs/fundamentals/creating-helpful-content
• Google Search Central, SEO Starter Guide: developers.google.com/search/docs/fundamentals/seo-starter-guide

Frequently asked questions

How long should a content brief be?

As long as it needs to be to state the reader, the question, the outline, and the boundaries, and no longer. For most small-business articles, one page is enough. A brief longer than the article it plans has stopped being a plan and started being a draft.

Who should write the brief, the business owner or the writer?

Either can write it, but the business owner should at least approve the reader and the question, because those two decisions carry the business judgement. The writer can then own the outline and the evidence, and challenge the brief where the research shows it is wrong.

Can one brief cover a whole topic cluster?

No. A brief plans one article. A cluster needs one brief per article, plus a short note on how the articles link together. Trying to plan a cluster in a single brief produces articles that overlap and compete with each other.

What if the draft does not match the brief?

Decide which one is right. If the research showed the brief was wrong, revise the brief and let the draft stand. If the draft drifted, revise the draft. What should not happen is publishing a mismatch and leaving the reader with a title that promises one article and a body that delivers another.