Webflow Migration Checklist: 12 Steps to Keep Your Rankings (2026)

A safe Webflow migration runs in four phases. First, crawl and benchmark your current site. Second, map every old URL to a new one and rebuild content with meta titles and schema intact. Third, load 301 redirects in Webflow before you connect the domain. Fourth, monitor Search Console for four to six weeks. The biggest cause of lost rankings after a migration is an incomplete redirect map so start there, not with the design.

Most sites that lose rankings after moving to Webflow were not failed by the platform. They were failed by a skipped step.

A URL changed and no one added a redirect. A meta title never made the move. Schema quietly disappeared at launch. Each gap costs traffic, and the gaps are avoidable.

This checklist covers all 12 steps we run on every migration. It is the same process we have used across 150+ client sites in 15+ countries. Work through it in order and your rankings should survive the move and often improve, because Webflow ships cleaner, faster code than most platforms you would migrate away from.

Use it as a working document. Copy the step list into a project tracker, assign an owner to each step, and check nothing off until it is verified, not just done.

Before you start the tools you will need

You do not need an expensive stack. You need five things:

• A crawler. Screaming Frog (free up to 500 URLs) or Sitebulb. This builds your URL inventory and exports your current meta data in one pass.
• Google Search Console. Your source of truth for which pages actually earn traffic. Verify access before you begin.
• Google Analytics (GA4). For landing-page and conversion baselines.
• A spreadsheet. Your redirect map and content inventory live here. Plain and reliable.
• A backlink checker. Ahrefs, Semrush, or the free tier of a tool like Ubersuggest. You need to know which pages hold links before you decide what to delete.

Set these up first. Half of the mistakes in a migration come from starting the rebuild before the audit.

Phase 1: Before you touch Webflow

This phase decides whether your rankings survive. It happens entirely outside Webflow, and it is the phase teams are most tempted to rush. Don't.

Step 1: Crawl your current site and inventory every URL

Run a full crawl. Export every URL pages, blog posts, PDFs, and images that rank in image search.

Then cross-check the crawl against Search Console's Pages report. Crawlers miss orphaned pages. Search Console does not, because it reports any page that earned an impression. A page can be invisible in your navigation and still bring in traffic every month.

This combined list is the foundation of your redirect map. The rule is simple: if a URL is not on the list, it will not get a redirect, and its rankings die at launch.

Save the export with these columns at minimum: URL, page title, meta description, H1, and indexable status. You will use all of them later.

Step 2: Benchmark your current rankings and traffic

You cannot prove a migration succeeded or catch what broke without a baseline.

Export the following before you change anything:

• From Search Console: top queries, top pages, clicks, impressions, and average position for the last three months.
• From GA4: organic landing pages, sessions, and conversions for the same window.
• A screenshot of your Core Web Vitals report.

Store these somewhere safe. In week two after launch, this baseline is the difference between "rankings are fine" and "we have a problem on these eight pages."

Step 3: Decide what to keep, merge, and kill

Not every page deserves to move. For each URL, pick one of three outcomes:

• Keep - rebuild it in Webflow as-is.
• Merge - combine thin or overlapping pages into one stronger page, then redirect the old URLs to it.
• Kill - redirect to the closest relevant page.

Decide from data, not from gut feel. A page that looks dated might hold your best backlinks or rank for dozens of long-tail queries. Check backlinks and 12 months of impressions before you delete anything.

Merging is underused and powerful. Three weak posts on the same topic often outrank as one comprehensive page. Migration is the natural moment to consolidate.

Step 4 - Build your 301 redirect map

This is the step that protects your rankings. It gets done before any design work.

Create a spreadsheet with two columns: old URL in column A, new URL in column B. Every URL from Step 1 gets a row. Then follow two rules we never break:

• Redirect to the closest equivalent page. Never to the homepage. Bulk-redirecting everything to / tells Google those pages are gone, so their link equity evaporates. Google treats mass homepage redirects as "soft 404s."
• One hop only. Old URL points to the final new URL directly. Never chain redirects through an intermediate URL - each hop leaks ranking signal and slows the page.

