What a content brief should contain, and what it shouldn't
A good content brief tells the writer what the page needs to accomplish, who it is for, what it must answer, and what to leave out.
4 min read
A content brief should remove ambiguity before writing starts.
It should tell the writer what the page is trying to do, who it is for, which questions it needs to answer, what evidence or context matters, and what does not belong.
It should not prescribe every sentence, force a fixed structure, or turn the assignment into a checklist of keywords.
The test is simple: could two competent writers use the same brief and still produce different pages that both solve the same problem well?
What should a content brief include?
A useful brief should include:
The primary query or topic: What is the page about?
The search intent: What is someone actually trying to do or decide?
The page goal: What should the page help the reader accomplish?
The audience: Who is this for, and what do they already know?
The answer or takeaway: What should someone understand by the end?
The questions to answer: Which specific questions need to be covered?
Evidence or sources: What data, examples, product information, or expert input should support the page?
What to leave out: Which adjacent topics belong somewhere else?
Internal links: Which pages should this page link to, and which pages should link back?
Business context: Is there a product, service, comparison, or next step the page should naturally connect to?
The brief should give the writer the constraints that matter without writing the article for them.
What should you leave out of a content brief?
Leave out:
Arbitrary word counts. Length should follow the question, not a target number.
Keyword-density requirements. Use the language naturally where it helps clarity.
A rigid H2/H3 template. Structure should follow the topic and reader need.
Generic tone instructions. “Friendly but authoritative” rarely helps anyone write better.
Competitor headings copied into the brief. Use competitors for research, not as a template.
Requirements with no reason behind them. If something must be included, explain why.
A brief should help the writer make better decisions, not give them more boxes to check.
What does a useful content brief look like?
Say the assignment is a page about how to choose a project management tool.
A weak brief might say:
Keyword: project management software
Search volume: 8,000
1,500–2,000 words
Include “project management tools” five times
H2s: Features / Benefits / Pricing / Best Tools / Conclusion
That gives the writer constraints, but almost no direction.
A stronger brief would say:
Audience: Operations or team leads comparing tools for a growing team
Intent: Evaluate whether they need a dedicated project management tool and how to compare options
Page goal: Help the reader identify the criteria that matter before choosing a platform
Questions to answer: Which features matter most? What changes by team size? When is a simpler tool enough? What switching costs should someone consider?
Evidence to include: Pricing models, collaboration limits, integrations, migration considerations, examples by team type
Leave out: Generic productivity advice and a long history of project management software
Internal links: Comparison pages, implementation guides, pricing pages, relevant product pages
The second brief still leaves room for the writer to make decisions. It just makes the assignment much harder to misunderstand.
Want to check yours?
Run the Content brief builder →
Why should a content brief say what not to cover?
Because weak pages often fail by expanding, not by missing one more section.
Without boundaries, a writer can keep adding adjacent topics until the page becomes a catch-all. That usually creates repetition, weak internal linking, and overlap with pages that should own those topics instead.
A good leave-out section makes ownership clear.
For example:
Do not explain the basics of project management methodology here. Link to the methodology guide instead.
That protects the purpose of the page and makes the site structure cleaner.
Who is the content brief actually for?
The brief is for whoever has to make the page good.
That might be a subject-matter expert, an SEO writer, an editor, an agency, or an AI-assisted workflow. The amount of detail should change depending on who is doing the work.
An experienced writer who knows the topic may need only the goal, audience, required questions, evidence, and exclusions.
A writer who does not know the subject may need more source material, definitions, product context, and examples.
The same applies to AI-assisted writing. More constraints do not automatically produce better output. Clear direction does.
Why should you keep the content brief after publishing?
Because it records why the page exists.
Months later, someone reviewing the page should be able to see:
what the page was meant to accomplish
who it was written for
which questions it was supposed to answer
which topics were intentionally excluded
which sources or evidence informed it
how it fits into the rest of the site
That makes refreshes, consolidation, and ownership decisions much easier.
If the brief only lives in a temporary document or disappears after publication, you lose that context.
How much detail should a content brief include?
Enough to prevent the wrong page from being written.
If the brief starts dictating exact sentences, every heading, and the order of every point, it has probably gone too far.
If it only contains a keyword and a word count, it has not gone far enough.
A good brief should make the important decisions clear while leaving the writer room to decide how best to communicate them.
What happens after the brief is done?
Once the brief is clear, the next step is structure.
Use the brief to define the page’s goal, audience, questions, evidence, exclusions, and business context. Then use the search results and topic research to decide how those pieces should be organized.
That distinction matters:
The brief defines what the page needs to accomplish.
The outline decides how the page should deliver it.
The Content Brief Builder can turn the research into the brief. The Article Structure tool can then use the SERP and related questions to organize the page.
A strong brief should make the page hard to misunderstand, not hard to write.
Keep reading
