What you'll learn

By the end of this you'll have a reusable SEO content brief template — the sections to fill before anyone writes a draft — plus guidance on how each field prevents thin posts, keyword cannibalization, and articles that rank nowhere because they tried to rank everywhere.

This is for teams publishing at scale: multiple authors, multiple hubs, one canonical URL per intent. The brief is the contract between SEO strategy and the person opening a blank doc.

Who this is for

  • Editors and content leads managing developer-focused blogs or resource hubs
  • Freelance writers who need clear scope before drafting long technical posts
  • Engineers who write occasionally and want a checklist so their tutorial doesn't ship without metadata, links, or a defined reader

Skip this if you publish twice a year and everyone already knows the site structure by heart. Briefs pay off when volume and contributors increase.

What is an SEO content brief?

Plain English: a one-to-two-page spec that answers "what are we writing, for whom, to satisfy which search, and how will we know it worked?" before words go on the page.

Without a brief, writers guess intent from a keyword string. With a brief, they know the primary entity, the angle that differentiates this post from the one you published last month, which internal links are mandatory, and what "done" looks like for SEO metadata.

A brief is not an outline stuffed with keyword density targets from 2014. It's a decision record that makes the draft faster and the edit pass shorter.

Prerequisites

  • Access to your site's hub structure (URLs, content types, existing posts on the topic)
  • A target keyword or question from search console, customer support, or product gaps — not only volume tools
  • Rough sense of who will write and who will approve technical accuracy
  • Your site's metadata conventions (title length, canonical rules, schema types)

Setup from zero

Copy the template below into Notion, Google Docs, or a markdown file in your repo. Every new post gets a brief issue or doc linked from the pull request.

Step 1 — Create the brief template file

Sections: working title, URL slug, hub, content type, search intent, primary entity, secondary entities, audience, unique angle, outline, FAQs, internal links, metadata draft, success metric, reviewer. Don't skip fields — empty fields are where mistakes live.

Step 2 — Run a cannibalization check

Search your site for the target topic. If two posts satisfy the same intent, merge or differentiate before briefing. The brief should name which existing URL this post complements — not competes with.

Step 3 — Assign intent and entity before outline

Intent drives structure. "How to configure X" gets steps; "X vs Y" gets comparison tables; "what is X" gets definitions first. Entity focus keeps vocabulary consistent — Google and humans both reward clarity.

Little tip: add a "do not cover" line to every brief. Writers expand scope when nervous. Explicit boundaries save 800 words of tangent and prevent overlap with next week's post.

Step 4 — Draft metadata in the brief

Write title tag, meta description, and h1 in the brief — they often differ slightly. If the writer also picks these at publish time, you'll fix duplicates under pressure.

Step 5 — Link brief to PR or CMS entry

The published post should link back to the brief (internal wiki link is fine). Six months later you'll want to know why the outline looked that way.

The mental model

The mental model for SEO briefs is one URL, one intent, one primary entity.

Cannibalization happens when two URLs chase the same intent with overlapping headings. Thin content happens when intent is vague ("AI tools") and the outline has no structure matched to what the searcher wanted. Briefs force a choice: this page wins for this query; other queries get other pages.

Internal links are how you tell crawlers and readers how ideas connect. A brief without mandatory links produces orphan posts — technically published, structurally invisible.

Key terms

Search intent — informational, commercial, navigational, or transactional; what the searcher wants to accomplish.

Primary entity — the main concept the page is about (e.g. "Next.js metadata API," not "SEO" broadly).

Cannibalization — multiple URLs on your site competing for the same query, diluting signals.

Canonical URL — the preferred URL for a piece of content; brief should state it explicitly.

SERP — search engine results page; shape your title/description for real listings, not just keywords.

Success metric — how you'll judge the post in 90 days (ranking range, impressions, conversions, support deflection).

Step-by-step: fill the brief

Copy this into your template and complete every section before drafting.

Brief header

  • Working title:
  • Slug: (kebab-case, matches repo/CMS)
  • Hub / content type: (e.g. resources / tutorial)
  • Author & reviewer:
  • Target publish date:

Strategy

  • Target query / question: (verbatim phrase from search or support)
  • Search intent: (informational / comparison / tutorial / news)
  • Primary entity: (one noun phrase)
  • Secondary entities: (2–5 related terms to use naturally)
  • Audience: (who already knows what)
  • Unique angle: (why this post exists vs existing SERP and vs our catalog)
  • Do not cover: (topics deferred to other URLs)

Outline (H2/H3)

List every h2 and major h3. Match intent — tutorials need prerequisites and steps; comparisons need criteria and verdict.

Example skeleton for a tutorial brief:

  1. What you'll learn
  2. Who this is for
  3. Prerequisites
  4. Setup from zero (steps)
  5. The mental model
  6. Step-by-step
  7. Common mistakes
  8. FAQ
  9. Takeaways

FAQs

