Website Migration SEO Checklist – How to Move Your Website Without Losing Rankings

• Facebook
• LinkedIn
• X
• WhatsApp

You’re thinking about moving to a new website platform. But one big question is holding you back: Can I move my website without losing SEO rankings?

You can, if you set up 301 redirects for every changed URL, keep your site structure consistent, and submit a new XML sitemap to Google Search Console. Most well-planned migrations recover fully within four to six weeks.

Read everything you need in one place: a plain-language explanation of what a website migration actually does to your SEO, a practical before/during/after checklist you can follow without being a developer, and an introduction to Webnode’s AI Migration Tool, a free tool that automates the technically complex parts of the process.

CONTENTS:

• What is Website Migration
• Common Reasons People Migrate Their Website
• What Types of Website Migration Exist
• Does Website Migration Affect SEO?
• What Google Re-Evaluates During Migration
• Website Migration SEO checklist
• The Most Common Migration Mistakes (and How to Avoid Them)
• How to Migrate Your Website the Easy Way
• Website Migration FAQ

TL;DR: Website migration means moving your site to a new platform, a new hosting provider, or a new domain, which causes Google to crawl the site again and evaluate it almost as if it were a new site. Skipping redirects is the single biggest cause of lasting SEO damage. Done correctly, rankings typically stabilize within 4–6 weeks (2–3 months if you’re also changing your domain). Webnode’s free AI Migration Tool automates the technical steps, so most owners complete the move in an afternoon.

What Is Website Migration

Website migration is the process of moving your website from one platform, host, or domain to another. In practice this means your pages, content, and URLs are changing location—and Google has to find and re-evaluate everything in its new home. That’s the simple explanation.

The more complete explanation is that website migration is any significant change to your site’s infrastructure that requires Google to re-crawl and re-index your content, which helps the search engine display relevant content in search engine results pages. That could mean switching to a new website builder, moving to a different web host, changing your domain name, or completely redesigning the structure of your site.

For many small business owners reading this, the most common scenario is a platform migration, moving from an older or difficult-to-manage builder to something more modern or interesting. Whether you’re weighing a website builder against a custom site or just ready to move on from a platform that no longer fits your needs, the principles in this guide apply.

Why Do People Migrate Their Websites? 7 Common Reasons

Let’s take a closer look at why people migrate, as the decision rarely comes out of nowhere. Most small business owners arrive at this point after months of frustration. Common triggers include:

• Outdated design: A competitor has a cleaner, faster, more professional-looking site and you’re losing customers before they even read your content
• Poor mobile experience: Your site looks fine on desktop but falls short or breaks on smartphones, which is where the majority of customers are
• High maintenance cost: WordPress in particular can become expensive once you factor in hosting, plugin subscriptions, security updates, and developer fees
• Platform limitations: Your current builder doesn’t support features you need, like online booking, ecommerce, or a blog
• No longer working with a developer: Maybe your relationship has changed with the professional who built your site, and now you cannot make basic updates yourself
• Speed issues: Your site loads slowly, which hurts both your visitor experience and your rankings
• Simply wanting something easier: You want a website you can actually manage yourself, without needing to understand code

Any one of the above is a legitimate reason to move on. The good news is that any or all of them can be addressed through a well-planned migration.

What Are the Types of Website Migration?

Not all migrations are the same, and the type you’re doing determines how much SEO risk is involved. Here are the details:

Platform migration

This means moving from one website builder or CMS to another, sometimes called website replatforming. For example, from WordPress, Wix, or Squarespace to a modern no-code builder. This is the most common migration type for small businesses and the focus of this guide going forward. The SEO risk is manageable with proper redirects and preparation.

Domain migration

This type of migration means changing your website’s URL entirely. For example, moving from mybusiness.co.uk to mybusiness.com. While it carries more SEO risk—since the accumulated ranking signals and backlinks tied to your old domain need to transfer over, and Google re-evaluates the new domain from scratch—it is generally recoverable with correct redirects and patience.

HTTP to HTTPS migration

With this migration, you are switching your site to use a secure connection. It’s a much simpler migration and, in most cases, a positive SEO signal because Google has used HTTPS as a ranking factor since 2014. If you haven’t made this switch yet, it’s overdue.

Full structural redesign

This involves reorganizing the architecture of your site—collapsing sections, rebuilding navigation, or rethinking your URL structure—often as part of a website redesign, and sometimes but not necessarily alongside a platform switch. 

