You can move a website to a new platform without losing traffic if every old address that people and Google use still works, either at the same address or through one permanent redirect to its matching new page, and if each page keeps its words, titles and structured data. When traffic drops after a migration, the usual cause is old addresses that stopped working.
We move business websites off WordPress, Wix, Squarespace and Webflow onto custom code, and this is the order we work in, whether the site belongs to an eye care practice, a rug cleaning company or a bookkeeping firm.
What Counts as a Website Migration
To Google, any change to your platform, your domain or your web addresses is a migration. That covers leaving Wix or WordPress, moving to a new domain, a redesign that renames pages, and merging two sites into one. Keeping the same domain and addresses carries the least risk. Changing the domain, the structure and the design at once carries the most, so change one thing at a time if you can.
Before the Move
1. Get every login first
Collect the logins for the domain registrar, the DNS host, the current platform, Google Search Console, Google Analytics and your Google Business Profile before anyone touches the site. Note which account owns each one. Launch day is a bad time to learn that a former employee owns the domain.
Check where your email runs, too. If your inbox uses your domain, the records that route and verify it (MX, SPF, DKIM and DMARC) have to come along when DNS changes.
2. Build a full URL inventory
List every address on the old site that still gets visits or links. Pull from several sources, since none is complete alone:
- A crawl of the live site, with a crawler such as Screaming Frog
- The site's XML sitemap
- The Pages tab in Search Console's Performance report, set to the full 16 months it keeps
- Landing pages in Google Analytics
- Pages other sites link to, from Search Console's Links report
- Old blog posts, event pages, PDFs and campaign pages that dropped out of the menu
- Any address printed on a QR code, a flyer or a business card
Pages that have fallen out of the sitemap often still show up in the Internet Archive's Wayback Machine. We've used it to recover a restaurant's old Squarespace addresses after launch, though it's easier to do before.
For each address, record its title, meta description, main heading, canonical tag, structured data, clicks and links.
3. Save a benchmark
Export your queries and pages from Search Console, plus landing pages and conversions from Analytics. After launch, this is how you tell normal movement from a real problem.
4. Keep addresses the same where you can
The safest redirect is the one you never need. If the new platform lets you keep your old addresses, keep them. When we moved S&S Rug Cleaners off a hosted site builder, all 54 pages kept their original addresses, so every existing link still lands on the same page.
Site builders often force their own patterns, such as /post/ in front of every Wix blog post. Those are the addresses most likely to break, so plan for them early.
5. Build the 301 redirect map
When an address has to change, map it. Use a spreadsheet with one row per old address and a column for its new page. The rules we follow:
- Use permanent redirects (301 or 308), not temporary ones (302).
- Send each old address to its closest matching new page. Google can treat a pile of redirects to the home page much like missing pages.
- Redirect in a single hop. If the old site already had redirects, point them straight at the final page so you don't build a chain.
- Cover the variations: with and without www, http and https, trailing slashes and capital letters.
- If a page is truly gone and nothing similar exists, let it return a 404 or 410 instead of forcing a poor match.
Test the whole map on the new site before launch. For Penny Patrol, a bookkeeping and fractional CFO firm, we copied its Squarespace site page for page and redirected each old address in a single hop.
6. Carry over everything on the page
A migration is a bad time to rewrite copy by accident. For every page, carry over:
- Title tags and meta descriptions
- Main headings and body copy
- Image alt text
- Internal links, updated to point at final addresses
- Canonical tags pointing at the new pages
- Structured data, such as Organization, LocalBusiness or Product markup
- Open Graph tags for social sharing
The less you change, the easier it is to explain anything that moves. That's why we often copy a site page for page first. Oculare's WordPress site was copied onto custom code and matched against the original page by page before it went live. Phoenix Parking Solutions' 24 pages came off Webflow the same way. Our post on leaving Squarespace, Wix or Webflow covers when a redesign on the way over makes sense, and medical practice website design covers the extra markup healthcare sites carry.
During the Move
7. Keep the new site hidden until launch
Build the new site behind a password or a noindex tag so Google doesn't index a half-finished copy. Then remove the block at launch. A live site whose robots.txt still says "Disallow: /" is one of the most common migration mistakes, and one of the most costly.
8. Test forms, tracking and integrations
Every form should reach the right inbox or system, and analytics, conversions and booking tools should all work on the new pages. When S&S Rug Cleaners' site moved, its quote and contact forms were switched over to the new site's own form system.
9. Switch DNS with care
Lower the DNS time to live a day or two ahead so the change spreads quickly. Copy every existing record, email first. If you're also moving to a new domain, send each old address to the same page on the new one, as we did when Phoenix Parking Solutions changed domains. Then tell Google with the Change of Address tool in Search Console.
10. Crawl the new site on launch day
Run a full crawl as soon as the site is live and check that:
- Every page returns a 200 status
- Every row in the redirect map lands on the right page in one hop
- No page carries a leftover noindex tag
- Canonical tags point to the new site, not the old one or the staging address
- Internal links go straight to final addresses, over https
11. Submit the new sitemap
Submit the new XML sitemap in Search Console. Run your most important pages through the URL Inspection tool and request indexing for them.
After the Move
12. Watch Search Console every week
For the first couple of months, check the Pages report for new "Not found (404)" errors and compare clicks and impressions with your benchmark. When Google still asks for an old address you missed, redirect it. Every site has a few, which is why we watch Search Console after every migration we run.
13. Leave the redirects in place
Google recommends keeping redirects for at least a year. Old links and bookmarks keep arriving for years, so there's rarely a reason to remove them.
14. Update the links you control
Change the website link on your Google Business Profile, social profiles, directory listings, email signatures and ad final URLs, so they point straight at the new pages instead of passing through redirects.
15. Expect a little movement
Some ranking movement is normal for a few weeks while Google recrawls the site, and a large site takes longer. A steady slide in clicks usually points back to missing redirects, a blocked page or lost content. Our SEO, AEO and GEO work picks up from there.
Common Website Migration Mistakes
- Redirecting every old address to the home page
- Forgetting old blog, event and PDF addresses
- Redirect chains that hop two or three times
- Leaving the staging block on the live site
- Canceling the old platform before exporting what it holds, such as an email list tied to the old site
Website Migration Checklist
Before the move:
- Collect domain, DNS, platform and Google logins
- Crawl the site and build a full URL inventory
- Save a Search Console and Analytics benchmark
- Keep addresses the same wherever possible
- Build and test a single-hop 301 redirect map
- Carry over titles, descriptions, headings, copy, alt text and structured data
Launch day:
- Remove the staging block
- Test forms, tracking and integrations
- Switch DNS and keep the email records
- Crawl the live site and test every redirect
- Submit the new sitemap in Search Console
After launch:
- Check Search Console weekly for 404s and changes
- Redirect any old address Google still requests
- Keep redirects for at least a year
- Update your listings, profiles and ads
Common Questions
How long does a website migration take?
It depends on the size of the site and whether it's copied or redesigned. Two of our page-for-page copies went live within two weeks of the build starting. Oculare's took 13 days. A move with a new design takes longer. Waiting on logins adds time, which is why we ask for access first.
Will I lose rankings when I migrate my website?
Some movement for a few weeks is normal. If every old address works, the content carries over and you fix stragglers quickly, things usually settle. Lasting drops tend to trace back to missing redirects or lost content.
Do I need redirects if my web addresses stay the same?
Not for pages whose addresses stay identical on the same domain. You still need them for any address that changes, including blog pages the old platform created.
What's the difference between a 301 and a 302 redirect?
A 301 tells search engines the move is permanent, so they swap the new address into their index and pass along the old page's standing. A 302 says the move is temporary, so Google may keep showing the old address. Use 301s, or 308s, for a migration.
If you're planning a move and want to keep what your site has built, get in touch.