One Webflow-specific catch: CMS-driven pages must live under a collection folder. Blog posts sit at /blog/post-name, for example. If your current blog lives at the root level, every post URL changes so plan those rows now, not at launch.

Our free Webflow 301 Redirect Generator turns this spreadsheet into paste-ready Webflow redirect rules, including wildcard patterns for structural changes.

Phase 2: The rebuild

Now you build. The work here is to recreate the site faithfully - and to carry over the invisible signals that rankings depend on.

Step 5 - Rebuild content in CMS Collections, not static pages

Anything repeatable belongs in a CMS Collection. Blog posts, case studies, team members, services, locations - all of it.

Two reasons. First, it is faster to migrate, because a CSV import handles hundreds of items at once. Second, it keeps future editing out of the Designer, so your marketing team can publish without a developer.

Map your old content types to collections before you import. Categories and tags become reference fields. Authors become a linked collection. Get this structure right first; restructuring a populated collection later is painful.

How common platforms map to Webflow CMS:

Step 6: Carry over every meta title and description

Meta titles are a ranking signal. Descriptions drive click-through. Both are easy to forget, because they are invisible in the Designer.

Pull every title and description from your Step 1 crawl export. Load them into Webflow's per-page SEO settings. For collection pages, bind the SEO fields to CMS fields so each item keeps its own metadata.

Resist the urge to "improve" them mid-migration. Change one variable at a time. Migrate first. Optimize later, once the dust settles and you can measure the effect cleanly.

Step 7: Re-implement your schema markup

Structured data never transfers automatically. It has to be rebuilt.

If your current site uses FAQ, Article, Organization, or HowTo schema, recreate it in Webflow:

• Sitewide schema (Organization, for example) goes in Project Settings → Custom Code.
• Per-post schema (FAQPage, Article) goes in an embed or a rich-text field on the CMS template.

Validate every type with Google's Rich Results Test before launch. And follow one hard rule: only ship schema for content that is visible on the page. Invisible schema is a spam-policy risk, not a shortcut. We learned this the hard way auditing 125 posts, and the cleanup was real work.

Read More: How to Add Schema Markup in Webflow

Step 8: Rebuild internal links with the new URLs

Internal links copied from your old site point at old URLs. They will technically work through your redirects. But every hop leaks a little equity and slows crawling.

Update them to point at the new URLs directly.

Use this pass to fix anchor text too. Link to important pages with the keyword they target, not "click here." Strong internal linking spreads authority to your money pages - it is one of the few SEO levers fully in your control.

Step 8b: Handle images and assets properly

This step gets skipped, and it costs both speed and image-search traffic.

• Compress before upload. Convert images to WebP. Old sites carry years of bloated originals that will drag your Core Web Vitals down.
• Keep descriptive filenames and alt text. Both feed image search. Pull existing alt text from your crawl and re-apply it.
• Redirect ranking images. If images earn search traffic, their URLs change on Webflow - add redirect rows for them too.

Phase 3: Launch week

The build is done. Now you switch over without dropping a signal.

Step 9: Load your 301 redirects before connecting the domain

In Webflow, go to Site Settings → Publishing → 301 Redirects. Paste your full map from Step 4.

Webflow supports wildcard patterns. A rule like /blog/(.*) → /articles/%1 handles a structural change across many URLs in one line. Use these for bulk path changes.

Do this before DNS cutover. The gap between "new site live" and "redirects live" is exactly where rankings get hurt. Close it to zero.

Read More: How to Set Up 301 Redirects in Webflow

Step 10: Cut over DNS and verify the details

Point your domain to Webflow. Confirm SSL is issued. Set your default domain - www or non-www - so the other version redirects to it.

Then check the unglamorous things that break silently:

• Favicon
• Custom 404 page
• Form notifications and integrations
• Analytics and tag manager scripts
• Indexing. Make sure no "noindex" survived from staging. Go to Site Settings → SEO and confirm indexing is enabled. Confirm the Webflow staging subdomain is set to noindex so it does not compete with your live site.

A leftover noindex is the fastest way to deindex a site overnight. Check it twice.

