How do I move my site from one website builder to another without losing search rankings?

You can’t guarantee zero ranking fluctuation, but you can greatly reduce the risk by treating the move as a technical migration—not just a redesign. The most important distinction is whether your domain and page URLs will stay the same.

Before you move

1. Inventory your current site. Export or record important URLs, page titles, meta descriptions, headings, canonical tags, images, structured data, and internal links. Use your sitemap, Search Console, and analytics to identify pages that get search traffic or links.
2. Keep URLs the same wherever possible. If a page’s URL must change, map its old URL to the closest equivalent new page. Avoid changing the domain, URL structure, design, and content all at once; changing one major thing at a time makes problems easier to diagnose. (developers.google.com)
3. Check the new builder’s SEO capabilities. Make sure it lets you use your domain, set page titles and descriptions, manage canonical tags, create a sitemap, control indexing, and—if URLs change—set up permanent redirects from the old URLs.
4. Build and test the new site before launch. Check that important pages are accessible to search engines, aren’t marked noindex, load correctly on mobile, and have working internal links.

At launch

• If URLs change: set up a permanent, server-side 301 or 308 redirect for each old URL to its matching new URL. Avoid sending many unrelated old pages to the homepage or creating long redirect chains. (developers.google.com)
• Update internal links, canonical tags, and your sitemap so they point to the new URLs. Submit the new sitemap in Google Search Console. (developers.google.com)
• If the domain changes: verify both domains in Search Console and use the Change of Address tool after redirects are in place. It isn’t for a builder or hosting change when your domain and URLs stay the same. (support.google.com)
• Keep your old site/domain and redirects working. Google recommends keeping redirects for at least a year; don’t cancel the old hosting or domain until you know the transition is working. (developers.google.com)

After launch

Check Search Console and analytics regularly for broken pages, indexing problems, unexpected traffic drops, and old URLs that aren’t redirecting properly. Test important URLs individually with Search Console’s URL Inspection tool. Some temporary ranking movement is normal while Google recrawls and processes the new site; for many small or medium-sized sites, that can take a few weeks or more. (developers.google.com)

If your domain and URLs stay exactly the same, this is usually a simpler hosting/platform migration: focus on keeping pages crawlable, returning the right content and status codes, and avoiding downtime. (developers.google.com)

If you share your current builder, new builder, and whether you’re keeping your domain and URLs, I can tailor this into a migration checklist for your setup.

The short answer: keep your old URLs working through permanent redirects, carry over the content that ranks, and watch Search Console closely after launch. Most ranking losses come from skipped steps, not from the new builder itself.

1. Inventory every URL before you build anything. Crawl the current site and export the pages that get search clicks and impressions from Search Console, plus landing-page traffic from your analytics. Combine the crawl with the Search Console page-level export for the last sixteen months, the analytics landing page report for the same period, and a backlink export. Also check campaign, QR code, and referral traffic before retiring any page.

2. Record your baseline. Save current rankings for your main keywords and your leads or sales numbers so you can tell later whether anything dropped. Without that inventory you cannot build a redirect map, and you will not know what you lost after launch.

3. Build a one-to-one redirect map. Every old URL that changes should point to its closest equivalent on the new site. If a page is being removed, the row says where its traffic and links go instead, which is usually the closest surviving parent, not the homepage. Google's guidance also says to send old URLs directly to their matching new pages and avoid chains and irrelevant homepage redirects.

4. Set up 301 redirects, and check your builder can do them. A 301 signals a permanent move. Use it for real moves and avoid 302s, which are for temporary changes. Keep each redirect to a single hop. Many website builders limit redirect control, so confirm before you commit: can you add individual page redirects, and does the platform support bulk imports? If not, that's a serious drawback for an SEO-sensitive site.

5. Keep what already ranks. Keep titles, headings, and main content on pages that perform well, at least through launch. Change the design and structure first, then improve copy one page at a time, so you can tell what caused any drop.

6. Prepare the new site. Build it on a staging version that search engines can't index, then test it. Update internal links and create a new XML sitemap. Check that the new site isn't accidentally blocked from crawling, and that canonical tags point to the right URLs.

7. Launch and monitor. On launch day, spot-check key old URLs to confirm they land on the correct new pages. Then watch Search Console for indexing errors and use URL Inspection on your most important pages. A year is the bare minimum length of time to keep 301 redirects in place. Also update external links where you can, since backlinks are the hardest things to recover.

Expectations: Google usually processes redirects within days, but it can take several weeks to months for Google to fully crawl your new site, transfer all link equity, and stabilize your rankings. A temporary dip in the first few weeks is normal. A sustained drop usually points to a missing redirect, a broken internal link, or changed content on a page that used to rank.

