Treat a migration as a controlled release
A website migration can change domains, URLs, platforms, rendering, navigation, templates, content, analytics, or several of these at once. Search risk increases when many variables change without a baseline and acceptance criteria.
Google's site move guidance recommends careful URL mapping, redirects, verification, and monitoring. The implementation still needs to reflect the specific architecture and business priorities.
Build the pre-launch inventory
Create one inventory from multiple evidence sources:
- Current crawlable and indexable URLs
- XML sitemaps
- Search Console landing pages
- Analytics and conversion landing pages
- Backlinked URLs
- Paid campaign destinations
- CRM or revenue-producing entry pages
- Image, document, and feed URLs where relevant
No single source is complete. A crawler can miss orphan pages. Analytics can miss low-traffic pages with valuable links. Sitemaps can contain outdated URLs.
Classify each source URL as keep, update, consolidate, redirect, noindex, or retire. Every redirect needs one final canonical destination that serves a genuinely equivalent purpose.
Establish content and metadata parity
For every valuable destination, compare:
- Primary purpose and search intent
- Main content and useful detail
- Title, description, and H1
- Canonical URL
- Robots directives
- Structured data
- Internal links
- Images and documents
- Conversion actions
- Language and regional signals
Visual similarity is not content parity. A redesign may remove sections, links, specifications, FAQs, or evidence that helped the previous page answer its intent.
Design one-hop redirect rules
Redirect each retired source directly to the final destination. Avoid source to intermediate to final chains. Broadly redirecting unrelated URLs to the homepage creates a poor user destination and weakens the meaning of the migration map.
Test:
- Exact paths
- Query parameter behavior
- Uppercase and lowercase variants
- Trailing slash rules
- HTTP and alternate host variants
- File and image routes
- Already redirected legacy URLs
Keep the redirect map in version control and retain it after launch. Valuable external links and old bookmarks can remain active for years.
Protect staging and launch controls
Staging should be access-controlled and noindexed. Before launch, verify that staging directives, development canonicals, debug output, and blocked assets do not enter production.
A launch checklist should include:
- Production host and HTTPS
- Robots and page-level index controls
- Canonicals and hreflang where relevant
- Sitemaps and feeds
- Redirect behavior
- Error responses
- Analytics and consent
- Forms and conversion events
- Security headers
- Representative mobile and desktop rendering
Do not remove the old environment until redirects, assets, and rollback options are confirmed.
Validate after deployment
Run tests immediately after release, then repeat them as search systems recrawl the site.
Compare the new environment against the approved inventory:
| Check | What to confirm | | --- | --- | | Status | Canonical pages return 200 and retired URLs follow the plan | | Redirect | One hop to an equivalent final destination | | Content | Important sections and evidence remain available | | Internal links | Navigation points directly to canonical URLs | | Sitemap | Only indexable 200 destinations are included | | Canonical | Matches the intended preferred URL | | Analytics | Sessions and valuable actions remain measurable | | Performance | Representative templates remain stable for users |
Monitor Search Console coverage, crawl behavior, submitted sitemaps, canonical selection, impressions, clicks, and representative rankings. Also monitor server errors and real conversion behavior.
Interpret movement carefully
Temporary volatility can happen as search engines process redirects and new pages. A decline does not identify its own cause. Compare by page group, query intent, market, device, and migration change.
Do not announce recovery from a single day of data. Record the baseline period, release date, known seasonality, paid campaign changes, tracking changes, and other confounding factors.
Limitations
No migration process guarantees preserved rankings or traffic. Search systems decide how signals are processed, and the new site may differ in quality, speed, architecture, relevance, or competitive context.
The practical goal is to reduce avoidable loss, preserve meaningful destinations, detect regressions quickly, and leave a documented path for correction.
Primary sources
- Google Search site move guidance Google Search Central accessed
- Google Search canonical URL guidance Google Search Central accessed