What a content brief actually is
A content brief is the working document that converts a primary keyword and a search intent into a writable page. The brief tells the writer exactly what the page must do: the keyword to target, the intent to match, the dominant SERP format to mirror, the entities to cover, the H2 outline to follow, the FAQ questions to answer, the internal links to include, the schema to add, and the call-to-action to end with.
The brief is not a writing prompt. It is a working specification. A good brief contains enough information that two different writers given the same brief would produce broadly the same page. A bad brief contains a topic name and a word count and leaves the writer to do the strategic work alone, which is how content programmes end up with pages that miss the intent.
The cleanest test: can the writer produce the page without making strategic decisions during writing? If yes, the brief is doing its job. If no, the brief has gaps the writer will fill with guesses, and the page will reflect those guesses.
Why briefs beat outlines
Most content programmes use outlines. An outline is just the H2 list and a few notes per section. Outlines made sense ten years ago when ranking pages was mostly a matter of getting the headings right and the word count up. They do not work in 2026, because the work to rank a page has shifted up the strategy stack.
Three concrete reasons briefs outperform outlines.
- Briefs lock the intent. The single most common reason a page fails to rank is intent mismatch. The keyword has commercial intent and the page was written as an informational guide, or vice versa. A brief specifies the intent upfront and the writer cannot drift away from it without noticing. An outline contains no intent guidance at all.
- Briefs lock the entity coverage. Competitor pages now cover specific entities (people, places, products, regulations, related concepts) that signal to Google the page is written by someone who knows the subject. A brief lists the must-cover entities from the SERP. An outline does not.
- Briefs lock the internal links. Internal linking is where most of the topical authority work lands, and most writers under-link by default. A brief lists the pages to link to (pillar up, siblings sideways, cross-pillar references, service pages, glossary terms) so the writer cannot ship a thin link profile.
The pages on this site that took ninety minutes to brief and three hours to write outperform pages on similar topics that took zero minutes to brief and six hours to write. The brief moves the strategic load from writing time to planning time, which is a much cheaper place to do it.
The eleven-section brief template
Every brief we write covers eleven sections, in this order. Each section is bullets, not prose. The whole document is two to four pages.
1. Primary keyword and intent
One keyword (the head term the page targets). One intent label (informational, commercial-investigation, transactional, or navigational). Two or three secondary keywords that are close variants of the primary. Anything ambiguous gets pinned here so it does not have to be guessed later.
2. SERP analysis
The top ten ranking URLs for the primary keyword, with a one-line note on each: page format (guide, comparison, listicle, tool, video), word count, and the dominant content type. The SERP is the brief's external reality check. The page being briefed has to match the dominant pattern of the SERP, not fight it.
3. Must-cover entities
A list of the entities that appear on most of the top-three competitor pages. People, places, products, regulations, processes, related concepts. Extracted by hand or with a tool like InLinks, Surfer or a structured LLM prompt. The writer must cover all of these. Entities missed here become ranking ceiling later.
4. H2 outline
The H2 headings the page will follow, in reading order. Each H2 has one or two bullets describing what the section must cover. The outline matches the intent and the must-cover entities; if it does not, redo the outline before the writer touches it.
5. FAQ candidates
Three to six questions pulled from People Also Ask, the related searches block, and the questions a real reader would ask after reading the page. These become the FAQ block with FAQPage schema. Pick the questions the page does not already answer in its body; the FAQ is for the leftover questions, not a recap of the H2 list.
6. Internal-link targets
Up to ten pages the writer must link to from this one. The pillar above. Three to five sibling clusters. One or two cross-pillar references. One or two service pages. Three to five glossary terms on first mention. The brief lists the destination URL and a suggested anchor variation so the writer has a starting point but can adapt to the local context.
7. External citations
Two to five external sources the page should cite for any claim that is non-obvious: Google documentation, named industry reports, peer-reviewed studies, regulatory pages. External citations are an E-E-A-T signal and a fact-checking aid for the editor.
8. Schema spec
The schema types to add. Article and BreadcrumbList are standard. FAQPage if there is a FAQ section. HowTo if the page is a step-by-step process. Person for the named author. Specific properties that the writer or developer might miss get listed here.
9. Word-count guidance
A target range based on the SERP average, not a fixed number. For most service-category clusters that lands at 1,800 to 2,800 words. Pillars run 4,000 to 8,000. The brief states the range and tells the writer to optimise for entity coverage and reader value, not for hitting the count.
10. CTA spec
The call-to-action block the page should end with. For informational pages on this site that is the standard free-audit CTA. For commercial pages it is the relevant service-page CTA with a phone number. The brief locks this so every page in the cluster ends consistently.
11. Deadline and reviewer
The publication date. The named author. The named SEO reviewer. The named editor. Without owners the brief is a wish list; with owners it is a contract. See editorial workflow for SEO content for the role descriptions.
The 45-minute brief workflow
The first brief takes two hours. The tenth takes 45 minutes. The workflow:
- Five minutes: lock the keyword and intent from the content map.
- Ten minutes: SERP scan. Open the top ten ranking URLs in a browser, scan their structure, capture the dominant pattern.
- Ten minutes: entity extraction. Pull entities from the top three URLs using a tool or an LLM prompt.
- Ten minutes: outline draft. Write the H2 list in reading order, mapped to the intent and the entities.
- Five minutes: FAQ pull. People Also Ask, related searches, and your own gut for the leftover questions.
- Five minutes: link, schema, CTA spec. Pull from the content map and the brief template defaults.
The SEO who writes the brief has the strategic load. The writer who writes the page has the craft load. The editor who reviews the page checks the brief was followed. Three roles, one workflow, repeatable.
Common mistakes
- Treating the brief as a working document, not a polished artwork.
- Extracting must-cover entities from the SERP, not from the writer's head.
- Specifying internal-link targets so they cannot be skipped.
- Locking the intent and the dominant SERP format upfront.
- Keeping the brief to two to four pages so it actually gets read.
- Reviewing the page against the brief, not against a vague sense of quality.
- Briefs that are just a topic name and a word count. The writer fills the gaps with guesses.
- Skipping the SERP scan and assuming you know the dominant format. You usually do not.
- Entity lists copied from a single competitor instead of the top three.
- Internal-link targets left to the writer's discretion. Most writers under-link by default.
- Word-count targets used as a quality measure instead of an entity-coverage target.
- Briefs that take three hours to write. The brief has to be cheaper than the page.
Tools that speed the work
- A brief template document. Google Doc or Notion. One template per content type (pillar, cluster, product page, service page). Reused for every brief.
- An entity extraction tool. InLinks, Surfer SEO, Frase, Clearscope, MarketMuse, or a structured ChatGPT/Claude prompt. Extracts the entities competitor pages cover for the target keyword.
- A SERP preview tool. A free Chrome extension that opens the top ten ranking URLs in tabs for the scan. SERPSimulator and similar tools work.
- Google Search Console. For existing pages, GSC's Performance report shows the queries the page already ranks for, which feeds the secondary keyword list. See the GSC glossary entry.
- A keyword research tool. Ahrefs, Semrush or one of the cheaper options for the volume and difficulty numbers that go in the brief header. See the keyword research chapter for the broader workflow.
For the wider on-page work the brief feeds into, see title tag best practice and header tag structure. For the search intent framework that drives the intent label in the brief, see understanding search intent.
Perth and WA context
Three patterns from running brief workflows for Perth and WA clients.
Trade and service businesses need explicit suburb briefing. A brief for a Perth tradies page has to specify the suburbs the page should mention, the local landmarks where relevant, and the service-area boundary. Writers given a generic Perth brief produce a generic Perth page; writers given a Fremantle brief with named local context produce a Fremantle page that ranks for Fremantle. See SEO Fremantle, SEO Joondalup and the local keyword research chapter for the modifier framework.
Mining and resources briefs need a named subject-matter reviewer. A WA mining services page briefed without input from someone who actually works in the FIFO or shutdown space gets the technical detail wrong, and the helpful-content systems catch the gap fast. The brief should specify the named reviewer for technical accuracy alongside the named SEO reviewer. See mining SEO and SEO Karratha for the category context.
Legal and healthcare briefs need an extra compliance line. For YMYL topics, the brief should specify the credentialled reviewer (lawyer, doctor, registered practitioner) who has to sign off the page before it ships. That extra line in the brief prevents the back-and-forth that otherwise happens at the editorial-review stage. See legal SEO and healthcare SEO for the category-specific patterns, and E-E-A-T explained for the underlying framework.
For the strategic frame the brief sits inside, see the Content Strategy pillar. For the keyword-clustering work that produces the brief's primary keyword, see keyword clustering. For the editorial workflow that the brief feeds into, see editorial workflow for SEO content. For the topical authority signal the brief contributes to, see topical authority explained.