How to Migrate from Webflow to Framer Without Losing SEO (2026)

Migrations don't kill SEO. Sloppy migrations do.

Every time someone posts about losing 60% of their traffic after moving to Framer, the replies blame the platform. The platform is almost never the problem. The problem is that they treated a migration like a design refresh. Rebuild the pages, flip the DNS, pray.

I've built on both Webflow and Framer. I know where each one breaks. Framer ships pre-rendered HTML, auto-generates sitemaps, runs on a global CDN, and handles 301 redirects natively. As a platform, it's fine for SEO. The reason migrations tank rankings is that five specific things get fumbled in the handover, and they're all preventable.

This guide walks through exactly what to audit before you touch Framer, how to preserve rankings during the rebuild, and the one gotcha that catches almost everyone: Framer redirects require the Pro plan or higher. If you're on Basic, you literally cannot do this correctly. More on that below.

Key Takeaways

• Framer redirects require the Pro plan ($30/month) or higher. Free and Basic plans cannot create 301 redirects at all.

• Framer ships with server-side rendering, automatic XML sitemaps, global CDN delivery, and native 301 redirect support with wildcards. As a platform, it's SEO-capable by default.

• The most common post-migration bug is Framer leaving canonical URLs pointed at the .framer.website staging subdomain instead of the production domain. Always verify in the page source before celebrating a launch.

• Webflow exports CMS content per Collection as CSV (Collections panel → Export). Framer imports CSV natively via the CMS Toolbar → Import. Code export from Webflow does not include CMS content.

• Webflow multi-reference fields do not port to Framer automatically. Import them as plain text fields, then relink manually.

• Framer's wildcard redirect syntax uses * for path segments and :1, :2, :slug for capture groups. /blog/* to /blog/:1 migrates an entire blog folder in one rule.

• A 10-20% impression dip in weeks 1-4 is normal. A sustained drop greater than 30% after 4 weeks means a technical issue, usually redirects or canonicals.

• Sites with 500+ indexed pages, 5+ locales, relational CMS depth, or full e-commerce are often better off staying on Webflow. Framer Pro caps at 150 pages, Scale at 300 baseline.

Why Webflow to Framer Migrations Lose SEO Traffic

It's not the platform. Framer's technical SEO fundamentals are solid:

• Server-side rendering at publish time, including responsive versions

• Automatic XML sitemap generation

• Global CDN via AWS CloudFront with Brotli and gzip compression

• Native 301 redirect support with wildcard matching (on Pro and above)

Every one of these is documented in Framer's official hosting guide. On paper, a Framer site should index and rank at least as well as a Webflow one.

Traffic drops during migration because five specific things go wrong, usually in combination:

1. Broken redirects. URLs change but no 301s are in place, so Google sees a pile of 404s where ranking pages used to be.

2. URL drift. Small "improvements" to slugs during the rebuild. /blog/seo-guide becomes /insights/seo-guide. Every backlink now points somewhere dead.

3. Metadata wipe. Meta titles and descriptions get defaulted or rewritten during the rebuild. The page still exists, but the ranking signals Google built for that exact meta are gone.

4. Schema loss. FAQ, Article, Organization, and Product schema that was on the Webflow site never gets rebuilt on the Framer side. Rich results disappear.

5. Canonical confusion. Framer can leave canonical URLs pointing at the .framer.website staging subdomain after publish. Google sees two sites claiming the same content and nobody wins.

