Changing your domain is a high-stakes technical event that can preserve or destroy years of SEO equity. This checklist covers the planning, redirect architecture, platform-specific configuration, and post-migration monitoring needed to execute a Canadian domain change without losing rankings or traffic.
Companies switch domains for rebrand alignment, acquisition integration, dropping outdated hyphens or keywords, geographic repositioning like adopting .ca for Canadian identity, or consolidating multiple properties. Each reason carries different SEO risk profiles. A rebrand to a completely new brand name requires careful messaging and backlink outreach because existing link anchors will suddenly mismatch. An acquisition merge faces duplicate content resolution when two catalogs overlap. Moving from .com to .ca can signal regional focus to Google but may confuse international backlinks that assumed global scope. The common thread is that search engines treat domain changes as site moves requiring explicit signals to transfer authority. Without those signals, crawlers interpret the new domain as an entirely separate entity and the old domain as abandoned or duplicate. Authority does not automatically follow. PageRank and trust metrics stay with the old URLs unless 301 redirects explicitly tell crawlers to transfer credit. Planning the change means auditing which URLs hold backlinks, which rank for priority keywords, and which conversion paths depend on specific URL structures. You need the old site's sitemap, a full crawl export, Google Analytics historical landing page data, and Search Console top queries report before you touch DNS.
Start with a complete crawl of the existing domain using Screaming Frog or similar tooling to capture every indexable URL, its status code, canonical tag, and internal link count. Export this as your source-of-truth inventory. Cross-reference it with Google Search Console performance data to identify which URLs drive impressions and clicks. Pages with zero traffic and zero backlinks can sometimes be retired rather than redirected, simplifying the map. For every URL you intend to preserve, define its exact destination on the new domain. This is 1:1 mapping: old homepage to new homepage, old product category to new product category, old blog post slug to new blog post slug. Avoid many-to-one redirects where dozens of old URLs point to the new homepage — that loses topical relevance signals and degrades user experience. If content is genuinely retired, map to the closest thematic equivalent or a proper 410 Gone if no equivalent exists. Document this mapping in a spreadsheet with columns for old URL, new URL, redirect type (301 permanent), and notes on backlink count or ranking keywords. This becomes your redirect ruleset. For Canadian businesses, check that bilingual content paths remain parallel — if /en/services and /fr/services exist on the old domain, they must map to equivalent /en/services and /fr/services structures on the new domain, not collapse into a single English page.
Server-side 301 redirects at the web server or load balancer level are the only acceptable method. Do not use JavaScript redirects, meta refresh tags, or canonical tags as substitutes — those are hints, not commands, and crawlers often ignore or delay them. If you run Apache, implement via .htaccess using RedirectMatch or RewriteRule directives. Nginx uses return 301 or rewrite permanent in the server block. For managed platforms like Shopify, use the built-in redirect manager and verify each entry processes as 301 in response headers. WordPress sites should handle redirects via a plugin like Redirection or Yoast Premium, but always test that the plugin output is actual 301 headers, not meta tags. After implementing, test a sample of redirects using curl or browser DevTools Network tab to confirm the HTTP response is 301 Moved Permanently with the correct Location header pointing to the new URL. Test edge cases: trailing slash variants, http versus https, www versus non-www, query parameters. All combinations of the old URL should resolve to the canonical new URL in a single hop. Chained redirects — old to intermediary to new — waste crawl budget and dilute equity. Ensure your new domain SSL certificate is active and the new site forces HTTPS before redirects go live. If the old domain expires or SSL lapses, browsers will block the redirect with a security warning.
Set up a new Google Search Console property for the new domain and verify ownership via DNS TXT record or HTML file upload. Keep the old domain property active and verified as well — you will monitor both during transition. In the old property, submit a Change of Address request under Settings. This tells Google explicitly that the site has moved and accelerates re-indexation under the new domain. Upload an XML sitemap to the new property listing all new URLs. Recrawl requests via URL Inspection can expedite discovery but do not replace sitemap submission. In Google Analytics, update the property settings to reflect the new domain and set up a separate view or data stream if you want to compare old versus new traffic side by side during transition. Update Google Business Profile URLs, social media profiles, email signatures, and any third-party directories or review platforms that link to the old domain. For Canadian businesses, update your CRA Business Number registration if the domain change reflects a legal name change, and revise bilingual marketing materials to reflect the new URL. Update CDN configuration and DNS records so the new domain resolves correctly. Lower TTL on DNS records a few days before migration to allow faster propagation adjustments if issues arise. Once redirects and DNS are live, audit internal links on the new site — menus, footers, blog cross-links — to point directly to new URLs rather than relying on redirects for internal navigation.
Expect a temporary traffic dip even with perfect execution — Google recrawls the old URLs, follows redirects, re-evaluates the new URLs, and recalculates rankings. This process typically spans two to four weeks. Monitor Google Search Console coverage reports daily for crawl errors, redirect errors, or soft 404s appearing on the new domain. Check that old URLs return 301 and new URLs return 200. Watch for indexation overlap where both old and new versions appear in the index simultaneously, which indicates redirect failures or mixed canonicals. Pull organic traffic and keyword rankings in your tracking tool to spot pages that lose visibility. If a high-value page drops, verify its redirect is live, check the new URL renders properly, ensure it did not lose on-page elements like schema or hreflang tags, and confirm backlinks still point to the old URL so the redirect transfers authority. Review Core Web Vitals and server response times — domain changes sometimes surface hosting or CDN misconfigurations that degrade performance. Canadian sites serving bilingual content should confirm hreflang annotations now reference the new domain and that language-switcher links are updated. After four weeks, if traffic and rankings have stabilized, you can reduce monitoring frequency. Keep the old domain registered and redirects active for at least twelve months to capture slow-moving backlinks and latent user bookmarks.
Not all domain changes are full-site swaps. Moving a blog from blog.olddomain.com to newdomain.com/blog requires subdirectory redirects and potentially different Search Console property setup if the subdomain was a separate property. Redirecting a subset of pages — such as retiring a product line — demands careful 410 or 301 decisions per URL. If migrating from a .com to a .ca to emphasize Canadian presence, consider whether international traffic previously targeted via hreflang needs new annotations pointing to a .com/ca subdirectory or a separate property. Quebec businesses must maintain French-language paths under Bill 96 digital presence expectations, so ensure /fr/ routes are preserved and redirected accurately. If the domain change coincides with a platform migration — WordPress to Shopify, or custom CMS to headless architecture — layer the redirect logic carefully and test staging environments before production cutover. Some scenarios warrant a phased rollout where certain sections migrate first, validated, then the remainder follows. In those cases, maintain separate redirect rulesets per phase and keep comprehensive logs of what moved when to simplify rollback if critical issues surface.
Google typically recrawls and reassigns rankings within two to four weeks if redirects are implemented correctly and the Change of Address tool is used in Search Console. However, slower-moving backlinks and cached search results may take additional weeks to fully update. Maintaining the old domain and redirects for at least twelve months ensures all inbound links and residual bookmarks eventually transfer authority to the new domain.
No. Meta refresh redirects are treated as soft hints by search engines and often delay or fail to transfer PageRank and ranking signals. They also degrade user experience with visible page loads. Server-side 301 redirects are the only method that reliably signals a permanent move and transfers SEO equity. Always implement redirects at the web server or load balancer level using proper HTTP status codes.
You should keep the old domain registered and serving 301 redirects for a minimum of twelve months to capture slow backlink updates and user bookmarks. After that, risk diminishes but does not disappear. Some high-authority sites maintain redirects indefinitely for legacy equity. If you let the old domain expire, it may be purchased by a third party, breaking existing backlinks and potentially harming your brand if repurposed for unrelated or harmful content.
Your Google Business Profile does not automatically update when you change domains. You must manually edit the website URL field in your profile dashboard to reflect the new domain. If you operate multiple locations, update each profile individually. For Canadian businesses with bilingual listings, ensure both English and French profile versions point to the correct new language paths. Mismatched URLs can confuse local searchers and reduce click-through from Maps results.
Ensure both the old domain's http and https versions redirect to the new domain's https version in a single hop. Do not chain redirects through http-to-https then old-to-new — configure rules so any variant of the old URL resolves directly to the canonical new URL. Test all combinations including www versus non-www to confirm single-hop 301s. This minimizes crawl budget waste and preserves link equity.
Update all hreflang annotations across every language and regional version to reference the new domain URLs. If moving from olddomain.com/ca to newdomain.ca, the hreflang tags on the new Canadian pages must point to the new URL structure, and alternate language versions on other domains or subdirectories must also update their annotations. Failing to synchronize hreflang after a domain change can cause incorrect language targeting and duplicate content issues in international search results.