Step 11: Submit your sitemap and request indexing

Webflow auto-generates a sitemap at /sitemap.xml. Submit it in Search Console on launch day.

Then request indexing manually for your most important pages - homepage, service pages, top-traffic posts. Do not mass-request every URL in one sitting. A steady batch per day looks natural and gets processed without friction.

Read more: How to generate & submit XML sitemap in Webflow

Phase 4: After launch

Migration is not done at cutover. The next six weeks decide the outcome.

Step 12: Monitor Search Console for 4–6 weeks

Expect some turbulence for two to four weeks. That is normal recrawling, not failure. Here is what to watch, and what each signal means.

• Coverage report. 404 errors mean URLs missing from your redirect map. Fix them the day they appear. This is the single most common post-launch issue.
• Position tracking. Compare against your Step 2 baseline. A page down more than 5–10 positions after four weeks deserves a look.
• Core Web Vitals. Webflow sites usually score well. Heavy images or animation can still drag INP and LCP. Compress and simplify if scores slip.
• Indexing status. Confirm Google is indexing your new URLs, not just crawling and dropping them.

If rankings have not returned to baseline within six weeks, audit the redirect map first. In our experience, that is the cause more often than everything else combined.

A realistic migration timeline (worked example)

Here is how the 12 steps map to a real schedule for a typical 40-page marketing site with a blog.

• Week 1: Steps 1–4. Crawl, benchmark, content decisions, redirect map.
• Weeks 2–3: Steps 5–8b. Build the design system, CMS structure, import content, carry over meta and schema, fix internal links and images.
• Week 4: Steps 9–11. QA, load redirects, DNS cutover, sitemap. Launch.
• Weeks 5–10: Step 12. Monitor and fix.

Smaller sites compress this. Larger sites stretch it. The full breakdown by site size sits in our guide to how long a Webflow migration takes.

Common mistakes this checklist prevents

Even careful teams trip on the same few things. Each is covered above, but they are worth flagging together:

1. Building the design before the redirect map.
2. Redirecting old pages to the homepage instead of their closest match.
3. Forgetting that root-level blog URLs change on Webflow.
4. Launching with a staging noindex still on.
5. Deleting "old" pages that quietly held backlinks.

We cover the full list in Webflow migration mistakes that tank rankings.

FAQs

1. How do you handle 301 redirects during a Webflow migration?

Build a spreadsheet that maps every old URL to its closest new equivalent. Paste the rules into Webflow's Site Settings → Publishing → 301 Redirects before you connect your domain. Redirect each page to its direct counterpart, never in bulk to the homepage, and avoid redirect chains.

2. Will I lose SEO if I migrate to Webflow?

Not if you do it correctly. Rankings drop after migrations because of missing redirects, lost meta data, or removed content not because of the platform. With a complete redirect map and faithful meta carryover, most sites recover to baseline within two to four weeks. Many improve, thanks to Webflow's cleaner code and faster load times.

3. How long should I keep 301 redirects after migrating?

Permanently, or at least 12 months. Google needs several crawls to transfer ranking signals. External sites will link to your old URLs for years. There is no cost to keeping redirects live in Webflow, so leave them.

4.Can I migrate to Webflow myself or do I need an agency?

Small sites - under about 20 pages with no complex SEO - are realistic DIY projects with this checklist. Sites with significant organic traffic, hundreds of URLs, or revenue riding on rankings usually justify professional help. One missed step in the redirect map can cost more than the migration.

5. Does Webflow change my URLs when I migrate?

Sometimes. CMS content must live under a collection folder, such as /blog/post-name. If your current posts live at the root level, those URLs change and need redirects. Static page URLs can usually stay identical.

6. How long does a Webflow migration take?

A typical marketing site of 15–50 pages takes three to six weeks. Small brochure sites take two to three. Large or content-heavy sites take six to ten weeks or more. The audit and redirect phase is non-negotiable regardless of size.

7. What is the most common reason migrations lose rankings?

An incomplete 301 redirect map. URLs that change without a redirect return 404s, and Google treats them as deleted content. A close second is a noindex setting accidentally left on from the staging site.