How to migrate a website without losing SEO: a practical guide for Canadian small businesses

Picture a roofing company in Hamilton that finally replaces its ten-year-old website. The new site looks great: faster, cleaner, easier to use on a phone. Then the phone goes quiet. The pages that used to bring in quote requests have vanished from Google, old links from a local directory now lead to dead pages, and the owner is left wondering whether the redesign was a mistake.

The redesign was probably not the problem. The migration was. A website migration is any major change to your domain, platform, URL structure, design, or hosting that affects how search engines crawl, index, and rank your site. Google has to re-learn where everything lives, and if you do not show it clearly, it guesses, and its guesses rarely favour you. The good news is that most migration damage is preventable, and the prevention is mostly planning, not expensive tools.

This guide walks through the full process for a Canadian small business: what counts as a migration, what to record before you move, how to build a redirect map, how to test before launch, what to do on launch day, and what to watch for the month after. Follow it in order, and a migration becomes a controlled project instead of a gamble with your main source of new customers.

The short answer

Learning how to migrate a website without losing SEO comes down to six jobs, done in this order. First, record a benchmark of your current rankings, traffic, and indexed pages so you can tell what actually changed. Second, list every old URL and map each one to its new home with a permanent 301 redirect. Third, carry over your page titles, headings, content, and internal links, changing as little as possible in the move itself. Fourth, test the whole new site on a staging copy that search engines cannot index. Fifth, launch carefully, update Search Console and your sitemap, and check the critical pages within hours. Sixth, monitor rankings, traffic, and crawl errors daily for the first month and fix problems fast.

One principle runs through all six jobs: change one big thing at a time. If you change your domain, your platform, your URL structure, and your content all on the same day, and traffic drops, nobody can tell which change caused it. Separate the migration from the redesign and the rewrite whenever you can. Move first, stabilize, then improve.

What counts as a migration

Many owners only think of a domain change as a migration, but several common projects carry the same risk. Moving from one platform to another, such as WordPress to Shopify, or a website builder to a custom site, is a migration. A redesign is a migration when it changes page URLs, templates, headings, or content, even if the domain stays exactly the same. Changing your URL structure, for example from /services/plumbing to /plumbing-services, is a migration. Moving from HTTP to HTTPS, switching hosts, or merging two websites into one are migrations too.

The risk level depends on how much changes. A redesign that keeps every URL, title, and heading intact and only refreshes the visual design is low risk. A domain change combined with new URLs and rewritten content is high risk, and it deserves the full process in this guide. Before you start, write down exactly which of these are changing: domain, platform, hosting, URL structure, design, content, or some combination. That list decides how careful you need to be, and it stops scope creep halfway through, when someone suggests "just changing the URLs too while we are at it."

Timing matters as well. If your business is seasonal, launch during a quieter period, not in your busiest week. A landscaper should not migrate in April, and a retailer should not migrate in late November. Give yourself a buffer of calm weeks after launch so a fixable problem is an inconvenience, not a crisis.

Step 1: benchmark everything before you move

You cannot prove a migration succeeded, or diagnose a drop, if you never recorded what "normal" looked like. At least two weeks before launch, write down the numbers that matter for your business, not vanity metrics. From Google Search Console, export your top pages by clicks and impressions, the queries bringing people to each page, and the total number of indexed pages. From your analytics, note monthly organic visits, your top landing pages, and how many enquiries, calls, or orders each one produces. From your current site, save a full list of URLs, including blog posts, service pages, and location pages that rarely get attention but still rank.

Also record the on-page details Google currently rewards. For each important page, note the page title, the main heading, and the key topics the page covers. A free crawler tool can export this in one pass, but even a careful spreadsheet works for a small site. Pay special attention to pages with links from other websites, because those links carry authority. Search Console has a links report that shows which of your pages other sites link to. Those pages are your most valuable assets in the move, and they must not be lost or redirected to an unrelated page.

Finally, save a copy of your current sitemap and your robots.txt file, and note any special technical details: pages that should stay out of search results, such as thank-you pages or internal pages, and any pages that intentionally redirect already. This benchmark document becomes your checklist after launch. If a page ranked before and does not rank after, you will know within days, not months. Our guide to setting up Google Search Console covers the free tool behind most of this step if you have not set it up yet.

Step 2: build the redirect map, the single most important document

A redirect map matches every old URL to its new destination. It is a simple spreadsheet with two columns: old URL and new URL. It is also the single most important piece of a migration, because it is what tells both visitors and Google where each page moved to. Every old URL that changes needs a permanent 301 redirect to the most relevant new page, implemented on the server, not with JavaScript or a meta refresh, which search engines handle less reliably.

Follow three rules when building the map. First, go one to one. Each old page should point to the new page that covers the same topic, not to a general page. Second, never redirect everything to the homepage. Sending hundreds of old pages to the homepage looks like a soft 404 to Google, which is a page that appears to exist but gives visitors nothing they were looking for, and it destroys the relevance signal each old page had built. Third, keep chains short. An old URL should point directly to its final destination, not through two or three intermediate redirects. Chains slow visitors down and weaken the signal passed along.

