How to Plan a Webflow Content Migration Without Losing SEO
A Webflow content migration succeeds when every source URL and content record has a documented destination. The work is less about copying text into a new CMS and more about preserving meaning, search history, relationships, and editorial ownership while the website changes underneath them.
This guide focuses on the migration operation itself. The broader rebuild decisions belong in the Webflow rebuild guide; the final production checks belong in the technical SEO checklist.
Create one source inventory
Combine URLs from the current sitemap, CMS exports, analytics, Search Console, Bing Webmaster Tools, backlink data, and a full site crawl. Each source sees a different part of the website, so relying on the sitemap alone will miss orphaned, redirected, or excluded pages.
Record the URL, status, canonical, title, H1, content type, traffic, backlinks, conversions, owner, and last meaningful update. Add notes for forms, downloads, embeds, schema, and unusual formatting that may not survive a standard export.
Give the inventory one accountable owner. Separate spreadsheets maintained by SEO, content, and development quickly produce conflicting redirect plans.
Assign a decision to every URL
Each source page needs one clear disposition.
- Keep: preserve the URL and move the content into the new system.
- Improve: retain the intent and URL while strengthening the page.
- Merge: consolidate overlapping pages into one stronger destination.
- Move: change the path and create a permanent redirect.
- Retire: remove a page when it has no useful replacement or continuing purpose.
Do not redirect every removed page to the homepage. A redirect should take the visitor to the closest meaningful replacement. If none exists, a clear retired state may be more accurate than an unrelated destination.
Map old content to the new CMS
Create a field map before importing. For every source field, identify the destination field, transformation rule, required format, and fallback when the source is empty.
Rich text needs special attention. Old bodies may contain inline styles, unexpected heading levels, embedded scripts, tables, relative links, and images without useful alternatives. Decide what will be cleaned automatically and what needs editorial review.
Test the map with a representative set: one short item, one long article, one record with lists and links, one with an embed, and one with missing data. Fix the process before processing hundreds of items.
Separate migration from rewriting
Trying to migrate, redesign, and rewrite every page at once makes errors difficult to trace. Mark which pages will move as-is, which receive light cleanup, and which require a full editorial rewrite.
Prioritize high-value pages by traffic, backlinks, conversion contribution, and strategic importance. Preserve useful language and evidence even when the visual design changes. A new template is not a reason to discard content that already satisfies the search intent.
Prepare files and images deliberately
Inventory downloadable files and image assets separately from page copy. Confirm which assets are still used, whether the source quality is adequate, and whether licences or privacy requirements affect reuse.
Use sensible filenames, modern formats, appropriate dimensions, and concise alt text for informative images. Decorative images should use empty alt text. Update embedded asset URLs so the new site does not depend on an old domain or private storage location.
Build the redirect map from the inventory
Create redirects as soon as URL decisions are approved, not during the final launch meeting. Each old public URL should reach its intended final destination in one step.
Check for loops, chains, pattern rules that catch the wrong page, query-string behaviour, and collisions with new routes. Keep the redirect map under version control or in a shared launch record so decisions remain visible.
Update links before publishing
Internal links inside migrated content should point directly to the new canonical destination. Do not rely on redirects to repair the site’s own navigation indefinitely.
Check rich text, navigation, components, footers, schema, downloadable files, and emails controlled by the website. Use descriptive anchor text and remove links to content that has no replacement.
Validate records in Webflow
- Confirm required fields and references resolved correctly.
- Inspect headings, paragraphs, lists, links, and embeds.
- Verify titles, descriptions, slugs, images, and alt text.
- Check publication dates, authors, categories, and FAQs.
- Preview static and CMS templates at every breakpoint.
- Compare record counts with the approved inventory.
- Run a link and metadata crawl before launch.
Use automated checks to find patterns, then manually inspect high-value and unusual content. A clean item count does not prove that the body retained its meaning.
Reconcile after launch
Crawl the old URL list against production and confirm status, final destination, canonical, and indexability. Submit the sitemap and inspect critical pages in search tools.
Monitor 404s, redirect errors, organic landing pages, indexing, rankings, backlinks, forms, and conversions. Keep a migration issue log and distinguish actual defects from normal reporting delays or search fluctuations.
A reliable migration leaves an audit trail: where each item came from, what changed, where it lives, and who approved the decision. That record is what lets the team fix issues without guessing after launch.
Keep a migration exception log
Some records will not fit the standard method. Track each exception, the decision, owner, and resolution instead of quietly fixing it in the import script. Exceptions often reveal a missing CMS field, an unsupported embed, or an old content type that needs a business decision.
Review the log before each migration batch. A solution found for one item may apply safely to dozens of others, while a one-off workaround should remain clearly identified.
Can a Webflow migration hurt SEO?
Yes. Search visibility can decline when valuable URLs change without redirects, content is removed, metadata is lost, internal links break, or crawl and indexing settings are incorrect.
What should a content migration inventory include?
Include every known URL, status, traffic, backlinks, conversions, canonical URL, title, description, H1, content owner, and the planned destination or action.
Should every old URL redirect to the homepage?
No. Redirect each old URL to the closest relevant replacement. If no meaningful destination exists, retiring the URL may be more accurate than an unrelated homepage redirect.
Which fields should a Webflow resource CMS include?
Typical fields include name, slug, summary, body, author, date, category, SEO title, meta description, image alt text, FAQs, and related content.
How should redirects be tested?
Test the full redirect map, confirm each source reaches the intended final URL in one step, crawl the production domain, and monitor 404 reports after launch.
What should be monitored after migration?
Monitor 404s, sitemap processing, index coverage, organic landing pages, rankings, conversions, canonical tags, and unexpected traffic changes.