A redesign carries real SEO risk because there are a lot of unavoidable changes happening at once. For this reason, a website redesign SEO checklist looks a lot like the migration one outlined in this article: document your URLs, map redirects, and preserve internal linking.

If you’re redesigning without switching platforms, rest assured that the same principles in this guide apply, and the same preventable mistakes lose Google rankings after a redesign.

In summary: there are four types of website migration of varying complexity and difficulty. Understanding which type applies to your situation helps assess the level of preparation required. Avoid mixing too many changes at once, when possible. The main focus of this guide is platform migration.

Does Website Migration Affect SEO?

Yes, but only temporarily, provided you plan carefully. Lasting damage almost always comes from skipped redirects, broken links, or launching without testing.

When you migrate a website, Google needs to re-crawl your content in its new location and reassign rankings accordingly. What does it mean for Google to “crawl” your website? Imagine digital spiders weaving a digital web between your webpages and figuring out how it all connects to the wider internet; that’s how Google evaluates you.

During this re-evaluation period, it’s completely normal to see some fluctuation in where your pages appear in search results. But rest assured, Google is working in the background. Think of it like updating your address at the post office: there’s a short window where some letters go to the wrong place before everything settles.

The businesses that experience lasting SEO damage after a migration are almost always the ones who skipped redirects, left broken links behind, or launched without testing. You can expect ranking fluctuation to be heaviest in the first two to four weeks after launch—this is normal and nothing to worry about.

A well-planned, same-domain migration, one that includes proper redirects, an updated sitemap, and careful monitoring, typically stabilizes within four to six weeks, often returning to or exceeding previous levels.

A migration that also changes your domain usually takes longer to stabilize, even if done correctly. You can expect results in two to three months.

What Google Re-Evaluates During a Website Migration

When you migrate your website, Google doesn’t simply “follow” it to the new location. It re-crawls the new site and evaluates it largely as it would a new property. According to Google Search Central, Google’s official documentation on site migrations, this re-evaluation covers several key signals.

Understanding what Google looks at most closely helps you focus your effort in the right places. For a deeper look at how these signals influence your visibility, see Webnode’s overview of the Google ranking factors that affect your website’s positioning.

Google Search Central.

URL Structure and Redirects

URLs are among the most critical factors in any migration. Every page on your current site has accumulated SEO value over time, from external links pointing to it, being indexed, and from user engagement signals. That value is tied to the page’s specific URL address.

When you migrate and a URL changes (which happens in almost every platform switch), you need to set up a 301 redirect for that page. A 301 redirect is a permanent signal to Google that a page has moved to a new address and that all its accumulated SEO value should be transferred along with it. Without this redirect, Google treats the old page as simply gone, and the ranking power it carried disappears.

Let’s look at a straightforward example. If your service page was yoursite.com/our-services and your new platform changes the URL to a slightly simpler yoursite.com/services, a 301 redirect from the old URL to the new one ensures Google arrives at the correct page, with all your SEO values intact. What’s more, this works for anyone who saved or linked to the old address on their blog or elsewhere.

Every important page needs a redirect, not just the homepage. Remember your product pages, blog posts, contact page, and any other page that has accumulated links or rankings over time that contributes to your business.

Internal Linking and Site Architecture

Google doesn’t evaluate individual pages in isolation. It maps how your pages connect to each other. Your internal link structure (the links between your own pages) helps Google understand which pages are important, how your content is organized, and how different topics on your site relate.

A migration that breaks internal links or reorganizes your navigation without care disrupts this map. If pages that used to link to each other no longer do, or if your structure becomes harder for Google to navigate, it can affect how well your content is understood and ranked.

The practical guidance is straightforward: keep your navigation structure and internal linking as consistent as possible during migration. Don’t reorganize everything at once; save structural improvements for after your new site has been indexed and rankings have stabilized. As noted above, this typically takes four to six weeks for a same-domain migration.

Page Speed and Core Web Vitals

Moving to a new platform almost always changes how fast your site loads. That change matters to Google.

Core Web Vitals are three specific metrics that Google uses as direct ranking signals. It’s worth knowing what they actually measure:

• LCP (Largest Contentful Paint) – how long it takes for the main content of a page to appear on screen. Google considers anything under 2.5 seconds good.
• INP (Interaction to Next Paint) – how quickly your page responds when a visitor clicks a button or taps a link. Under 200 milliseconds is the target.
• CLS (Cumulative Layout Shift) – how much the page layout jumps around while content is loading. A score of 0.1 or below is considered stable.

Where can you measure your Core Web Vitals metrics? Check the metrics of any website you own directly with Google Search Console.

