Brain Name: Content Brain
Document Type: Active Reference Framework
Status: Active Reference Framework
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, existing website content review, content audits, site tone analysis, content inventory, internal linking review, content refresh planning, SEO content briefs, affiliate content packs, publishing readiness, repurposing, future Site Content Intelligence Employee, and future Content Brain system wiring
Parent: Content Brain
Last Reviewed: 2026-06-03
Purpose
The Content Brain Site Content Intelligence Framework defines how Content Brain reviews an existing website before creating new content.
Its purpose is to make sure Content Brain understands the site it is working on before it creates content briefs, SEO briefs, affiliate support content, internal linking plans, refresh plans, repurposing plans, or publishing readiness checks.
Content should not be created in isolation.
Before new content is created, Content Brain should understand:
what content already exists
what topics are already covered
what the site already sounds like
what tone and voice the site uses
what trust signals already exist
what internal links already exist
what content is outdated
what content is missing
what pages are thin
what pages overlap
what pages should be refreshed
what pages should be repurposed
what content gaps matter most
what content would naturally fit the site
This framework exists so Content Brain can create site-specific content rather than generic content.
Current Status Notice
This page should be kept as an Active Reference Framework.
It is not a first-layer operator page.
It supports the active operational layer by adding a site-intelligence step before content creation, content refresh, repurposing, internal linking, SEO briefing, or affiliate content planning.
Use this framework when Content Brain needs to understand an existing site before deciding what content should be created or improved.
This page may later support a future AI Employee candidate:
Site Content Intelligence Employee
Do not create the employee yet.
Manual workflow use should prove the need first.
Core Principle
Content should fit the site it belongs to.
A good content system should understand the existing website before creating new content.
Site-specific content is stronger than generic content because it can match:
existing tone
existing structure
existing topics
existing audience expectations
existing trust signals
existing content gaps
existing internal link opportunities
existing offer support needs
existing SEO structure
existing conversion pathways
Content Brain should not create content that feels disconnected from the website.
Content Brain should create content that feels like it belongs.
Why This Framework Matters
Many content systems create generic content because they start from a topic or keyword without understanding the website.
That creates problems:
new content sounds different from existing pages
content repeats what already exists
content misses internal linking opportunities
content ignores old pages that should be refreshed
content creates duplicate topics
content does not match the site’s trust style
content does not support existing offers
content does not connect to the real reader journey
content becomes harder to manage later
This framework prevents Content Brain from producing disconnected content.
It gives Content Brain a site-aware foundation before content work begins.
Definition
Site Content Intelligence is the structured review of an existing website’s content before new content decisions are made.
It identifies:
existing content assets
content style
content tone
topic coverage
content gaps
content duplication
content quality
internal linking opportunities
refresh opportunities
repurposing opportunities
trust signals
affiliate support gaps
SEO structure
reader journey gaps
brand voice patterns
future content priorities
Site Content Intelligence helps Content Brain decide whether to:
create new content
refresh existing content
repurpose existing content
merge overlapping content
improve internal links
create an SEO brief
create an affiliate content pack
create funnel support content
hold the request for more research
escalate to another Brain
Where This Fits In The Content Brain Workflow
This framework sits between:
Content Brain Workflow
and
Content Brain Content Briefs / Content Brain SEO Content Briefs / Content Brain Affiliate Content Packs / Content Brain Refresh / Content Brain Internal Linking / Content Brain Repurposing
The improved workflow is:
Input received.
Content Brain Workflow classifies the request.
Site Content Intelligence checks the existing site where needed.
Content Brain decides whether to create, refresh, repurpose, merge, internally link, or park.
The correct operational page is used.
Publishing Readiness checks the final output before use.
This prevents new content from being created blindly.
When To Use This Framework
Use this framework when:
working on an existing website
creating SEO content for a site
creating affiliate support content for a site
planning internal links
refreshing existing pages
repurposing old content
building a content cluster
creating content for a client site
creating content for an MWMS Brain site
matching tone or voice matters
the site has existing pages that may overlap
the site has no clear content inventory
a new brief may duplicate old content
the operator is unsure what already exists
Content Brain needs site-specific context before creating content
Do not use this framework when:
there is no existing site
the content is purely internal planning
the content is a one-off system note
site tone does not matter
the request is urgent and clearly does not depend on existing content
Site Content Intelligence Outputs
A Site Content Intelligence review may produce:
Site Content Inventory
Site Voice And Tone Summary
Topic Coverage Map
Content Gap List
Internal Linking Opportunity List
Refresh Opportunity List
Repurposing Opportunity List
Duplicate Or Overlap Warning
Thin Content Warning
Trust Signal Summary
Affiliate Support Gap List
SEO Structure Notes
Reader Journey Notes
Recommended Next Content Assets
Site-Specific Content Instructions
Briefing Notes For Content Brain
These outputs should be practical.
The goal is not to create a huge audit for the sake of it.
The goal is to help Content Brain make better content decisions.
Site Content Inventory
The Site Content Inventory records what already exists on the website.
It may include:
page title
URL
content type
topic
status
last updated date where known
primary intent
audience stage
related offer where relevant
internal links
content quality notes
refresh need
repurposing potential
risk notes
The inventory helps prevent duplicate content creation.
It also helps Content Brain decide whether a new page is needed or whether an existing page should be improved.
Site Voice And Tone Summary
The Site Voice And Tone Summary defines how the site currently sounds.
It may include:
formal or informal tone
expert or beginner-friendly tone
direct or educational tone
high-energy or calm tone
humorous or serious tone
technical or plain-English style
sales-focused or trust-focused style
short-form or long-form style
common phrases
phrases to avoid
brand personality
This helps new content match the site’s existing feel.
The goal is not to copy every old style mistake.
The goal is to preserve useful consistency while improving quality.
Topic Coverage Map
The Topic Coverage Map shows what the site already covers.
It may identify:
main topics
subtopics
content clusters
hub pages
supporting pages
missing spokes
orphan topics
overdeveloped topics
underdeveloped topics
affiliate support topics
SEO topic gaps
trust topics
FAQ topics
comparison topics
The Topic Coverage Map helps Content Brain avoid random topic creation.
It also supports Content Brain Topic Architecture Framework and Content Brain Topic Cluster And Hub Architecture Framework.
Content Gap List
The Content Gap List identifies useful missing content.
Gaps may include:
missing problem-awareness pages
missing solution explanation pages
missing FAQ pages
missing trust pages
missing comparison pages
missing affiliate support pages
missing internal support pages
missing SEO pages
missing refresh notes
missing repurposing assets
missing product education content
missing decision-support content
Each gap should include why it matters.
Do not list gaps only because more content could be created.
A useful gap should support reader understanding, search usefulness, affiliate support, conversion readiness, trust, internal linking, or system learning.
Internal Linking Opportunity List
The Internal Linking Opportunity List identifies where pages should connect.
It may include:
hub-to-spoke links
spoke-to-hub links
related article links
trust support links
FAQ links
comparison page links
affiliate support links
refresh-related links
reader journey links
orphan page fixes
Internal links should help the reader first.
SEO benefit should come from useful structure.
Use Content Brain Internal Linking for deeper planning.
Refresh Opportunity List
The Refresh Opportunity List identifies existing pages that may need improvement.
Refresh triggers may include:
outdated information
thin content
weak structure
poor intent match
weak internal links
old claims
missing trust signals
duplicated sections
poor information gain
low usefulness
changed offer context
changed search intent
weak publishing readiness
Use Content Brain Refresh when a page should be improved instead of creating new content.
Repurposing Opportunity List
The Repurposing Opportunity List identifies existing content that can be reused safely.
Repurposing opportunities may include:
article to email
article to social post
article to YouTube description
article to VEO3 support
guide to checklist
FAQ to support content
comparison to internal training
framework to client-facing explanation
Repurposing should preserve meaning.
It should not strengthen claims, change audience stage, or create compliance risk.
Use Content Brain Repurposing for deeper review.
Duplicate Or Overlap Warning
Content Brain should identify when a new content idea overlaps with existing content.
Overlap may include:
same topic
same search intent
same audience
same content purpose
same offer support role
same keyword focus
same funnel stage
same FAQ coverage
same comparison angle
If overlap exists, decide whether to:
refresh existing page
merge content
expand existing page
create a different angle
park the request
create a supporting spoke page
Do not create duplicates just because the wording is slightly different.
Thin Content Warning
Thin content risk appears when a page:
repeats generic information
has no information gain
has no clear purpose
has weak examples
has weak internal links
has no trust support
has no useful next step
is too shallow for the reader intent
exists only because AI can generate it
Thin content should be improved, merged, refreshed, or retired.
Do not create new thin content.
Trust Signal Summary
The Trust Signal Summary records what the site currently uses to build trust.
Trust signals may include:
clear author or brand identity
experience signals
case studies
testimonials
FAQ sections
disclosures
transparent limitations
contact information
support pages
proof explanations
comparison fairness
clear expectation-setting
safe claim handling
If trust signals are weak, Content Brain may recommend trust-building content or Publishing Readiness improvements.
Use Content Brain E E A T Content Trust Framework where trust is important.
Affiliate Support Gap List
For affiliate sites or affiliate content paths, Site Content Intelligence should check whether the site has:
problem-awareness content
solution-awareness content
product education content
comparison content
FAQ content
trust content
pre-sell content
VSL preparation content
YouTube support content
email support content
objection-handling content
expectation-setting content
affiliate disclosure awareness
If affiliate support gaps exist, Content Brain may route to:
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Conversion Support Framework
Content Brain Publishing Readiness
Affiliate Brain where offer status is unclear
Compliance Brain where claim risk exists
SEO Structure Notes
SEO structure notes may include:
main topics
search intent alignment
topic clusters
hub pages
spoke pages
internal link gaps
orphan pages
keyword cannibalisation risk
information gain gaps
thin content risk
refresh opportunities
missing entity coverage
content format mismatch
SERP mismatch notes where known
Search Intelligence Brain owns search validation and SERP interpretation.
Content Brain can record SEO structure notes but should not replace Search Intelligence Brain.
Reader Journey Notes
Reader Journey Notes identify how a visitor may move through the site.
They may include:
where the reader enters
what they likely know
what they need next
where confusion may happen
which page should come next
which internal links are missing
where trust support is needed
where the CTA may be too early
where content is too shallow or too complex
which pages support decision readiness
Reader journey notes help Content Brain create content that fits the site’s natural flow.
Site-Specific Content Instructions
After reviewing the site, Content Brain should produce site-specific instructions for future briefs.
These may include:
write in this tone
avoid these phrases
use this type of explanation
link to these pages
do not duplicate these pages
refresh this page before creating new content
use these trust signals
avoid unsupported claims
match this audience awareness level
include these internal links
follow this structure
use these approved terms
These instructions make future content sound and feel like it belongs on the site.
Site Content Intelligence Review Process
Step 1: Identify Site Purpose
Before reviewing content, define what the site exists to do.
Ask:
What is the site’s main purpose?
Who is the audience?
What business model does it support?
What offers or services does it support?
What kind of content does the site already publish?
What action should visitors eventually take?
If the site purpose is unclear, content decisions will be weak.
Step 2: Inventory Existing Content
Create a basic inventory of important pages.
Record:
page title
URL where available
content type
topic
intent
quality notes
internal link notes
refresh notes
overlap notes
This does not need to be perfect at first.
A useful lightweight inventory is better than no inventory.
Step 3: Analyse Voice And Tone
Review several representative pages.
Identify:
how the site explains topics
how formal or informal it is
how much personality it uses
how it handles trust
how it presents offers
how it uses CTAs
how it speaks to beginners or advanced readers
how direct or soft the tone is
This becomes the site voice summary.
Step 4: Map Topic Coverage
Identify the main content topics and clusters.
Ask:
What topics are strong?
What topics are weak?
What topics are missing?
What topics overlap?
What topics support offers?
What topics support search?
What topics support trust?
What topics support internal linking?
This becomes the topic coverage map.
Step 5: Identify Content Gaps
Identify gaps that matter.
Good gaps support:
reader understanding
search usefulness
trust
affiliate support
conversion readiness
internal linking
refresh discipline
repurposing
Do not create a content gap just because more content could exist.
The gap must serve a purpose.
Step 6: Identify Refresh And Repurposing Opportunities
Before recommending new content, check whether existing content should be:
refreshed
expanded
merged
retired
repurposed
internally linked
New content is not always the best answer.
Sometimes the best action is to improve what already exists.
Step 7: Identify Internal Linking Opportunities
Look for pages that should be connected.
Ask:
What should link to this page?
What should this page link to?
What hub does this page belong to?
What spoke pages support this page?
Are there orphan pages?
Are there missing trust links?
Are there missing affiliate support links?
Internal linking helps the site feel more coherent.
Step 8: Create Site Content Intelligence Report
The report should include:
site purpose
site voice summary
existing content inventory
topic coverage map
content gaps
refresh opportunities
repurposing opportunities
internal linking opportunities
trust signal notes
affiliate support gaps where relevant
SEO structure notes where relevant
recommended next actions
The report should be clear enough that Content Brain can create better briefs from it.
Site Content Intelligence Decision Table
| Situation | Decision |
|---|---|
| Similar content already exists | Refresh, expand, merge, or internally link before creating new content |
| Site tone is clear | Match useful tone patterns in new briefs |
| Site tone is weak or inconsistent | Improve clarity while preserving brand fit |
| Topic cluster exists but has missing spokes | Create targeted supporting content |
| Topic is missing and useful | Create content brief or SEO brief |
| Existing page is outdated | Use Content Brain Refresh |
| Existing content can be reused | Use Content Brain Repurposing |
| Internal links are weak | Use Content Brain Internal Linking |
| Offer support gaps exist | Use Content Brain Affiliate Content Packs or Affiliate Funnel Support |
| Claim risk exists | Route to Compliance Brain |
| Search intent is unclear | Route to Search Intelligence Brain |
| Evidence is missing | Route to Research Brain |
| Site purpose is unclear | Park until clarified |
| New content would duplicate existing content | Do not create until overlap is resolved |
Relationship To Active Operational Layer
Use this framework with the active Content Brain pages.
Use Content Brain Workflow when a content request needs classification.
Use this Site Content Intelligence Framework when existing site context matters.
Use Content Brain Content Briefs after site context is understood.
Use Content Brain SEO Content Briefs when search content is needed.
Use Content Brain Affiliate Content Packs when affiliate support content is needed.
Use Content Brain Affiliate Funnel Support when content supports funnel stages.
Use Content Brain Internal Linking when page relationships are found.
Use Content Brain Refresh when existing content should be improved.
Use Content Brain Repurposing when existing content can be reused.
Use Content Brain Publishing Readiness before output is used or handed off.
Relationship To Content Brain Workflow
Content Brain Workflow classifies the request.
This framework checks the existing site context.
Workflow answers:
What kind of request is this?
Site Content Intelligence answers:
What already exists on the site, and what should we do based on that?
Relationship To Content Brain Content Briefs
Content Brain Content Briefs creates the brief.
This framework informs the brief with site-specific context.
Content Briefs should use site intelligence to define:
tone
audience
existing pages
internal links
content gaps
claims to avoid
handoff destination
signal to watch
Relationship To Content Brain SEO Content Briefs
SEO Content Briefs should use site intelligence to avoid creating disconnected SEO pages.
Site Content Intelligence can provide:
existing topic coverage
internal link opportunities
search content gaps
page overlap warnings
refresh opportunities
topic cluster notes
Search Intelligence Brain still owns search validation.
Relationship To Content Brain Internal Linking
Site Content Intelligence may discover internal linking opportunities.
Content Brain Internal Linking should be used to plan the actual link structure.
Site Content Intelligence identifies the opportunity.
Internal Linking defines the link plan.
Relationship To Content Brain Refresh
Site Content Intelligence may identify content that should be updated.
Content Brain Refresh should be used when the best action is to improve existing content rather than create new content.
Relationship To Content Brain Repurposing
Site Content Intelligence may identify strong existing content that can be reused.
Content Brain Repurposing should be used to adapt approved content safely into other formats.
Relationship To Content Brain Publishing Readiness
Publishing Readiness should check whether new content fits the site.
Site Content Intelligence provides useful context for this check.
Publishing Readiness should confirm:
new content matches site tone
new content does not duplicate existing pages
new content links to relevant pages
new content respects trust and claim boundaries
new content has a clear place in the site
Relationship To Content Brain Topic Architecture Framework
Topic Architecture defines how topics should be structured.
Site Content Intelligence identifies the current real-world topic structure on the site.
Together, they help Content Brain decide what should be created, refreshed, merged, or linked.
Relationship To Content Brain Topic Cluster And Hub Architecture Framework
Site Content Intelligence may identify existing hub and spoke structures.
It may also reveal missing hubs, weak spokes, orphan pages, or cluster gaps.
Use Topic Cluster And Hub Architecture Framework for deeper cluster planning.
Relationship To Content Brain Information Gain Framework
Site Content Intelligence helps determine whether new content adds value or simply repeats what the site already has.
Information Gain Framework should be used when deciding whether the new content deserves to exist.
Relationship To Content Brain E E A T Content Trust Framework
Site Content Intelligence identifies trust signals and trust gaps on the site.
E E A T Content Trust Framework should be used when trust, authority, expertise, experience, transparency, or claim safety matters.
Relationship To Content Brain Cross-Brain Integration Map
Site Content Intelligence may create inputs and outputs for other Brains.
Possible outputs include:
Research Brain research gaps
Search Intelligence Brain validation requests
Affiliate Brain offer support gaps
Compliance Brain claim-risk notes
Data Brain signal requests
HeadOffice priority notes
Use Cross-Brain Integration Map when routing site intelligence to other Brains.
Cross-Brain Relationships
Research Brain
Research Brain may receive:
content gap questions
missing evidence requests
audience language questions
topic clarity requests
problem understanding gaps
Research Brain owns evidence quality.
Search Intelligence Brain
Search Intelligence Brain may receive:
search validation requests
SERP review needs
keyword cannibalisation concerns
topic cluster search questions
SEO content opportunity notes
Search Intelligence Brain owns search validation.
Affiliate Brain
Affiliate Brain may receive:
affiliate support gaps
offer education gaps
pre-sell content gaps
trust support gaps
comparison content gaps
Affiliate Brain owns offer logic.
Conversion Brain
Conversion Brain may receive:
decision-friction notes
CTA mismatch notes
trust gap notes
reader journey friction
Conversion Brain owns conversion logic.
Compliance Brain
Compliance Brain may receive:
claim-risk notes
disclosure concerns
sensitive topic concerns
comparison risk
testimonial risk
Compliance Brain owns compliance interpretation.
Data Brain
Data Brain may receive:
signal-to-watch recommendations
performance question notes
refresh measurement needs
content inventory tracking needs
Data Brain owns measurement reliability.
HeadOffice
HeadOffice may receive:
priority recommendations
site content risk notes
content system gaps
future build candidates
workflow friction notes
HeadOffice owns priority and direction.
Future Site Content Intelligence Employee Candidate
This framework may later support a future AI Employee candidate:
Site Content Intelligence Employee
Possible mission:
Review an existing website before Content Brain creates new content.
Possible responsibilities:
crawl or review visible site content
summarise existing pages
identify site voice and tone
map topic coverage
find content gaps
find refresh opportunities
find repurposing opportunities
find internal linking opportunities
identify affiliate support gaps
identify trust gaps
prepare a Site Content Intelligence Report
feed site-specific instructions into Content Brain briefs
This employee should not be created yet.
Manual workflow should prove that the function is repeatedly useful.
Future Site Content Intelligence Report Template
A future report may include:
Site Name:
Site URL:
Site Purpose:
Primary Audience:
Business Model:
Main Offers:
Current Content Inventory:
Site Voice Summary:
Tone Notes:
Topic Coverage Map:
Main Topic Clusters:
Thin Content Risks:
Duplicate Or Overlap Risks:
Refresh Opportunities:
Repurposing Opportunities:
Internal Linking Opportunities:
Trust Signals:
Trust Gaps:
Affiliate Support Gaps:
SEO Structure Notes:
Reader Journey Notes:
Recommended Next Content Assets:
Pages To Avoid Duplicating:
Pages To Refresh Before Creating New Content:
Claims To Avoid:
Approval Owner:
Recommended Next Operational Page:
Signal To Watch:
Future Plugin Or UI Candidate
This framework may later support:
Site Content Intelligence Report Generator
Site Content Inventory Tool
Site Voice And Tone Extractor
Content Gap Finder
Internal Linking Opportunity Finder
Refresh Opportunity Finder
Repurposing Opportunity Finder
Affiliate Support Gap Finder
Content Brief Generator input layer
SEO Brief Generator input layer
Content Operations Dashboard site intelligence panel
Do not build these yet.
Manual workflow must prove operational need before plugin, UI, queue, dashboard, generator, automation, or AI Employee development begins.
Build-Readiness Criteria
This function becomes build-ready only when:
manual site reviews are repeated
the report format becomes stable
operators find the output useful
site intelligence improves briefs
site intelligence reduces duplicate content
site intelligence improves internal linking plans
site intelligence improves refresh decisions
site intelligence improves repurposing decisions
fields are clear
handoff destinations are clear
approval ownership is clear
M can be given a clean build specification
Until then, this remains an Active Reference Framework and Future Employee Candidate.
Drift Protection
This framework must prevent:
new content being created without checking existing site content
generic content that does not match the site
duplicate content creation
topic overlap
tone mismatch
internal linking missed opportunities
refresh opportunities being ignored
repurposing opportunities being missed
affiliate support gaps being missed
site-specific trust signals being ignored
AI content sounding disconnected from the site
Content Brain creating content before understanding the site
site intelligence being treated as final SEO validation
site intelligence being treated as final compliance approval
site intelligence replacing Research Brain, Search Intelligence Brain, Affiliate Brain, Compliance Brain, Data Brain, or HeadOffice authority
future Site Content Intelligence Employee being built before manual workflow proves need
Architectural Intent
The Content Brain Site Content Intelligence Framework exists to make Content Brain more site-aware.
Its purpose is to stop Content Brain from creating isolated, generic, off-brand, or duplicate content.
It helps Content Brain understand the actual website before producing new content.
The long-term intent is for Content Brain to create content that:
fits the site
sounds consistent with the site
connects to existing pages
fills real gaps
supports existing offers
strengthens internal linking
improves refresh discipline
supports repurposing
protects trust
supports future system build
This framework is a bridge between content audit, content strategy, content briefing, and future AI Employee automation.
Final Rule
Before creating important new content for an existing site, Content Brain should ask:
What already exists?
How does the site currently sound?
What content gaps are real?
What pages should be refreshed first?
What internal links are missing?
What content would naturally fit this site?
If those answers are unclear, do not rush into content creation.
Run Site Content Intelligence first.
Change Log
Version: v1.0
Date: 2026-06-03
Author: HeadOffice
Change: Created Content Brain Site Content Intelligence Framework as an Active Reference Framework and future Site Content Intelligence Employee candidate. Defines how Content Brain reviews existing site content, voice, tone, topic coverage, gaps, internal links, refresh opportunities, repurposing opportunities, trust signals, affiliate support gaps, and site-specific content instructions before creating new content. Added review process, decision table, active operational layer relationships, cross-brain relationships, future report template, future plugin/UI candidates, build-readiness criteria, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
Content Brain Site Content Intelligence Framework
Pages Updated:
None
Pages Renamed:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry should be updated later to include this new page after creation.
Canon Version Update Required:
No
Change Log Entry Required:
Recommended later in Content Brain Page Registry.
END CONTENT BRAIN SITE CONTENT INTELLIGENCE FRAMEWORK v1.0