Brain Name: Content Brain
Document Type: Framework
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain, Data Brain, Experimentation Brain, future Search Intelligence Brain, mwmscontentbrain.site operational SEO refresh work, content improvement planning, and future content refresh queue planning
Parent: Content Brain
Last Reviewed: 2026-05-08
Content Brain SEO Testing And Refresh Framework
Operational Copy Notice
This page is an operational copy used on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR version, the MCR version overrides it.
This protects source-of-truth discipline.
Purpose
The Content Brain SEO Testing And Refresh Framework defines how MWMS improves existing content through structured SEO testing, content refreshes, and performance review.
The purpose is to:
prevent content decay
improve rankings
recover lost traffic
validate SEO changes
create repeatable content improvement loops
increase content usefulness
improve content trust
strengthen internal linking
capture learning from refresh work
SEO improvement must be treated as testing, not guessing.
Content should not be changed randomly simply because it is old, underperforming, or visually outdated.
Every meaningful SEO refresh should have a reason, a baseline, a hypothesis, a change record, and a review point.
Scope
This framework applies to:
existing SEO articles
authority articles
topic cluster pages
hub pages
spoke pages
affiliate support pages
comparison pages
review support pages
pre-sell content
trust support content
landing support content
content refresh work
SEO content testing
internal linking updates
title and heading changes
content expansion work
content consolidation work
This framework governs:
SEO refresh logic
testing discipline
baseline measurement
SERP reanalysis
content improvement briefs
performance review
refresh learning capture
content decay response
This framework does not govern:
new topic selection by itself
campaign execution
paid traffic tests
formal statistical testing by itself
capital allocation
final compliance approval
plugin implementation
Supabase implementation
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
Most SEO optimisations are hypotheses.
A content change is not automatically an improvement.
It must be:
measured
compared
reviewed
learned from
SEO refresh work should not be treated as casual editing.
A refresh should produce both:
an improved content asset
a learning signal for the system
Definition
SEO Test
An SEO test is a structured change made to improve organic performance.
Examples:
title update
heading update
content depth change
FAQ addition
internal linking change
trust section addition
entity coverage improvement
information gain improvement
CTA adjustment
Content Refresh
A content refresh is an update to an existing page designed to improve:
relevance
quality
rankings
traffic
engagement
trust
conversions
internal linking strength
content usefulness
All content refreshes are SEO tests.
Not all SEO tests are content refreshes.
When To Run A Content Refresh
Refresh content when:
rankings decline
traffic drops
content becomes outdated
competitors improve
SERP intent changes
page is stuck below desired ranking
conversion performance weakens
content is thin
trust signals are weak
internal links are missing
information gain is weak
reader questions are unanswered
Refresh Opportunity Signals
Data Brain should identify pages with:
ranking decay
traffic decay
high impressions but low CTR
high ranking potential
high conversion value
outdated information
weak engagement
high bounce or early exits
low internal link movement
old content that supports active revenue pathways
manual review may also identify refresh opportunities where data is incomplete.
SEO Refresh Process
Step 1: Identify Candidate Page
Select page based on:
traffic value
ranking opportunity
conversion importance
content decay
strategic importance
topic cluster role
affiliate support role
trust importance
A page should not be refreshed only because it exists.
It should have a clear reason for review.
Step 2: Benchmark Current Performance
Record baseline before making changes.
Baseline may include:
current rankings
traffic over last 90 days
impressions
click-through rate
conversions
engagement signals
scroll depth
internal link clicks
conversion assist
current content structure
current publish or update date
If baseline data is unavailable, mark the limitation clearly.
Do not pretend a refresh is a measurable test if no baseline exists.
Step 3: Re Run SERP Analysis
Before changing the page, review:
current top-ranking pages
SERP intent
content formats
featured snippets
People Also Ask
competitor updates
content depth expectations
trust signals
entity coverage
information gaps
SERP changes should inform the refresh plan.
Do not patch old content without understanding the current search environment.
Step 4: Build New Content Brief
Do not only patch old content.
Create a fresh refresh brief using:
SERP analysis
information gain plan
entity coverage
internal linking plan
E E A T improvements
reader intent
trust gaps
conversion support needs
current weakness
refresh hypothesis
The Content Brain SEO Content Brief Standard and Content Brain Content Brief Template should guide this step.
Step 5: Update And Publish
Refresh may include updates to:
title
meta description
headings
outdated sections
missing sections
examples
citations
media
internal links
CTA
FAQ section
comparison section
proof section
trust section
entity coverage
information gain
After publishing, resubmit the URL in Google Search Console where appropriate.
Record the update date.
Step 6: Measure Result
Wait a reasonable review window.
Typical review window:
4 to 13 weeks
Compare against baseline:
rankings
traffic
impressions
CTR
conversions
engagement
internal link clicks
conversion assist
Do not judge too early.
SEO changes often need time.
Step 7: Record Learning
Document:
what changed
why it changed
what improved
what declined
what stayed neutral
what signal was unclear
what should be tested next
what should be reused elsewhere
what should be avoided next time
Learning capture is mandatory for meaningful refresh work.
If learning is not recorded, the system does not improve.
Testing Types
MWMS may use:
time based tests
title tag tests
heading tests
content depth tests
CTA tests
internal linking tests
structure tests
FAQ tests
trust section tests
information gain tests
entity coverage tests
refresh versus no refresh comparisons where available
Testing should remain proportional to the importance of the page.
Not every minor update requires heavy experiment structure.
Measurement Metrics
Track where available:
keyword rankings
impressions
clicks
CTR
organic traffic
conversions
engagement
assisted value
scroll depth
internal link clicks
topic cluster movement
conversion support behaviour
content decay recovery
Measurement must be interpreted carefully.
A single metric rarely tells the full story.
Data Brain Integration
Data Brain owns:
baseline measurement
performance tracking
decay detection
reporting
signal reliability interpretation
measurement limitations
Content Brain may use Data Brain signals, but must not over-interpret weak or incomplete data.
Experimentation Brain Integration
Experimentation Brain owns:
hypothesis structure
test interpretation
learning loop discipline
decision discipline
formal experiment logic where required
If SEO testing becomes formal or high-stakes, Experimentation Brain should govern test structure and interpretation.
Content Brain Integration
Content Brain owns:
content refresh execution
brief update
content quality improvement
internal linking updates
trust improvement
information gain improvement
content structure improvement
Content Brain must keep refresh work aligned with the wider Content Brain Workflow Map.
Search Intelligence Brain Future Integration
A future Search Intelligence Brain may later support:
query movement analysis
SERP monitoring
entity gap detection
content decay alerts
keyword clustering
refresh prioritisation
Until that exists, Content Brain, Data Brain, and Research Brain should work within current boundaries.
Refresh Hypothesis Template
Hypothesis:
If we update:
[page element]
Because:
[reason]
Then we expect:
[measurable outcome]
Measured by:
[metric]
Review date:
[date]
Example:
Hypothesis:
If we add an FAQ section and strengthen internal links
Because:
the page has impressions but low engagement and weak section depth
Then we expect:
better engagement and improved query coverage
Measured by:
scroll depth, impressions, CTR, and ranking movement
Review date:
8 weeks after publication
Refresh Record Template
Page Title:
URL:
Refresh Owner:
Date Refreshed:
Reason For Refresh:
Baseline Data:
SERP Findings:
Hypothesis:
Changes Made:
Internal Links Added:
Trust Improvements Added:
Information Gain Added:
Review Window:
Review Date:
Result:
Learning Captured:
Next Action:
Refresh Decision Options
After review, assign one decision:
No Further Action
Minor Follow Up Edit
Second Refresh Needed
Improve Internal Links
Add Trust Section
Add FAQ Section
Add Comparison Section
Improve Entity Coverage
Improve CTA Alignment
Merge With Another Page
Split Into Multiple Pages
Repurpose
Retire
Escalate To Data Brain
Escalate To Experimentation Brain
Escalate To HeadOffice
Each decision should have a clear reason.
Failure Modes Prevented
This framework prevents:
random content updates
unmeasured SEO changes
stale content decay
duplicate refresh work
weak ranking recovery
no learning capture
refresh work without SERP review
refresh work without baseline data
refresh work without hypothesis
content changes that damage trust
content changes that create cannibalisation
Relationship To Content Brain SEO Content Brief Standard
The SEO Content Brief Standard defines how SEO briefs should be structured.
This framework uses the SEO brief process when refreshing important content.
A refresh should often begin with a new or updated brief.
Relationship To Content Brain Information Gain Framework
The Information Gain Framework defines how content adds value beyond existing results.
Refresh work should improve information gain where a page is weak, stale, shallow, or repetitive.
Relationship To Content Brain Topic Cluster And Hub Architecture Framework
The Topic Cluster And Hub Architecture Framework defines how pages connect.
SEO refresh work should review whether the page still fits its cluster, hub, spoke role, and internal linking pathway.
Relationship To Content Brain Internal Linking Strategy Framework
Internal linking is often one of the safest refresh improvements.
Refresh work should review:
links into the page
links out of the page
hub and spoke relationships
anchor text
reader journey
Relationship To Content Brain E E A T Content Trust Framework
Refresh work should improve trust where needed.
This may include:
updated sources
better limitations
clearer author or source signals
stronger proof
safer claims
transparent disclosures
Relationship To Content Brain Content Optimization Framework
Content Optimization defines broader signal-informed improvement.
This framework defines the SEO testing and refresh subset of that improvement process.
Relationship To Content Brain Copy Map
The Content Brain Copy Map classifies this page as:
Destination: Copy To Content Brain
Reason: Content refresh workflow
Source Of Truth: MCR
Future Destination: mwmscontentbrain.site
Future Use: Content refresh workflow
Plugin Or UI Later: Future content refresh queue
This operational copy follows that classification.
Future Plugin Or UI Candidate
This framework may later support:
Content Refresh Queue
SEO Refresh Checklist
Refresh Hypothesis Form
Content Review Screen
Content Operations Dashboard
Content Signal Feedback Dashboard
Internal Linking Planner
These should not be built yet.
Manual SEO refresh workflow must prove operational need before plugin or UI development begins.
Drift Protection
The system must prevent:
refreshing without baseline data
changing pages without hypothesis
measuring too early
ignoring SERP changes
updating without information gain
failing to record results
refreshing content randomly
treating editing as testing
creating duplicate content during refresh
plugin or UI refresh tools being built before manual use proves the structure
mwmscontentbrain.site replacing MCR source-of-truth authority
Architectural Role
This framework acts as the content improvement loop of MWMS.
It ensures content does not remain static.
It keeps content:
current
competitive
measurable
improving
learning-producing
Architectural Intent
This framework ensures MWMS treats SEO as an ongoing improvement system.
It transforms content from:
publish and hope
into:
test, measure, learn, improve
The long-term intent is for refresh work to become a repeatable Content Brain operating function.
Manual refresh workflow must be proven before future refresh queues, dashboards, or automated alerts are built.
Final Rule
If performance is not measured, the refresh is not a test.
If learning is not recorded, the system does not improve.
If no hypothesis exists, the change is only an edit.
Content refresh must improve the page and teach the system.
Change Log
Version: v1.1
Date: 2026-05-08
Author: HeadOffice
Change: Created operational copy for mwmscontentbrain.site. Added Operational Copy Notice, Source Of Truth protection, Parent update for live site, expanded refresh process, added Search Intelligence Brain future integration, refresh record template, refresh decision options, cross-framework relationships, future plugin or UI boundaries, and drift protection against mwmscontentbrain.site replacing MCR authority.
Version: v1.0
Date: 2026-05-02
Author: Content Brain
Change: Created SEO Testing And Refresh Framework to define structured content refresh testing, baseline measurement, SERP reanalysis, and performance review loops.
Change Impact Declaration
Pages Created:
Content Brain SEO Testing And Refresh Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN SEO TESTING AND REFRESH FRAMEWORK v1.1