Content Brief Specification: Fields, Templates, and Acceptance Criteria for B2B & SaaS

Standards & Governance

Content Brief Specification: Fields, Templates, and Acceptance Criteria

Standardize every brief so writers, SEOs, designers, and SMEs ship the right thing on the first try. This specification defines fields, acceptance criteria, and templates that align with Google’s helpful content guidance, structured data rules, and plain language principles.

Updated Aug 2025 • ~30 to 40 min read

Want this spec tailored to your team Ask a quick question

Objective and scope

This standard defines the required fields and quality bars for a B2B and SaaS content brief. The brief aligns intent, entities, sources, structure, and success metrics before any words are written. It draws on Google’s Search Essentials, plain language guidance from plainlanguage.gov, and accessibility practices from W3C WCAG.

Always cite primary sources when you include data or claims. Use reputable sources such as Statista market data, U.S. Census Bureau, Bureau of Labor Statistics, and vendor documentation. Follow FTC advertising guidance for truthful claims.

Brief fields

These fields form a complete brief. Keep names stable across templates and CMS.

Strategy

Objective: one clear outcome and time frame
Audience: role, industry, maturity, region
Problem statement: how they describe pain
Angle: point of view or thesis

Search & entities

Primary intent: informational, investigational, transactional
Queries: short list with variants
Entity list: canonical terms and definitions
SERP notes: people also ask, features, gaps

Evidence

Sources: 3 to 7 high quality links
Data points: metric, timeframe, source URL
Expert input: SME, quotes, review plan
Compliance: legal or risk flags

Structure

H2 and H3 outline: question or task style
Answer blocks: 40 to 60 words per section
Tables or visuals: where decisions need clarity
Schema plan: Article, FAQ, HowTo, Product, Breadcrumb

Conversion & routing

Primary CTA: one action with tracking id
Secondary CTA: optional softer step
Internal links: hub, next step, and proof
Navigation notes: where this page lives

Delivery

Format: article, comparison, template, tool
Assets: images, diagrams, embeds
Timeline: draft, review, publish dates
Success metrics: KPIs and targets

Acceptance criteria

Each field has a done definition so briefs are consistent and audit ready.

Field	Done when	Authority reference
Objective	States outcome, audience, timeframe, and the decision you want the reader to take	Helpful content
Audience	Lists role, industry, company size, region, and constraints in their language	Plain language
Angle	Explains what is different about your point of view in one or two sentences	NN/g writing
Primary intent	One intent selected and justified with SERP observations	Search Essentials
Entity list	Includes canonical names, 1 line definitions, and synonyms	Structured data
Sources	At least 3 primary or high trust sources with titles and anchor text	FTC guidance
H2 and H3 outline	Headings written as questions or tasks, each with a short answer block	NN/g on scanning
Schema plan	Chosen types match visible content and policy	Schema policies
CTAs	One primary action with tracking id and one optional secondary	GA4 events
Success metrics	Metric, target, and how measured in GA4 or Search Console	Search Console
Compliance	Claims are sourced, privacy and accessibility risks noted, reviewers assigned	WCAG

Templates

JSON schema for briefs

{
  "title": "Content Brief",
  "type": "object",
  "required": ["objective","audience","angle","intent","entities","outline","sources","cta","metrics"],
  "properties": {
    "objective": {"type":"string", "maxLength": 240},
    "audience": {
      "type":"object",
      "properties":{
        "role":{"type":"string"},
        "industry":{"type":"string"},
        "companySize":{"type":"string"},
        "region":{"type":"string"},
        "pain":{"type":"string"}
      }
    },
    "angle":{"type":"string","maxLength":200},
    "intent":{"type":"string","enum":["informational","investigational","transactional"]},
    "queries":{"type":"array","items":{"type":"string"}, "minItems":3, "maxItems":10},
    "entities":{
      "type":"array",
      "items":{"type":"object","properties":{"name":{"type":"string"},"definition":{"type":"string"},"aliases":{"type":"array","items":{"type":"string"}}}}
    },
    "outline":{
      "type":"array",
      "items":{"type":"object","properties":{"heading":{"type":"string"},"answer":{"type":"string"},"notes":{"type":"string"}}}
    },
    "sources":{"type":"array","items":{"type":"object","properties":{"title":{"type":"string"},"url":{"type":"string","format":"uri"}}}},
    "schemaPlan":{"type":"array","items":{"type":"string"}},
    "cta":{"type":"object","properties":{"primary":{"type":"string"},"secondary":{"type":"string"},"trackingId":{"type":"string"}}},
    "internalLinks":{"type":"array","items":{"type":"object","properties":{"anchor":{"type":"string"},"href":{"type":"string"}}}},
    "assets":{"type":"array","items":{"type":"string"}},
    "compliance":{"type":"array","items":{"type":"string"}},
    "metrics":{"type":"array","items":{"type":"object","properties":{"name":{"type":"string"},"target":{"type":"string"},"source":{"type":"string"}}}},
    "timeline":{"type":"object","properties":{"draft":{"type":"string"},"review":{"type":"string"},"publish":{"type":"string"}}}
  }
}