Here’s the silver lining: if you’re migrating from an older, clunkier platform, your Core Web Vitals are likely to improve on a modern builder. Migration is a genuine opportunity to give Google better performance signals than your current site delivers, strengthening your rankings in the long run.

Backlink Profile and Domain Authority

Every link from another website pointing to one of your pages enhances your SEO authority. The better the website directing to you, the more you benefit. These are called external links or backlinks, and they are one of the most important ranking factors for Google.

Bear in mind that during a migration, any link pointing to an old URL that no longer exists will redirect incorrectly. This will weaken your SEO authority, which is another reason proper 301 redirects are non-negotiable. They preserve the link equity you’ve earned from external sites, even when those site owners never update their links.

If your migration involves a full domain name change, expect a more significant re-evaluation period as Google transfers authority to the new domain. But don’t worry, this is nothing to lose sleep over. It’s simply part of the process. Your values are recoverable, but it takes longer than a same-domain platform migration. Be patient, keep watch, and your rankings will return.

Website Migration SEO Checklist: 21 Steps (Before, During, After)

The steps below are designed for small business owners, not developers. You don’t need technical know-how to follow this website migration checklist, just attention to detail and a willingness to check your work.

Move through the three phases in order: 1) prepare before you move, 2) protect what matters during the move, and 3) verify everything after you go live. Save or print this checklist and tick items off as you complete them.

Pre-Migration Checklist: What to Prepare Before You Move

1. Crawl your current site and export all your URLs

Use Screaming Frog (free for up to 500 URLs) to crawl your current website and export a list of every page address. This becomes your master reference document for the entire migration. Without it, you have no reliable way to confirm every page has been accounted for.

2. Record your current rankings and traffic

Log into Google Search Console and Google Analytics and take screenshots or exports of your current performance data. You need a before-snapshot so you can compare results after the migration and quickly identify anything that needs attention.

3. Identify your most important pages

Which pages drive the most traffic? Which rank for the keywords that bring in customers? Flag these in your exported Screaming Frog files and in any notes you make. These are the pages you cannot afford to lose during the migration.

4. Back up your entire current website

Before you change anything, create a full backup of your existing site. Most platforms have a built-in export or backup function (check if you need a premium package to access this feature from your provider). This is your safety net—if anything goes wrong, you can recover your site, no sweat!

5. Create a redirect map

Open a spreadsheet with two columns: old URL on the left, new URL on the right. Work through your exported file and map every page that will change address on the new platform. This document is what you’ll use to set up your 301 redirects during the migration.

Note: if you’re keeping your current domain name, Webnode will handle 301 redirects on your behalf.

6. Confirm your new platform supports everything you need

Before committing to the move, verify that your new platform supports the features your business depends on, such as contact forms, ecommerce, a blog, booking integrations, or anything else. Every platform is unique, and discovering a missing feature after you’ve migrated will be a headache and may be expensive to fix.

7. Set up Google Search Console for your new site in advance

Add your new domain or property to Google Search Console before you migrate. This ensures you can monitor the new site from the moment it goes live. You’ll need it to submit your sitemap straight after launch. More on that in a moment.

During Migration: What to Protect While You Move

1. Implement every 301 redirect from your redirect map

This is the most critical step in the entire migration. Using the redirect map you created in the pre-migration phase, set up a 301 redirect on your new platform for every URL that is changing. Don’t skip pages that seem unimportant. A link you’ve forgotten about could be driving customers to your site every day.

Remember, if you’re keeping the same domain name, Webnode can handle redirects so you don’t have to.

2. Transfer all page content accurately

Move your text, images, page titles, and meta descriptions to the new platform carefully. Critically, do not update your content at the same time as your platform. If you want to refresh website copy or replace images, do it after the migration has settled. Changing everything at once makes it nearly impossible to diagnose problems if something goes wrong.

3. Keep your URL structure as close to the original as possible

Even if your new platform uses slightly different URL formats, try to match your existing structure as closely as you can. The fewer URLs that change, the fewer redirects you need and the less risk you carry overall.

4. Make sure your new site has an XML sitemap

An XML sitemap is a file that lists all the pages on your website so that Google can find and index them easily. Your new platform should generate this automatically. Confirm that it does and that the sitemap covers all your important pages. You’ll submit it to Google right after going live.

5. Set canonical tags correctly

A canonical tag tells Google which version of a page is the definitive one, preventing duplicate content issues. Most modern website builders handle these automatically, but it’s worth confirming, especially if your site has multiple versions of similar pages.

