The biggest fear in a WordPress to Webflow migration is losing the search traffic you have spent years building. It is a reasonable fear, because migrations are one of the few events where a site can lose a large share of its organic traffic in a matter of days. But the losses are rarely caused by the platform. They come from a short list of avoidable mistakes: URLs that change without a redirect, metadata that does not make the journey, and settings left over from staging.
This guide walks through the whole process from an SEO point of view: why rankings move during a migration, what to capture before you touch anything, the WordPress-specific details that catch people out, how to launch safely, what to monitor afterwards and how to diagnose a drop if one happens. If you want the build side of the project as well, my WordPress to Webflow migration guide covers the practical steps in order.
Will Migrating from WordPress to Webflow Hurt SEO?
It does not have to. Search engines rank pages, not platforms. Google has no preference for WordPress over Webflow or the other way around. What it evaluates is the page at a given URL: the content, the links pointing to it, how the rest of the site links to it, and how quickly and reliably it loads. If a migration keeps those things intact, rankings should hold. If it breaks them, rankings fall, whatever the platform.
That is why a migration is a risk-management exercise more than a design exercise. Every URL that ranks today carries accumulated signals: backlinks from other sites, internal links, a history of clicks. When a URL changes, those signals only follow if you tell search engines where the page went, which is the job of a 301 redirect. When content, titles or headings change at the same moment, you add a second variable and make any drop much harder to explain.
Some short-term movement is normal. Google has to re-crawl the site, process the redirects and reassess the pages, so you may see positions wobble for a few weeks. What you are watching for is a sustained decline on specific pages, because that almost always has a cause you can find and fix.
The Most Common Causes of Traffic Loss
Nearly every post-migration traffic drop I have seen discussed traces back to one or more of these:
- Missing or wrong redirects: old URLs return 404 errors, or all redirect to the homepage instead of the matching page. Redirecting everything to the homepage is treated by search engines much like a 404.
- Changed URL structure: posts moved from /post-name/ to /blog/post-name without a redirect.
- Lost metadata: titles and descriptions generated by an SEO plugin were not carried across, so Google rewrites them or ranks the page differently.
- Noindex left on: pages, or the whole site, left blocked from search after launch.
- Robots.txt blocking: a rule copied over from, or left behind by, staging.
- Forgotten URL types: category, tag, author and pagination URLs that were indexed but not redirected.
- Content changes: pages rewritten, shortened or removed at the same time as the move.
- Lost structured data: schema that a WordPress plugin generated and the new site does not have.
- Broken internal links and images: links still pointing at the old site, or media that disappeared with it.
- Redirect chains and loops: multiple hops that slow crawling and dilute signals.
Before You Migrate: Build the Baseline
The work you do before the build decides how safe the launch is. You want a complete record of what the site looks like and how it performs today, so you can compare against it later.
1. Benchmark performance
Export your pages and queries from Google Search Console, with clicks, impressions, click-through rate and average position. Take at least a few months of data, and ideally a comparison with the same period last year if your business is seasonal. Also export your top landing pages and conversion data from your analytics. This is the evidence you will use to judge whether the migration worked.
2. Crawl the existing site
Use a crawler such as Screaming Frog to capture every URL with its status code, title, meta description, H1, canonical tag and word count. A crawl finds pages you had forgotten about, such as old landing pages or attachment pages, and gives you a record of what each page said before the move.
3. Combine your URL sources into one list
A crawler only finds pages that are linked internally. Pages can still receive traffic or backlinks without being linked from anywhere. So build a master list from several sources: the crawl, your current XML sitemap, the pages report in Search Console, landing pages in analytics and, if you have access to one, a backlink export from a tool such as Ahrefs or Semrush. Remove duplicates and you have the list of URLs that matter.
4. Decide what happens to each URL
Go through the list and put every URL into one of four groups:
- Keep: the page moves to Webflow at the same URL.
- Change: the page moves but its URL must change, so it needs a 301 redirect.
- Merge: several thin pages become one stronger page, and the old URLs redirect to it.
- Retire: the page is removed. If it has traffic or backlinks, redirect it to the closest relevant page. If it has neither, a 404 or 410 is fine.
Rank your pages by traffic, conversions and backlinks, and give the top tier the most care. For a typical site, a small share of pages produces most of the organic traffic, and these are the ones you cannot afford to get wrong.
5. Hold back content changes
It is tempting to rewrite while you rebuild. Resist it. If rankings move after launch and you changed the design, the URLs and the copy all at once, you cannot tell which change caused it. Migrate the content faithfully, let the site settle, and then make improvements in a second phase where each change can be measured.
My website migration checklist turns these steps into a plan you can follow, and the post on auditing your Webflow site's SEO before and after a migration goes deeper on the audit itself.
WordPress-Specific Details That Catch People Out
WordPress generates more URLs than most people realise, and plugins add more. Here are the ones to check before you build the redirect map.
Permalink structure
WordPress lets you choose any permalink pattern: /post-name/, /2023/05/post-name/, /category/post-name/ and so on. Webflow CMS items always sit under a collection folder, for example /blog/post-name, and static pages sit at the root. That means a post that lived at the root of a WordPress site will have a new URL in Webflow unless you work around it. Where the URL must change, plan the redirect rule up front. If you have a lot of posts under a predictable pattern, one wildcard redirect can often cover the lot.
Category, tag, author and date archives
WordPress creates archive pages for categories, tags, authors and dates. Some of these may be indexed and receiving traffic, particularly category pages. Decide whether each archive type has a Webflow equivalent, such as a filtered blog page or a category template, and redirect accordingly. Tag and date archives are usually thin, so redirecting them to the main blog page is normal.
Pagination, feeds and attachment pages
Paginated URLs such as /blog/page/2/ and feed URLs such as /feed/ may appear in your crawl or in Search Console. Attachment pages, where WordPress gives each uploaded image its own URL, are often indexed by accident. Give each of these a sensible destination rather than letting them 404 if they have any history.
Parameter and ID URLs
Older WordPress sites sometimes answer to ID-based URLs like ?p=123 or ?page_id=45. Query-string URLs cannot be redirected with a simple path rule, so check whether these appear in your data. If they do not, you can ignore them.
Media and uploads
Images in WordPress live under /wp-content/uploads/. If other sites hotlink your images, or if your images rank in Google Images, those URLs will disappear after the move. It is not worth redirecting every upload, but it is worth checking whether any images drive meaningful traffic.
Carrying Over Metadata, Content and Structured Data
Titles and descriptions
Most WordPress sites rely on Yoast, Rank Math or a similar plugin for page titles and descriptions. Those values live in the plugin's fields, not in the standard post content, so they are easy to leave behind. Export them alongside the content, or capture them from the crawl, and import them into SEO title and description fields in your Webflow CMS collections. Then bind those fields in the collection template's page settings, so every item gets its own title and description. For static pages, enter them in each page's settings.
Canonical tags and headings
Check that each page has a self-referencing canonical tag, and that it points to the version of the URL you want indexed. Check that each page has one H1 and that the heading order is logical. Rich text imports sometimes carry over odd heading levels from the old editor.
Internal links and images in content
Posts often contain absolute links back to the old domain and links to old URL patterns. After import, search your content for the old paths and update them so visitors do not pass through redirects unnecessarily. Make sure every image has alt text, because alt text does not always survive an import cleanly.
Structured data
Plugins like Yoast output Organization, Article and breadcrumb markup automatically. Webflow does not add equivalent schema for you, so decide which types you had and recreate them. For CMS templates you can add JSON-LD in custom code and bind dynamic fields such as the headline and publish date. Test the result with Google's Rich Results Test.
Setting Up Redirects in Webflow
Redirects are the single most important SEO task in a migration. In Webflow they live in Site settings → Publishing → 301 redirects. You can add rules one at a time, use wildcards to cover a whole folder, or import a CSV for large lists. Importing a CSV overwrites the redirects you already have, so export the current list before you import. Redirects only take effect after you publish.
A few principles keep redirects clean:
- Redirect each old URL to the closest equivalent page, not to the homepage.
- Point redirects at the final destination URL so there are no chains.
- Test wildcards on a sample before relying on them.
- Keep the redirects in place for at least a year, and preferably as long as the site exists.
My Webflow 301 redirects guide has the syntax and worked examples.
Launch Day Checks
Test everything on the Webflow staging domain first, then run through this list around the switch:
- Confirm the live site is not set to noindex and that robots.txt allows crawling.
- Open a sample of old URLs, especially your top pages, and check that each returns a single 301 to the right page.
- Check that titles, descriptions, canonical tags and structured data are present on key pages.
- Test internal links, forms and images.
- Submit the new sitemap in Search Console.
- Confirm analytics and conversion tracking are firing.
- Keep the old WordPress site available, and backed up, until DNS has fully switched and you have confirmed everything works.
Where you can, launch at a quiet time for your traffic and avoid combining the migration with a domain change, since a domain change is a second, separate risk. If you cannot afford a hard cutover, my post on migrating to Webflow in stages with a reverse proxy explains how to move section by section.
After Launch: What to Monitor
First week
- Watch the Pages report in Search Console for new “Not found (404)” and “Redirect error” entries.
- Check that important pages are being indexed.
- Crawl the live site again for broken links and redirect chains.
First few weeks
- Compare clicks and impressions for your top pages against your benchmark.
- Look at queries that lost position and inspect the pages behind them.
- Fix any 404s that still receive traffic or have backlinks.
Following months
- Review performance monthly and watch for gradual declines.
- Then start the improvements you held back, such as content updates and speed work. My 7 best SEO practices for your Webflow website is a good place to start.
If Traffic Drops: How to Diagnose It
- Find which pages lost traffic by comparing before and after in Search Console, rather than looking at the total. A site-wide drop and a drop on ten pages have very different causes.
- Check the status of those URLs. Are they redirecting, returning 404, or blocked?
- Check indexing. Use URL inspection to see whether Google can crawl and index them.
- Compare content and metadata between the old and new versions of the page.
- Check redirect quality. Make sure each old URL goes to the closest relevant page, with no chains.
- Check site-wide settings such as noindex, robots.txt and canonical tags.
- Fix, then request re-crawling of the most important URLs.
Recovery takes time, because Google has to re-crawl and reassess the pages. The sooner the cause is fixed, the sooner the pages settle.
Do You Need Help?
I'm Nikolai, a Webflow Premium Partner who migrates websites for SaaS companies. I handle the URL audit, redirect map and post-launch monitoring so you keep your rankings through the move. See my Webflow migration services or get in touch.
Frequently Asked Questions
Will migrating from WordPress to Webflow hurt my SEO?
Not if the migration is done carefully. Keep URLs where possible, redirect every URL that changes, and carry over your titles, descriptions and structured data.
Why did my traffic drop after migrating to Webflow?
The usual causes are missing redirects, changed URLs, lost metadata, noindex or robots.txt settings left on, and content changes made at the same time as the move.
How long does it take for rankings to recover after a migration?
It varies with the size of the site and how quickly issues are fixed. Some movement is normal in the first weeks. A sustained drop on important pages means something needs fixing.
Do I need to keep my WordPress site after migrating?
Keep it available, and backed up, until DNS has fully switched and you have confirmed everything works. After that you can turn it off.
Should I change my content while migrating from WordPress to Webflow?
Avoid it where possible. Making large content changes at the same time makes it hard to tell what caused any ranking change. Improve content after the migration settles.
How do I redirect WordPress URLs in Webflow?
Add 301 redirects under Site settings → Publishing → 301 redirects, using wildcards for patterns, then publish the site.
What happens to my WordPress category and tag pages?
Decide whether each has a Webflow equivalent. Category pages that receive traffic should redirect to a matching category view; thin tag and date archives can redirect to the main blog page.