What about pages with no equivalent on the new site? If a page is genuinely gone, let it return a proper 404 or 410 status, which tells Google the page is intentionally removed, rather than forcing it to an unrelated page. But think twice before deleting a page that ranks or earns links. Often the right answer is to fold its content into the closest surviving page and redirect to that page, so the value is preserved rather than thrown away. Review the map with fresh eyes before launch: every row should make sense to a human visitor who clicked the old link expecting specific content.

One more rule that saves businesses real money: keep the old domain registered and its redirects live for at least a year after a domain change, and longer if you can. Links from other websites, bookmarks, printed materials, and old emails keep pointing at the old domain for years. If the old domain expires or the redirects stop, that traffic and authority disappear with it. The renewal cost of one domain in CAD is small compared with rebuilding lost rankings.

Step 3: carry over content and on-page signals

A new platform or template will tempt you to rewrite everything, and a redesign often quietly strips content. Resist both urges during the migration itself. If a page ranked with a certain title, keep that title, or something very close to it. If it ranked with a particular main heading, keep that heading. Meta descriptions do not directly move rankings, but they do affect whether people click your result, so keep them unless you are fixing one that is genuinely broken.

The same discipline applies to body content and internal links. If the old page answered a question in 800 words and the redesigned version answers it in 200 words plus a large image, rankings will usually follow the content down. Check that valuable content, internal links between your pages, and image descriptions all carried over to the new templates. Pay attention to the details templates love to change without telling you: a template that rewrites every page title, adds the business name to every heading, or drops the footer links can quietly change signals across the whole site.

There is one legitimate exception. If your old content was thin, duplicated, or misleading, a migration is a reasonable moment to fix it, but do it as a separate, documented change, and accept that you are adding risk. The cleanest sequence is: migrate with content intact, confirm rankings stabilized, then improve content page by page so you can measure each change. Our guide to what pages a small business website should have is a useful check for whether the new site covers the core pages at all.

Step 4: test on staging before anyone sees the new site

Build the new site on a staging copy that search engines cannot index, and test it thoroughly before launch. Block search engines from the staging site, either with a password or with a robots rule, because a staging copy that Google indexes can compete with your real site and create duplicate content problems. Then crawl the staging site the same way you crawled the old one and compare.

Your staging checklist should include: every redirect from the map returns a 301 status and lands on the correct page, with no chains or loops; every important page returns a 200 status and loads properly on a phone; page titles and headings match the old site, or match the intended changes you documented; internal links point to new URLs, not to old ones that will redirect; forms, booking steps, and checkout actually work end to end; page speed is no worse than the old site, and ideally better; and the robots.txt file on staging does not accidentally carry over to the live site blocking everything. That last one is a classic migration disaster: a staging block left in place on launch day makes the whole new site invisible to Google.

Test with real people, not just tools. Ask someone who has never seen the site to find a service, get a price or quote step, and contact you, all on a phone. Watch where they hesitate. A migration that preserves rankings but breaks the contact form has still failed the business, even if the traffic chart looks fine.

Step 5: launch day, in order

Launch day should feel boring, because all the decisions were made earlier. Put the redirects live first, then the new site, then verify in this order. Check that the homepage and your five most important pages load correctly and show the right titles. Click through the redirect map samples yourself, including at least one old URL from each section of the old site. Confirm the robots.txt file on the live site allows crawling, and that the staging block is gone.

Next, handle Search Console. If you changed domains, use the Change of Address tool, which tells Google the site has moved from one domain to another. Note that this tool is only for domain or subdomain moves: a redesign, a platform change, or a URL path change on the same domain does not need it. In all cases, submit the new sitemap in Search Console and ask Google to index your most important new pages. Update your Google Business Profile website link if the domain changed, and update your social profiles, directory listings, and email signatures over the following days, starting with the listings that send you the most traffic.

Within hours, check Search Console for new crawl errors and check your analytics for a sudden drop in organic traffic or enquiries. A small, temporary fluctuation after a move is normal while Google re-reads the site, and it is not a reason to panic-edit on day one. A sharp, sustained drop, or a flood of 404 errors, is a reason to act immediately: it usually points to a missing redirect, a wrong robots rule, or a broken template.

Step 6: monitor for 30 days, then for 90

The first month after launch is when fast fixes matter most. Check Search Console daily for the first two weeks, then weekly: coverage errors, pages Google cannot index, redirect errors, and any page that was indexed before and is now missing. Compare organic traffic and rankings against your benchmark weekly, page by page, not just as a site total. A site total can hide a disaster on your best page behind a gain somewhere unimportant.

Fix problems in priority order: broken redirects and 404s on pages that used to rank or earn links first, then missing content or changed titles on pages that slipped, then site speed or mobile issues. Keep a simple log of what you changed and when, so you can connect a recovery to the fix that caused it. Expect rankings to settle over weeks rather than days, and give a clean migration roughly a month before judging it fully, longer for a large site or a domain change.