6. Don’t launch on a Friday

Yes, really. This practical wisdom comes from experienced migration teams: launch mid-week. If something goes wrong after going live, you want your working week ahead of you to identify and fix it, not a weekend watching traffic drop with no support available.

7. Test everything before going live

Check your redirects using Redirect Checker. To do that, paste in your old URLs and confirm each one returns a 301 status code pointing to the correct new page. Test your contact forms, your checkout process if you have one, and every important page on both desktop and mobile before flipping the switch.

Post-Migration Checklist: What to Verify After You Go Live

1.     Submit your new XML sitemap to Google Search Console

Log into Google Search Console, go to sitemaps, and submit your new sitemap URL. This is the fastest way to prompt Google to crawl and index your new site.

2.     Check for crawl errors in Google Search Console

Monitor the coverage report in Google Search Console daily for at least the first two weeks after going live. Any 404 errors (pages not found) or other crawl issues should be investigated and resolved immediately. Don’t let them sit.

3.     Verify all redirects are working correctly

Run your old URLs through Redirect Checker again after going live. Confirm you’re seeing 301 responses, not 302s (temporary redirects) or 404s (broken pages).

4.     Test your site on mobile

Use a tool like PageSpeed Insights or SE Ranking to confirm your new site renders correctly on smartphones. Mobile usability is a direct ranking factor, and it’s easy to overlook in the rush of going live.

5.     Check your page speed and Core Web Vitals

Run your new site through PageSpeed Insights and compare the results to your pre-migration baseline. If your scores have dropped significantly, investigate the cause before it starts affecting your rankings.

6.     Monitor your rankings weekly for the first month

The first two to four weeks after a migration are the most important to monitor. Check your organic traffic and ranking positions weekly in Google Search Console and Google Analytics. Some fluctuation is expected. Continued drops after week four are the signal to investigate further.

7.     Confirm no important page is returning a 404

Cross-reference your list of top-performing pages against the coverage report in Google Search Console. Any important page returning a 404 needs an immediate redirect fix or content restoration.

Once your new site is stable and indexed, use Webnode’s guide on how to do SEO for your website to build on the foundation you’ve preserved. You can also use the tips in getting your website to show up on Google to accelerate your post-migration visibility.

What Are The Most Common Migration Mistakes (and How to Avoid Them)

Keep the following list close at hand so that you don’t have to unravel any complicated mistakes later.

Skipping 301 redirects entirely

This is the single most common cause of permanent SEO damage after a website migration. Some small business owners assume their new platform will handle redirects automatically. Most don’t, unless you specifically configure them.

But good news, the fix is straightforward: create your redirect map during the preparation phase and implement every redirect before going live. It’s the most important thing you’ll do in this entire process, and knowing about it in advance means it doesn’t catch you off-guard.

And in even better news, Webnode handles 301 redirects on your behalf if you keep the same domain name.

Forgetting to migrate meta titles and meta descriptions

Your meta title and meta description are what appear in Google search results and they’re a core element of your on-page SEO. Many platforms don’t automatically carry these over when you copy content across. After the migration, check every page to confirm these have transferred correctly and haven’t been replaced with generic defaults or left blank.

Launching without testing on mobile

According to DataReportal, more than half of website visits come from smartphones. A new platform might display beautifully on your laptop but break completely on mobile screens. Always test your new site on mobile using a mobile-friendly test in PageSpeed Insights, not just by looking at it on your own device. Your own phone may not represent the full range of screen sizes your visitors use.

Not setting up Google Search Console before the migration

If you don’t have Google Search Console configured on your new site before you launch, you’re flying blind from day one. You won’t be able to submit your sitemap, monitor for crawl errors, or spot ranking drops until you’ve set it up, by which point problems may already be accumulating. Set it up in advance, and it’s one less thing to manage after going live.

Changing too many things at once

Platform migration, plus a domain change, a full content refresh, and a structural reorganization—all at the same time—multiplies your SEO risk significantly. When something goes wrong in a complex migration, each additional change you’ve made makes it harder to identify the cause. If you want to change your domain name or significantly update your content and structure, plan to do each of those things separately. Ideally, with several weeks between them and your platform migration. Don’t rush it.

In summary: There are plenty of mistakes that can complicate your migration experience, but these can be easily avoided. What’s more, Webnode has an AI solution to help.

How to Migrate Your Website the Easy Way—With AI

Reading through this checklist, you might be thinking, This is exactly the kind of technical work I was trying to avoid, and that’s a fair reaction. 

