Why SEO preservation matters during a WordPress-to-Webflow migration

Most WordPress-to-Webflow migrations lose rankings not because of the platform change, but because of when SEO enters the conversation. By the time someone asks, "Did we handle the redirects?" the damage is already done. And the stakes are higher than they used to be: a site that loses crawlability during migration doesn't just drop down the page on Google. It becomes harder for AI systems to find, parse, and cite. The visibility hit compounds in ways that weren't true two years ago.

The honest solve is to treat migration risk as a legitimate constraint, not a last-minute checklist item. The teams that lose rankings after migration are almost always the ones that treated SEO as a box to tick after the site was built, rather than something that shapes every build decision from the start.

The pre-migration SEO audit most teams skip is why rankings drop after launch

Before you move a single page, you need a complete map of what you're migrating and what's currently earning traffic. This isn't optional, and it's not something to do over a weekend. A thorough pre-migration audit typically takes about a week for a site of moderate complexity.

The audit should document, at minimum:

• URL inventory: Export every indexed URL using a crawl tool like Screaming Frog or Sitebulb. Include URLs that aren't in your sitemap but are indexed. These are often the ones that get missed in redirect mapping, and they're usually the most surprising ones: old utility pages, one-off landing pages that were set up years ago and never touched again. Clients rarely know these exist until you show them the crawl. That bloat needs to be accounted for before you build your redirect map, not after.
• Traffic by URL: Pull 12 months of organic traffic data from Google Search Console, filtered by page. Identify which URLs are driving traffic, not just which ones you think are important. These are the pages where redirect errors are catastrophic, not just inconvenient.
• Ranking keywords by page: For your top 20 traffic pages, document the primary keywords each page ranks for. This gives you a baseline to measure against post-launch and helps you prioritize monitoring once the new site is live.
• Backlink targets: Export your backlink profile and identify which URLs have meaningful external link equity pointing at them. These pages need precise redirects, not approximations.
• Metadata inventory: Export all title tags, meta descriptions, H1s, and canonical tags. In WordPress with Yoast SEO, you can pull this data directly from the Yoast export or via a crawl. Every line of this data needs to be reproduced exactly in Webflow, and the only way to do that without omissions is to have the full inventory before you build.
• Schema markup: Document any structured data currently implemented on your WordPress site, including Organization, Article, FAQ, and BreadcrumbList schemas. Webflow doesn't replicate these automatically.

One additional thing to look for during the audit: subdomains and externally hosted tools. If parts of the existing site live on a subdomain or are custom-built and hosted in a CDN outside the main platform, those are often the hardest assets to migrate. The problem is rarely technical. More often, nobody knows who owns them or has access credentials. Catching these early saves weeks of back-and-forth during build.

How to export your WordPress site and map 301 redirects

WordPress gives you two primary export options: the native WordPress XML exporter and the REST API. For blog content migration, the XML exporter is the more practical starting point. But for more complex CMS structures, Finsweet's CMS Import tool is the most reliable bridge into Webflow's native CMS.

Before import, though, expect to spend real time cleaning the data. WordPress exports carry years of accumulated inconsistencies: encoding translations that produce nonsensical character strings in the new platform, formatting from old page builders that don't convert cleanly, and content structures that have no equivalent in Webflow. HTML tables are a common example. Webflow's rich text editor doesn't support HTML tables natively, so any content that relied on them has to be handled through a custom embed. Attempting to automate that conversion produces unpredictable results. The reliable approach is to do it manually.

On most enterprise migrations, a significant share of the total project time goes to data cleaning and transformation, not to building. Teams that account for this in the project plan are far less likely to blow their timelines.

Redirect mapping is where most migrations lose their SEO equity, and the content export is the easier part of the two.

Here's the rule: every URL that currently exists in Google's index needs a 301 redirect to the closest equivalent page on the new site. The redirect mapping spreadsheet should contain three columns: the old URL, the new URL, and the redirect status. Before launch, every row needs a populated destination.

Redirect complexity scales with site architecture. On straightforward sites, mapping is tedious but not technically difficult. The harder scenarios involve CMS-driven content that previously lived under multiple sub-directories. If a site had, say, a Services collection where individual pages appeared under both /industries/services/ and /solutions/services/ depending on context, that structure can't be replicated in Webflow. 

Webflow requires a single collection to live under a single path. So before the redirects can be configured, you have to make an architectural decision: what is the new, unified directory structure for this content? That decision has SEO implications, and it needs input from both the development side and the strategy side. For a client like Bell, where this kind of multi-level CMS structure was in play, the redirect mapping process included that upstream decision before a single redirect was written.

A few specific errors that are common enough to call out by name:

• Redirect chains: A chain occurs when URL A redirects to URL B, which redirects to URL C. Each hop dilutes link equity and slows crawl speed. Chains longer than two hops should be collapsed into direct redirects before launch.
• Redirect loops: URL A redirects to URL B, which redirects back to URL A. These cause crawlers to abandon the URL entirely. They're more common than you'd expect, especially when a CMS migration changes URL structures, and someone tries to preserve both old and new versions of the same slug.
• Redirects to the homepage: When a page doesn't have a clear equivalent on the new site, redirecting to the homepage is tempting. Resist it. A homepage redirect signals to Google that the content is gone, not moved. If there's no equivalent page, redirect to the most topically relevant page on the new site. If that page doesn't exist yet, build it.

