Webflow SEO Migration: What to Check Before Launch

Key takeaways

• Website migration SEO problems are cheap to fix on staging and expensive after launch, while search engines are recrawling the site.
• Crawl the old site and the staging site with the same settings, then compare titles, H1s, canonicals and status codes line by line.
• The most damaging launch mistakes are indexing settings: a page left on noindex, staging left indexable, or AI search crawlers blocked by default.
• Scripts and tags carried over from old builds slow sites down: cleaning them up took Blue J's Lighthouse performance score from 13 to 80.
• On MinIO's migration to Webflow, SEO had its own audit phase before launch, and “no critical SEO issues” was written into the acceptance criteria before work started.

This article covers the SEO checks to run in the last one to two weeks before a Webflow migration goes live. For the full project, from sign-off to 90 days after launch, use our enterprise Webflow migration checklist.

If you want the SEO side of your migration handled by a team that also builds in Webflow, see Beqi's SEO and AEO services.

Why check SEO before launch, not after?

Because every SEO mistake that reaches the live site costs traffic until search engines recrawl it, while the same mistake on staging costs nothing.

After launch, Google has to discover each change, process each redirect and re-evaluate each page. A missing redirect or a stray noindex tag can take weeks to show up in Search Console, and weeks more to recover. On staging, you find it with a crawl and fix it in minutes.

Kreshnik's input: Almost every discovery call we have touches on SEO: pages that were no-indexed by accident, rankings lost in an earlier migration, nobody sure how AI tools describe the company. When we trace it back, the cause is nearly always the same. SEO was checked after launch, by whoever had time, instead of before launch.

What should you compare between the old site and staging?

Every SEO element of every page that has traffic or links: status code, title, meta description, H1, canonical, indexing status and internal links.

Run the same crawler, with the same settings, on the live site and on staging. Export both to a spreadsheet and match them by page. Anything that changed should have a reason: a better title, a merged page, a retired section. Anything that changed without one is a bug.

Beqi tip: Crawl staging with the old site's URL list, not only by following links. Pages that exist on the old site but are missing from staging won't show up in a link based crawl, and those are the pages that need redirects.

How do you check redirects before they go live?

Validate the redirect map on staging, then test the live redirects in the first hour after launch.

• Every old URL has a destination: no row in the map is empty.
• Every destination exists: each new URL returns a 200 on staging, not a 404.
• No chains or loops: each old URL goes to its final destination in one step.
• No bulk redirects to the homepage: each page goes to its closest match.
• Rules in the right order: Webflow runs redirects in the order they were added, so specific rules go before wildcards.
• Export before importing: importing a redirect CSV in Webflow replaces all existing redirects.

Which indexing settings cause the most damage at launch?

The ones that are invisible on the page: indexing switched off where it should be on, or on where it should be off.

• Staging indexing: turn it off for the webflow.io subdomain under Site settings > SEO > Indexing, so staging never competes with the live site.
• Page-level noindex: the Sitemap indexing toggle in Page settings adds a noindex tag and removes the page from the sitemap. Check that it is only off on pages you meant to hide, including CMS items.
• Crawler controls: Webflow's indexing settings can generate robots.txt rules for groups of bots, including AI bots. Make sure search engines and AI search crawlers are allowed.
• Canonical and domain: set the global canonical URL to your production domain, and confirm one version (www or non-www) redirects to the other.
• Sitemap: check that the sitemap lists only pages you want indexed. Webflow now adds a last-modified date per page, which helps search engines find changes.

How do you check metadata and structured data on CMS templates?

Check the template bindings once, then check a sample of real items, because empty or unusual CMS fields are where templates fail.

• SEO title and description: bound to CMS fields in the template's settings, with a sensible fallback when a field is empty.
• Open Graph: title, description and image set for templates and static pages, so shared links don't show the wrong preview.
• Structured data: JSON-LD for articles, services, organization and FAQs that matches what is visible on the page. Test it with Google's Rich Results Test.
• Image alt text: carried over for images that carry meaning, not left empty after the import.

Beqi tip: If your JSON-LD pulls values from CMS fields, check those fields for double quotes. One quote in a summary or title breaks the JSON on that page, and because it sits in a template, the problem can repeat across every item without anyone noticing.

What should you check for AI search visibility before launch?

That AI search tools can still reach your content and find the same answers they used before.

