How to Migrate to Webflow Without Losing SEO: A 10-Step Checklist

You can migrate to Webflow without losing SEO if you keep three things intact: every URL that has traffic or backlinks, the content and metadata on those pages, and the technical signals Google uses to understand your site. In practice that means a full URL inventory before you start, a 301 redirect for every URL that changes, and close monitoring in Google Search Console for the first 90 days after launch.

Most businesses that move to Webflow come from WordPress, Wix, Squarespace or an older custom CMS. The reasons are usually the same: the old site is slow, hard to edit, or needs a developer for every change. Webflow fixes those problems, but a careless move can wipe out years of search visibility in a week.

We have moved B2B, SaaS and service websites to Webflow at Made Tight, and the sites that keep their rankings all follow the same process. This guide walks you through it in 10 steps, from the audit you run before design starts to the checks you run three months after launch.

Key takeaways

• Rankings drop when URLs break, not when platforms change. Google ranks pages, not platforms. Keep the pages and their signals, and the platform switch is invisible to search engines.
• The URL inventory is the most important document in the project. Every URL with traffic, backlinks or conversions needs a clear destination on the new site.
• 301 redirects carry your rankings over. Set them up in Webflow before launch, test them on launch day, and keep them in place for good.
• Expect small fluctuations, not a crash. A well-planned migration usually sees minor movement for a few weeks, then stable or better rankings thanks to faster, cleaner pages.

Why websites lose rankings after a migration

A migration rarely hurts SEO by itself. Rankings drop because something Google relied on disappears or changes without notice. These are the most common causes we see when a business asks us to fix a migration done elsewhere:

• Broken URLs. Old pages return a 404 error because nobody redirected them. Every backlink pointing to those pages now leads nowhere, and the authority they carried is lost.
• Changed URL structure without redirects. A blog that lived at /2021/05/post-name now lives at /blog/post-name, but the old addresses were never mapped.
• Missing content. Pages are "simplified" during the redesign, and the sections that answered search queries are cut.
• Lost metadata. Title tags, meta descriptions, alt text and headings are not carried over, so pages lose relevance for the terms they ranked for.
• Technical settings left on default. The staging site stays blocked from indexing, the sitemap is never submitted, or canonical tags point to the wrong domain.
• Slower pages. Heavy images and unoptimized scripts make the new site slower than the old one, which hurts both rankings and conversions.

The good news: every one of these is preventable. The 10 steps below are built to catch each of them before launch.

Step 1: Benchmark your current SEO performance

Before anything changes, record where you stand today. Without a baseline you cannot tell whether a drop after launch is a real problem or normal movement.

Export these numbers and save them in a shared folder:

• Google Search Console: clicks, impressions, average position and the top 100 pages and queries for the last 12 months. Export the Pages and Queries reports as CSV files.
• Google Analytics 4: organic sessions, conversions from organic traffic and your top landing pages.
• Keyword rankings: the positions of your 20 to 50 most valuable keywords, from a rank tracker such as Ahrefs, Semrush or SE Ranking.
• Backlinks: the pages on your site with the most referring domains. These are the pages you can least afford to break.
• Core Web Vitals: your current scores from PageSpeed Insights for the homepage and three or four key templates.

Take screenshots too. A screenshot of your Search Console performance chart on the day before launch is the fastest way to compare later.

Step 2: Crawl the old site and build a complete URL inventory

The URL inventory is the single most important document in a migration. It lists every address on your current site, so nothing gets lost when the structure changes.

Use a crawler such as Screaming Frog, Sitebulb or the site audit tool in Ahrefs or Semrush, then combine the results with other sources, because a crawl only finds pages that are linked internally:

• The crawl: every page, image, PDF and file the crawler can reach.
• Your XML sitemap: pages that are listed but may not be linked anywhere.
• Search Console: pages that received clicks or impressions in the last 12 months.
• Analytics: landing pages that received any traffic, including from ads and email campaigns.
• Backlink tools: URLs that other websites link to, even if they no longer exist on your site.

Remove duplicates and keep one master spreadsheet. For each URL, note its status code, title tag, meta description, H1, organic clicks, backlinks and whether it converts. A typical 50-page business site often turns into 200 to 500 URLs once you include old blog posts, tag pages, PDFs and image files.

Step 3: Decide what to keep, merge or retire

A migration is a good moment to clean up, but every removal needs a reason and a destination. Go through the inventory and give each URL one of four labels:

• Keep: the page moves to Webflow with the same content, ideally at the same URL. This is the default for anything with traffic, backlinks or conversions.
• Improve: the page moves and gets better content, structure or design. Keep the topic and the main keyword the same.
• Merge: two or more thin pages on the same topic become one stronger page. The old URLs redirect to the new one.
• Retire: the page has no traffic, no backlinks and no business value. It still gets a redirect to the closest relevant page, never a 404 if it had any visits in the last year.