The difference between a 10-20% temporary dip (normal) and an 80% collapse (the horror stories you've seen) is whether these five things were audited before launch or discovered three weeks later in Search Console.

When Webflow to Framer Is Safe, and When It's Risky

Not every site should move. This is the section most migration guides skip because they're written by agencies selling migration services, and agencies can't afford to say no.

Here's the honest breakdown.

Safe to migrate:

If you're migrating a site in one of these categories, starting from a template that already ships with SEO configured (meta fields, OG images, schema hooks, clean heading hierarchy) can save you the "did I forget something?" risk of rebuilding from a blank canvas. Our Framer agency templates and SaaS templates are built with this in mind. But even without a template, the migration is well within reach for any of these site types.

Risky to migrate:

If your site falls in the second table, the right move is probably to stay on Webflow and invest in performance and content instead. If you still want to review whether Framer's plan limits match your site's needs, our Framer vs Webflow pricing comparison breaks down the actual cost per tier.

How Long Does a Webflow to Framer Migration Take?

Realistic timelines by site size, assuming a dedicated team member with basic Framer familiarity. Add 2-4 weeks if your team is learning Framer during the migration, or if stakeholder approval cycles are slow.

If your timeline is tighter than the ranges above, scope down. Pick the top 20% of pages by traffic, migrate those first, and move the long tail in a second phase. Rushing a full migration into 2 weeks is where most horror stories start.

The Pre-Migration SEO Audit

This is the step 90% of migration horror stories skipped. Do it before you open Framer.

The goal is simple: know exactly what you're preserving before you start rebuilding.

1. Crawl your current Webflow site.

Use Screaming Frog or Ahrefs Site Audit to pull every indexed URL. Export to a spreadsheet. For each URL, capture:

• Current meta title and meta description

• H1 and H2 hierarchy

• Internal links pointing to it

• External backlinks (Ahrefs, Moz, or GSC Links report)

• Current ranking keywords (GSC → Performance → filter by page)

• Clicks and impressions over the past 90 days

How to Export Webflow Content for Framer

Webflow exports CMS content per Collection as CSV. The export includes Item IDs, which matter when you need to map references between collections. In the Webflow Designer: Collections panel → open the Collection → Export. Do this for every Collection on your site.

One critical note: Webflow's code export does not include CMS content. If you're relying on the code export to capture your blog, you'll end up with empty Collection list templates. Always use the CSV export from the CMS panel for content.

There's no "Export to Framer" button. The CSV flow is the supported path. On the Framer side, you'll import these CSVs via CMS Toolbar → Import (covered in the next section).

3. Export your existing Webflow 301 redirects.

Site Settings → Publishing → 301 redirects → Export. This gives you a CSV of every redirect already running on your Webflow site. You'll recreate these in Framer. They're part of your SEO infrastructure and you don't want to lose them.

4. Document your schema markup.

Run your top pages through Google's Rich Results Test or Schema.org validator. Record every schema type present: FAQPage, Article, Organization, Product, BreadcrumbList. These need to be rebuilt in Framer, usually via custom code blocks.

5. Baseline your Search Console data.

Screenshot or export the last 90 days of: clicks, impressions, average position, indexed pages. You'll compare against this weekly after launch.

Put all of this in a single migration spreadsheet. When something looks off two weeks after launch, this spreadsheet tells you whether it's a real problem or noise.

How to Preserve Rankings During the Rebuild

With the audit in hand, here's how to rebuild without losing equity.

Match URLs exactly where possible. If /blog/framer-seo-checklist ranks, the new Framer version lives at /blog/framer-seo-checklist. Don't "clean up" URLs mid-migration. Every slug change is one more redirect you need to maintain forever.

Port metadata page-by-page. Don't trust any "automatic" port. There isn't one between these platforms. Open each page in Framer, paste in the exact meta title and meta description from your Webflow audit. Framer has dedicated fields for these in the page settings panel.

Rebuild heading hierarchy deliberately. One H1 per page, semantic H2s for major sections, H3s only where a section has genuine subsections. Framer won't enforce this. You have to. A common mistake: using text styles in Framer that look like headings but render as <p> tags. Check the inspector.

Import CMS content via CSV. Framer added native CSV import directly in the CMS Toolbar. Click Import, map your Webflow CSV columns to Framer Collection fields, and upload. It works for text, numbers, dates, images (if hosted publicly), and booleans.

The place it gets messy: Webflow's multi-reference fields. Framer supports relational CMS on Pro and above, but the one-to-many mapping from Webflow doesn't port automatically. For each multi-ref field, create a plain text field during import and manually relink afterward. This is tedious but it's where most CMS migrations silently break.

Rebuild schema markup with custom code. Framer supports custom code globally in Site Settings (good for Organization and LocalBusiness schema) or at the page level via code embeds (good for Article, FAQPage, Product). If you're adding FAQ or Article schema to blog posts, my Framer SEO Checklist for 2026 walks through the exact JSON-LD setup.

Verify canonical URLs before publish. This is the bug that catches everyone. After publishing, check the source code of at least 5 pages. Look for the <link rel="canonical"> tag. It should point to your production domain (e.g., https://yourdomain.com/blog/post), not https://your-project.framer.website/blog/post. If it's pointing at the staging subdomain, Google will treat your staging site as the authoritative version and your real domain as a duplicate.

[IMAGE: Screenshot of Framer's page settings panel with the meta title, meta description, and canonical URL fields highlighted]

Setting Up 301 Redirects in Framer (Where Everyone Fails)

Here's the fact that catches most people off guard, and the one no competing article leads with clearly: Framer redirects require the Pro plan ($30/month) or higher. If your Framer site is on the Free or Basic plan, you cannot set up 301 redirects at all. This is per Framer's own documentation.

If you're migrating any site with existing search traffic, Basic is not an option. Budget for Pro before you start the migration.

With that out of the way:

Where to find it: Site Settings → Redirects. Every redirect you create is automatically a 301 (or 308 for wildcard matches). There's no option to create a 302 or any other type, which is exactly what you want for a migration anyway.

Manual redirects: Enter the old URL in the "From" field, the new URL in the "To" field. Publish to apply. Drag to reorder rules when priority matters.

Wildcard redirects for blog migrations: This is the feature that saves hours.

The * captures any path segment. :1, :2, etc. reference matched groups in the new URL. :slug matches specific named segments between slashes.

What you can't do: Framer redirects only work within the same domain. If you're moving from oldcompany.com to newcompany.com, the domain-level redirect has to happen at your DNS or hosting provider first. Then connect the new domain in Framer and handle sub-paths as normal.

One thing to avoid: "Redirect everything to the homepage." This is the lazy option, and Google treats it as a soft 404. Ranking equity from the old page doesn't transfer because the new destination has nothing to do with the original page's topic. Either map to a genuinely relevant page or don't redirect at all. Just let it 404 and remove the page from your sitemap.

Launch Day and the First 90 Days

Pre-launch checks (before DNS swap):

1. Verify canonicals on 10 top pages. View source, confirm <link rel="canonical"> points to production, not .framer.website.

2. Test 10 redirects in Framer's preview. Make sure the rules actually fire.

3. Check your sitemap. Framer auto-generates it at yourdomain.com/sitemap.xml. Open it, confirm every page you want indexed is listed.

4. Set up the new Google Search Console property if your domain is changing. If not, keep the existing one. The property follows the domain.

5. Run Lighthouse on your 5 top-traffic pages. Performance and SEO scores above 90. Anything below, investigate before launch.

Launch day:

1. Swap DNS to point to Framer.

2. Within an hour of propagation, test 20 redirects live using a redirect checker like httpstatus.io. Confirm each returns a 301 to the correct destination.

3. Submit the new sitemap in Search Console.

4. Use "URL Inspection" in GSC to request indexing for your top 20 pages directly. This speeds up re-crawl significantly.

5. Spot-check mobile rendering on your top pages. Framer handles this well, but verify.

First 90 days. Watch these weekly in Search Console:

• Coverage report: Indexed pages count should stay within 10% of pre-migration. A larger drop means crawl or redirect issues.

• Performance → Queries: Compare to your baseline from the audit. Expect 10-20% fluctuation for the first 2-4 weeks. This is normal.

• Performance → Pages: Top pages should recover impression volume within 3-6 weeks. If a top page is still down 40% after 6 weeks, something's broken. Usually a redirect or canonical issue.

• Core Web Vitals: Framer usually improves these. Confirm.

If sustained drop is greater than 30% across the top 10 pages after 4 weeks, stop. Something specific is wrong. Re-audit redirects, canonicals, and metadata before doing anything else.

Who Should Stay on Webflow

Some sites genuinely shouldn't move, at least not yet. Be honest about whether yours is one of them.

Framer CMS Limits That Break Migrations

Framer's current CMS limits by plan: Basic (1 collection, 1,000 items, 30 pages), Pro (10 collections, 2,500 items, 150 pages), Scale (20 collections, 10,000 items, 300 pages baseline, expandable to 40 collections and 40,000 items with add-ons), Enterprise (custom, up to 100,000 items). If your Webflow site is already past the Pro thresholds, budget for Scale or evaluate whether migration makes sense at all.

Stay on Webflow if:

• Your CMS depends on deep relational structures. If you're running 5+ collections with multi-reference fields linking them, the mapping work in Framer will be significant and error-prone.

• You run 5+ locales and localization is central to your SEO. Framer's locale add-ons stack up fast, and the localization UX is less mature than Webflow's.

• You have 500+ indexed pages and your growth strategy is content volume. Framer Scale caps at 300 pages baseline (expandable). If you're publishing weekly and already past 500, the page limits will bite.

• You run real e-commerce with inventory management. Framer isn't built for this. Lightweight paid products via Stripe or Lemon Squeezy work fine. A full store doesn't.

• Your team is already deep in Webflow workflows (Editor roles, Logic, Memberships). The productivity loss in retraining can outweigh the design upside.

Our Framer enterprise capabilities breakdown goes deeper on where Framer's limits actually bite for content-heavy operations.

For most marketing sites, the ones actually asking this question, moving is the right call. Just do the audit first.

What a Successful Migration Actually Looks Like

To give you a sense of realistic outcomes, here's a representative before/after for a medium-sized marketing site migration (25 pages, 3 CMS collections):

Before (on Webflow):

• 25 pages, 3 CMS collections

• Heavy IX2 animations across the homepage and landing pages

• PageSpeed score: 73

• Publishing workflow: 2-3 days per update, developer required for anything beyond text changes

After (on Framer):

• Same 25 pages, CMS consolidated to 2 collections (one multi-ref relationship was flattened)

• Native Framer animations replaced IX2

• PageSpeed score: 92

• Publishing workflow: same-day, designer-led, no developer needed

Migration stats:

• Duration: 5 weeks

• Team: 2 people (designer + part-time developer for schema and redirects)

• SEO outcome: 15% impression dip in weeks 1-3, fully recovered by week 6, net positive by month 3

The PageSpeed jump is typical. Framer's SSR plus CDN plus automatic image optimization usually improves Core Web Vitals compared to even a well-built Webflow site. The SEO fluctuation in the first month is also typical and not cause for panic if your redirects and canonicals are clean.

The Real Takeaway

Migration is an SEO project, not a design refresh. If you treat it like "rebuild the pages, ship it, see what happens," you will lose traffic. If you treat it like an inventory-and-transfer problem (audit every URL, map every redirect, verify every canonical), Framer preserves everything Google associates with your domain, and often improves performance on top.

Framer the platform isn't the risk. The handover is.

If you're migrating an agency, SaaS, or portfolio site, a Framer template that ships with SEO pre-configured removes one more place where things can go wrong. Use code OMAKASE20 for 20% off any of our templates. It works across the full catalog.

FAQ

Does migrating from Webflow to Framer hurt SEO?

No, not inherently. Framer supports server-side rendering, automatic sitemaps, 301 redirects with wildcards, and custom schema via code blocks. Everything Google needs to rank a site. Traffic drops when URLs change without redirects, metadata gets wiped during rebuild, or canonical URLs point at the wrong domain after publish. Execute the migration carefully and rankings preserve.

Do I need to keep the same URLs when migrating from Webflow to Framer?

Yes, wherever possible. Every URL change requires a 301 redirect to preserve the ranking signals Google has built for that page. Matching URLs exactly eliminates the risk of redirect loops, chains, or missed pages. Only change slugs during a migration if there's a real reason to, and set up the 301 before launch.

How do I move my Webflow CMS content to Framer?

Export each Webflow Collection as a CSV from the Collections panel (this includes Item IDs). Then in Framer, use CMS Toolbar → Import, map your CSV columns to Framer Collection fields, and upload. Text, numbers, dates, booleans, and images (if publicly hosted) transfer cleanly. Multi-reference fields don't map automatically and need to be relinked manually.

Which Framer plan do I need for redirects?

Pro ($30/month) or higher. The Free and Basic plans don't include redirect functionality. If you're migrating any site with existing search traffic, Pro is the minimum plan. There's no reliable workaround on Basic.

How long before Google re-indexes my site after migration?

Top pages typically re-crawl within 3-14 days if you submit the new sitemap in Search Console and use URL Inspection to request indexing for priority pages. Full re-indexing of a 100-page site usually completes within 4-6 weeks. If top pages are still showing impression drops greater than 30% after 6 weeks, there's a technical issue worth investigating. Start with redirects and canonicals.