SEO migration: preparing URLs, redirects and monitoring
1. Core Principles and SEO Migration Risk Management
Migrating a website involves changing URL addresses, directory structures, or domain names. This technical intervention modifies the baseline used by search engines to crawl, evaluate, and rank web pages. Without a rigorous methodology, architectural changes can lead to a prolonged loss of search visibility and organic traffic.
Ranking fluctuations during a migration are normal and expected as search engines recrawl and reindex the new addresses. The re-evaluation timeframe ranges from several weeks for medium-sized websites to several months for larger structures. There is no guaranteed recovery timeline, as the processing pace depends directly on the number of URLs and server processing capacity. For official recommendations on managing site moves, consult the Google Search Central documentation: Google Search Central
2. Pre-Migration Audit and Comprehensive Asset Inventory
Before implementing any technical changes on the server, the first step is to establish a complete inventory of the existing site structure. This preliminary audit identifies all active URLs, associated metadata, and indexable assets that generate organic traffic.
The inventory must catalogue title tags, meta descriptions, header tags, and JSON-LD structured data schemas. It is also necessary to map indexed media files and pages receiving high-quality incoming links. All retained target URLs on the new platform must return an HTTP 200 status code and be ready for search crawlers without artificial blocks.
3. URL Mapping and 301 Redirection Strategy
Map each old URL to a relevant destination in the same language. Several consolidated articles may lead to one equivalent complete article. Use 404 or 410 when no useful equivalent remains. Mapping does not guarantee unchanged rankings.
3.1 Essential Redirection Practices
Use a permanent server-side redirect, generally 301 or 308, to the final destination. Avoid chains and loops. Check each destination’s status and indexability before launch.
3.2 Redirection Errors to Avoid
Do not redirect every old page to the homepage: an unrelated destination may be treated as a soft 404 and confuse visitors. Google recommends keeping redirects for at least a year; retain them longer when links or visitors still use them. This does not guarantee a reindexing timetable.
4. Multilingual Specifics and Language Structure Preservation
For multilingual platforms using structures such as /fr/ and /en/, the migration must preserve strict language separation. A French URL must redirect specifically to its exact French equivalent on the new architecture.
The hreflang annotations must be updated to target the new canonical URLs. Forced automatic redirects based on IP geolocation or browser language settings must be avoided. Such automated redirects can prevent search engine crawlers from discovering and indexing localized language variations.
5. Google Search Console Configuration and Change of Address Tool
Verify Search Console properties covering the old and new sites and variants in use. A DNS-verified Domain property covers subdomains and protocols; a URL-prefix property has a narrower scope. Preserve verification methods after the change.
5.1 Conditions for Using the Change of Address Tool
The Change of Address tool is designed for domain-level moves, such as example.com to example.org. Check the
5.2 Tool Exclusion Cases
The Change of Address tool must not be used for HTTP to HTTPS moves, path-level directory changes on the same domain, or switches between www and non-www versions. In these scenarios, only 301 redirects and canonical tags should be implemented. Once the site move is initiated, updated XML sitemaps must be submitted to accelerate URL discovery.
6. Post-Migration Monitoring and Performance Optimization
Following redirect activation, continuous technical monitoring must be established. Server log analysis verifies search crawler behavior and ensures the hosting infrastructure has sufficient computing capacity to handle the temporary crawling spike.
Monitoring should track index coverage reports, unexpected 404 errors, and organic traffic shifts. Technical performance optimization must include tracking Core Web Vitals metrics: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Documentation on Core Web Vitals is accessible here: Google Search Central
For a move planned in 2027, define responsibilities and launch criteria before changing URLs. Back up configuration, prepare a correction procedure and monitor priority pages after launch. An error-free first day does not mean monitoring is finished.
A mapping check
Fictional example: before a redesign, an SME maps ten old pages to their French and English destinations. It tests statuses, internal links and removal of staging noindex. Two pages without equivalents remain 404. This check prepares launch without guaranteeing rankings.