Document Type: Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Data Brain, Experimentation Brain, Affiliate Brain
Parent: Content Brain
Last Reviewed: 2026-04-26
Purpose
The Content Brain SEO Testing And Refresh Framework defines how MWMS continuously improves content performance through structured testing and controlled updates.
Content is not static.
Content must evolve based on:
- performance data
- user behaviour
- search competition
- algorithm changes
This framework ensures content is:
- monitored
- tested
- improved
- revalidated
Core Principle
Content must be treated as a testable asset.
If content is not tested:
→ performance stagnates
Definition
Content Testing:
The process of making controlled changes to content and measuring performance impact.
Content Refresh:
Updating existing content to improve performance, accuracy, and relevance.
Role Within MWMS
This framework supports:
- Content Brain optimisation
- Data Brain measurement
- Experimentation Brain validation
- Affiliate Brain performance improvement
It directly influences:
- rankings
- traffic
- engagement
- conversion rates
Testing Objective
Every test must answer:
“What change improves performance?”
Content Baseline Rule
Before testing, baseline performance must be recorded.
Metrics include:
- rankings
- impressions
- clicks
- CTR
- time on page
- bounce rate
- conversions
Without baseline:
→ results cannot be measured
Test Types
Content can be tested through:
- Title Testing
Change headline or title.
Impacts:
- CTR
- rankings
- Structure Testing
Change layout or sections.
Impacts:
- engagement
- clarity
- Depth Testing
Add or reduce content.
Impacts:
- rankings
- dwell time
- Information Gain Testing
Add new insights.
Impacts:
- differentiation
- ranking improvement
- CTA Testing
Change calls to action.
Impacts:
- conversion rate
- Internal Linking Testing
Adjust link structure.
Impacts:
- authority flow
- rankings
Test Isolation Rule
Each test must change:
→ one major variable
Multiple changes:
→ reduce clarity
Test Duration Rule
Tests must run long enough to:
- stabilise performance
- reduce noise
- gather meaningful data
Stopping early creates false conclusions.
Refresh Trigger Rule
Content should be refreshed when:
- rankings drop
- traffic declines
- competitors improve
- content becomes outdated
- new opportunities appear
Refresh Types
- Light Refresh
- update data
- fix errors
- improve clarity
- Moderate Refresh
- expand sections
- improve structure
- add examples
- Major Refresh
- rewrite content
- reposition topic
- rebuild structure
Refresh must always:
→ improve value
Measurement Rule
After refresh or test:
Compare:
- before vs after performance
Metrics must show:
- improvement
- stability
- no negative impact
Experiment Registry Rule
All tests must be recorded in:
Ads Brain Experiment Registry
Record:
- test type
- change made
- date
- baseline
- result
- conclusion
Iteration Rule
Testing must feed back into:
- content briefs
- information gain system
- internal linking strategy
- messaging systems
Learning must improve future content.
Ranking Stability Rule
Do not over-refresh.
Too many changes can:
- reset ranking
- create volatility
Balance is required.
Content Lifecycle Rule
Content moves through:
Create
↓
Rank
↓
Test
↓
Improve
↓
Stabilise
↓
Refresh
↓
Repeat
Content must remain active.
Cross Brain Integration
Content Brain
- creates and updates content
Data Brain
- tracks performance
Experimentation Brain
- validates results
Affiliate Brain
- benefits from improved traffic
Conversion Brain
- benefits from improved clarity
Required Tracking
- ranking position
- impressions
- clicks
- CTR
- time on page
- conversions
These signals guide decisions.
Failure Modes Prevented
- stagnant content
- ranking decay
- outdated information
- missed optimisation opportunities
- guess-based updates
Drift Protection
The system must prevent:
- updating content without measurement
- testing multiple variables at once
- ignoring performance signals
- over-refreshing content
- failing to record results
Architectural Intent
This framework ensures MWMS content becomes:
→ a continuously improving system
rather than:
→ a one-time output
It connects content directly to:
- data
- testing
- optimisation
Final Rule
If content is not improving:
→ it is falling behind
Change Log
Version: v1.0
Date: 2026-04-26
Author: HeadOffice
Change
Created SEO Testing And Refresh Framework defining structured content optimisation, testing rules, and performance measurement.
Change Impact Declaration
Pages Created:
Content Brain SEO Testing And Refresh Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
Content Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
END