Markdown brief template

# Content Brief: <Working Title>

**Objective**  
Outcome, audience, timeframe, decision.

**Audience**  
Role, industry, company size, region, pain in their words.

**Angle**  
Point of view in one to two sentences.

**Primary intent**  
Informational | Investigational | Transactional

**Queries**  
- <query 1>  
- <query 2>  
- <query 3>

**Entity list**  
- Term — one line definition. Aliases: <list>  
- Term — one line definition.

**SERP notes**  
Features present, gaps, PAA questions.

**Outline (H2/H3)**  
- H2: <question or task>  
  - Short answer: 40 to 60 words  
  - Notes: table, example, or schema
- H2: <...>

**Sources**  
- [<Title>](https://developers.google.com/search/docs/fundamentals/search-essentials)  
- [<Authority data>](https://data.census.gov/)  
- [<Methodology>](https://www.nngroup.com/articles/writing-digital-copy/)

**CTAs**  
Primary: <label> (trackingId: cta_article_top)  
Secondary: <label>

**Internal links**  
- Hub: <anchor> → /resources/  
- Next step: <anchor> → /solutions/<x>/

**Schema plan**  
Article, FAQ, Breadcrumb.

**Compliance**  
Claims, privacy, accessibility notes, reviewers.

**Assets**  
Images, diagrams, embeds.

**Success metrics**  
- Metric — target — measured in GA4 or Search Console.

Example filled brief

Example for a comparison page. Replace details with your product and market.

Strategy

Objective: Help managers choose a customer onboarding tool and drive 3 percent click to trial within 30 days
Audience: SaaS product managers in North America at 50 to 500 employee companies
Angle: Compare implementation speed and integration depth with verified evidence
Primary intent: investigational

Search & entities

Queries: onboarding software comparison, best user onboarding tools, onboarding for B2B SaaS
Entities: onboarding checklist, product tour, PQL, activation rate
SERP notes: PAA asks about pricing, integrations, and time to value

Evidence

Sources: Google helpful content, Statista market data, vendor docs
Data points include integration counts and availability of SSO
SME: Head of Implementation for quotes

Structure

H2: What is customer onboarding software
H2: Quick comparison table by criteria
H2: How to choose based on team size and stack
FAQ with 3 questions
Schema: Article, FAQ, Breadcrumb

Conversion & routing

Primary CTA: See a fast walkthrough (trackingId: cta_compare_top)
Secondary CTA: Download checklist
Internal links: hub → /resources/, solution → /solutions/product-onboarding/

Metrics

3 percent click to trial from table buttons
Average time on page and scroll depth
Queries and CTR in Search Console

Workflow, reviews, and compliance

States and roles

Draft, In review, Approved, Scheduled, Published
Author, SEO, SME, Legal, Publisher
Only Legal can mark compliance complete

Claim and citation policy

Every numeric claim needs a nearby citation. Prefer primary sources and vendor docs. For economic or labor data use BLS or Census. For methodology claims link to research like NN/g.

Accessibility and language

Follow WCAG and plain language. Use descriptive link text and clear headings. See WCAG and plainlanguage.gov.

If you include testimonials or endorsements, follow FTC Endorsement Guides.

Success metrics and GA4

Pick a small set of metrics that map to the brief objective and the page type. Track them in GA4 and Search Console.

Engagement

Engaged sessions per user
Scroll depth or anchor clicks
Average engaged time

Conversion

Primary CTA click rate
Lead or trial start marked as conversion
Assisted conversions from content group

Visibility

Queries and CTR in Search Console
Coverage and enhancements
Rich results validation

GA4 event hints

// Example GA4 events for an article
gtag('event','cta_click',{label:'Watch a 3 min walkthrough',location:'article_top',tracking_id:'cta_article_top'});
gtag('event','anchor_click',{anchor:'#comparison-table',location:'toc'});

Event setup and conversions are documented in GA4 events and conversions. Web performance guidance lives on web.dev.

Implementation checklist

Duplicate the JSON or Markdown template
Define objective, audience, and angle in 240 words or fewer
Set primary intent and list 3 to 10 queries with notes
Write entities with one line definitions and synonyms
Draft H2 and H3 outline and short answer blocks
Collect 3 to 7 primary sources and note claim locations
Choose schema types that match the page
Pick one primary CTA with a tracking id
List hub, next step, and proof links
Set success metrics and where to measure in GA4 or Search Console
Book SME, SEO, and Legal reviews with dates
Publish the brief in your CMS or doc hub for version control

FAQ

How long should a brief be

Most briefs fit on one or two pages. The goal is clarity, not volume. Use short fields and links to evidence, not pasted research.

Do I include keywords or only intent

Include both. Lead with intent, then list the top queries and related variants. Match headings to the searcher’s task and use internal links to the next step.

Where do performance targets come from

Use your baseline in GA4 and Search Console. Pick targets that reflect page type. For example a comparison page target is CTA clicks, while a glossary page target is “read next” rate.

Should designers see the brief

Yes. Designers need the objective, audience, entities, tables, and schema plan so layout supports clarity and accessibility.

Implement this brief standard Ask a quick question