If you tell me which builders you're moving between and roughly how many pages the site has, I can help you draft a redirect map or check whether the destination builder supports what you need.

Moving your website to a new builder is a significant change, but you can protect your search rankings by following a structured, methodical process. The primary goal is to ensure that Google and other search engines can easily find your content at its new home.

1. Pre-Migration Preparation (The Most Critical Phase)

Most migration issues are actually planning failures. Before moving anything, document your current site.

• Audit Your Current Site: Use a crawler tool (like Screaming Frog) to export a list of every URL on your current site.
• Identify Top Performers: Look at Google Search Console and your analytics to identify pages that bring in the most organic traffic, backlinks, and leads. These are your highest-priority pages.
• Create a Redirect Map: This is the most important file in your migration. Create a spreadsheet that lists every old URL and its corresponding new URL. If a page doesn’t have a direct equivalent, map it to the most relevant category or parent page—avoid simply redirecting everything to your homepage.

2. During the Build

• Maintain URL Structure: If possible, keep your URL slugs the same. If the new platform forces different URL patterns, your 301 redirect map (created in step 1) becomes essential.
• Keep Content Consistent: Ensure that the content on your new pages matches the intent and topic of the old ones. If you significantly rewrite or delete content, you risk losing the relevance that helped you rank.
• Use a Staging Environment: Build your new site in a private staging area. Do not make the site live until you have tested the redirects and ensured no "noindex" tags are accidentally left on the pages.

3. Launch Day & Post-Launch

• Implement 301 Redirects: Use 301 (Permanent) Redirects for every moved or changed URL. A 301 redirect tells search engines that the move is permanent and passes your "link equity" (ranking power) to the new page. Do not use 302 (temporary) redirects for a permanent move.
• Update Internal Links: Once live, update internal links within your site to point directly to the new URLs to avoid unnecessary redirect chains.
• Submit Your New Sitemap: Submit your new XML sitemap via Google Search Console to help Google discover your new site structure faster.
• Monitor for Errors: Keep a close eye on Google Search Console for "404 Not Found" errors. If you see a spike in errors, your redirect map may need adjustments.

Summary Checklist for Success

Expect some fluctuation: It is normal to see some ranking volatility for a few weeks while search engines re-crawl and re-index your site. As long as your redirects are in place and your content is high-quality, most sites recover their rankings after the transition period.

You can’t guarantee zero ranking fluctuation, but careful planning can preserve most of the signals Google has built up for your site. The biggest risk is changing URLs or losing important content without giving search engines a clear path to the new pages.

Before you move

1. Record a baseline. Export your important URLs and note current organic traffic, rankings, indexed pages, and conversions. Save a copy of your site, including page text, titles, descriptions, images, and metadata.
2. Build and test the new site before switching. Check that important pages are accessible, work on mobile, and aren’t accidentally blocked from search engines.
3. Map old URLs to new URLs. Make a spreadsheet pairing each valuable old page with its closest equivalent on the new site. Keep URLs the same where possible. Google recommends preparing this URL mapping before a move. ²

When you launch

1. Set up permanent redirects. For every URL that changes, use a server-side permanent redirect—usually a 301—from the old page directly to its relevant new page. Avoid sending lots of unrelated old URLs to the homepage; if a page has no replacement, it may be better to return a proper 404 or 410. ²
2. Update the new site’s signals. Check internal links, canonical tags, and the XML sitemap so they use the final new URLs. Submit the new sitemap in Google Search Console. ²
3. If the domain changes, verify both domains in Search Console and use the Change of Address tool. It’s not needed if you’re keeping the same domain and only changing builders or hosting. ³
4. Keep the old site/domain and redirects working. Google advises keeping redirects for at least 180 days; in practice, keep them much longer if you can, especially while old URLs still get visits or appear in search. ³

After launch

1. Monitor Search Console and analytics for indexing problems, redirect errors, lost traffic, broken pages, and sudden changes to important queries. Test a sample of old URLs to confirm each reaches the right new page.
2. Fix issues promptly and expect some settling time. If rankings dip, first check that pages are available to Google, redirects work, key content is intact, and the new sitemap is being read.

If the domain and URL paths stay the same, the move is generally simpler: focus on keeping the pages accessible and ensuring the new builder doesn’t change your content or block crawling. ¹

Sources: Google Search Central’s guides to site moves with URL changes ², changing hosting without URL changes ¹, and the Search Console Change of Address tool ³.