Resource
The Webflow migration playbook.
A six-phase framework for replatforming onto Webflow without losing rankings, traffic, or authority.
Most Webflow migrations fail in one of two predictable ways: they're treated as a redesign project (and SEO gets neglected until launch week), or they're treated as a pure SEO project (and the design and CMS architecture suffers). This playbook is built to keep both honest.
The phases below assume a marketing site of 50–300 pages. Larger or multi-locale migrations take longer at every phase but follow the same framework.
Phase 1 — Inventory
Week 1–2- Full URL crawl of the existing site (Screaming Frog or similar)
- Page-by-page traffic data export from Google Analytics for the trailing 12 months
- Top-100 ranking keywords and their landing pages (Ahrefs or Semrush)
- Backlink profile export for high-value referring domains
- Schema audit of existing structured data
- Asset inventory: images, PDFs, videos to migrate
Phase 2 — Architecture
Week 3–5- New IA proposal mapped against existing URLs
- 1:1 redirect map drafted (every old URL points somewhere)
- CMS schema designed (collections, fields, references)
- Page templates planned (one per high-volume page type)
- Internal linking model documented
- Decisions logged for URLs that will not be preserved (and why)
Phase 3 — Build
Week 6–12- Design system and component library built in Webflow
- CMS collections created and populated with sample content
- Templates built and tested with real data
- Schema implementation for each template
- Content migration: editorial pages, blog, resources
- Asset migration: images optimized and uploaded
Phase 4 — Pre-launch QA
Week 13–14- Crawl the staging site, compare against URL inventory
- Validate every redirect manually (or scripted)
- Validate every schema instance with Schema Markup Validator
- Run Lighthouse on top 20 templates
- Accessibility audit (axe + manual)
- Submit staging sitemap to Search Console for crawl preview
Phase 5 — Launch
Week 15- Final crawl of the existing site as last-known-good baseline
- DNS cutover with redirects active
- Submit new sitemap to Search Console immediately
- Request indexing for top-25 traffic pages
- Monitor crawl logs for 404s in the first 72 hours
Phase 6 — Post-launch
Week 16–24- Daily crawl + Search Console monitoring for the first month
- Track rankings for top-100 keywords weekly
- Fix any redirect chains, 404 surges, or schema errors immediately
- Quarterly review of organic traffic vs. pre-launch baseline
- Honest postmortem: what worked, what didn't, what to do differently
Need help running this?
The agencies in our migration directory all use a version of this playbook — and have the receipts.
See migration specialists