Be careful with blog content. Old posts often bring in a steady stream of long-tail searches that nobody notices until they are gone. If a post gets organic clicks, keep it, even if it feels outdated. You can refresh it later.

Step 4: Plan your URL structure in Webflow and map every old URL

The safest migration keeps every URL exactly as it is. If /services/branding exists today, it should exist tomorrow. When URLs stay the same, Google barely notices the move.

Webflow has one structural rule you need to plan for: CMS items always live under a collection folder. A blog post in Webflow sits at an address like /blog/post-name, and it cannot sit at the root of the domain. Many WordPress sites publish posts directly at /post-name or under dated paths like /2023/04/post-name. Those URLs will change, so they need redirects.

Add two columns to your URL inventory, "New URL" and "Redirect type", and fill them in for every row:

• Same URL: no redirect needed. Note it anyway, so you can test it on launch day.
• Changed URL: the old address gets a 301 redirect to the new one. Map it to the most relevant page, not to the homepage.
• Merged page: every old URL redirects to the single new page that replaces them.
• Retired page: redirect to the closest relevant page, such as the parent category or a related service page.

A few rules make the mapping cleaner:

• Keep slugs short and descriptive. If you must change a URL, use the move to remove dates, IDs and stop words, for example /blog/webflow-seo-checklist instead of /2022/03/17/the-complete-webflow-seo-checklist-for-2022.
• Match the old structure where you can. If your blog lived under /blog, create a Webflow collection called Blog so posts keep the same prefix.
• Avoid redirect chains. Every old URL should point straight to its final destination. A chain like A to B to C loses link value and slows crawling.
• Decide on www and trailing slashes now. Pick one version of the domain and stick to it in every redirect and canonical tag.

Step 5: Set up 301 redirects in Webflow

A 301 redirect tells browsers and search engines that a page has moved permanently. Google passes the ranking signals of the old URL to the new one, so a correct 301 is how your rankings travel with you.

In Webflow you manage redirects in Site settings, Publishing tab, 301 redirects. Each rule has an old path and a new path. You can:

• Add single redirects for individual pages, for example /about-us to /about.
• Use pattern redirects for whole groups of URLs. Webflow supports capture groups, so a rule like /blog/(.*) to /articles/%1 moves every blog post in one line, keeping each post's slug.
• Import redirects in bulk from a CSV file when you have hundreds of URLs to map.

A few details matter here:

• Use relative paths for the old URL. Write /old-page, not the full domain.
• Redirect to live pages only. A redirect that points to a page that does not exist yet becomes a 404 the moment you publish.
• Do not redirect everything to the homepage. Google treats mass redirects to the homepage as soft 404s, and the authority of those pages is lost.
• Keep redirects forever. Backlinks to old URLs keep working only as long as the redirect exists. There is no reason to remove them later.

If you are keeping your domain, you do not need Google's Change of Address tool. That tool is only for moves to a new domain. For a domain change, set up redirects first, then submit the change in Search Console under Settings, Change of address.

Step 6: Move your content without losing what ranks

Google ranks your pages for the words on them. If a redesign shortens a service page from 1,200 words to 300, that page will usually lose the searches it used to answer. The design can change completely, but the substance should come with it.

Static pages. Pages like your homepage, service pages and about page are rebuilt in the Webflow Designer. Copy the text from the old site into your new design, section by section. Keep the headings that carry keywords, and keep the questions and answers that bring in long-tail searches.

Blog posts and other CMS content. Webflow's CMS imports content from CSV files. The usual workflow:

1. Export your content from the old CMS. In WordPress you can export posts with a plugin that creates a CSV with titles, slugs, body content, dates, categories, featured images and SEO fields.
2. Create the collection in Webflow with a field for every piece of data you exported, including SEO title, meta description and featured image alt text.
3. Clean the CSV. Remove leftover shortcodes, page builder markup and broken embeds. These often break the formatting in Webflow's rich text field.
4. Import the CSV into the collection and map each column to its field.
5. Check a sample of posts in the Designer for formatting, images and internal links before you import the rest.

For very large blogs with hundreds of posts, a migration tool or a small script using the Webflow API saves days of manual work. Either way, keep each post's slug identical to the old one wherever you can.

Internal links. Old content is full of links to old URLs. Redirects will catch them, but internal links should point straight to the new address. After import, search your content for the old domain or old paths and update them.

Step 7: Carry over metadata, images and structured data

Content is only half of what Google reads. The other half sits in the page settings and the code.

Title tags and meta descriptions. Copy the exact title and description of every page that ranks. In Webflow you set them in each page's settings, and for CMS collections you can bind them to fields, so every post pulls its own SEO title and description. If you rewrite titles, do it after the migration has settled, not during it. Changing everything at once makes it impossible to tell what caused a drop.

