Serverless edge migration checklist
Move off a monolithic CMS origin without losing SEO equity or breaking forms: DNS, redirects, env isolation, RLS, and cutover monitoring.
Preparation
- URL inventory exported from the current CMS / Search Console
- 301 redirect map drafted for changed paths (old → new)
- Critical pages and metadata have parity targets (title, H1, body intent)
- All lead forms and webhooks listed with destination systems
Platform & secrets
- Git-connected host configured (e.g. Cloudflare Pages) with preview deploys
- Preview and production env vars isolated; no production secrets in the client bundle
- Security / cache headers planned for static assets and HTML
- Media strategy decided (local public + CDN/R2 if used) and verified with 200 responses
Data, forms, and edge logic
- Database policies reviewed (e.g. Supabase RLS: insert-only public paths where appropriate)
- Form/API routes validate and rate-limit at the edge before writes
- CRM/email side effects are async (retries / dead-letter), not blocking thank-you
- Synthetic checks cover new form endpoints before DNS cutover
Cutover & first week
- Redirects tested on preview or staging host
- DNS / custom domain attached; HTTPS certificate valid
- Search Console sitemap resubmitted; spot-check key URLs with URL Inspection
- CWV and uptime monitored for the first week after cutover
- Rollback owner named; previous deploy or DNS plan documented