Migrating from Webflow to EmDash: a practical SEO checklist
Plan URLs, collection data, media and redirects before switching your Webflow site to Astro and EmDash.
Treat migration as a website project
A Webflow-to-EmDash migration includes more than a content import. Your CMS structure, Astro frontend, media storage, forms, URLs and deployment all need a destination. The goal is to keep useful pages accessible and editorial work manageable after the switch.
There is no honest promise of zero SEO impact. A careful plan reduces avoidable mistakes and gives you evidence to investigate changes. Start with the existing site’s important pages and user journeys rather than rebuilding a design and deciding what to do with its URLs at the end.
Inventory URLs and record a baseline
Collect URLs from the sitemap, a site crawl, internal links and Search Console when available. Record each page’s purpose, title, canonical URL and destination. Include static pages, collection pages, translated routes and old redirects that still receive visits.
For each URL, choose to preserve it, redirect it to an equivalent page or retire it deliberately. Prioritise pages with organic visits, conversions or backlinks. Save the inventory outside the old platform so it remains usable during launch. Keep a separate list of forms, embeds and integrations to test.
Move content separately from presentation
Webflow code export does not provide a functioning CMS migration. Collection content can be exported separately as CSV. Map its columns to your EmDash schema and rebuild the rendering in Astro. A shared field name does not ensure the two platforms use the same representation.
The current Sneaps Import/Export plugin can handle supported collection fields, but is not a complete Webflow site importer. Relationships, media and unsupported field types need separate work. Test representative rich text, links and special characters before a bulk transfer. Keep the original files.
CSV import walkthroughPreserve paths and rebuild redirect rules
Keep existing paths when they still make sense. When a path changes, map the old URL directly to its closest replacement. Export existing Webflow redirect rules and translate them for the new serving layer; do not assume Webflow settings continue to operate after traffic moves elsewhere.
Test representative old URLs against the destination before launch. Check the HTTP response and final page, not only a browser that eventually opens something. Avoid chains, loops and a blanket redirect to the homepage. Put redirect rules where requests for the public domain will actually be handled.
Check SEO output and media on staging
Compare page titles, descriptions, headings, canonicals and indexability with the inventory. Check that sitemap URLs use the final public domain, including the chosen www convention, and that language alternates point to real equivalents. Inspect internal links for temporary staging domains.
Transfer required media to storage you control and verify crops, alt text and embedded assets. Check the rendered article body, not just the entry count in the admin. A page can exist and still lose its images, meaningful headings or useful links during conversion.
Launch with a rollback and a follow-up plan
Choose a cutover window, preserve backups and decide how you will handle content edited between the initial export and launch. Test the final public domain, robots.txt, sitemap, forms and important redirects immediately after the switch. Remove staging-only indexing restrictions only where appropriate.
Monitor Search Console, broken links and requests to missing pages in the following weeks. Compare like-for-like periods and investigate specific URL changes instead of attributing every fluctuation to the CMS. Keep the mapping and launch notes: they are useful when a client asks why a particular page moved.