Brain Name: Content Brain
Document Type: Operational Linking Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain internal linking, SEO content support, topic cluster support, hub and spoke planning, affiliate content support, authority content support, trust content support, pre-sell content support, refresh work, repurposing work, reader journey planning, link equity planning, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator internal linking 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 Internal Linking defines how the operator plans useful internal links between MWMS content assets.
Its purpose is to help decide:
which pages should link together
why those pages should link together
where links should be placed
what anchor text should be used
how the link supports the reader journey
how the link supports SEO structure
how the link supports topic clusters
how the link supports affiliate funnels
how the link supports trust and authority
how the link supports refresh and repurposing work
Internal linking is not just navigation.
It is a controlled system for reader movement, authority flow, topic connection, funnel support, and content discovery.
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 internal linking 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 internal links for:
SEO articles
authority articles
topic cluster pages
hub pages
pillar pages
spoke pages
affiliate support content
affiliate product content packs
affiliate funnel support content
pre-sell articles
comparison articles
review support content
FAQ content
objection-handling content
trust-building content
landing page support content
refresh work
repurposing work
content optimization
reader journey support
conversion support content
What This Page Does Not Control
This page does not control:
search demand validation
final SEO authority
affiliate offer approval
affiliate claim approval
conversion strategy approval
campaign approval
budget approval
test validation
final compliance approval
data interpretation
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 Rule
Internal links must help the reader first.
A link should exist because it creates a useful connection between pages.
Do not add internal links only because a keyword exists.
Do not force internal links into pages where they do not help the reader.
Do not use misleading anchor text.
Do not hide affiliate intent.
Do not create link patterns that make the site feel spammy, manipulative, or confusing.
Every meaningful internal link should support at least one of these:
reader journey
topic relationship
authority structure
SEO discovery
affiliate funnel education
trust building
conversion support
refresh improvement
repurposing usefulness
Internal Linking Principles
Internal links should be:
useful
relevant
contextual
natural
clear
reader-first
topic-aligned
funnel-aware
search-supportive
trust-supportive
easy to understand
safe around affiliate content
Internal links should not be:
forced
random
keyword-stuffed
misleading
over-optimized
irrelevant
hidden
manipulative
confusing
added only for SEO
Internal Link Types
Use the correct link type for the job.
Contextual Links
Links placed naturally inside body content.
Use these when one page directly helps explain, support, or expand another page.
Hub Links
Links from a main hub, pillar, or authority page to supporting pages.
Use these for topic clusters and structured content ecosystems.
Spoke Links
Links from supporting pages back to a hub or pillar page.
Use these to reinforce topic structure and reader navigation.
Funnel Links
Links that move the reader through an affiliate, sales, or decision journey.
Use these carefully and only when the next step is relevant.
Trust Links
Links to supporting trust pages, FAQ pages, evidence pages, explanation pages, or clarification pages.
Use these when readers may need confidence before taking the next step.
Refresh Links
Links added or improved during content refresh.
Use these when old content needs better connections to newer, stronger, or more relevant content.
Repurposing Links
Links added when approved content is adapted into another format.
Use these when a repurposed asset should send readers back to the original source, related article, support page, or funnel page.
Affiliate Support Links
Links that support affiliate education, pre-sell, comparison, objection handling, FAQ, or product support content.
Use these with extra care.
Affiliate-related internal links must be clear, honest, and relevant.
Internal Linking Checklist
Use this checklist when planning meaningful internal links.
1. Source Page
Field:
Source Page:
Operator instruction:
Record the page where the internal link will be placed.
If the source page is unclear, do not create the link yet.
2. Target Page
Field:
Target Page:
Operator instruction:
Record the page the link will point to.
The target page should be useful to the reader and relevant to the current context.
3. Link Purpose
Field:
Link Purpose:
Options:
Reader education
Topic expansion
Authority support
Hub and spoke support
Affiliate funnel support
Trust building
Comparison support
Objection handling
Pre-sell support
Refresh improvement
Repurposing support
Conversion support
Navigation support
Other
Operator instruction:
Choose the main reason the link exists.
If there is no clear reason, do not add the link.
4. Reader Journey Purpose
Field:
Reader Journey Purpose:
Operator instruction:
Explain how the link helps the reader.
Examples:
Helps the reader understand the next concept.
Moves the reader from problem awareness to solution awareness.
Supports a reader who wants more detail.
Helps the reader compare options.
Gives the reader a trust or FAQ page before taking action.
If the link does not help the reader, remove it.
5. Topic Relationship
Field:
Topic Relationship:
Options:
Directly related
Supporting topic
Parent topic
Child topic
Adjacent topic
Comparison topic
Trust support topic
Not related
Operator instruction:
Choose the relationship between the source and target pages.
Do not link unrelated pages just for SEO.
6. Funnel Relationship
Field:
Funnel Relationship:
Options:
Awareness to education
Education to trust
Trust to pre-sell
Pre-sell to product support
Comparison to decision support
Objection handling to FAQ
FAQ to next step
Follow-up to support content
Not funnel-related
Operator instruction:
If the link supports a funnel journey, identify the relationship.
Do not force funnel links into informational pages too early.
7. Link Type
Field:
Link Type:
Options:
Contextual
Hub link
Spoke link
Funnel link
Trust link
Refresh link
Repurposing link
Affiliate support link
Navigation link
Other
Operator instruction:
Choose the link type.
8. Anchor Text
Field:
Anchor Text:
Operator instruction:
Write the intended anchor text.
Anchor text should be:
clear
natural
specific
honest
useful to the reader
Avoid:
keyword stuffing
generic overuse
misleading promises
clickbait
over-optimized repetition
Example of weak anchor text:
Click here
Example of better anchor text:
how internal linking supports topic clusters
9. Anchor Text Risk
Field:
Anchor Text Risk:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record risk if the anchor text is affiliate-related, claim-related, conversion-heavy, or could mislead the reader.
If risk is medium, high, or unknown, review before use.
10. Placement
Field:
Placement:
Options:
Introduction
Early body section
Middle body section
Late body section
FAQ section
CTA section
Related reading section
Sidebar
Footer
Other
Operator instruction:
Record where the link should appear.
A link should appear where it naturally helps the reader.
11. Link Priority
Field:
Link Priority:
Options:
High
Medium
Low
Optional
Operator instruction:
Choose priority based on usefulness, SEO structure, funnel value, and reader benefit.
High priority links should be strongly relevant.
12. Internal Link Direction
Field:
Internal Link Direction:
Options:
Source to target only
Target back to source
Two-way link
Hub to spoke
Spoke to hub
Cluster cross-link
Funnel progression link
Operator instruction:
Decide whether the link should be one-way, two-way, or part of a broader cluster.
13. Affiliate Or Offer Connection
Field:
Affiliate Or Offer Connection:
Options:
Yes
No
Indirect
Unknown
Operator instruction:
Record whether the link supports an affiliate offer, product page, pre-sell content, comparison page, VSL support page, or affiliate content pack.
If yes or unknown, check claim and compliance risk.
14. Compliance Risk
Field:
Compliance Risk:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record risk level if the internal link points to sensitive claims, affiliate content, product claims, health topics, finance topics, income claims, legal claims, urgency, scarcity, or comparison content.
If risk is medium, high, or unknown, identify the review owner.
15. Required Review Owner
Field:
Required Review Owner:
Options:
Not required
Content Brain
Search Intelligence Brain
Research Brain
Affiliate Brain
Compliance Brain
Ads Brain
HeadOffice
Other
Unknown
Operator instruction:
Identify who should review the link if risk exists.
Do not approve risky links without the correct owner.
16. Internal Link Status
Field:
Internal Link Status:
Options:
Planned
Needs review
Approved
Added
Removed
Parked
Rejected
Operator instruction:
Keep status current.
17. Signal To Watch
Field:
Signal To Watch:
Options:
internal link clicks
scroll depth
time on page
page views
search impressions
search clicks
ranking movement
affiliate clicks
VSL clicks
conversion assist
manual feedback
Other
Operator instruction:
Record what signal should be watched after link placement.
Do not over-interpret weak signals.
Data Brain owns data quality.
Internal Linking Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Link helps reader and topic relationship is strong | Add link |
| Link helps SEO structure and reader journey | Add link |
| Link supports clear hub and spoke structure | Add link |
| Link supports affiliate funnel but risk is low | Add link carefully |
| Link supports affiliate funnel but claim risk exists | Needs review |
| Anchor text is forced or over-optimized | Rewrite anchor text |
| Target page is weak or outdated | Refresh target page first |
| Source page is weak or unclear | Improve source page first |
| Topic relationship is weak | Do not add link |
| Link is only for SEO and not useful to reader | Do not add link |
| Compliance risk is unknown | Park until reviewed |
| Destination page is not ready | Park link |
When To Add A Link
Add the link when:
the reader benefit is clear
the topic relationship is strong
the anchor text is natural
the destination page is useful
the link supports the page purpose
the link does not mislead
the link does not create unsupported claims
the link does not increase compliance risk without review
the link supports the wider content structure
When To Park A Link
Park the link when:
the target page is not ready
the source page is not ready
the topic relationship is weak
the anchor text is unclear
the affiliate connection is unclear
compliance risk is unknown
approval owner is unclear
the link may change the meaning of the content
the link belongs to another Brain decision
Parked does not mean rejected.
It means missing information must be resolved first.
When To Remove Or Avoid A Link
Remove or avoid the link when:
it does not help the reader
it is irrelevant
it is forced
it misleads the reader
it over-optimizes anchor text
it points to weak or outdated content
it creates claim risk
it hides affiliate intent
it confuses the funnel journey
it makes the page feel spammy
it only exists for SEO manipulation
Topic Cluster Linking
Use internal links to support topic clusters.
A topic cluster should usually include:
one hub or pillar page
supporting spoke pages
related FAQ content
comparison content where relevant
trust-building content where relevant
affiliate support content where relevant
refresh links where relevant
The hub should link to important supporting pages.
Supporting pages should link back to the hub where useful.
Related supporting pages may cross-link when the relationship helps the reader.
Do not over-link every page to every other page.
Affiliate Internal Linking
Affiliate internal links require extra care.
Affiliate internal links may connect:
problem-aware article to solution-aware article
solution-aware article to pre-sell content
pre-sell content to product support page
comparison article to FAQ page
FAQ page to trust page
objection-handling content to product education
YouTube support content to article or VSL support page
email support content to product education
Affiliate links should not create false certainty.
They should support education, clarity, trust, and reader fit.
Refresh-Based Internal Linking
During refresh work, review internal links.
Ask:
Are there better newer pages to link to?
Are old links still relevant?
Are target pages still accurate?
Are anchors still natural?
Are important pages orphaned?
Are affiliate links still safe?
Are trust pages linked where needed?
Are internal links supporting the current search intent?
Refresh work should improve structure, not just update words.
Repurposing-Based Internal Linking
When approved content is repurposed, consider internal links.
Ask:
Should the repurposed asset link back to the original article?
Should the original article link to the repurposed asset?
Should email or social content point to a support page?
Should YouTube descriptions link to a relevant article?
Should FAQ content link to a deeper guide?
Repurposing links should preserve meaning and avoid claim drift.
Internal Link Quality Guardrails
Good internal links are:
clear
natural
useful
relevant
contextual
reader-friendly
topic-aligned
safe around claims
aligned with content purpose
Bad internal links are:
forced
irrelevant
misleading
spammy
over-optimized
too frequent
too commercial too early
unrelated to reader intent
used to hide affiliate intent
used to manipulate without adding value
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 creating 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 SEO Content Briefs for search-focused content 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:
Internal Linking Planner
Topic Cluster Planner
SEO Brief Generator
Content Brief Generator
Publishing Readiness Checklist UI
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 Internal Linking Strategy Framework
After Content Brain Internal Linking is created and checked, the older Content Brain Internal Linking Strategy Framework page should be handled as follows:
If it is only a duplicate operational internal linking 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 internal linking pages.
The active operator internal linking page should be:
Content Brain Internal Linking
Drift Protection
The system must prevent:
internal links being added without reader benefit
internal links being added only for SEO manipulation
anchor text becoming keyword-stuffed
affiliate links being hidden or unclear
internal links creating unsupported claims
outdated pages receiving important links without refresh
topic clusters becoming messy
hub and spoke structures becoming unclear
orphan pages being ignored
links being added without clear purpose
old internal linking framework pages being treated as the current operator internal linking page after this clean page is created
future UI being built before manual internal linking use proves need
Content Brain taking authority from Search Intelligence Brain, Research Brain, Affiliate Brain, Ads Brain, Experimentation Brain, Conversion Brain, Compliance Brain, Finance Brain, Data Brain, SIT Brain, or HeadOffice
Architectural Intent
Content Brain Internal Linking exists to make internal linking structured, useful, and governed.
Its role is to connect content assets in a way that supports readers, SEO structure, affiliate funnels, trust, authority, and long-term content maintenance.
Internal linking should help MWMS create:
clearer reader journeys
stronger topic clusters
better authority flow
better content discovery
better affiliate education paths
stronger refresh outcomes
better repurposing pathways
reduced orphan page risk
cleaner site structure
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 internal link should be added unless it helps the reader, supports the content purpose, and connects relevant pages.
Internal links must not be forced, misleading, or added only for SEO.
When in doubt, park the link 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 internal linking page for mwmscontentbrain.site based on MCR Content Brain Internal Linking Strategy Operational Copy direction and the existing Content Brain Internal Linking Strategy Framework. Defines the live Content Brain Internal Linking page for the first operational Content Brain layer, including link types, internal linking checklist, decision table, add rules, park rules, avoid rules, topic cluster linking, affiliate internal linking, refresh-based linking, repurposing-based linking, 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 Internal Linking
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Internal Linking Strategy Framework
Pages Deprecated:
Content Brain Internal Linking Strategy Framework as active operator internal linking page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN INTERNAL LINKING v1.0