• Crawler access: robots.txt and any firewall allow OAI-SearchBot, which OpenAI uses to show websites in ChatGPT search, and other AI search crawlers you want to appear in.
• Answer sections kept: FAQ blocks and direct answers often get dropped in a redesign. Check they survived on staging.
• Content in the HTML: text inside tabs or accordions should be in the page source, not loaded later by a script.
• A baseline of AI answers: ask ChatGPT, Perplexity, Claude, and Gemini what buyers ask about you, and save the answers to compare after launch.

How do you check page speed before launch?

Test the templates that carry the most traffic, on mobile and desktop, before the DNS switch.

Run Lighthouse or PageSpeed Insights on staging for the homepage, a service page, a blog post and a landing page. Look for oversized images, unused scripts and CSS carried over from the old site, and tag manager setups that load third-party tags before the content.

Our experience: Blue J came to us with a Webflow site built outside standard practices, a slow and buggy GTM setup, and no SEO or AEO work in place. We removed unused and overused scripts and CSS classes, cleaned up the GTM setup and fixed the site's SEO. Its Lighthouse scores went from 13 to 80 for performance, 55 to 91 for accessibility, 74 to 100 for best practices and 68 to 92 for SEO. New marketing pages now go live in two to three days instead of two to three weeks.

What goes on a pre-launch SEO sign-off?

One line per check, with how to test it and when it passes. Nothing launches until every line passes.

How did MinIO handle SEO before launch?

As a separate phase with its own pass criteria: technical SEO was audited and fixed before QA, and “no critical issues” was agreed in writing before the work started.

What did MinIO need?

MinIO needed its marketing site moved from a custom build to Webflow without changing how it looked or worked, and a search footprint that survived the move.

Which SEO checks were part of the migration?

• Every page: titles, meta descriptions and heading hierarchy.
• Site level: an XML sitemap, 301 redirects and canonical tags.
• Accessibility: an audit and fixes across all pages and images, including ARIA labels, alt text and keyboard navigation.
• Staging: changes reviewed on a staging domain before they reached the live site.

How was “done” defined?

The acceptance criteria were written into the agreement before work started: every page loads without errors in the major browsers, the SEO and accessibility audits report no critical issues, the CMS works, and every integration runs as specified. The plan gave SEO and accessibility their own three-day audit, followed by a full week of QA and client review before the DNS cutover.

MinIO: “Beqi's been a true technical partner for our web team—fast, flexible, and always willing to jump in where we need them. They've helped bring both structure and scalability to how the website is built behind the scenes, which has made it so much easier for our marketing team to move as fast as MinIO is growing.” Kelsey Kenyon, Head of Integrated Marketing

MinIO kept Beqi on as its Webflow team after launch, with redirects, titles and slugs kept in order as the site grows. Read the MinIO case study.

What should your team do next?

1. Book the SEO QA window: at least one week before launch, with time to fix what the crawl finds.
2. Crawl both sites: the old site and staging, with the same settings and the old URL list.
3. Fill in the sign-off table: one owner per line, and no launch until every line passes.
4. Plan the first hour after launch: who crawls the old URLs and checks redirects, indexing and tracking.

Beqi's SEO and AEO services include migration SEO, from the URL map to the first 90 days after launch.

Frequently asked questions

Can you test 301 redirects in Webflow before launch?

You can validate the redirect map before launch: every old URL has a destination, and every destination exists on staging. The redirects themselves take effect when you publish, so test them by crawling the old URL list in the first hour after launch.

Should the Webflow staging site be indexed?

No. Turn off staging indexing in Site settings so the webflow.io subdomain doesn't appear in search results or compete with your live site.

What breaks SEO most often in a CMS migration?

Changed URLs without redirects, SEO titles and descriptions that didn't carry over, and pages accidentally set to noindex. All three can be caught on staging before launch.

How long before launch should SEO QA start?

At least a week before launch, and longer for large sites. You need time for one full crawl of both sites, a round of fixes, and a second crawl to confirm.

Do we need to allow AI crawlers for SEO?

Not for Google rankings, but yes if you want to appear in AI search. OpenAI, for example, shows websites in ChatGPT search through OAI-SearchBot, which you can allow while still blocking the crawler it uses for model training.

How is pre-launch SEO different from the full migration checklist?

The checklist covers the whole project, from sign-off to 90 days after launch. Pre-launch SEO QA is one part of it: the technical checks on staging that decide whether search engines and AI tools see the new site correctly on day one.