Even clearly explained, there are a lot of steps—and for small business owners who are already stretched thin, the thought of managing redirects, sitemaps, and crawl error reports on top of running a business is often the exact reason many put off switching website builders for years.

This is where Webnode’s AI Migration Tool comes in. It’s built to handle the most technically complex parts of a website migration automatically, so you don’t have to do them manually. Webnode migration feels like an opportunity rather than an ordeal.

How Webnode’s AI Migration Tool Works—Step by Step

The process is designed to be simple from start to finish—just four simple steps. First, head over to the AI migration tool. Then: 

1. Enter your existing website URL. Paste in your current site’s address and Webnode’s AI will begin scanning it.

Webnode AI Migration Tool. Simply paste your URL.

This process may take a few minutes, but there’s no need to stay glued to your screen. Feel free to carry on browsing the internet, close your window, or even make a coffee. Once your migration is completed, you’ll receive email confirmation.

2. The AI imports your content. Your text, images, and page architecture/structure (not to be confused with layout/design) are pulled in automatically. You’re not rebuilding from zero.

3. Customize with Webnode’s drag-and-drop editor. You’ll have a basic structure based on the imported content. Now it’s time to adjust colors, fonts, text, and layout details. No coding at any stage.

Inside the drag-and-drop editor.

4. Publish and go live. Your migrated, redesigned site is ready.

And good news, the migration tool is free. You only upgrade to a paid plan when you’re ready to publish with a custom domain.

What It Migrates Automatically and What You Stay in Control Of

Now we know that migration can be accomplished in four short steps, let’s get into the details of what’s done automatically and what isn’t, which is where you come in.

What Webnode’s AI handles automatically:

• Preservation of existing URL paths for regular pages where possible, so pages that keep the same address don’t need a 301 redirect at all (only applies if you’re keeping the same domain name; blog post URLs work differently)
• Any existing page titles, meta descriptions, and keywords
• Scanning and importing your current content (text and images)
• Generating a basic layout based on your original site architecture, designed for you to build upon
• Mobile-responsive design built in by default

Migration Tool limitations at present:

• Only available in English language
• Migration limit is 20 pages (including hidden pages). If you migrate more than twenty pages, you’ll get an error message.
• No online stores (you need to recreate this after migration, if required)

What you control:

• Your domain name setup or transfer. See our domain transfer guide
• Redirects when migrating from a different URL structure (this also applies when you keep the same domain but a URL structure changes. For example, in Webnode blog posts)
• Website redesign, including favicons 
• Any content updates or refinements you want to make post-migration
• Email services connected to the domain
• Integrations with external services (Google Analytics, Search Console, Google Tags, etc.)
• Widgets are not transferred automatically

The most common scenario is that you want to keep your current domain name but move to the Webnode platform. Using the Webnode AI Migration Tool, you can migrate up to twenty pages without creating 301 redirects for regular pages. But your blog post URL structure will change. For these, you’ll need to manually create redirects directly in your new Webnode site once it’s live. 

How are blog articles migrated?

Unlike regular pages, Webnode blog posts always use the fixed URL structure (/l/article-url). As a result, the URLs of your migrated blog posts will change. To ensure visitors and search engines are redirected to the new URLs, you’ll need to manually configure 301 redirects in the editor. See more about alternative URLs here.

Who Is This Tool Best Suited For?

Webnode’s AI Migration Tool is designed for small business owners, bloggers, freelancers, and anyone running a personal website. It’s especially valuable if your current site looks outdated, was built on an ageing platform you can no longer easily update, or was originally created by a developer you no longer work with.

It’s not built for large enterprise sites with hundreds of complex pages, custom API integrations, or heavily bespoke functionality—those sites are better served by a fully custom developer-led migration.

That said, for most small businesses and personal brands, Webnode’s AI tool removes the technical barriers that have made migration feel impossible, and replaces them with a clear step-by-step process. The migration itself is something most people can complete in an afternoon.

---

Website Migration FAQ

Ready to migrate your website without technical headaches? Start with Webnode’s free AI Migration Tool

• Facebook
• LinkedIn
• X
• WhatsApp

---

Jamie Faulkner writes and edits copy to build community, inform, and inspire action through blogs, newsletters, and email strategy. He is particularly interested in sustainability, technology, travel, health and fitness, and education. Above all, he is passionate about storytelling—both in the marketing world, helping brands connect with their audiences, and through his published short fiction. Jamie is also the co-founder of education provider Discourse Hub, where he teaches and creates content for blogs, newsletters, and social media.