SEO migrations demand rigorous pre-launch validation, structured redirect mapping, and post-launch monitoring to preserve organic revenue. This guide covers the crawl-level mechanics, team coordination checkpoints, and timeline realities that determine whether a platform swap, domain move, or site consolidation protects your existing search visibility.
A migration crosses the SEO threshold when you alter URLs, change domains, swap CMS platforms, merge sites, move from HTTP to HTTPS, or restructure your information architecture in a way that breaks existing indexation. Rebranding a domain, consolidating regional sites, switching from Shopify to a headless stack, or collapsing subdirectories all count. The common thread is that Google must re-crawl, re-evaluate canonical signals, and re-associate ranking history with new addresses.
Not every website change is a migration. Updating page templates, refreshing content, or adjusting internal link anchor text within stable URLs does not require redirect planning. The distinction matters because true migrations carry downside risk if redirect chains break, canonical tags conflict, or crawl budget gets wasted on soft-404 loops. If your URLs stay identical and your domain remains unchanged, you are deploying an update, not executing a migration.
Start by crawling your current site with Screaming Frog, Sitebulb, or DeepCrawl to generate a complete URL list — not just what appears in your XML sitemap, but every page Googlebot can discover through internal links. Export that crawl with response codes, canonical declarations, indexation status, and inbound link counts. Cross-reference against Google Search Console's coverage report to catch pages Google knows about that your crawler missed, often due to orphaned links or external backlinks.
Pair the crawl data with an organic landing-page report from Google Analytics covering the past twelve months. Rank URLs by sessions and conversion events so you know which pages carry revenue weight. This inventory becomes your redirect source list. For Canadian sites operating bilingual structures, verify that /en/ and /fr/ hierarchies are both captured; missing a French-language section during mapping will orphan that traffic. The baseline audit is not optional — you cannot write accurate redirects without knowing what currently exists and what currently performs.
Build a spreadsheet with three columns: old URL, new URL, redirect type. Every row represents one mapping decision. Aim for 1:1 redirects wherever topical equivalence exists — an old product page should point to the new product page, not a category landing or homepage. Use 301 permanent redirects for URLs that have moved and will not return. Reserve 302 temporary redirects only for short-term placeholder scenarios.
Avoid wildcard or regex redirect rules unless you have verified that pattern matching will not introduce collateral errors. A wildcard that strips query parameters might break tracking; a category-level redirect that dumps twenty product URLs onto one overview page will dilute relevance signals. When no direct equivalent exists — such as a discontinued service page — redirect to the closest thematic parent rather than the homepage. For .ca domains migrating to .com or vice versa, confirm hreflang annotations match the new domain structure so Google does not treat the move as duplicate content across geographies. Test a sample of mappings in staging before pushing rules to production.
Deploy the new site architecture and redirect rules in a staging environment that mirrors production server configuration. Run a full crawl against staging, following redirects and checking terminal HTTP codes. Look for redirect chains longer than one hop, mixed HTTP/HTTPS destinations, or loops where page A redirects to page B which redirects back to A. Validate that canonical tags on the new URLs point to themselves, not back to old addresses.
Submit a handful of staging URLs to Google Search Console's URL Inspection tool if your staging environment is accessible to Googlebot, or use a local crawl paired with manual browser checks. Confirm that structured data carries over correctly, particularly for Canadian retailers using Product schema with CAD pricing. Review mobile rendering and Core Web Vitals in staging; migrations often surface performance regressions when switching platforms. Treat staging validation as a rehearsal — any issue found here is one you will not face in production.
Schedule the migration during a low-traffic window if your analytics show predictable daily patterns. Flip DNS records or push production code, then immediately verify that the homepage and five high-traffic landing pages return the correct HTTP codes and content. Check that your XML sitemap now lists new URLs and is accessible at the new location. Submit the updated sitemap in Google Search Console and trigger a crawl of your most important pages using the URL Inspection tool's request-indexing feature.
Monitor server logs or a real-time analytics dashboard for the first two hours. Look for unexpected spikes in 404 errors, redirect loops, or bot traffic anomalies. If Googlebot begins crawling heavily within minutes, that is normal — search engines prioritize sites they trust and will attempt to re-index quickly. Do not panic if impressions dip slightly in the first 24 hours; Google is recalculating signals. Keep your old domain's hosting and redirects live indefinitely, or at minimum for twelve months, so that external backlinks and stale bookmarks continue to resolve.
Traffic and ranking stabilization typically unfolds over 60 to 90 days, not days or weeks. In the first two weeks, watch Google Search Console's coverage report for new errors — particularly 'Crawled - currently not indexed' or 'Discovered - currently not indexed' statuses on pages that previously ranked. Cross-check against your redirect map to ensure mappings are resolving correctly. Review position and click data in the Performance report, filtering by page to spot any URLs that lost visibility.
Between weeks three and eight, compare organic landing-page sessions in Google Analytics year-over-year, accounting for seasonality. Canadian agencies often see regional traffic shifts if the migration changed geo-targeting settings or moved from a .ca to .com domain without proper hreflang. By day ninety, most sites have regained ranking equilibrium if redirects were accurate and content remained substantively unchanged. If traffic remains depressed past that window, audit for technical issues like faulty canonicals, orphaned pages, or server performance problems introduced during the platform swap. Document the migration timeline and any corrective actions in a post-mortem so future projects benefit from the lessons.
SEO migration execution involves developers, DevOps or hosting engineers, content managers, and an SEO lead. A typical mid-sized migration — 500 to 5,000 URLs, single domain, straightforward CMS-to-CMS swap — requires two to four weeks for discovery and mapping, one to two weeks for staging validation, and three weeks of post-launch monitoring. Larger enterprise migrations with multiple domains, international hreflang configurations, or custom redirect logic can extend discovery to six weeks and post-launch oversight to eight.
Agency fees in Canada generally reflect scope rather than URL count. A discovery and redirect-mapping engagement might range from mid-four to low-five figures CAD, depending on site complexity and whether the agency also handles staging QA. Post-launch monitoring is often billed as a retained hourly block or fixed sprint. In-house teams should allocate at least one full-time equivalent for migration planning and execution, plus developer time for redirect rule implementation. Treat the migration as a project with discrete phases, not an overnight switch, and communicate realistic expectations to stakeholders about the monitoring tail.
Google begins re-crawling immediately but full ranking stabilization typically takes 60 to 90 days. High-authority sites with strong crawl budgets often stabilize faster, while newer or less-trusted domains may see longer adjustment periods. Monitor Search Console coverage and performance reports weekly to track indexation progress and catch any errors early.
Use 301 permanent redirects for URLs that have moved permanently. A 301 signals to Google that ranking credit should transfer to the new address. Reserve 302 temporary redirects only for short-term placeholders or A/B tests where the old URL will return. Mixing redirect types or using 302s during a permanent migration can delay ranking signal consolidation.
Yes, keep the old domain and its redirects live indefinitely if possible, or at minimum for twelve months. External backlinks, social shares, and bookmarks will continue pointing to old URLs. If you let the domain expire, those inbound signals vanish, and users encounter dead links. Maintaining the redirects preserves both user experience and accumulated link equity.
Inaccurate or missing redirect mappings cause the majority of migration failures. Wildcard rules that redirect entire sections to a homepage, orphaned URLs with no redirect at all, or redirect chains longer than one hop all dilute ranking signals. A 1:1 redirect map built from a complete pre-migration crawl is the most reliable way to preserve traffic.
Map /en/ and /fr/ URL structures separately and ensure hreflang tags on the new site correctly reference both language versions. If the new platform changes the URL pattern for French content, each old French URL needs an explicit redirect to its new French equivalent. Do not assume a single redirect rule will cover both languages if their paths diverge.
Phased migrations are possible for large sites with distinct sections — for example, migrating a blog subdirectory first, then product pages. However, each phase requires its own redirect map, staging validation, and monitoring window. Phasing adds coordination overhead and extends the total timeline. For most sites under 10,000 URLs, a single coordinated migration is simpler and faster than staggered rollouts.