Website Replatforming Risk Register
A pre‑launch risk register for redesigns, CMS migrations and framework changes, covering the SEO and delivery issues that tend to surface too late.
Resources
Practical tools for planning, checking, and recovering search‑critical web platform work.
Use these checklists, matrices, and worksheets when a redesign, replatform, CMS change, or React/Next.js build needs evidence, not assumptions. The groups below are organised by the situation you are trying to de‑risk: planning a move, auditing JavaScript SEO, recovering after launch, or keeping CMS and structured data controls aligned.
Choose by situation
Start with the resource that matches the risk in front of you, then use the neighbouring checks where the same platform change affects routes, content, metadata, CMS control, or recovery work.
Plan a Replatform
Use these before routes, redirects, rendered HTML, and launch ownership are locked in.
Website Replatforming Risk Register.
Audit React and Next.js SEO
Use this when indexation depends on rendered HTML, metadata, and crawler‑visible links.
Recover After a Launch Drop
Use this when a release, redesign, or migration has changed traffic, crawl behaviour, or indexation.
Control CMS and Schema Risk
Use these when headless CMS fields, editorial controls, JSON‑LD, and page evidence need to stay aligned.