Headings. Each page should keep one H1 that matches its main topic, with H2 and H3 headings in a logical order. Webflow lets you set the heading level on any text element, so the visual design never has to dictate the heading structure.

Images and alt text. Upload images in modern formats and at the size they display. Webflow can convert images to WebP or AVIF, which cuts file size without visible quality loss. Add alt text to every image that carries meaning. If your old images ranked in Google Images, keep their file names descriptive.

Open Graph data. Set the social sharing title, description and image for key pages, so links shared on LinkedIn and other networks still look right.

Structured data. Schema markup does not carry over automatically. Rebuild it in Webflow through custom code in page settings or in the CMS template. The most useful types for a business site are:

• Organization or LocalBusiness on the homepage, with your name, logo, address and social profiles.
• Service on service pages.
• BlogPosting on articles, with the author, date published and date modified.
• FAQPage on pages with visible questions and answers.
• BreadcrumbList for sites with deeper structures.

Structured data also helps AI search tools like ChatGPT, Perplexity and Google AI Overviews understand what your business does and which pages answer which questions.

Step 8: Set up technical SEO in Webflow before launch

Webflow handles much of technical SEO for you, which is one of the main reasons businesses move to it. Still, a few settings need a deliberate choice before you go live. Work through this list in Site settings and in the page settings of your main templates.

Indexing of the staging site. While you build, the site lives on a webflow.io subdomain. In Site settings, under SEO, turn on the option to disable indexing of the Webflow subdomain, so Google never indexes the staging copy as a duplicate of your real site.

Default domain. In the Publishing tab, add your custom domain and set the version you chose (with or without www) as the default. Webflow then redirects the other version automatically.

Canonical tags. Set the global canonical URL in the SEO settings to your default domain. Webflow then adds a self-referencing canonical tag to every page, which prevents duplicate content issues from tracking parameters and alternate URLs.

XML sitemap. Turn on the auto-generated sitemap. Webflow keeps it updated every time you publish. Exclude thin or utility pages, such as thank-you pages, password pages and internal style guides, using each page's sitemap setting.

Robots.txt. Keep it simple. Allow crawling of the whole site and reference your sitemap. Never copy a robots.txt from staging that blocks everything.

SSL. Webflow issues SSL certificates automatically. Make sure every internal link and canonical uses https.

404 page. Design a useful 404 page with your navigation, a search option or links to your main services. It will not save rankings, but it keeps visitors from leaving when they hit a link you missed.

Speed. Webflow hosts sites on a global CDN, so the platform is fast by default. What slows pages down is what you add: oversized images, autoplay videos, heavy animation libraries and third-party scripts. Compress images, lazy load anything below the fold, and load chat widgets and tracking scripts only where you need them. Then run PageSpeed Insights on the staging site and compare the scores with the baseline from Step 1. The new site should be at least as fast as the old one.

Tracking. Install Google Analytics 4, Google Tag Manager and any conversion pixels before launch, and confirm that forms and booking buttons still fire their conversion events. A migration that keeps rankings but breaks conversion tracking leaves you blind for weeks.

Step 9: Launch day checklist

Pick a launch day with low traffic, usually early in the week, and avoid launching right before a holiday or a big campaign. Have the person who built the site and the person who owns SEO available for the whole day.

Work through this list in order:

1. Freeze content on the old site. No new posts or edits from 24 hours before launch, so nothing gets lost between platforms.
2. Lower the DNS TTL a day or two before, so the domain switches over quickly.
3. Publish the Webflow site to your custom domain and update the DNS records Webflow gives you.
4. Check that the site loads on the main domain, with and without www, over https.
5. Test your redirects. Take the 50 most important old URLs from your inventory and open each one. Every one should land on the right new page with a single 301. Then run a crawler over the full list of old URLs and look for 404s, redirect chains and 302s.
6. Check indexing settings. Confirm that the live site is not blocked by robots.txt or a noindex tag, and that canonical tags point to the live domain.
7. Submit the new sitemap in Google Search Console and in Bing Webmaster Tools.
8. Request indexing for the homepage and your five to ten most important pages with the URL Inspection tool in Search Console.
9. Test forms and conversions. Submit every form, click every booking button and confirm that the leads arrive and the conversion events fire in GA4.
10. Keep the old site available in a private backup for a few weeks, in case you need to check old content or settings.

Step 10: Monitor and fix in the first 90 days

The work does not end at launch. Google needs time to recrawl your site and process the redirects, and that is when problems surface.

Week 1: check every day.