Three to five real questions from People Also Ask, support tickets, or Slack. Each gets a dedicated answer in the draft — not stuffed into one paragraph.

| Anchor text | Target URL | Why |
|-------------|------------|-----|
| | | |

Minimum three internal links on long posts; one must be hub index or pillar content.

Metadata draft

  • Title tag (≤ 60 chars):
  • Meta description (≤ 155 chars):
  • H1 (on-page):
  • Canonical: (usually same as live URL)
  • Schema type: (Article, BlogPosting, HowTo, etc.)

Assets

  • Hero image subject and alt text
  • Diagrams or code samples needed
  • Image dimensions for CLS (width/height)

Success metric (90 days)

  • Primary: (e.g. top 20 for target query, or 500 organic sessions)
  • Secondary: (newsletter signups, time on page, internal link clicks)

Little tip: write the meta description as a promise you fulfill in the first screen — not clickbait. Editors can reject drafts that don't match the description in paragraph one.

Working examples

Filled snippet — resource post

  • Target query: "lighthouse performance nextjs"
  • Intent: informational + practical fixes
  • Primary entity: Lighthouse performance audit on Next.js
  • Unique angle: content-site budgets, not SPA dashboards
  • Do not cover: general React perf patterns without Next.js context
  • Mandatory links: /developers/nextjs/nextjs-metadata-and-seo, /resources/lighthouse-perf-cheat-sheet

Anti-pattern brief (too vague)

  • Target query: "AI"
  • Intent: informational
  • Outline: Introduction, Benefits, Future, Conclusion

That brief produces a thin post. Narrow the entity or don't publish.

Patterns / when to use brief variants

| Brief type | Extra sections |
|------------|----------------|
| Tutorial | Prerequisites, code repo link, version pins |
| Comparison | Products compared, scoring criteria, affiliate disclosure |
| News | weekOf, sources, freshness note |
| Resource / checklist | Downloadable sections, update cadence |
| Case study | Company context, metrics allowed public |

Common mistakes

Keyword without intent — volume tools suggest head terms; briefs need the specific question you answer.

Outline copied from competitors — match intent, don't clone structure; your entity graph is different.

No internal links planned — links added during "final polish" never happen.

H1 equals title tag verbatim every time — sometimes fine, often wasteful; brief should decide consciously.

Success metric missing — without it, nobody revisits underperforming posts.

Troubleshooting

Writer ignores the brief — briefs fail when they're vague. "Do not cover" and outline H2s are non-negotiable; angle is negotiated once.

Two posts still overlap after publish — merge or 301 the weaker URL; update the survivor's brief with combined intent.

Ranks but doesn't convert — intent mismatch: informational post ranked for transactional query. Brief wrong intent type; adjust angle or create a separate landing page.

Technical reviewer bottlenecks — brief should name reviewer upfront and flag sections needing code verification vs prose only.

Checklist

  • [ ] Cannibalization check done; complementary URLs named
  • [ ] Intent, primary entity, and unique angle filled
  • [ ] H2 outline matches intent type
  • [ ] 3+ FAQs and 3+ internal links specified
  • [ ] Title, description, H1 drafted in brief
  • [ ] Success metric and reviewer assigned
  • [ ] Brief linked from CMS issue or PR

Practice task

Pick a post you've published without a brief. Reverse-engineer a brief from the live URL: infer intent, entity, and what you'd require differently. Then pick one upcoming post and write the brief first — don't open the draft doc until the outline and links sections are complete. Compare how long the edit pass takes.

FAQ

How long should a brief take?
30–45 minutes for an experienced editor on a standard tutorial; longer for comparisons requiring product research. Cheaper than rewriting a drifted draft.

Do freelancers need this?
Yes. Freelancers can't read your team's head. The brief is how you transfer hub strategy without a two-hour call.

Should briefs include keyword density?
No. Include entities and questions to answer. Natural language beats formulas.

What if strategy changes after publish?
Update the brief note and the post together. Briefs are living specs for major refreshes.

What to learn next

  • Next.js metadata and SEO — implement what the brief specifies
  • SEO IA for AI media — hub structure that briefs plug into
  • Lighthouse performance cheat sheet — performance requirements for content templates
  • [Next.js metadata and SEO](/developers/nextjs/nextjs-metadata-and-seo)
  • [SEO IA for AI media](/case-studies/seo-ia-for-ai-media)
  • [Checklist: ship an AI feature](/resources/checklist-ship-ai-feature)

Takeaways

SEO content briefs turn publishing from improvisation into a repeatable spec: one intent per URL, entities named upfront, internal links mandatory, metadata drafted before prose, success defined for 90 days.

Writers move faster when decisions are made once. Editors spend less time fixing scope. Hubs stay coherent as the catalog grows.

If you remember only one thing: write the brief before the draft — intent and links decided late become rewrites, cannibalization, and posts that nobody can find in your own site search.