How to Migrate a Website (and WordPress) Without Losing SEO

Every migration conversation I have eventually arrives at the same sentence, usually said with real fear: “We can’t afford to lose our rankings.” It’s the right thing to be afraid of. For a lot of the funded companies we work with, organic search is a meaningful chunk of pipeline, and a botched migration can wipe out years of accumulated authority in a weekend.

So let me be direct about the good news and the bad news. The good news: a WordPress migration does not have to cost you a single position in search. The bad news: keeping your rankings is entirely down to discipline you apply before launch, and most teams don’t apply enough of it.

This isn’t theory for me. In October 2026 we moved our own site from Framer to Astro with this exact process: a crawl of every URL, a 116-row redirect map, and daily checks after launch. Google’s clicks didn’t dip: 190 to 300 a week before the move, 354 in the first four days after it (the launch film added some brand searches, so I read that as “held”, not “grew”). A 404 tracker caught a few old paths we’d missed, such as /blog, and we redirected them in the first days. That’s the whole job: the search side of a migration is the part you cannot wing.

Here’s exactly how to protect SEO through a move off WordPress. (If you’d rather hand the move to a team, these are the steps our website migration services follow.)

First, Understand Why Migrations Lose Rankings

You can’t prevent a problem you don’t understand. Migrations cost traffic through three mechanisms, and only three:

1. Broken URLs. Google has indexed your current URLs and assigned authority to them. External sites link to those exact URLs. If a URL changes and there’s no redirect, every bit of ranking power pointing at it hits a dead end. This is the number one cause of migration traffic loss, by a wide margin.

2. Lost on-page signals. Title tags, meta descriptions, heading structure, alt text, and schema represent years of on-page optimisation. They don’t carry themselves to a new platform. If your rebuild doesn’t reproduce them deliberately, you’ve discarded them.

3. Crawl and indexing problems. A missing sitemap, a stray noindex tag, a robots.txt that blocks the new site, or broken canonicals can stop Google from properly crawling and indexing the new pages.

That’s the entire risk surface. Control these three and you keep your rankings. Everything below is how.

The Pre-Migration SEO Audit

This is where the work actually lives. Do it thoroughly and the rest is execution.

Crawl everything. Screaming Frog or Ahrefs Site Audit. Export every URL the site has: pages, posts, archives, PDFs. This is your master list. For a quick first list from your sitemap, our free migration planner shows which URLs keep their path on the new platform and which need a 301.

Identify your traffic-driving pages. From Google Search Console, export your top organic landing pages over the last 12 months. These are sacred. They get the most careful handling in the migration.

Map your keyword rankings. Pull current positions for your important terms from Ahrefs and Search Console. This is your baseline: without it, you can’t tell whether anything actually moved after launch.

Audit your backlinks. Find which specific URLs have external links pointing at them. A page with twenty referring domains carries authority you must preserve at that URL or redirect cleanly. Losing it is losing the authority.

Document on-page SEO. For every page worth keeping: title tag, meta description, H1, and structured data. You’re going to reproduce all of it.

I’ll repeat the thing I tell every client: nearly every migration that loses traffic traces back to a thin or skipped audit. The audit is not the boring prelude to the real work: it is the work.

Build a 301 Redirect Map for Every Single URL

If you take one thing from this post, take this.

A 301 redirect is a permanent redirect, and it passes the large majority of a page’s ranking authority to its new location. It is the mechanism that lets you change URLs without losing rankings. Build one for every URL that changes.

In short: start from your full crawl, give every old URL one of three outcomes (shown below), never mass-redirect to the homepage, and make every redirect a single hop. The full method, from finding every URL to testing the rules after launch, is in our guide on how to build a 301 redirect map.

One decision per old URL

Every old URL from the crawl

• Same URL

  Keep it

  No redirect

• Changed URL

  301 to the new URL

• Retired

  301 to the closest relevant page

Never mass-redirect to the homepage

Both Webflow and Framer handle 301s natively. The platform isn’t the hard part. The completeness of the map is.

Preserve On-Page SEO Deliberately

Nothing about your on-page optimisation transfers automatically. On the new site:

• Reproduce every title tag and meta description from your audit.
• Keep your heading structure intact: one H1 per page, a logical hierarchy below it.
• Re-add image alt text.
• Rebuild structured data on the pages that had it.
• Restore internal links. WordPress sites build up internal links over years, and a clean rebuild usually loses them. Internal links pass authority and signal topical structure: rebuild them, don’t lose them.

Get the Technical Foundation Right

