A content brief is the specification a writer receives before drafting: the target query, the search intent, the angle, the structure, and the constraints. It exists because "write something about X" is how you pay for the same article twice — once to write it, once to fix it.
What goes in a real brief
A working brief isn't a keyword and a word count. Here are the fields from a template that's survived contact with actual writers:
- Primary query + intent — the search term and what the searcher is trying to accomplish
- Audience — who's reading and what they already know
- Angle — the one-sentence reason this piece deserves to exist when ten others rank
- Working title and suggested H2 skeleton (suggested, not mandated)
- Questions to answer — from People Also Ask, sales calls, support tickets
- Entities and subtopics to cover — and, just as important, what NOT to cover
- Internal links — specific URLs to link out to, and pages that should link in after publish
- Sources — approved references, data, subject-matter experts to quote
- Length guidance — a range with reasoning, never a quota
- CTA and conversion goal — what a successful reader does next
- Meta title and description draft or guidance
Why each field earns its place
Every field above exists because leaving it out breaks something specific downstream. That's the test for adding fields, too — if you can't name what breaks without it, cut it.
| Brief field | What breaks without it |
|---|---|
| Primary query + intent | Writer targets the words, misses the intent — a how-to query gets an opinion essay |
| Audience definition | Beginner explainers for expert readers, or jargon walls for novices |
| Angle / reason to exist | You publish the eleventh interchangeable version of what already ranks |
| Questions to answer | The piece covers the topic but not the reader's actual sticking points |
| What NOT to cover | Scope creep — and cannibalization of the adjacent article you published in March |
| Internal links (in and out) | Orphaned content; "add links later" means never |
| Approved sources | Writers cite whatever ranks — often your competitor, sometimes garbage |
| Length guidance with reasoning | Padding toward a quota, or a skeleton draft of a topic that needed depth |
| CTA / conversion goal | Traffic that reads, nods, and leaves |
| Meta guidance | The CMS default: title truncated, description auto-generated from the intro |
The single highest-leverage field is the angle. A brief can specify everything else perfectly, but if it can't say why this piece will be different, the writer can't manufacture that difference on their own. For the full build process, see how to create SEO content briefs.
How to check it on your own site
Audit your briefs the way you'd audit anything else — against outcomes:
- Pull the last five published pieces and set each next to its brief. No briefs to pull? That's your finding.
- Count revision rounds per piece. Consistently two-plus rounds means the brief is underspecified — find which field the feedback keeps rewriting, because that's the field your template is missing.
- Check the internal links. Did the specified links make it into the published piece? Did the "pages that should link in" ever get updated? Crawl the new URLs and look at their inlink counts.
- Compare intent to outcome in Search Console after 60–90 days: is the piece getting impressions for the queries the brief targeted, or something else entirely? Persistent mismatch is a briefing failure, not a writing failure.
- Ask a writer to mark up a blank template — which fields they use, which they skip. Fields nobody reads should be fixed or deleted.
Common briefing mistakes (and fixes)
- Shipping a SERP-scraper export as the brief. Auto-generated term lists and competitor headings produce a collage of what already exists. Fix: tools inform the brief; a human writes the angle.
- Mandating exact H2s copied from ranking pages. You've pre-committed the writer to plagiarism-with-extra-steps. Fix: outline the questions to answer, let structure follow.
- Word-count quotas. "Minimum 2,000 words" buys you 600 words of padding. Fix: a range plus the reasoning ("this needs full setup steps, expect 1,500+").
- No "don't cover" section. Every piece sprawls into its neighbors' territory and pages start competing with each other. Fix: name the adjacent articles and draw the boundary explicitly.
- Briefing from stale research. A brief written in Q1 and assigned in Q4 targets a SERP that no longer exists. Fix: re-check the SERP the week the writer starts.
FAQ
How long should creating a brief take?
Long enough to include real research — typically an hour or two per brief once the template exists. If briefs take ten minutes, they're probably template exports; if they take a full day, you're writing the article twice.
Should the brief include a full outline?
A suggested skeleton, yes; a locked one, no. Writers who can't deviate from the outline can't fix its mistakes. Constraints belong on scope, intent, and facts — not on paragraph order. Our guide to briefs writers can actually execute is built around this balance.
Who should write the brief?
Someone who has done the keyword research and understands the business goal — usually the SEO or content strategist. The worst arrangement is the writer briefing themselves after the fact to satisfy a process checkbox.
Are brief-generation tools worth using?
As accelerators, yes — they compress the SERP-analysis grunt work. As replacements, no, because the two fields that matter most (angle and what-not-to-cover) require judgment about your site, your audience, and your existing content. Tools don't know you published the adjacent article in March.
Do briefs matter for updating existing content, or only new pieces?
Updates arguably need them more — the writer must know what to preserve (rankings, links, quoted passages) as well as what to change. A refresh without a brief is how a page that ranked #6 comes back ranking nowhere.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
