SEO Content Briefs
Why briefs exist
A content brief is the translation layer between SEO research and a writer who has never run a keyword tool. Without one, writers default to writing what they personally find interesting about a topic, which routinely misses what the SERP has already decided the topic needs. A good brief removes guesswork from both ends: the writer doesn't need to do their own SEO research, and the SEO doesn't need to review-and-reject three drafts before the structure is right.
The test of a good brief is simple: could two different competent writers, given the same brief, produce two different articles that both rank? If the brief is specific enough to guide structure and intent but not so rigid it dictates sentences, it's done its job.
Search intent comes first
Before anything else, a brief has to state the dominant search intent for the target query, because intent determines format more than topic does. The four classic buckets — informational, navigational, commercial investigation, transactional — aren't just theory; they map directly to what's sitting in positions 1-10 right now.
The fastest way to verify intent isn't to guess from the keyword's wording, it's to look at the actual SERP: if it's full of "best X" listicles and comparison tables, the intent is commercial investigation even if the keyword itself looks informational. If it's full of definitional explainer pages, the intent is informational regardless of commercial-sounding modifiers in the keyword. Mismatched intent is the single most common reason a well-written page fails to rank — the content answers a question the searcher wasn't asking.
Intent type vs. what the brief should specify
| Intent | SERP signal | Format the brief should call for | Primary CTA |
|---|---|---|---|
| Informational | Explainer pages, Featured Snippets, Wikipedia/definitions | Direct-answer opening + depth sections | Related-content link, email capture |
| Commercial investigation | "Best X", comparison tables, review sites | Comparison table + criteria breakdown | Product/pricing link |
| Transactional | Product/category pages, pricing pages | Short, conversion-focused, minimal fluff | Buy/signup CTA |
| Navigational | Brand/homepage results | N/A — don't build new content against this intent | N/A |
The core sections of a usable brief
A brief that works in practice — not just in theory — contains a consistent set of fields regardless of the tool or template used:
- Target keyword(s) and search volume — the primary query plus close variants the page should also capture.
- Search intent — stated explicitly, with the SERP evidence behind it.
- Target word count range, derived from the median length of ranking pages, not an arbitrary round number.
- Required entities and subtopics — the concepts, tools, or terms that competitor pages consistently cover (see the entity section below).
- Competitor analysis — the top 3-5 ranking URLs, their structure, and what each does well or poorly.
- Suggested H2/H3 outline — a draft skeleton, not a mandate, that the writer can rework.
- Internal linking targets — which existing pages should link to this one, and which should be linked from it.
- Meta title/description guidance — character limits and the primary keyword placement.
- Audience and tone notes — who's reading this and at what level of expertise.
TARGET KEYWORD: "server side tagging setup" (vol: 480/mo, KD: 34)
SECONDARY: "gtm server container" (320/mo), "server side gtm vs client side" (210/mo)
INTENT: Informational / how-to (SERP = 7 of 10 are tutorial-style guides)
TARGET LENGTH: 2,400-2,900 words (median of top 5 ranking pages: 2,650)
REQUIRED ENTITIES (appear in 4+ of top 5 competitors):
Google Tag Manager, server container, Cloud Run, first-party cookie,
client identifier, tag latency, data layer
COMPETITOR SNAPSHOT:
#1 competitor-a.com - strong diagram, weak on cost breakdown
#3 competitor-b.com - thorough cost section, outdated screenshots (GTM UI changed)
#4 competitor-c.com - video-first, thin text (opportunity: be the best text version)
SUGGESTED OUTLINE:
H1: How to Set Up Server-Side Tagging in GTM
H2: What server-side tagging actually changes
H2: Prerequisites (GCP account, domain access)
H2: Step-by-step container setup
H2: Cost breakdown (Cloud Run pricing walkthrough)
H2: Common mistakes
INTERNAL LINKS IN: /consent-mode, /cookieless-tracking
INTERNAL LINKS OUT TO THIS PAGE: /ga4-setup-guide, /gtm-fundamentalsEntities: the part most briefs skip
Search engines increasingly evaluate topical depth by checking whether a page mentions the network of concepts that genuinely comprehensive content on a topic would mention — not just the exact keyword. A brief that only lists the target keyword and leaves entity coverage to chance produces pages that rank for the headline term but fail to capture the long tail of related queries that a thorough page would naturally pick up.
Building the entity list is mechanical: read the top 5-8 ranking pages and note every recurring named concept, tool, or term that shows up across multiple of them. Anything mentioned in 3+ competitor pages but absent from your draft is a credible signal of thin coverage, independent of word count.
A brief is not a word-count mandate
Briefing for E-E-A-T signals
Beyond structure and keywords, a brief for anything in a sensitive or expertise-driven space (health, finance, legal, technical how-tos with real consequences if wrong) should specify who is credited as the author or reviewer, what credentials or experience should be referenced, and what original data, screenshots, or firsthand testing the piece should include. Pages that read as generic aggregations of other pages, with no signal of direct experience, increasingly underperform pages that show evidence the author actually did the thing being described — a real screenshot of your own dashboard outperforms a stock image of someone else's.
Reviewing drafts against the brief
The brief also defines the review checklist. Before a draft goes live, check it against the brief's required entities (grep for each one — literally search the draft text for each required term), confirm the intent match holds (does the format match what's actually ranking, not just what the brief predicted), and verify the internal linking was actually added, since it's the step most frequently forgotten under deadline pressure. A brief that's never checked against the finished draft is just a wish list.
What's next
Briefs assume you already know which gaps are worth briefing in the first place — that prioritization work happens upstream.
See also: Content Gap Analysis →
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.