• Submit a fresh XML sitemap in Search Console at launch.
• Set canonical tags correctly so you don’t create duplicate-content confusion.
• Check robots.txt: make sure nothing blocks the new site and no leftover staging noindex tags survive to production. A stray noindex is one of the fastest ways to vanish from search.
• Verify the new site in Search Console before launch if the platform allows it.
• Confirm Core Web Vitals on the live pages. Speed is a ranking factor and migrations are a chance to improve it.

Launch Carefully, Then Watch Like a Hawk

Launch early in the week so you’re around to catch problems. Implement all redirects at go-live. Then, for the first three to four weeks:

• Submit the sitemap and request indexing of priority pages.
• Monitor organic traffic daily against your baseline.
• Watch the Coverage report for crawl errors and unexpected 404s.
• Re-crawl the live site to catch missed redirects and broken links.
• Track rankings for your priority keywords.

Expect a small wobble in week one: Google needs to re-crawl and re-index, and that takes a little time. That’s normal and it recovers. What’s not normal is a decline that keeps going past a few weeks. That means something is broken, and in my experience it’s almost always a redirect gap. This is exactly the signal we caught on our own relaunch, and catching it early is the difference between a footnote and a crisis.

The order that keeps rankings

1. 01

   Audit

   Crawl every URL, export top pages, rankings and backlinks.

2. 02

   Redirect map

   A single-hop 301 for every changed or retired URL.

3. 03

   On-page SEO

   Titles, metas, headings, alt text, schema, internal links.

4. 04

   Technical checks

   Sitemap, canonicals, robots.txt, no stray noindex.

5. 05

   Launch and watch

   Early in the week, then daily checks for 3 to 4 weeks.

←→

Moving From Framer, Webflow, Wix or Squarespace

Nothing in this guide is specific to WordPress. The three ways rankings get lost are the same on every platform, and so is the fix: a full URL inventory, a single-hop 301 for every path that changes, on-page signals carried over page by page, and a technical check before launch. What changes from one platform to the next is where the URLs break.

• Framer. Paths can usually stay the same, but images and files live on Framer’s CDN and stop working when the plan ends, so every asset has to move too. We moved our own site from Framer to Astro in six days: 116 old URLs were mapped before the switch, 65 kept their path, 43 got a 301 and 8 were retired on purpose. Teams that outgrow Framer’s CMS usually go from Framer to Webflow instead.
• Webflow. Most Webflow paths can stay exactly as they are, so the URL risk is low to medium. The work is in exporting every CMS collection while the old site is live and checking each item after import. See Webflow to Framer and Webflow to Astro.
• Wix. Wix URL patterns such as /post/ always change, so every blog URL needs a redirect. That makes Wix to Webflow the riskiest move on this list, and the one where a complete redirect map matters most.
• Squarespace. Blog and collection paths usually change on the way out. Squarespace to Framer follows the same process as above, with extra care on collection URLs.
• WordPress. Still the most common starting point. The destination-specific versions are WordPress to Webflow, WordPress to Framer and WordPress to Astro.

Whatever you’re leaving, run your sitemap through our free migration planner before you commit to a destination. It shows which paths survive the move and which need a 301.

What We Tracked on Our Own Move

We followed this process when we moved designme.agency from Framer to Astro in October 2026, and it’s too early for a fair before and after on rankings: Google needs weeks to recrawl a whole site. Here is what we could already measure.

• The redirect map. Before the switch we mapped 116 old URLs: 65 kept their path, 43 got a 301 and 8 were retired on purpose. In the first week, 404 reports turned up a few more old links, and the map grew to 124 rows. That’s the gap this guide warns about, caught in days instead of months.
• Indexing a week in. On 20 October, Search Console showed 160 of the 229 URLs in our sitemap indexed, and 26 of them still last crawled before the switch, so Google was ranking the old versions of those pages. The fix is the one in the launch checklist above: a sitemap with real last-modified dates and indexing requests for the pages that matter most.

We’ll add the Search Console numbers for clicks, impressions and positions once eight weeks of data are in.

The Bottom Line

Losing SEO in a migration is a choice, not an accident. It happens to teams that treat search as a launch-day afterthought instead of a pre-launch discipline. Audit completely, redirect every URL, reproduce every on-page signal, get the technical foundation right, and monitor obsessively for the first month. Do that and you keep every position you’ve earned, and often gain some, because the new site is faster and cleaner than the old one.

For the platform-specific versions of this process, see how to move WordPress to Webflow, step by step and how to move WordPress to Framer, step by step. For the full operational sequence, the redesign and migration checklist lays out every step in order.

DesignMe migrates websites for funded B2B SaaS and AI companies with SEO preservation built into the process from the first audit, because protecting the traffic the old site earned is the entire point. If you’re moving off WordPress and rankings are on the line, our intro call is 30 minutes:

designme.agency/intro