Changing domain, moving from HTTP to HTTPS or launching a new site with a different URL structure is a delicate operation. Without a proper website migration plan, you can lose Google rankings, break external links and miss leads that used to land on pages that no longer exist.
At the end of summer many companies restart digital projects: redesigns, CMS changes or brand consolidation under one domain. Before you hit «publish», you need a redirect map and a validation plan.
What a website migration is and when you need one
A website migration is not just «uploading the new site». It means moving content, URLs, metadata and trust signals from a source to a destination. Common scenarios:
- Domain change (from .es to .com, rebranding or company merger).
- URL restructuring (from /services/web-design to /web-design).
- CMS or platform change (from WordPress to custom development, or vice versa). If you face that choice, read WordPress vs custom websites.
- HTTP to HTTPS migration or subdomain consolidation (www vs non-www).
Google treats each URL as an entity with history. If it vanishes without notice, traffic drops.
The 301 redirect map: your anti-drop insurance
The core tool is the 301 redirect: it tells search engines a URL has permanently moved. Without 301s, visitors see 404 errors and Google loses accumulated relevance signals.
Before launch, build a spreadsheet with three columns:
- Old URL (what Google indexes today).
- New URL (functional equivalent on the new site).
- Status (pending, implemented, verified).
Prioritise pages with traffic, conversions and backlinks. Use Google Search Console to find URLs that drive the most clicks.
Pre-launch checklist
- Complete 301 redirect map tested on staging.
- Updated XML sitemap with new URLs. See also XML sitemap and robots.txt.
- Robots.txt without accidental blocks on the new domain.
- Updated internal links (do not rely only on redirects).
- Canonical tags on every page pointing to the definitive URL.
- Metadata reviewed: titles and descriptions aligned with content.
- Forms, analytics and conversion tags working. See Google Tag Manager.
- Active SSL certificate and forced HTTP → HTTPS redirect.
Launch day and the first week
Schedule the switch during low-traffic hours. After go-live:
- Manually verify the 20 most important URLs (home, services, contact, top articles).
- Submit the new sitemap in Search Console and use the domain change tool if you changed domain.
- Monitor 404 errors in analytics and Search Console every 48 hours.
- Check speed: a redesign can affect Core Web Vitals.
Do not expect results in 24 hours. Google may take weeks to reindex; the curve usually stabilises in 4–8 weeks when redirects are correct.
Common mistakes that cost rankings
Redirecting everything to the homepage. A 301 from /services/seo to home loses topical relevance. Each old URL should point to its equivalent.
Redirect chains. A → B → C slows pages and dilutes signals. Redirect directly A → C.
Forgetting external links and campaigns. Update URLs in Google Ads, newsletters, social profiles and printed QR materials.
Not notifying partners with backlinks. Ask them to update links to the final destination.
Launching without a backup. Export content and keep a copy of the old site before migrating.
When to get professional help
If your site has hundreds of URLs, multiple languages or critical integrations (online store, client area), an improvised migration multiplies risk. A team experienced in web development can audit URLs, implement server redirects and validate launch without surprises.
Conclusion: migrate with data, not hope
A successful website migration depends less on the new design and more on transfer precision. URL map, verified 301 redirects, active monitoring and patience. That is how you change domain or restructure your site without giving Google months of accumulated work.
