Brain Name: Content Brain
Document Type: Operational Refresh Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain refresh work, SEO content refresh, content improvement, search intent review, research update review, claim review, internal linking updates, affiliate content refresh, product support content refresh, comparison content refresh, FAQ refresh, trust content refresh, pre-sell content refresh, repurposing review, merge review, redirect review, retirement review, content testing discipline, refresh signal feedback, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator refresh 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 Refresh defines how the operator reviews, improves, refreshes, merges, redirects, retires, or parks existing content.
Its purpose is to stop content from becoming outdated, weak, disconnected, inaccurate, thin, poorly linked, or misaligned with current search intent and business priorities.
Content refresh should improve:
usefulness
accuracy
structure
search intent alignment
research quality
trust
claim safety
internal linking
affiliate support
reader experience
conversion support
repurposing potential
signal feedback
Refresh work must not become random rewriting.
A page should not be refreshed just because it is old.
A refresh should happen because there is a clear reason and a useful improvement path.
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 refresh 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 reviewing or improving existing content.
Use it for:
SEO article refresh
authority content refresh
topic cluster content refresh
affiliate support content refresh
affiliate product content refresh
comparison content refresh
review support content refresh
pre-sell content refresh
FAQ content refresh
objection-handling content refresh
trust content refresh
AIBS education content refresh
internal linking updates
research update review
claim review
search intent review
content quality review
content consolidation
merge review
redirect review
retirement review
repurposing review
performance-based content review
What This Page Does Not Control
This page does not control:
technical SEO implementation
redirect implementation
sitewide architecture changes
new topic selection by itself
campaign execution
paid traffic testing
capital allocation
final compliance approval
formal statistical testing by itself
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
Do not refresh content just because it is old.
Refresh content when there is a clear reason and a useful improvement path.
A refresh should be triggered by at least one of these:
search intent changed
content is outdated
research has changed
offer or product details changed
claims need review
content quality is weak
internal links are missing or outdated
performance has dropped
content is thin
content is duplicated
content is no longer useful
reader questions are unanswered
trust signals are weak
affiliate support is outdated
comparison logic is outdated
funnel role has changed
repurposing opportunity exists
A refresh should produce either:
a stronger content asset
a clearer content decision
a useful system learning signal
Refresh Principles
Refresh work should be:
purposeful
evidence-informed
reader-focused
search-aligned
claim-safe
internally linked
measurable where possible
recorded
reviewable
connected to the correct Brain
Refresh work should not be:
random
cosmetic only
guess-based
unsupported
claim-heavy
keyword-stuffed
performed without a trigger
performed without an approval owner
performed without a destination or next step
Refresh Versus Rewrite
A refresh improves an existing asset while preserving its core purpose.
A rewrite substantially changes the content, positioning, structure, or message.
Use refresh when:
the topic is still useful
the page still has a role
the search intent is mostly the same
the page needs improvement
the content needs updating
the internal links need strengthening
the claims need review
Use rewrite when:
the page no longer matches intent
the content is structurally weak
the message is outdated
the audience has changed
the page cannot be fixed with targeted improvements
Use merge, redirect, retire, or park when the page no longer deserves standalone treatment.
Refresh Checklist
Use this checklist before refreshing existing content.
1. Page Or Asset Name
Field:
Page Or Asset Name:
Operator instruction:
Record the page, article, support asset, email, YouTube description, FAQ, comparison, or other content asset being reviewed.
2. Current URL Or Location
Field:
Current URL Or Location:
Operator instruction:
Record where the asset currently lives.
Examples:
WordPress URL
draft location
Google Doc
YouTube description
email file
internal page
If the location is unclear, park the refresh.
3. Source Brain
Field:
Source Brain:
Options:
Content Brain
Search Intelligence Brain
Research Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Conversion Brain
Sales Brain
AIBS Brain
Data Brain
HeadOffice
Manual Operator Observation
Other
Operator instruction:
Record where the refresh request or signal came from.
If source Brain is unclear, park the request.
4. Supporting Brains
Field:
Supporting Brains:
Operator instruction:
Record any Brains supplying support.
Examples:
Search Intelligence Brain for intent or SERP change
Research Brain for updated evidence
Affiliate Brain for offer status
Compliance Brain for claim risk
Data Brain for performance signal
Ads Brain for campaign support context
Conversion Brain for funnel role
HeadOffice for priority
If none, write:
Not applicable
5. Refresh Trigger
Field:
Refresh Trigger:
Options:
Outdated information
Search intent changed
Performance declined
Research update
Offer changed
Product changed
Claim risk
Compliance risk
Internal linking gap
Thin content
Poor structure
Weak trust signals
Missing FAQ
Missing comparison support
Weak affiliate support
Repurposing opportunity
Merge opportunity
Redirect review
Retirement review
Manual quality concern
Other
Operator instruction:
Choose the reason the asset is being reviewed.
If there is no clear trigger, do not start refresh work yet.
6. Source Signal
Field:
Source Signal:
Operator instruction:
Record the signal that triggered the refresh.
Examples:
ranking drop
search impressions drop
clicks dropped
manual review
new research
offer update
affiliate issue
compliance concern
customer question
SERP change
internal link gap
thin content observation
Data Brain signal
HeadOffice priority
If no signal exists, write:
No clear signal — refresh not ready.
7. Current Content Purpose
Field:
Current Content Purpose:
Operator instruction:
Describe what the content currently appears to be for.
Examples:
educate problem-aware readers
support an affiliate funnel
answer a search query
build authority
support internal linking
handle objections
prepare reader for VSL
If the purpose is unclear, the asset may need rewrite, merge, or retirement.
8. Desired Content Purpose
Field:
Desired Content Purpose:
Operator instruction:
Describe what the content should do after refresh.
If the desired purpose is different from the current purpose, this may be a rewrite rather than a refresh.
9. Current Audience
Field:
Current Audience:
Operator instruction:
Record who the asset appears to serve now.
Include:
audience type
awareness stage
pain point
desired outcome
market or location if relevant
knowledge level
10. Audience Fit Review
Field:
Audience Fit Review:
Options:
Still fits
Mostly fits
Needs adjustment
Wrong audience
Unknown
Operator instruction:
Confirm whether the content still matches the intended audience.
If audience fit is poor, decide whether to rewrite, merge, or retire.
11. Search Intent Review
Field:
Search Intent Review:
Options:
Still aligned
Partly aligned
No longer aligned
Needs Search Intelligence Brain review
Not SEO content
Operator instruction:
For SEO content, review whether the content still matches search intent.
Check:
query intent
SERP pattern
reader expectation
top-ranking page types
common questions
content format
depth required
If search intent has changed, update the brief or route to Search Intelligence Brain.
12. SERP Review Needed
Field:
SERP Review Needed:
Options:
Yes
No
Maybe
Not applicable
Operator instruction:
Use SERP review when organic search visibility matters.
If yes, identify whether Search Intelligence Brain or manual review is needed.
13. Research Update Needed
Field:
Research Update Needed:
Options:
Yes
No
Maybe
Unknown
Operator instruction:
Identify whether the content needs updated evidence, examples, data, sources, product notes, market intelligence, or audience language.
If research is missing, route to Research Brain.
14. Research Basis
Field:
Research Basis:
Operator instruction:
Record the research, source material, Brain notes, SERP observations, performance data, or evidence supporting the refresh.
If missing, write:
Research basis missing — refresh not ready for public update.
15. Offer Or Product Status
Field:
Offer Or Product Status:
Options:
Approved
Review-ready
Research needed
Testing candidate
Changed
Rejected
Not applicable
Unknown
Operator instruction:
For affiliate content, confirm whether the related offer or product is still valid.
If offer status is unclear, route to Affiliate Brain or Research Brain.
16. Claim Review
Field:
Claim Review:
Options:
Claims still safe
Claims need review
Claims outdated
Claims too strong
Claims unsupported
No claims
Unknown
Operator instruction:
Check whether the content includes claims that need review.
Watch for:
health claims
income claims
legal claims
product performance claims
guarantees
scarcity
urgency
testimonials
comparisons
unsupported claims
If claim risk exists, route to Compliance Brain or the required approval owner.
17. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims that must not be added, repeated, strengthened, or reintroduced.
Do not leave this blank for affiliate, health, finance, legal, income, product, or compliance-sensitive content.
18. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the risk level.
If risk is medium, high, or unknown, identify the review owner before use.
19. 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 refresh involves sensitive claims, product claims, affiliate content, health, finance, income, legal, urgency, scarcity, testimonials, or comparisons, identify the required review owner.
Do not mark refresh complete if review ownership is unclear.
20. Content Quality Review
Field:
Content Quality Review:
Options:
Strong
Acceptable
Needs improvement
Thin
Generic
Weak
Operator instruction:
Review whether the content is useful, specific, clear, current, and worth keeping.
Watch for:
generic AI language
thin explanations
missing examples
weak structure
no clear answer
outdated sections
missing FAQs
weak trust support
poor reader journey
21. Information Gain Review
Field:
Information Gain Review:
Options:
Strong
Acceptable
Weak
Missing
Not applicable
Operator instruction:
For SEO and authority content, check whether the page adds something useful beyond generic content.
If information gain is weak, identify what can be improved.
22. Structure Review
Field:
Structure Review:
Options:
Strong
Acceptable
Needs improvement
Weak
Operator instruction:
Check:
title
introduction
section flow
headings
FAQ section
comparison section if relevant
trust section if relevant
CTA or next step
internal link placement
reader journey
If structure is weak, refresh should include structural improvement.
23. Internal Link Review
Field:
Internal Link Review:
Options:
Complete
Needs internal links
Links outdated
Links risky
Not applicable
Operator instruction:
Review whether internal links should be added, changed, removed, or updated.
Use Content Brain Internal Linking for meaningful linking plans.
Check:
orphan page risk
hub links
spoke links
topic cluster links
affiliate support links
trust page links
refresh links
repurposing links
24. External Reference Review
Field:
External Reference Review:
Options:
Complete
Needs sources
Sources outdated
Sources risky
Not applicable
Operator instruction:
Review whether external sources, references, examples, or citations need updating.
Do not invent sources.
25. CTA Review
Field:
CTA Review:
Options:
Still fits
Needs update
Wrong CTA
No CTA needed
Unknown
Operator instruction:
Check whether the CTA still fits the audience, funnel stage, offer status, and content purpose.
Do not force a commercial CTA where it does not fit.
26. Refresh Action Needed
Field:
Refresh Action Needed:
Options:
Update
Expand
Rewrite
Merge
Redirect
Retire
Park
Repurpose
Monitor
No action
Operator instruction:
Choose the main action.
Use the decision table below if unsure.
Refresh Decision Table
| Situation | Decision |
|---|---|
| Content is still useful but outdated | Update |
| Content is useful but thin | Expand |
| Content no longer matches intent | Rewrite or merge |
| Content overlaps stronger page | Merge |
| Content has no standalone value | Retire or redirect |
| Content has traffic but poor usefulness | Refresh carefully |
| Content has claim risk | Needs compliance review |
| Offer status unclear | Park / send to Affiliate Brain |
| Research basis missing | Needs Research Brain review |
| Search intent unclear | Needs Search Intelligence Brain review |
| Internal links are weak | Add or update links |
| Content has strong reuse potential | Repurpose |
| Content belongs to another Brain | Route back |
| No clear trigger exists | Monitor or park |
27. Update Plan
Field:
Update Plan:
Operator instruction:
List exactly what should be changed.
Examples:
update intro
add FAQ section
replace outdated statistics
add trust section
remove unsupported claim
add internal links
improve headings
expand comparison section
merge with related page
rewrite CTA
remove outdated offer mention
Do not begin refresh work without a clear update plan.
28. Sections To Keep
Field:
Sections To Keep:
Operator instruction:
List sections that still work and should be preserved.
29. Sections To Change
Field:
Sections To Change:
Operator instruction:
List sections that need editing, expansion, removal, rewriting, or review.
30. Sections To Remove
Field:
Sections To Remove:
Operator instruction:
List sections that should be removed because they are outdated, unsupported, irrelevant, weak, risky, duplicated, or no longer useful.
31. Merge Review
Field:
Merge Review:
Options:
Merge needed
No merge needed
Maybe
Unknown
Operator instruction:
Use merge review when the content overlaps another stronger or similar page.
If merge is needed, identify the stronger target page.
32. Redirect Review
Field:
Redirect Review:
Options:
Redirect needed
No redirect needed
Maybe
Unknown
Operator instruction:
Use redirect review when a page is retired, merged, or no longer useful as a standalone page.
Technical redirect implementation is not handled by this page.
33. Retirement Review
Field:
Retirement Review:
Options:
Retire
Keep
Maybe
Unknown
Operator instruction:
Use retirement review when the content has no clear purpose, no value, no traffic, no internal link role, and no strategic use.
Do not retire content without checking whether it has internal linking, authority, affiliate, or historical value.
34. Repurposing Review
Field:
Repurposing Review:
Options:
Repurpose
No repurposing needed
Maybe later
Unknown
Operator instruction:
Identify whether the refreshed content can become email, social, YouTube support, FAQ support, VEO3 pre-video support, affiliate follow-up, or sales support.
Use Content Brain Repurposing where meaningful.
35. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the refresh before use.
Examples:
HeadOffice
Content Brain
Search Intelligence Brain
Research Brain
Affiliate Brain
Compliance Brain
Ads Brain
Experimentation Brain
Finance Brain
Data Brain
Martyn
Other
If approval owner is missing, do not mark refresh complete.
36. 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 refreshed asset goes next.
If destination is unclear, park the refresh.
37. Signal To Watch
Field:
Signal To Watch:
Options:
search impressions
search clicks
ranking movement
page views
time on page
scroll depth
internal link clicks
affiliate clicks
VSL clicks
email clicks
YouTube views
conversion assist
manual feedback
Other
Operator instruction:
Record what signal should be watched after the refresh.
Do not over-interpret weak signals.
Data Brain owns data quality.
38. Review Date
Field:
Review Date:
Operator instruction:
Set a future review date or review trigger.
Examples:
review after 30 days
review after 60 days
review after first ranking movement
review after first 100 clicks
review after campaign test
review after offer update
39. Refresh Status
Field:
Refresh Status:
Options:
Draft
Needs research
Needs SERP review
Needs compliance review
Needs approval owner
Ready for update
In update
In review
Ready for handoff
Handed off
Published
Monitoring
Parked
Closed
Rejected
Operator instruction:
Keep status current.
Do not mark refresh complete if trigger, research, claim risk, approval owner, or handoff destination is unclear.
Refresh Testing Discipline
Most SEO optimisations are hypotheses.
A content change is not automatically an improvement.
Meaningful refresh work should have:
a baseline where available
a reason for the change
a change record
a review point
a signal to watch
a learning outcome
Do not assume the refresh worked just because the page was changed.
Baseline Before Refresh
Where possible, record baseline data before major refresh work.
Possible baseline signals include:
current rankings
search impressions
search clicks
page views
time on page
scroll depth
affiliate clicks
VSL clicks
internal link clicks
conversion assist
manual feedback
Baseline data may be incomplete.
Do not delay every small refresh because perfect data is unavailable.
But for important pages, record what is available.
Change Record
For meaningful refresh work, record what changed.
Examples:
updated title
changed heading structure
added FAQ section
expanded thin section
added trust section
removed unsupported claim
updated offer details
added internal links
removed outdated content
merged duplicate page
changed CTA
rewrote introduction
A change record helps future review.
Learning Review
After refresh, review what happened.
Possible outcomes:
improved
declined
no clear change
too early to tell
measurement unclear
needs second refresh
needs merge
needs retirement
needs repurposing
Data Brain owns signal reliability.
Content Brain can record observations but should not over-interpret weak data.
When To Mark Refresh Ready
Mark refresh ready only when:
refresh trigger is clear
source Brain is clear
content purpose is clear
search intent has been reviewed where relevant
research basis is recorded
claim risk has been checked
content quality issue is understood
refresh action is selected
update plan is clear
approval owner is known
handoff destination is clear
signal to watch is defined
If any major item is missing, do not mark ready.
When To Park Refresh
Park the refresh when:
trigger is unclear
content purpose is unclear
search intent is unclear
research basis is missing
offer status is unclear
claim risk is unclear
compliance sensitivity is unknown
approval owner is missing
handoff destination is unclear
the page may need technical SEO review
the request belongs to another Brain
Parked does not mean rejected.
It means missing information must be resolved before work moves forward.
Refresh Quality Guardrails
Good refresh work should:
improve usefulness
improve accuracy
improve clarity
improve structure
update outdated information
add missing context
strengthen trust safely
improve internal links
align with current intent
remove unsupported claims
record the change
define the next review signal
Bad refresh work:
rewrites randomly
adds fluff
adds unsupported claims
changes meaning without approval
over-optimizes keywords
removes useful context
ignores intent
ignores internal links
ignores claim risk
has no update plan
has no review signal
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 Internal Linking for page connection planning
Content Brain Repurposing for adapting approved content
Future Plugin Or UI Candidates
This page may later support:
Content Refresh Queue
SEO Refresh Planner
Content Operations Dashboard
Content Signal Feedback Dashboard
Internal Linking Planner
Repurposing Planner
Publishing Readiness Checklist UI
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 Testing And Refresh Framework
After Content Brain Refresh is created and checked, the older Content Brain SEO Testing And Refresh Framework page should be handled as follows:
If it is only a duplicate operational refresh 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 refresh pages.
The active operator refresh page should be:
Content Brain Refresh
Drift Protection
The system must prevent:
refreshing content without a clear trigger
random rewriting
refreshing just because content is old
adding unsupported claims during refresh
changing meaning without approval
ignoring current search intent
ignoring research updates
ignoring internal links
ignoring claim risk
ignoring offer status
merging pages without review
retiring pages without checking value
redirect decisions being treated as handled by Content Brain alone
old SEO testing and refresh framework pages being treated as the current operator refresh page after this clean page is created
future UI being built before manual refresh 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 Refresh exists to make content improvement structured, useful, and governable.
Its role is to turn existing content into better assets or clearer decisions.
Refresh work should help MWMS:
prevent content decay
improve search usefulness
recover weak pages
update outdated information
remove risky claims
strengthen internal links
improve affiliate support
improve trust
capture learning from content changes
decide when to merge, redirect, retire, repurpose, or monitor content
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 content should be refreshed without a clear trigger, clear improvement path, known risk level, approval owner, and signal to watch.
Refresh should improve usefulness, accuracy, trust, structure, and system alignment.
When in doubt, park the refresh 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 refresh page for mwmscontentbrain.site based on MCR Content Brain SEO Refresh Operational Copy and the existing Content Brain SEO Testing And Refresh Framework. Defines the live Content Brain Refresh page for the first operational Content Brain layer, including refresh triggers, source signals, search intent review, research update review, offer status review, claim review, compliance sensitivity, content quality review, information gain review, structure review, internal link review, refresh action decisions, update planning, merge review, redirect review, retirement review, repurposing review, approval ownership, handoff destination, signal tracking, refresh testing discipline, baseline recording, change records, learning review, ready rules, parking rules, 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 Refresh
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain SEO Testing And Refresh Framework
Pages Deprecated:
Content Brain SEO Testing And Refresh Framework as active operator refresh page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN REFRESH v1.0