Webflow to Framer SEO migration
Moving from Webflow to Framer does not need to reduce search visibility. Keep valuable URLs and content stable, map every changed path, recreate metadata and structured data, and verify the live site in Search Console. Separate the platform change from unnecessary content or URL changes so problems are easier to diagnose. The step-by-step migration guide covers the rest of the move.
Before the migration
1. Crawl the Webflow site
Crawl all static, CMS, localized, utility, and campaign routes. Record each URL’s status, canonical, indexability, title, description, headings, internal links, and content type. Include links inside Webflow rich-text fields.
2. Build a URL map
Give every source URL one outcome: keep, redirect, merge, or remove. Keep useful paths and CMS slugs unchanged where possible. Include existing Webflow redirect destinations so the new setup does not create chains.
3. Save metadata and a performance baseline
Export titles, descriptions, social metadata, canonicals, structured data, noindex rules, localized alternatives, and image alt text. Save Search Console clicks, impressions, queries, pages, conversions, and Core Web Vitals so you can compare the result after launch.
During the migration
4. Keep URLs and content stable
Preserve page paths, CMS slugs, localized routes, headings, useful copy, and internal-link relationships unless there is a clear reason to change them. Update rich-text links and re-host important Webflow CDN assets in Framer.
5. Add permanent redirects
Redirect only changed or removed URLs. Send each source URL directly to the closest relevant destination and avoid chains, loops, and broad redirects to the homepage.
Framer supports exact, wildcard, capture-group, and named-parameter redirects. When importing redirects in bulk, use a CSV with from and to columns. Entries that match an existing from path update that redirect, while other existing redirects remain unchanged. If the domain changes, keep the old domain configured so it can forward requests. See Framer’s bulk redirect import guide.
6. Recreate metadata and structured data
Set a unique title, description, social preview, canonical, and search visibility for each important page and CMS template. Recreate useful JSON-LD with custom code and validate what appears on the published page.
Use structured data that matches visible content. FAQ content can make the page easier to understand, but FAQ rich results in Google are generally limited to authoritative government and health sites.
7. Check localization and indexing
Map each Webflow locale to the correct Framer route. Check language alternatives, canonicals, internal links, localized CMS slugs, noindex settings, sitemap.xml, and robots.txt. Framer automatically generates a sitemap and robots.txt for published sites.
8. Test before launch
Test representative static, CMS, localized, and utility URLs. Check metadata, canonicals, structured data, redirects, internal links, mobile rendering, forms, analytics, the 404 page, sitemap.xml, and robots.txt.
After the migration
9. Verify production and Search Console
Repeat the checks on the production domain after DNS and SSL are active. If the domain or subdomain changes, verify both the old and new properties in Search Console before launch and keep a verification method that survives the cutover. Submit the Framer sitemap in Search Console and inspect important URLs. Use Google’s Change of Address tool only when the domain or subdomain changes, not for a platform-only move on the same domain.
10. Monitor and fix
Monitor crawl errors, indexing, canonicals, traffic, conversions, and important rankings. Fix 404s, redirect chains, blocked pages, incorrect canonicals, missing metadata, and broken internal links by cause. Keep redirects for as long as possible, generally at least one year, following Google’s site-move guidance.
Webflow to Framer SEO questions
Does moving from Webflow to Framer hurt SEO?
Not by itself. The main risks come from changing URLs, removing useful content, losing metadata or structured data, breaking internal links, or missing redirects. Keeping those signals stable and testing the production site reduces the risk.
Do unchanged URLs need redirects?
No. If the domain and full path stay the same, the page can keep serving at that URL. Add a redirect only when the source URL changes or is intentionally removed.
Does Framer create a sitemap and robots.txt?
Yes. Framer generates sitemap.xml and robots.txt for published sites. Verify both files after launch and submit the sitemap in Search Console. Framer also serves optimized pages as structured markdown to supported AI agents, which you can preview by adding ?md to a published URL. See Make your site readable by AI agents.
Should I use Google’s Change of Address tool?
Use it when the migration changes the domain or subdomain. Do not use it for a move from Webflow to Framer that keeps the same domain.
Finish with the Webflow to Framer migration checklist.