• Search Console, Pages report: watch for spikes in "Not found (404)" and "Page with redirect". A few are normal. Dozens mean a group of URLs was missed.
• Search Console, Crawl stats: confirm that Google is crawling the new site and that most responses are 200 or 301.
• Analytics: compare organic sessions and conversions with the same days a week earlier.
• Fix broken URLs immediately. Add a redirect for every 404 that had traffic or backlinks.

Weeks 2 to 4: check twice a week.

• Rankings: compare your tracked keywords with the baseline. Small movements of a few positions are normal while Google reprocesses the site.
• Top pages: compare clicks per page with your benchmark export. A page that lost most of its clicks usually points to a missing redirect, missing content or a changed title.
• Backlinks: check that your most-linked old URLs redirect correctly. If an important site links to an old URL, you can ask them to update the link.

Months 2 and 3: check weekly.

• Trends, not days: compare four-week periods with the same period before launch.
• Core Web Vitals: check the field data in Search Console once enough real visits have been recorded.
• Content improvements: once traffic is stable, start the improvements you held back during the migration, such as rewriting titles, refreshing old posts and adding internal links.

After three months, most well-planned migrations are back at the baseline or above it. Webflow sites often gain over time, because pages load faster and marketing teams publish more when editing is easy.

8 migration mistakes that cost rankings

These are the problems we see most often when a business asks us to rescue a migration that went wrong.

• Starting the redirect map after launch. Redirects added a week later still help, but by then Google has already found the 404s and backlinks have stopped passing value. Map every URL before you publish.
• Redirecting everything to the homepage. It looks tidy, but Google treats it as a soft 404. Each old page should point to its closest match.
• Forgetting non-page URLs. PDFs, images, old landing pages from ad campaigns and pages linked from email signatures all have traffic or backlinks too.
• Leaving staging settings on. A noindex tag or a blocking robots.txt copied from the staging site can drop the whole site from Google within days.
• Changing URLs, design, content and domain at once. Every change adds risk. If you can, migrate first and improve second, so you can see what affects rankings.
• Cutting content for the sake of design. A minimal service page looks clean, but if it lost the paragraphs that answered buyer questions, it will lose the searches too.
• Ignoring internal links. Old links that hop through redirects slow down crawling and dilute the signals between your own pages.
• Not tracking conversions. Traffic can look fine while forms quietly stop working. Test every form and booking button on launch day.

How long does it take to recover rankings after a migration?

With a complete redirect map and the content intact, most sites see small fluctuations for two to six weeks while Google recrawls and processes the redirects. After that, rankings usually settle at the old level or improve. Large sites with thousands of URLs can take two to three months to stabilize, because Google needs more time to recrawl everything.

A drop that lasts longer than eight weeks, or a drop of more than 20 to 30 percent in organic clicks, almost always points to a specific problem: missing redirects, missing content, indexing blocks or a slower site. Go back to the URL inventory, compare the top pages before and after, and fix the pages with the biggest losses first.

If you are moving to Webflow from WordPress and still weighing the platforms, our guide to Webflow vs WordPress compares editing, SEO, security and running costs.

FAQ

Will I lose SEO if I move my website to Webflow? Not if the migration is planned. Rankings depend on your pages, content and links, not on the platform. Keep your URLs where you can, redirect the ones that change with 301s, and carry over your content and metadata, and Google treats the move as the same site in a new home.

How do I set up 301 redirects in Webflow? Go to Site settings, open the Publishing tab and find the 301 redirects section. Add the old path and the new path for each page, use pattern rules with capture groups for whole folders, or import a CSV file for large lists. Publish the site, then test the most important redirects in a browser.

Can I keep the same URLs when I move from WordPress to Webflow? For most static pages, yes. Blog posts and other CMS content in Webflow live under a collection folder, such as /blog/post-name, so posts published at the root of a WordPress site will need new URLs and 301 redirects.

How long does a migration to Webflow take? For a typical business website with 20 to 60 pages and a blog, plan four to six weeks for design, build, content migration and testing. The SEO preparation in Steps 1 to 4 should start before design, not after.

Do I need to tell Google I moved to Webflow? If you keep the same domain, no. Submit your new sitemap and request indexing for key pages in Search Console. If you also change your domain, use the Change of Address tool after your redirects are live.

Can Made Tight migrate my site to Webflow? Yes. We handle the full migration: URL inventory, redirect map, custom design, Webflow build, content and CMS import, technical SEO setup and monitoring after launch. We also look after hosting and maintenance once the site is live.

Planning a move to Webflow?

A migration is the best chance in years to fix a slow, hard-to-edit website. It is also the easiest moment to lose the traffic you built. We plan every Webflow migration around your existing rankings first, then design and build a site your team can run without a developer.

Book a 30-minute intro call and we will review your current site and what it would take to move it, or see how we work as a Webflow agency. After launch, our hosting and website maintenance plans keep the site fast and secure.

Next week: How to choose a Webflow agency.