A content brief is a one-page plan for a single article: the target keyword, the reader's goal, the questions to answer, the sources to use and the page's job. Write it before drafting. A good brief fits on one page and prevents the rewrites that come from unclear aims.
Why does a content brief matter?
Most weak articles are not badly written. They answer the wrong question, repeat a page you already have, or bury the useful part. A brief forces those decisions to happen before the writing starts, when changing them costs a few minutes instead of a full rewrite.
It also helps if you are the only writer. Future you, six weeks from now, will not remember why a post was meant to exist. The brief is the record.
What goes in a content brief?
Keep it to the fields that change what gets written. Every extra field is something nobody will read.
| Field | What to write | Why it matters |
|---|---|---|
| Target keyword | The one phrase the page is for | Stops two pages competing for the same query |
| Reader and goal | One sentence: who is asking and what they want to do next | Sets the angle and the depth |
| Direct answer | The answer in 40 to 60 words | Becomes the opening paragraph |
| Questions to cover | 5 to 8 sub-questions, each a future heading | Defines the outline |
| What is missing elsewhere | One thing the current top results skip | Gives the page a reason to exist |
| Sources | Links you have opened, with the fact each supports | Keeps claims checkable |
| Internal links | Existing pages to link to and from | Connects the page to the rest of the site |
| Next step | What the reader should do after finishing | Keeps the page tied to a goal |
How do you write one, step by step?
1. Pick the keyword and check you do not already cover it
Search your own site for the phrase and its close variants. If a page already answers the question, update that page instead. Our post on keyword cannibalization explains what happens when two pages chase the same query.
2. Write down the reader's goal in one sentence
Not "people interested in SEO." Try "a founder with a five page site who wants to know whether to start a blog." The sentence decides the vocabulary, the examples and how much background to include. Google's SEO starter guide advises you to "think about the words that a user might search for," because experts and beginners often search with different terms for the same thing.
3. Look at what already ranks
Search the keyword and open the top five results. Note the format (guide, list, tool), the headings they share, and anything they leave out. This is the same check described in our guide to search intent. The shared headings are questions you probably need to answer. The gaps are your opening.
4. Draft the direct answer
Write the 40 to 60 word answer now, before the outline. If you cannot, you do not know the topic well enough yet, and no writer will fix that for you. This paragraph is also the part most likely to be quoted in a search snippet or an AI answer.
5. List the questions as headings
Turn each sub-question into a likely <h2> and put them in the order a reader would ask them. Add a last section of four to six short questions for an FAQ. Keep each question narrow enough that it can be answered in a few short paragraphs.
6. Name the proof
For every claim that needs a source, write the link in the brief. Google's guidance on helpful content asks whether a page "provides original information, reporting, research, or analysis" and whether it adds "substantial value when compared to other pages in search results." If the brief has no original angle and no source, expect a page that repeats the top results.
7. Plan the links
List two to four existing pages to link to and any older pages that should link back once the new one is live. A page nobody links to can end up as an orphan page. If the post belongs to a group of related pages, say which one, as covered in our guide to topic clusters.
What does a finished brief look like?
Here is a short example for a post on blogging frequency.
- Keyword: how often should you blog
- Reader and goal: a founder with no blog who wants a realistic schedule
- Direct answer: as often as you can publish pages worth reading, which for most small teams is a few a month
- Questions: Is there a magic number? What does quality cost? What happens if you stop? How do you plan a schedule?
- Gap: top results give numbers without explaining the trade-off
- Links: the post on article length, the content audit guide
That is under 100 words, and a writer can start from it without a meeting.
What are the common mistakes?
- Briefs that are really outlines. An outline lists headings. A brief explains why the page exists and what makes it different.
- Copying competitor headings. Use the shared headings as a checklist, then add the thing they skip.
- No stated reader. Without one, the draft tries to serve everyone and ends up general.
- Too long. If the brief runs past a page, writers skim it. Cut fields until each one changes the draft.
- Never checking the result. After publishing, compare the page to the brief. Did it answer every question? Use what you learn to improve the next one. A content audit is a good place to do this in bulk.
Frequently Asked Questions
How long should a content brief be?
One page is enough. If a writer cannot find the keyword, the reader goal and the questions to cover in a glance, the brief is too long.
Do I need a content brief if I write alone?
Yes, a short one. Five lines noting the keyword, the reader, the answer and the gap will save you from drifting halfway through a draft.
Should a brief include word count?
Only as a rough guide. The right length is the one that answers the questions in the brief, not a number copied from competitors.
Can AI write the brief?
It can draft the questions and outline from the top results. You still need to supply the reader goal and the original angle, because those come from knowing your business.
When should I update a brief?
When you refresh the post. Revisit the questions and sources, then change the page to match. Our guide to refreshing old posts covers the process.