Brain Name: Content Brain
Document Type: Operational SEO Brief Standard
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain SEO content planning, search-aligned content briefs, authority content, topic cluster content, affiliate support SEO content, comparison content, review support content, pre-sell content, refresh briefs, internal linking, information gain planning, E E A T planning, entity relevance, conversion support, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator SEO content brief page for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with MCR, MCR wins.
This page is designed for practical operator use.
It is not a full MCR governance page.
Purpose
Content Brain SEO Content Briefs defines the working structure for planning search-aligned, useful, trustworthy, and conversion-supportive content inside Content Brain.
Its purpose is to stop SEO content from being created randomly, thinly, or only around keywords.
A strong SEO content brief ensures that content is:
aligned with search intent
supported by research
informed by SERP patterns
useful to the reader
structured clearly
built around information gain
supported by entity and topic relevance
connected to internal links
aware of E E A T requirements
aligned with conversion or business purpose where relevant
reviewable before production
measurable after publishing
refreshable later
SEO content must not move into drafting unless the brief is clear enough to guide useful production.
Source Of Truth
MCR defines the governing version of Content Brain.
mwmscontentbrain.site operates the working version.
This page is the working operator version of the Content Brain SEO content brief system.
Do not treat this page as a replacement for:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Those remain MCR control pages.
What This Page Is For
Use this page when planning:
SEO articles
authority articles
topic cluster articles
pillar pages
comparison pages
review support pages
affiliate support articles
pre-sell articles
landing page support content
trust-building content
refresh briefs
repurposing briefs where search intent matters
content updates driven by SERP changes
content improvement work
internal linking support content
This page helps the operator turn search demand, audience intent, research, and business purpose into a usable SEO content brief.
What This Page Does Not Control
This page does not control:
search demand validation
SERP authority interpretation
research verdicts
affiliate offer approval
compliance approval
campaign approval
budget approval
test validation
plugin implementation
Supabase implementation
Brain Room routing
HeadOffice reporting build work
M’s active development areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
Good SEO content is engineered, not improvised.
Content should not be written just because a keyword exists.
Before production begins, the operator must understand:
what the reader wants
what the search intent is
what top-ranking pages are doing
what information gaps exist
what original value MWMS can add
what the content must include
what claims must be avoided
what internal links are needed
what trust signals are required
what conversion or next-step role the content supports
If these are unclear, the brief is not ready.
SEO Brief Required Inputs
Every meaningful SEO content brief should define:
primary topic
search intent
target audience
reader problem
SERP pattern
content type
information gain angle
entity and topical relevance
content structure
E E A T requirements
internal links
external references where needed
conversion or next step
claims to avoid
approval owner
signal to watch
status
SEO Content Brief Template
Use the template below for search-focused content.
1. Brief Name
Field:
Brief Name:
Operator instruction:
Give the brief a clear internal name.
Use the topic, audience, product, funnel role, or search intent.
Example:
Creatine Benefits For Menopause SEO Brief
2. Date Created
Field:
Date Created:
Operator instruction:
Record the date the brief was created.
3. Source Brain
Field:
Source Brain:
Options:
Search Intelligence Brain
Research Brain
Affiliate Brain
HeadOffice
Ads Brain
Experimentation Brain
Content Brain
Manual Operator Observation
Other
Operator instruction:
Record where the SEO content request, keyword, topic, or opportunity came from.
If the source is unclear, park the brief.
4. Supporting Brains
Field:
Supporting Brains:
Operator instruction:
Record any Brains supplying supporting logic.
Examples:
Research Brain for evidence
Search Intelligence Brain for search demand and SERP notes
Affiliate Brain for offer context
Compliance Brain for claim risk
Ads Brain for traffic support context
Conversion Brain for page role
Data Brain for performance signals
HeadOffice for priority
If none, write:
Not applicable
5. Content Asset Type
Field:
Content Asset Type:
Options:
SEO article
Authority article
Pillar page
Topic cluster article
Comparison article
Review support article
Affiliate support article
Pre-sell article
FAQ content
Trust-building page
Landing page support content
Refresh update
Repurposed SEO content
Internal linking support content
Other
Operator instruction:
Choose the content type that best matches the search intent and business purpose.
6. Target Query Or Topic
Field:
Target Query Or Topic:
Operator instruction:
Record the main topic, keyword, question, or search opportunity.
Do not over-focus on one keyword if the topic requires broader coverage.
7. Primary Keyword
Field:
Primary Keyword:
Operator instruction:
Record the primary keyword if one exists.
If not confirmed, write:
Primary keyword not confirmed.
8. Secondary Keywords
Field:
Secondary Keywords:
Operator instruction:
List supporting keywords, related questions, comparison phrases, long-tail variations, or adjacent topics.
Use this to guide coverage, not keyword stuffing.
9. Search Intent Classification
Field:
Search Intent Classification:
Options:
Informational
Commercial
Transactional
Navigational
Local
Mixed
Unknown
Operator instruction:
Choose the closest intent type.
If intent is mixed or unclear, explain the pattern.
10. User Goal
Field:
User Goal:
Operator instruction:
Explain what the searcher is trying to achieve.
Examples:
Learn how something works.
Compare options before purchase.
Understand whether a product is suitable.
Find a safe answer to a sensitive question.
Prepare before watching a VSL.
If the user goal is unclear, the brief needs more research.
11. Target Audience
Field:
Target Audience:
Operator instruction:
Define who the content is for.
Include:
audience type
awareness stage
pain point
desired outcome
market or location if relevant
knowledge level
12. Audience Awareness Stage
Field:
Audience Awareness Stage:
Options:
Unaware
Problem aware
Solution aware
Product aware
Most aware
Existing lead
Existing buyer
Internal operator
Business owner
Operator instruction:
Choose the awareness stage that matches the content job.
13. Funnel Role
Field:
Funnel Role:
Options:
Awareness
Education
Trust building
Pre-sell
Comparison
Objection handling
Decision support
Follow-up
Retention
Internal support
Not applicable
Operator instruction:
Choose where the content fits in the journey.
If this is affiliate or conversion-support content, funnel role must be clear.
14. Business Purpose
Field:
Business Purpose:
Operator instruction:
Explain why MWMS is creating this content.
Examples:
Build topical authority.
Support an approved affiliate offer.
Improve internal linking to a money page.
Answer a recurring audience question.
Refresh a declining page.
Create trust before a VSL click.
If the business purpose is vague, park the brief.
15. SERP Analysis
Field:
SERP Analysis:
Operator instruction:
Record what the current search results show.
Include:
top ranking page types
common formats
common headings
common answer patterns
content depth
tone
media use
FAQ patterns
comparison patterns
trust signals
If SERP analysis is missing, write:
SERP analysis missing — Search Intelligence Brain or Research Brain review needed.
16. Top Ranking Pages
Field:
Top Ranking Pages:
Operator instruction:
List URLs, page names, or summaries of the strongest competing pages.
Do not copy competitors.
Use this to understand what the search result expects and where MWMS can improve.
17. Content Type Observed
Field:
Content Type Observed:
Options:
Blog post
Guide
List
Comparison
Review
Product page
Landing page
FAQ
Video
Forum result
Mixed
Other
Operator instruction:
Record the dominant content type appearing in the results.
If the SERP is mixed, explain the mix.
18. Common SERP Patterns
Field:
Common SERP Patterns:
Operator instruction:
Record what high-ranking pages commonly include.
Examples:
definitions
step-by-step explanations
pros and cons
FAQ sections
comparison tables
expert quotes
product recommendations
risk warnings
how-to sections
visuals
short answer blocks
19. Content Gaps Identified
Field:
Content Gaps Identified:
Operator instruction:
List what competing pages are missing or doing poorly.
Examples:
weak explanations
outdated information
thin examples
poor structure
missing FAQs
weak trust signals
no real decision support
no internal next step
unclear answer
weak comparison logic
These gaps become possible information gain opportunities.
20. Information Gain Angle
Field:
Information Gain Angle:
Operator instruction:
Define what MWMS can add that makes the content more useful than generic content.
Examples:
clearer explanation
better decision framework
stronger examples
better audience-specific guidance
safer claim handling
better internal linking
better comparison logic
better funnel support
clearer pre-click education
If no information gain exists, reconsider whether the content is worth producing.
21. Entity And Topical Relevance
Field:
Entity And Topical Relevance:
Operator instruction:
List important entities, concepts, subtopics, related terms, brands, problems, solution categories, audience language, and supporting ideas.
Use this to improve topical coverage without keyword stuffing.
22. E E A T Requirements
Field:
E E A T Requirements:
Operator instruction:
Record what trust, experience, expertise, authority, or transparency signals the content needs.
Examples:
clear author or brand positioning
source references
practical examples
limitations
disclaimers
comparison fairness
evidence notes
transparent affiliate positioning
review path
If topic risk is high, stronger E E A T support is required.
23. Research Basis
Field:
Research Basis:
Operator instruction:
List the research, sources, Brain notes, SERP observations, audience language, or evidence supporting the brief.
If the research basis is missing, write:
Research basis missing — content not ready for production.
24. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims the content must not make.
Include:
unverified product claims
income claims
health claims
legal claims
guarantees
scarcity claims
urgency claims
exaggerated comparisons
unsupported performance claims
unsupported testimonials
unverified “works for everyone” language
Do not leave this blank for affiliate, health, finance, income, legal, or product-related content.
25. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the risk level.
If risk is medium, high, or unknown, identify who must review the content before use.
26. Required Compliance Review
Field:
Required Compliance Review:
Options:
Not required
Compliance Brain
HeadOffice
Affiliate Brain
Ads Brain
Legal review
Other
Unknown
Operator instruction:
If the content includes sensitive claims, product recommendations, health, finance, income, legal, urgency, scarcity, testimonials, or comparisons, identify the review owner.
Do not mark the brief ready if review ownership is unclear.
27. Content Structure
Field:
Content Structure:
Operator instruction:
Outline the recommended content structure.
Include:
working title
introduction
main sections
supporting sections
FAQ section if needed
comparison section if needed
trust section if needed
objection-handling section if needed
CTA section if needed
internal link placements
next step
Structure should match intent.
Do not force a sales structure onto informational content too early.
28. Required Sections
Field:
Required Sections:
Operator instruction:
List the must-have sections.
Examples:
definition
problem explanation
solution overview
product fit
pros and cons
comparison
FAQ
trust section
how-to
safety notes
who this is for
who this is not for
next step
29. FAQ Questions
Field:
FAQ Questions:
Operator instruction:
List reader questions that should be answered.
FAQ questions should come from search intent, audience objections, SERP patterns, or real content gaps.
30. Internal Links Needed
Field:
Internal Links Needed:
Operator instruction:
List pages, articles, support assets, trust pages, topic hubs, offer pages, or related content that should link to or from this asset.
Use Content Brain Internal Linking if the plan is meaningful.
31. External References Needed
Field:
External References Needed:
Operator instruction:
List any external references, sources, examples, or citations required.
Use reliable sources where factual support is needed.
Do not invent sources.
32. CTA Or Next Step
Field:
CTA Or Next Step:
Options:
Read next page
Watch video
Watch VSL
Click affiliate link
Join list
Book call
Reply
Save
Share
No CTA
Other
Operator instruction:
Choose the next step that matches the content intent and funnel role.
Do not force a commercial CTA on early informational content unless justified.
33. Conversion Support Role
Field:
Conversion Support Role:
Options:
Awareness support
Trust support
Pre-sell support
Comparison support
Objection support
Decision support
Retargeting support
Internal support
Not applicable
Operator instruction:
Record whether the content supports conversion indirectly or directly.
Conversion support does not mean aggressive selling.
34. Handoff Destination
Field:
Handoff Destination:
Options:
WordPress page
Blog post
Affiliate funnel
YouTube description
YouTube script
VEO3 pre-video
Newsletter
Social post
Sales support
Internal knowledge
Refresh queue
Repurposing queue
Other
Operator instruction:
Record where the finished content will go.
If destination is unclear, the brief is not ready.
35. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the content before use.
Examples:
HeadOffice
Search Intelligence Brain
Research Brain
Affiliate Brain
Compliance Brain
Ads Brain
Experimentation Brain
Finance Brain
Martyn
Other
If approval owner is missing, do not mark the brief ready.
36. Signal To Watch
Field:
Signal To Watch:
Options:
search impressions
search clicks
ranking movement
affiliate clicks
VSL clicks
page views
time on page
scroll depth
internal link clicks
email clicks
YouTube views
YouTube retention
conversion assist
manual feedback
Other
Operator instruction:
Record what signal should be watched after publication or use.
Do not over-interpret weak signals.
Data Brain owns signal quality.
37. Brief Status
Field:
Brief Status:
Options:
Draft
Needs research
Needs SERP review
Needs approval owner
Needs compliance review
Ready for drafting
In drafting
In review
Ready for handoff
Handed off
Published
Parked
Closed
Rejected
Operator instruction:
Keep status current.
Do not mark ready if search intent, research basis, compliance risk, approval owner, or handoff destination is unclear.
SEO Brief Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Search intent clear, research basis clear, risk low, approval owner known | Ready for drafting |
| Search intent unclear | Needs Search Intelligence Brain review |
| SERP analysis missing | Needs SERP review |
| Research basis missing | Needs Research Brain review |
| Topic too broad | Narrow the brief |
| Topic too thin | Park or merge into another page |
| Information gain unclear | Needs improvement before drafting |
| Compliance risk unknown | Needs compliance review |
| Claims to avoid missing | Needs claim safety review |
| Internal links unclear | Needs internal linking review |
| Approval owner missing | Needs owner decision |
| Handoff destination unclear | Park |
| Request belongs to another Brain | Route back to correct Brain |
When To Mark Ready For Drafting
Mark the SEO brief ready for drafting only when:
source Brain is clear
search intent is clear
target audience is clear
business purpose is clear
SERP pattern is understood
information gain angle exists
research basis is recorded
content structure is clear
claims to avoid are listed
compliance sensitivity is known
internal linking needs are considered
approval owner is known
handoff destination is clear
signal to watch is defined
If any major item is missing, do not mark the brief ready.
When To Park An SEO Brief
Park the brief when:
search intent is unclear
audience is unclear
topic is too broad
topic is too thin
SERP pattern is unknown
research basis is missing
information gain is weak
claims to avoid are missing
compliance risk is unknown
approval owner is missing
handoff destination is unclear
the request belongs to another Brain
Parked does not mean rejected.
It means the missing information must be resolved before content work moves forward.
SEO Quality Guardrails
SEO content should be:
useful to humans first
clear in structure
specific in explanation
stronger than generic AI content
aligned with real search intent
supported by reliable information
honest about limitations
connected to internal links
reviewable after publication
Do not create SEO content that is:
thin
generic
keyword-stuffed
claim-heavy
unsupported
misleading
duplicative
written only to target a keyword
unclear about next step
Relationship To Other Operational Pages
Use this page with:
Content Brain for the homepage and operator starting point
Content Brain Workflow for the full workflow
Content Brain Content Briefs for general content briefs
Content Brain Publishing Readiness for final checks
Content Brain Affiliate Content Packs for affiliate product content pack planning
Content Brain Affiliate Funnel Support for funnel-stage mapping
Content Brain Internal Linking for page connection planning
Content Brain Repurposing for adapting approved content
Content Brain Refresh for improving existing content
Future Plugin Or UI Candidates
This page may later support:
SEO Brief Generator
Content Brief Generator
Internal Linking Planner
Topic Cluster Planner
Publishing Readiness Checklist UI
Content Production Queue
Content Refresh Queue
Content Operations Dashboard
Content Signal Feedback Dashboard
Do not build these yet.
Manual use must prove the need first.
No Build Rule
Do not start any of the following from this page:
plugin work
custom UI work
Supabase work
Brain Room routing
automation
queue build
dashboard build
generator build
cross-brain task routing
This page is part of the first manual operational layer only.
Old Page Handling
This page replaces the operator role of the older page:
Content Brain SEO Content Brief Standard
After Content Brain SEO Content Briefs is created and checked, the older Content Brain SEO Content Brief Standard page should be handled as follows:
If it is only a duplicate operational SEO brief page, delete it.
If it is needed for historical reference, move it to a legacy/reference area and mark it clearly as legacy.
Do not keep both as active operator SEO brief pages.
The active operator SEO brief page should be:
Content Brain SEO Content Briefs
Drift Protection
The system must prevent:
SEO content being created without search intent
SEO content being created without research basis
SEO content being created without SERP understanding
SEO content being created without information gain
SEO content being created only to target keywords
SEO content becoming thin AI content
affiliate SEO content being created before offer status is clear
claim risk being ignored
internal linking being forgotten
old SEO brief standard pages being treated as the current operator SEO brief page after this clean page is created
future UI being built before manual SEO brief use proves need
Content Brain taking authority from Search Intelligence Brain, Research Brain, Affiliate Brain, Ads Brain, Experimentation Brain, Compliance Brain, Finance Brain, Data Brain, SIT Brain, or HeadOffice
Architectural Intent
Content Brain SEO Content Briefs exists to make SEO content planning structured, useful, and governed.
Its role is to connect search demand with clear content planning before drafting begins.
SEO briefs should help MWMS create content that:
answers real search intent
adds information gain
supports authority
builds trust
supports internal linking
supports affiliate or conversion journeys where appropriate
can be refreshed later
can be measured after publication
feeds useful signals back into the ecosystem
The long-term intent is:
MCR defines Content Brain.
mwmscontentbrain.site operates Content Brain.
Future plugin or UI systems automate repeated workflows only after manual use proves the need.
Final Rule
No meaningful SEO content should move into drafting without clear search intent, audience, research basis, information gain, structure, approval owner, and handoff destination.
SEO content must serve the reader first.
Search visibility should be earned through usefulness, clarity, trust, and structure.
When in doubt, park the brief and route the missing decision back to the correct Brain.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Created clean operator SEO content brief page for mwmscontentbrain.site based on MCR Content Brain SEO Content Brief Standard and the existing Content Brain SEO Content Brief Standard page. Defines the live Content Brain SEO Content Briefs page for the first operational Content Brain layer, including SEO brief inputs, search intent, SERP analysis, information gain, entity relevance, E E A T requirements, content structure, internal linking, conversion support, decision table, ready rules, parking rules, SEO quality guardrails, relationship to other operational pages, no build rule, old page handling, drift protection, and manual-first future plugin/UI boundaries.
Change Impact Declaration
Pages Created:
Content Brain SEO Content Briefs
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain SEO Content Brief Standard
Pages Deprecated:
Content Brain SEO Content Brief Standard as active operator SEO brief page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN SEO CONTENT BRIEFS v1.0