Content Writing
How to Create an Effective SEO Content Brief (With Example)
The 13 fields of a useful SEO content brief, a complete filled-in example, a 30-minute research routine and the signs your briefs are causing rewrites.
An effective SEO content brief tells the writer five things: the query and the intent behind it, who the reader is and what they should be able to do afterwards, the questions the post must answer, what this post will add that the current results do not, and the practical constraints (length range, links, call to action, deadline). It fits on one page. Everything else, including exact headings and keyword counts, is better left to the writer.
What a Brief Is For
A brief exists to stop the two failures that cost the most time: a draft that answers the wrong question, and a draft that answers the right question in the same way as everyone else. Both are cheap to prevent at the brief stage and expensive to fix at the edit stage.
It is not an outline with keywords pasted in. A list of H2s copied from the top ten results produces an article that looks like the top ten results, which is the opposite of what a new page needs to rank. The brief should carry the thinking; the writer should do the writing.
The Fields That Matter
| Field | What to write | Why it matters |
|---|---|---|
| Primary query | One phrase, worded as searchers word it | Sets the title, H1 and opening |
| Secondary queries | 3–8 phrases with the same intent | Become headings or FAQs; anything with different results belongs in another post |
| Search intent and format | "Informational, how-to; results are step-by-step guides with templates" | The single biggest cause of failed posts is the wrong format |
| Reader | Role, knowledge level, situation | Decides vocabulary, depth and examples |
| Outcome | "After reading, the reader can…" | Gives the writer a test for every paragraph |
| Must-answer questions | 5–10, from search results, sales calls and support | Ensures the post is complete |
| Our angle | What this post adds that ranking pages lack | The reason the post deserves to rank |
| Evidence | Sources to use, data you hold, people to quote | Prevents invented claims and generic filler |
| Exclusions | Subtopics to leave out or summarise and link | Avoids overlap with your other posts |
| Internal links | 3–6 target URLs, plus the service page | Builds the cluster at the drafting stage |
| Call to action | The one next step | Stops the "contact us for all your needs" ending |
| Length range | Based on what the answer needs, e.g. 1,200–1,600 | A range, not a target |
| Logistics | Deadline, reviewer, format, where it will be published | Avoids a day lost to "who signs this off?" |
A Filled-In Example
- Primary query: how to write a grant application cover letter.
- Secondary: grant cover letter example, grant cover letter template, what to include in a grant cover letter.
- Intent and format: informational how-to. Top results are guides with one example letter; two include a downloadable template.
- Reader: a development manager at a small charity, has written applications before but not for this funder type. Short on time.
- Outcome: reader can draft a one-page cover letter for a trust or foundation in under an hour.
- Must answer: how long it should be; what goes in each paragraph; who to address it to; whether to repeat the application summary; common reasons letters are skipped; what to attach.
- Our angle: ranking pages give one generic example. We will give two annotated examples (a small local trust and a large national foundation) and a paragraph-by-paragraph template, written by someone who has reviewed applications.
- Evidence: the funders' own published guidance where available; no statistics unless sourced.
- Exclusions: writing the full application (link to our existing guide); finding funders (out of scope).
- Internal links: full grant application guide; budget justification post; the bid writing service page.
- CTA: "If you want the full application reviewed before submission, book a review."
- Length: 1,200–1,600 words plus the template.
- Logistics: draft due Thursday; reviewed by the head of bids; delivered as a Google Doc.
That brief took about thirty minutes, most of it reading the current results. It leaves the writer free to decide the structure while making it nearly impossible to deliver the wrong article.
How to Research a Brief in 30 Minutes
- Search the primary query (5 minutes). Note the format of the top five results, any featured snippet, and the "People also ask" questions.
- Skim the top three pages (10 minutes). List what each covers and, more usefully, what none of them covers well. That gap becomes "our angle". Reading intent from results is covered in more depth in understanding search intent before writing.
- Check your own site (5 minutes). Search for existing posts on the subject. If one already targets this intent, you are briefing an update, not a new post.
- Add the questions only you have (5 minutes). Sales calls, support tickets and comments contain questions keyword tools miss.
- Fill in the constraints (5 minutes). Links, CTA, length range, deadline.
How Prescriptive Should It Be?
Detailed on substance, light on form. A useful rule:
- Specify: the query, intent, reader, outcome, must-answer questions, angle, evidence and exclusions.
- Suggest: a rough structure if the format is unusual, and internal links.
- Leave out: exact H2 wording, keyword repetition counts, a word count to hit exactly, and lists of "LSI keywords" pulled from a tool.
Writers given a list of 25 terms to include will include all 25, and the post will read like it. If you want to keep secondary phrases tight, see how many keywords to target in one blog post.
Briefing for Expertise
Google's helpful content guidance asks whether content shows "first-hand expertise and a depth of knowledge" and whether it is "self-evident to your visitors who authored your content". A brief is where you plan for that. Add a line for who supplies the expertise: a 20-minute call with the account manager, a set of real examples, the internal process document. A writer cannot invent first-hand experience, and should not be asked to.
Who Writes the Brief
Whoever understands both the search landscape and the business goal, which is often not the writer. In a small team that might be the marketing lead; in an agency, the strategist or account manager. When a writer briefs themselves, it is still worth doing as a separate step before drafting: it catches wrong-intent posts before 1,500 words are spent on them.
The context changes the emphasis. Briefing a white-label writer for a client adds voice notes and approval rules, covered in how to brief a white label writer. Briefing a copywriter on a website page needs positioning and proof rather than queries, set out in what a copywriter needs from you before they write.
Signs a Brief Is Not Working
If the first drafts you receive keep needing structural rewrites, the brief is the problem, not the writer. Look at which field was missing or vague. It is almost always the intent and format, the reader, or the angle.
- Drafts are accurate but generic: the "our angle" field is empty or says "more comprehensive".
- Drafts overlap other posts: no exclusions listed.
- Drafts end on a weak or wrong CTA: the CTA field is missing.
- Drafts invent statistics: no evidence field, and no instruction to source claims.
What to Do This Week
Turn the table above into a one-page template in whatever tool your team uses. Fill it in for the next post on your plan, timing yourself, and send it to the writer with a request for comments on anything unclear. If you would rather hand over the brief and the writing, our blog writing service works from a brief like this, with revisions until the brief is met.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
An outline lists the sections of an article. A brief explains why the article exists: the query and intent, the reader, the outcome, the angle and the constraints. A brief can include a suggested outline, but an outline alone leaves the writer guessing about everything that decides whether the post succeeds.
One page is usually enough. If the brief runs to four pages, it is probably dictating headings and keyword counts that the writer should decide. The aim is to remove guesswork about substance, not to script the article. Thirty minutes of research is typical for a standard blog post.
Include a range based on what the answer needs, not a fixed target. Google's guidance warns against writing to a particular word count in the belief that Google prefers one. A range tells the writer the expected depth while leaving room to stop when the question is answered.
No. Tools can speed up collecting questions and competitor headings, but the parts that matter most, the reader, the outcome and your angle, come from knowing the business. A shared document template works perfectly well. Use tools for the research, not as a substitute for the thinking.
Yes, as research rather than a model. Listing the top results with a note on what each lacks helps the writer find the gap. Asking them to match a competitor's headings produces a copy of that article, which gives Google no reason to prefer yours.