Refresh vs Rewrite Decision Tree for AI Content
Choose refresh, rewrite, merge, or hold based on search exposure, reader value, and quality risk.
AI Content Refresh Playbook
Information asset -> refresh diagnostic -> implementation sprint
How to use this library
The AI Content Refresh Playbook library is designed as a working shelf, not a link directory. Start with Refresh vs Rewrite Decision Tree for AI Content when the problem is still broad, then use Thin Section Repair for AI-Assisted Articles or Source Gap Inventory Before Content Refresh to turn the finding into a decision record.
A good pass through this library should produce one artifact: a checklist result, scorecard, route map, or repair queue that another operator can review. When the artifact shows repeated unknowns, use the services route with concrete examples; when it resolves the issue, keep the page as a reference and move to the next bottleneck.
For backlink value, each page should be useful without a sales conversation: it must define the failure mode, show the fields to inspect, and leave the reader with a reusable operating object.
Thin Section Repair for AI-Assisted Articles
Repair thin sections by adding artifacts, comparisons, checks, and reader decisions instead of padding words.
Source Gap Inventory Before Content Refresh
Inventory missing proof, outdated references, and unsupported claims before editing public copy.
Refresh Measurement Window for Search Pages
Set T+7, T+14, and T+28 reads for refreshed pages so teams do not overreact too early.
Refresh Rollback Notes for Public Articles
Write rollback notes that preserve the previous title, meta, body hash, and measurement state.