After 30 days, move to a monthly check for another two months: rankings for your main pages, organic enquiries, and any remaining crawl errors. If traffic has not recovered to near its benchmark after 90 days, something structural is still wrong, such as lost content, lost links, or a template problem, and it is worth getting a technical review rather than waiting longer. Do not keep rewriting content in the meantime to "fix" the drop, because each rewrite adds another variable and makes diagnosis harder.

Canadian details worth getting right

A few details are specific to Canadian businesses. If you are moving to or from a .ca domain, remember that .ca domains are managed through CIRA-accredited registrars, and the registrant details and transfer process differ slightly from generic domains. Start any domain transfer early, keep the old domain registered and redirecting, and do not let the old domain lapse during the transition. If your site serves customers in Quebec or across Canada in both official languages, preserve both language versions of each page and their relationship to each other, so French pages redirect to French pages and English pages to English pages, not all to one language.

Privacy and legal pages deserve the same care as service pages. If your site has a privacy policy, terms page, or accessibility statement, migrate those pages with working links, and check that consent and cookie tools still work on the new platform. Our guide to whether your website needs a privacy policy in Canada covers why those pages matter. Also update your business listings consistently: a domain change that reaches Google but not your chamber listing, your supplier directory, or your Yelp page leaves customers and search engines with conflicting information. Our local SEO guide covers the consistency work in detail.

The mistakes that tank rankings

Most migration disasters come from a short list of avoidable errors. Redirecting everything to the homepage is the most common. Forgetting the redirect map entirely, and assuming the new platform handles it, is a close second. Leaving a staging block on the live site, or publishing a robots.txt file that blocks crawling, can make a site invisible overnight. Deleting ranking pages during a redesign, or merging several ranking pages into one thin page, throws away years of earned visibility. Changing the domain, platform, URLs, and content all at once makes any drop impossible to diagnose. And launching without a benchmark means nobody notices the drop until a customer mentions it months later.

Be equally wary of shortcuts sold as migration services. Anyone who promises zero ranking change, guarantees a top position after a move, or cannot show you a redirect map and a benchmark document is not running the process in this guide. A legitimate provider will explain each step, show you the map before launch, report on rankings and enquiries rather than only on traffic, and leave you owning your domain, your Search Console property, and your redirects. If a provider wants to register your new domain in their own name, walk away, because regaining control of your own domain is a painful and sometimes expensive process.

When to hire help, and what it should cost

A small site with a handful of pages and no domain change can often be migrated by a careful owner following this guide, especially if the platform offers built-in redirect tools. Hire help when the site is large, the domain is changing, the platform is changing, or organic search brings in a meaningful share of your enquiries, because the cost of a lost ranking usually exceeds the cost of doing the migration properly. In CAD terms, compare proposals on the same basis: whether they include the benchmark, the redirect map, staging tests, launch checks, and 30 days of monitoring, rather than only the design or build price. Our pricing page explains how Webloped projects are structured in CAD if you want a reference point.

Also consider timing the migration with a redesign decision. If your site also needs a visual overhaul, our guide to website redesign costs in Canada helps you budget that part separately from the migration work. Keeping the two budgets and timelines distinct is itself a migration best practice: it stops a design project from quietly swallowing the SEO safeguards.

How Webloped fits in

We are a web design and AI automation company based in Cambridge, Ontario. We handle migrations as a planned project, not as an afterthought to a redesign: benchmark first, redirect map before build, staging tests before launch, and monitoring after launch, so your rankings survive the move. Our services page outlines what we do. If you are planning a redesign, a platform switch, or a domain change, send us a message or email contact@webloped.ca. Tell us your current platform, whether your domain or URLs will change, and which pages bring in your enquiries now, and we will tell you honestly which steps matter most for your site.

Frequently asked questions

Will my rankings drop temporarily after a migration?

Some fluctuation is normal while Google re-crawls and re-indexes the new site, even after a well-run migration. A small, short dip that recovers over a few weeks is typical. A large or sustained drop usually means something specific broke, such as missing redirects, blocked crawling, or lost content, and it should be investigated against your benchmark rather than waited out.

How long should I keep old redirects in place?

Keep them for at least a year after a domain change, and indefinitely if the cost is negligible and the old URLs still receive traffic or links. Other websites, bookmarks, and printed materials keep pointing at old addresses long after you have forgotten them. Removing redirects early is one of the easiest ways to lose rankings you had already recovered.

Do I need Google's Change of Address tool for a redesign?

No. The Change of Address tool is only for moves to a new domain or subdomain. A redesign, a platform change, or a change to URL paths on the same domain does not need it. For those moves, correct redirects, an updated sitemap, and monitoring in Search Console are the right tools.

Can I redesign and migrate at the same time?

You can, but it adds risk, because a traffic drop afterwards could come from the design, the URLs, the content, or the platform, and you will not know which. When possible, separate them: migrate first with content and URLs intact, confirm rankings stabilized, then redesign or rewrite as a second project. If you must do both at once, be extra careful with the redirect map and the content checks, because those are your safety net.