In Webflow, 301 redirects are managed directly in the site settings under the Hosting tab. You can add them manually or import a CSV. For sites with more than 50 redirects, the CSV import is worth the setup time.

Transferring metadata, schema, and on-page SEO elements

Webflow has solid native SEO controls, including per-page title tags, meta descriptions, Open Graph fields, and canonical URL management. None of this transfers from WordPress automatically. You're rebuilding it from the inventory you created in the audit phase.

A few areas where teams consistently underinvest:

Schema markup

Webflow doesn't have a built-in schema editor. You'll need to add JSON-LD schema blocks via custom code embeds or use a third-party integration. For sites with significant blog content, Article schema on every post is worth implementing from day one. For service pages, add Organization and Service schema. For FAQ content, add FAQPage schema around any FAQ sections.

Schema complexity varies significantly by site. For clients with established, sophisticated schema setups, including dynamic canonical structures tied to CMS fields, the migration requires careful custom code work. Webflow recently enabled pulling CMS fields into JSON-LD schema directly, but some builds required workarounds to maintain the same dynamic, automatic behavior that existed on the old platform. A migration that carries over your rankings but drops your schema is one that preserves your Google traffic while quietly exiting AI search. Getting the schema right is technical work, and it matters for both.

H1 structure

Webflow gives designers significant layout flexibility, which sometimes results in visual headings that aren't semantically coded as H1s. Before launch, crawl the new site and verify that every page has exactly one H1 that matches or closely reflects the primary keyword target for that page.

Image alt text

Alt text from WordPress doesn't migrate into Webflow's asset manager. If your image alt text contains keywords with meaningful search value, that needs to be manually re-entered for every asset.

Canonical tags

Webflow sets canonical tags automatically based on the published URL. For most sites, this is correct behavior. For sites with staging environments, URL parameters, or paginated content, verify that canonicals are resolving correctly after launch, not before.

The 60-day post-launch window is your highest-leverage moment

A temporary ranking decline after migration is normal. Google needs to recrawl and re-evaluate the new site's structure, and that process takes time. Most sites see rankings stabilize within 60 to 90 days when the migration is executed cleanly.

The mistake teams make is treating this as a waiting game. The 60-day window after launch is the highest-leverage period for catching and correcting issues before they become entrenched. Post-launch SEO auditing for 404s, broken links, and orphan pages should be a standard part of the process, not an optional follow-up. Addressing those issues within the first two weeks matters more than most teams realize.

‍

One metric worth monitoring that most post-migration checklists skip is AI referral traffic. Ag-nts data from Edgar Allan's Webflow client base shows AI-driven referral traffic fluctuating significantly in the weeks after a major site change. If AI systems that were previously citing your content stop citing it post-migration, the likely cause is crawlability issues or schema that didn't carry over correctly.

Structuring your Webflow site for AI search visibility

Most WordPress-to-Webflow migration guides stop at traditional SEO, and that's no longer sufficient.

AI systems, including ChatGPT, Perplexity, and Google's AI Overviews, are increasingly the first point of contact for buyers researching vendors and solutions. If your site isn't structured to be findable and extractable by these systems, you're invisible to a growing share of your audience at exactly the moment they're closest to making a decision.

The structural factors that determine AI citability overlap with traditional SEO but are not identical.

1. Extractable summaries

AI systems favor content with clear, concise summary statements near the top of the page. A TL;DR section, a structured intro paragraph, or a well-written meta description increases the probability that an AI system will extract and cite your content accurately.

2. FAQ schema

FAQ Page structured data is among the most consistently cited content formats in AI search. Every substantive page on your site should include an FAQ section with at least three to five questions written in the language buyers use, paired with direct, two-to-three sentence answers.

3. Clear entity definition

AI systems need to understand what your company does, who it serves, and why it's relevant before they'll cite it confidently. An "About" page or service page that defines your organization with specific, named claims, rather than vague positioning language, gives AI systems the entity clarity they need to include you in relevant answers.

4. Content that names names

Specific companies, specific tools, specific outcomes. Generic positioning language is invisible to AI systems. Specific claims with named companies and real outcomes are citable. The specificity is the point.

This is what Edgar Allan’s Visibility Engineering and Optimization methodology addresses in full: building and optimizing sites so they're legible to both human visitors and the AI systems that increasingly mediate what those visitors find first.

Partner with Edgar Allan for your WordPress to Webflow migration

WordPress-to-Webflow migration is not a template project. The SEO preservation work, the redirect mapping, the schema implementation, the post-launch monitoring, and the AI visibility optimization all require someone who understands how these systems interact, not just how to use the tools.

Edgar Allan has managed enterprise WordPress-to-Webflow migrations for companies including Walker & Dunlop, GeneDx, and others who had both significant SEO equity to protect and ambitious performance targets to hit on the other side. See the work here.

If you're planning a migration or evaluating the timing, get in touch. The window to structure a new site for AI visibility closes faster than most teams expect, and it's much harder to reopen after launch.

Webflow Migration SEO Checklist