Migrating to a new domain requires careful technical execution and realistic expectations about traffic fluctuation. This guide walks through the planning, implementation, and monitoring phases that protect your existing search visibility while establishing authority on the new URL.
Rebranding, mergers, trademark conflicts, and geographic expansion all trigger domain migrations. A Toronto company acquiring a national competitor might consolidate onto the stronger brand domain. A Quebec firm expanding into English Canada sometimes shifts from a .qc.ca to a bilingual .ca. The technical challenge is that every URL on your old domain has accumulated link equity, crawl history, and user signals over months or years. When you switch domains, you're asking Google to transfer that trust to entirely new URLs. The algorithm does honor proper 301 redirects, but it treats the new domain as partially unproven until it observes consistent behavior—traffic patterns, engagement metrics, and link validation. Expect turbulence. The goal is controlled turbulence with a net path upward, not a magic same-day switch. Understanding that Google needs verification time prevents panic when you see temporary ranking fluctuations in week two or three.
Export every URL currently indexed on the old domain using Search Console performance data or a crawl tool like Screaming Frog. You need the complete list—product pages, blog posts, category pages, PDFs, everything. Next, define the corresponding destination URL on the new domain. Identical structure migrations are simplest: oldsite.com/services/seo becomes newsite.com/services/seo with a 1:1 match. Structural changes require judgment. If you're flattening categories or renaming sections, map each old URL to the most relevant new equivalent. Orphaned content that no longer fits should redirect to a topically similar page, not the homepage. Build this mapping in a spreadsheet with columns: Old URL, New URL, Redirect Type (301), Notes. This sheet becomes the implementation blueprint. Do not skip URLs because they seem low-value; broken links erode trust and waste the crawl budget Google allocates to discovering your new domain. Validate the mapping by sampling 20-30 URLs and confirming the new destinations actually exist and serve the same user intent.
Implementation method depends on your server and CMS. Apache servers use .htaccess files with RewriteRule directives. Nginx requires location blocks in the config file. Cloudflare and other CDNs offer bulk redirect features in their dashboard. WordPress has plugins, but server-level redirects perform faster and survive theme changes. The redirect must be a 301 (permanent), not a 302 (temporary). Google treats 302s as signals that the old URL will return, so it doesn't transfer authority. For large sites—hundreds or thousands of pages—manual entry isn't practical. Generate the redirect rules programmatically from your mapping spreadsheet. Most web hosts or agencies can script this in under an hour once the mapping is clean. Test a small batch first: redirect 10-15 URLs, verify they land correctly and return a 301 status code, then deploy the full set. Redirects should be live before you update any external references or submit the change of address in Search Console. This ensures Google encounters the 301 immediately when it recrawls.
Verify ownership of the new domain in Google Search Console as a separate property. You'll run both old and new properties in parallel for several weeks. In the old property, navigate to Settings and use the Change of Address tool—this officially notifies Google of the migration. Submit the new domain's XML sitemap in the new property so Google discovers the full URL set quickly. Update the sitemap reference in robots.txt on the new domain. Monitor the old property's coverage report; you should see indexed URLs gradually drop as Google recrawls and finds the 301s. In the new property, watch for indexing of the new URLs. This process is not instant. Google recrawls based on perceived site importance and historical crawl rate. A site that updated daily gets recrawled faster than a static five-page brochure. Typical timeline: noticeable indexing shifts within one week, majority transfer by week three, full stabilization by week six to eight.
Links from other sites pointing to your old domain still work because of the 301s, but you want canonical signals pointing directly to the new domain over time. Start with properties you control: social media profiles, email signatures, Google Business Profile, Bing Places, Apple Maps, industry directories. Canadian businesses must update CRA Business Number records if the domain is part of official correspondence, and revise any provincial registry entries. Contact your top referring domains—partners, suppliers, media outlets—and request they update their links. This isn't urgent in week one, but over six months you want high-authority backlinks pointing to the new domain natively. The 301 passes most link equity, but direct links are cleaner. For paid advertising, update all destination URLs in Google Ads, Facebook, LinkedIn campaigns before the migration goes live, or budget for a brief pause to swap them. Emails in flight with old URLs will still work, but new campaigns should reference the new domain exclusively.
Expect organic traffic to dip temporarily. Google needs time to recrawl, validate redirects, and reassign ranking signals. A well-executed migration typically sees a 5-15% traffic decline in weeks two through four, then recovery and often a small lift by week eight as the new domain's cleaner structure or updated content takes effect. Track this in Google Analytics with date-range comparisons and annotations marking migration day. Segment by landing page to identify any URLs that lost disproportionate traffic—these may have redirect issues or content mismatches. Check Search Console for crawl errors, redirect chains (old URL → middle URL → new URL, which slows things down), and soft 404s. If certain pages aren't recovering, audit the 301 implementation for those URLs and confirm the new content satisfies the same search intent. Canadian traffic sources sometimes behave differently—government and university referrals may take longer to update their links, while social and paid adapt immediately. Patience and data-driven adjustments in the first two months determine whether the migration becomes a growth lever or a prolonged recovery project.
A straightforward migration—identical structure, 50-200 pages—typically requires 15-25 hours of technical work: audit, mapping, redirect setup, testing, and monitoring. Agencies often price this as a fixed project in the low four figures CAD. Complex migrations with structural changes, e-commerce SKU mappings, or multilingual French/English content can extend to 40-60 hours. DIY is feasible for small sites if you're comfortable editing server config files and interpreting Search Console data. The biggest cost isn't labor—it's the opportunity cost of a botched migration that loses rankings for high-value keywords. Hiring expertise makes sense when organic traffic drives material revenue or leads. Timeframe is rarely urgent; plan for a six-week window from kickoff to stable post-migration metrics. Migrations executed in a rush—late Friday deployments, untested redirect files—cause extended traffic loss that takes months to recover. Treat this as a deliberate project with checkpoints, not a quick domain swap.
Most migrations show significant indexing and ranking transfer within three to four weeks, with full stabilization typically occurring by week six to eight. Google's recrawl speed depends on your site's historical update frequency and authority. High-traffic sites with strong backlink profiles migrate faster than small, infrequently updated sites. You'll see gradual shifts in Search Console as old URLs drop from the index and new URLs gain impressions.
Yes, maintain the old domain and its 301 redirects for at least one year. This gives Google ample time to recrawl all URLs, transfer authority, and update its index. It also ensures any lingering external links continue to function. After twelve months, you can evaluate traffic logs on the old domain—if redirects are receiving negligible hits, you can consider letting it expire. Renewing a domain annually is inexpensive insurance against broken links.
Properly implemented 301 redirects preserve most of your ranking authority. Expect temporary fluctuations—a 5-15% traffic dip is common in the first few weeks as Google recrawls and reassigns signals. Rankings for high-authority pages often recover to pre-migration levels or better within six weeks. The key is accurate URL mapping and clean technical execution. Poorly configured redirects or missing mappings will cause ranking loss that's harder to recover.
All-at-once migrations are cleaner and less confusing for both users and search engines. Partial migrations—moving some sections while leaving others on the old domain—create split authority and complicate tracking. If your site is extremely large, you can phase redirects by section, but each section should migrate completely in one step. Avoid leaving the same content accessible on both domains simultaneously, as this creates duplicate content issues and dilutes signals.
Your Google Business Profile is tied to your business entity, not your domain, so local map rankings don't automatically drop. However, you must manually update the website URL in your profile settings to point to the new domain. This update is immediate in the dashboard but can take a few days to reflect in search results. Local organic rankings—the standard blue links below the map pack—follow the same migration rules as non-local pages and require proper 301 redirects.
Yes, 301 redirects pass the majority of link equity from backlinks on the old domain to the corresponding new URLs. Google treats the redirect as a strong signal to transfer authority. Over time, it's beneficial to contact high-value referring sites and request they update their links to point directly to the new domain, but this isn't urgent. The redirects will continue to function and pass value as long as the old domain remains active.