Website Migration Without Losing Your Google Rankings
You can move to a new platform, a new domain, or a new design without losing your Google rankings if every old URL permanently redirects to its closest new equivalent, the content that earned those rankings comes along, and you tell Google about the move through Search Console. Most traffic drops after a migration come from skipped redirects, deleted pages, or a staging setting left switched on, not from the move itself. Expect some short-term movement in search results while Google recrawls, then a return to your previous level if the groundwork was done right.
What it is, in plain English
A website migration is any change big enough that Google has to relearn your site: switching platforms (say, from Wix to WordPress or from WooCommerce to Shopify), moving to a new domain, restructuring your URLs, or launching a redesign that rewrites most pages. A simple theme swap that keeps every page and address the same usually isn't a migration in this sense.
Google ranks individual pages, not your business as a whole. Each page has built up history: links from other sites, clicks from searchers, and a place in Google's index. When a page's address changes and nothing points from the old one to the new one, that history doesn't transfer. The old URL starts returning an error, and the new page has to earn its position from scratch.
For a small business, this matters because a handful of pages often bring in most of the leads: a service page that ranks for your city, a product category, a menu page. Lose those, and the phone gets quieter for weeks or months while you figure out why. The goal of a careful migration service is simple: the customer searching for you tomorrow finds you just as easily as they did yesterday.
How to migrate step by step
The work splits into three stages: before launch, launch day, and the weeks after. The first stage takes the most time and prevents most of the damage.
- Inventory every URL you have now. Export the full list of live pages from your current platform, your XML sitemap (a file that lists your pages for search engines), and Google Search Console. Don't forget blog posts, PDFs, image-heavy gallery pages, and old landing pages from past ad campaigns.
- Find the pages that actually earn traffic. In Search Console's Performance report and in Google Analytics, sort pages by clicks and by leads or sales. These pages get extra attention: their wording, headings, and structure should survive the move mostly intact.
- Build a redirect map. This is a spreadsheet with two columns: every old URL and the single most relevant new URL it should point to. Old service page to new service page, old product to the same product. Sending everything to the homepage is the classic shortcut, and Google tends to treat those redirects like dead pages.
- Set up the new site on a hidden staging copy. Staging is a private version of the site used for testing. Block it from search engines while you work, so Google doesn't index a half-finished duplicate.
- Carry over on-page SEO. Page titles, meta descriptions, headings, image alt text, structured data (code that tells Google your hours, prices, or reviews), and internal links between your own pages. Platforms rarely move these cleanly on their own.
- Launch and switch on the redirects at the same moment. Use 301 redirects, which tell browsers and Google that a page has moved permanently. Then remove the staging block, check that robots.txt (the file that tells crawlers what they may visit) isn't blocking the whole site, and make sure HTTPS works on every version of your address.
- Tell Google. Submit the new sitemap in Search Console. If you changed domains, verify both domains and use the Change of Address tool. Update your Google Business Profile website link, your social profiles, and any directory listings you control.
- Watch closely for the next several weeks. Check Search Console for crawl errors and pages that are "not found," test your top URLs by hand, and compare clicks against the same period before launch. Google advises keeping redirects in place for at least a year; in practice, leave them indefinitely.
Pre-launch checklist
Run through this table on the day before launch and again right after. Each line is a common reason a migration loses traffic.
| Check | What goes wrong if you skip it | How to verify |
|---|---|---|
| Every old URL has a 301 to a relevant new page | Old links and search results lead to error pages | Test the old URL list with a crawler or redirect checker |
| No redirect chains (A to B to C) | Slower pages, and some link value can get lost along the way | Each old URL should reach its final page in one hop |
| Staging "noindex" and password removed | Google drops the whole site from results | View page source on live pages; check robots.txt |
| Titles, headings, and content on top pages preserved | Pages rank lower for the searches they used to win | Compare old and new versions of each top page |
| Analytics and conversion tracking installed | You can't tell whether leads dropped or tracking broke | Submit a test form and confirm it registers |
| New sitemap submitted, Search Console verified | Google finds the new structure slowly | Sitemaps report in Search Console shows it as read |
| Internal links point to new URLs directly | Your own site sends visitors and crawlers through redirects | Crawl the new site and look for links that redirect |
Examples for small businesses
A home services contractor rebuilding an old site. A roofing or HVAC company often has one page per service and per town it covers, built up over years. The new design merges them into fewer, cleaner pages. That's fine, as long as each old town page redirects to the page that now covers that town, and the new page still names the town, the service, and the phone number clearly. Delete those pages without redirects and the company quietly vanishes from searches in its surrounding towns.
A dental office or med spa changing its domain. After a rebrand, the practice moves from an old name to a new one. Beyond page-by-page redirects, this one needs the Change of Address tool in Search Console, an updated website link in the Google Business Profile, and updated links in insurance directories and booking platforms. Keep the old domain registered and renewed, because letting it lapse breaks every redirect at once.
An e-commerce store moving to Shopify. Shopify uses fixed URL patterns such as /products/ and /collections/, so nearly every product address changes. Shopify has a built-in URL redirect tool that accepts a bulk import, which makes the redirect map the core of the project. Product descriptions, reviews, and image alt text need to come across too, or product pages lose the detail that helped them rank.
A restaurant or cafe replacing a menu-builder site. The old site might host its menu as a PDF that ranks for "[restaurant name] menu." If the new site shows the menu as a regular web page, redirect the old PDF address to it. Update the menu and ordering links in your Google Business Profile the same day, since many diners go straight from Maps to the menu.
Common mistakes
- Leaving the staging block on. A single "noindex" setting carried over from the test site tells Google to remove every page. It's easy to miss because the site looks perfectly normal to visitors.
- Redirecting everything to the homepage. It feels safe, but a visitor looking for a specific service lands somewhere generic, and Google tends to treat it as if the old page simply disappeared.
- Rewriting the copy on your best pages during the move. Changing platform and content at the same time makes it hard to tell what caused a drop. Move first, then improve content in a later round, one page at a time.
- Using temporary redirects. A 302 redirect signals a temporary move. For a permanent migration, use 301 so Google knows to update its index.
- Launching right before your busy season. Even a clean migration can shuffle rankings for a while. Pick a slower month if your business has one.
- Not tracking before and after. Without a snapshot of rankings, traffic, and leads from before launch, you can't prove the move went well or spot what slipped.
And an honest note: if you're only refreshing the look and every page keeps its address and content, you don't need a full migration process. A quick check of titles, tracking, and mobile layout after launch is enough.
What it costs and what drives the price
Migration pricing is driven mostly by how many URLs you have and how different the old and new sites are, not by the design itself. A small brochure site with a dozen pages moving to a new theme on the same domain is a modest job. A store with thousands of products switching platforms and domains at the same time is a project in its own right.
- Number of pages and products. Every URL needs a mapped destination and a test after launch.
- Platform change. Moving between systems (WordPress, Wix, Squarespace, Shopify, WooCommerce) means exporting content, rebuilding templates, and handling URL patterns that the new platform may force on you.
- Domain change. Adds Search Console work, updates to external listings, and more monitoring.
- Data that has to move. Customer accounts, order history, reviews, blog archives, and forms connected to tools like HubSpot or your booking software.
- Monitoring period. Checking Search Console and fixing errors for weeks after launch is where many cheap quotes cut corners.
When comparing quotes, ask each provider to show you the redirect map they'll build and how long they'll watch Search Console after launch. A quote that doesn't mention either is pricing a rebuild, not a migration.
FAQ
Will I lose SEO if I change my website?
Not if old URLs redirect to matching new pages, your top pages keep their content, and nothing blocks search engines after launch. Some ranking movement in the first weeks is normal while Google recrawls.
How long does it take Google to recognize a site migration?
It depends on the size of the site and how often Google crawls it. Small sites are often reprocessed within weeks; larger ones can take longer. Submitting a sitemap and fixing crawl errors quickly helps.
Do I need 301 redirects when changing website platforms?
Yes, whenever any page address changes. Platforms like Shopify, Squarespace, and WordPress each structure URLs differently, so most platform switches change at least some addresses.
How long should I keep redirects after a website migration?
Google recommends at least a year. Keeping them permanently costs little and protects old links from other sites, bookmarks, and printed materials.
What is a website migration service?
It's help planning and running the move: inventorying URLs, building the redirect map, carrying over on-page SEO, testing before launch, and monitoring Search Console afterward.
Can I migrate my website myself?
For a small site on the same domain with few URL changes, often yes, using the checklist above. Domain changes, platform switches with many products, or sites that bring in most of your leads are where outside help pays for itself.
Planning a move and worried about what it will do to your traffic? Tell us what's broken or what you're changing, and we'll map out the migration with you. You can also see what else we build at yafini.com.