A bad brief produces generic content no matter how good the writer is. Here's the exact structure that turns a keyword and a deadline into an article that actually ranks.
Most content briefs are a keyword, a word count, and a deadline pasted into a Slack message. The writer does their best with what they've got, produces something competent but generic, and the article underperforms — not because the writer is bad, but because they were never given the information needed to write something that beats what's already ranking. A brief is not a task assignment; it's a compressed research handoff. The better the brief, the less the writer has to guess, and the more consistently the output actually competes.
Start With the Search Intent, Not the Keyword
Every brief should open by naming what the searcher actually wants, in plain language, before any keyword appears. "best CRM software" and "best CRM software for real estate agents" look like the same task but demand entirely different articles — one is a broad comparison for people still exploring the category, the other assumes the reader has already narrowed to an industry and wants a shortlist plus reasoning specific to their workflow. Pull up the current top five to ten results for the target query and categorize what they're actually delivering: is it a listicle, a single-product deep dive, a how-to, a comparison table, a definition-first explainer? If eight of the top ten results are listicles and you brief a single-product review, the article will struggle regardless of quality, because it's answering a question the searcher isn't asking. This single step — actually looking at what's ranking before writing the brief — catches more mismatches than any other part of the process.
Give the Writer the Competitive Landscape, Not Just a Target
A brief that says "beat this article" without specifics forces the writer to reverse-engineer the competition from scratch, which is slow and inconsistent. Instead, hand over:
- The URLs of the top five ranking pages for the primary keyword.
- A short note on what each one does well and what it's missing — a stale statistic, a section that's too shallow, an angle nobody has covered, an outdated screenshot or process.
- The specific gap the new article should fill. This is the single most valuable line in the brief: the reason this piece should exist beyond "we needed content for this keyword."
Without a stated gap, writers default to summarizing the existing consensus, which produces an article that's competent but redundant — never a reason for anyone, human or algorithm, to prefer it over what's already ranking.
Specify the Structure, Not Just the Topic
Headings shape how both readers and AI systems parse an article, so they shouldn't be left to improvisation. A strong brief includes a suggested H2/H3 outline built from three sources: the questions real people are asking (from "People Also Ask" boxes, forum threads, or sales and support conversations), the subtopics competitors cover, and any genuine gap identified above. The outline doesn't need to be final — a good writer will adjust it — but it gives them a skeleton instead of a blank page, and it forces the person writing the brief to actually think through the article's logic before handing it off. Include a rough word count per section rather than just a total, since a total word count alone tends to produce even, generic coverage across every section instead of depth where it actually matters — see ideal blog post length for SEO for how to set that total itself from actual competitor research rather than a fixed house rule, and hand writers a word counter to track progress against each section's target as they draft.
Include the Actual Search Queries, Not Just the Head Term
A brief built around one keyword misses the cluster of related phrasings the article should realistically be able to rank for. List the primary target term alongside four to eight closely related variations and questions — the kind of long-tail phrasing that shows up in autocomplete, "People Also Ask," and related-search sections. The writer doesn't need to keyword-stuff these in; they need to know the full scope of what the article is expected to answer so related questions get addressed naturally in the body rather than left out entirely because nobody flagged them.
Name the Reader, Specifically
"Business owners" is not an audience description a writer can use. "A founder of a 10-person company who has never worked with a development agency and is nervous about getting locked into a bad contract" is. The more specific the reader profile, the more specific the writer's word choices, examples, and level of assumed knowledge become — and specificity is exactly what separates content that feels written for someone from content that feels written for a search algorithm. Include the reader's likely objections and existing misconceptions if you know them; a good writer will address those directly, which is often the most useful part of the finished piece.
Provide Facts, Data Points, and Internal Expertise Up Front
Writers — especially freelance or agency writers working across many clients — cannot know your company's specific data, opinions, or hard-won operational lessons unless someone hands those over. If there's a real statistic, a genuine internal opinion, a specific process detail, or a lesson learned that would make the article better than a generic overview, put it in the brief explicitly. This is usually the difference between an article that reads as authoritative and one that reads as competent but interchangeable with a dozen others on the same topic. If the company has no unique data or opinion to add on a given topic, that's worth noticing before commissioning the piece at all — it's a signal the topic may not be worth writing about yet.
Set Explicit Formatting and On-Page Requirements
Avoid ambiguity on the mechanical requirements that are easy to forget under deadline pressure:
- Target meta title and description constraints (character limits, required keyword placement).
- Whether the piece needs a comparison table, FAQ section, or specific schema-friendly structure.
- Internal linking targets — which existing pages should be linked to, and with what anchor text, so the writer isn't guessing at what's relevant.
- Tone and reading-level guidance, especially if the brand voice differs from generic "professional" default.
- Image and diagram needs, specified early enough that visual assets can be produced alongside the draft rather than bolted on afterward.
Build a Reusable Template, Not a One-Off Document
The efficient version of this process is a standing template — a shared document or lightweight form with every section above as a fillable field — rather than reconstructing the brief from memory each time. A consistent template does two things: it forces whoever is commissioning the article to actually do the intent and competitive research rather than skip it under time pressure, and it gives writers a predictable format they get faster at working with over time, since they know exactly where to find the outline, the audience, and the facts every time.
Match Brief Depth to the Value of the Content
Not every piece deserves the full treatment described above, and pretending otherwise slows a content operation down without improving output where it doesn't matter. A cornerstone page targeting a competitive commercial keyword — the kind of page expected to drive leads or sales for years — justifies real time spent on competitive research, a detailed outline, and internal fact-gathering. A minor supporting post feeding an internal link structure or covering a long-tail question doesn't need the same investment; a shorter brief covering intent, a rough outline, and one or two internal links is enough. Tiering briefs this way — full treatment for the pages that matter most, a lighter template for everything else — keeps the process sustainable at volume instead of becoming a bottleneck that quietly encourages people to skip the process altogether once deadlines pile up.
Common Brief Failures That Undermine Good Writers
A handful of mistakes show up repeatedly even in teams that otherwise take briefing seriously. The most damaging is treating the brief as a one-way handoff with no room for the writer to push back — a good writer who reads the top-ranking competitors will sometimes notice the assigned angle is wrong, and a brief process with no feedback loop back to whoever commissioned it just produces content built on a stale assumption. A close second is over-specifying structure to the point that every article in a content library reads identically, section for section, which flattens exactly the differentiation a strong content strategy is trying to create. A third is writing the brief for the keyword the team wants to rank for rather than the keyword real searchers actually use — internal jargon and the external phrasing customers search for are often meaningfully different, and a brief built on the wrong one produces content that reads correctly internally but never matches how anyone actually searches.
Review the Draft Against the Brief, Not Against Vibes
The final step closes the loop: when the draft comes back, check it against the brief's stated intent and gap, not just against a generic sense of "does this read well." Did it answer the specific question identified at the start? Did it fill the gap that justified writing the piece? Did it hit the structural and factual requirements? An article can be well-written and still miss the brief entirely if the review step only checks prose quality. This is also the point at which it's worth re-checking the live search results one more time — rankings shift, and a brief written two weeks ago may already be slightly out of date by the time the draft is ready for publishing.
Brief for the Editor Too, Not Just the Writer
A brief that only speaks to the writer misses half the process, because whoever edits and approves the piece needs the same context to judge it fairly. If the editor wasn't part of building the brief, hand them the same document rather than letting them review the draft cold against their own unstated expectations — nothing derails a project faster than a writer executing a brief precisely and an editor rejecting it because they had a different, never-written-down idea of what the piece should be. Circulating the brief itself for a quick sign-off from whoever will approve the final draft, before the writer ever starts, catches this mismatch when it costs nothing to fix instead of after a full draft has already been written against the wrong assumptions.
A brief built this way takes real time to put together — often as much time as writing a short article. That's the trade a disciplined content operation makes deliberately: a strong brief turns an average writer into one who reliably produces competitive work, and it turns a strong writer's talent toward the actual competitive gap instead of a generic pass at the topic. Content teams that skip this step are, in effect, asking writers to do keyword research, competitive analysis, and audience definition on top of writing — and then wondering why output is inconsistent.
