Key takeaways
- Most migration traffic losses come from missing or wrong redirects, lost content and accidental noindex/robots blocks.
- Crawl and benchmark everything before you touch anything.
- Map every valuable old URL to the most relevant new URL with a 301 redirect.
- Test on staging, launch at a quiet time, then monitor daily for at least four weeks.
Management and maintenance at Yves Media regularly include database migration and moving websites between hosts, platforms and domains. Migrations are where years of SEO work can be undone in a single afternoon — or carried over safely. The difference is preparation. Here is the plan we follow.
Types of migration and their risk
| Migration type | Examples | SEO risk |
|---|---|---|
| Hosting / server | New host, new server, CDN change | Low (if URLs and content stay identical) |
| Protocol | HTTP → HTTPS | Low–medium |
| Design / template | New theme, new layout | Medium (content and internal links change) |
| Structure / URL | New URL patterns, merged sections | High |
| Platform / CMS | Builder → WordPress, WordPress → headless | High |
| Domain | Rebrand, new TLD, merging sites | High |
Phase 1: Plan and benchmark
- Define goals and scope; avoid bundling unnecessary changes.
- Choose a launch window with low traffic and full team availability (not before a holiday).
- Export Search Console performance data (queries and pages) for the last 16 months.
- Record rankings for priority keywords and AI visibility for key prompts.
- Export analytics landing-page data, conversions and revenue per page.
- Back up files and the database completely.
Phase 2: Inventory every URL
Combine URLs from several sources to make sure nothing valuable is missed:
- A full crawl of the current site.
- XML sitemaps.
- Search Console pages report and analytics landing pages.
- Backlink tools (pages with external links).
- Server logs (URLs search engines still request).
Deduplicate and classify each URL: keep, merge, redirect or remove.
Phase 3: Redirect mapping
- Map each old URL to the most relevant new URL — not to the homepage.
- Use 301 (permanent) redirects, implemented server-side or via a reliable redirect manager.
- Avoid chains: old URL → final URL in one hop. Update existing redirects to point to new targets.
- For content you are removing without a replacement, return 404 or 410 rather than redirecting to an irrelevant page.
- Preserve parameters where they matter (campaign tracking, pagination) and test pattern-based rules carefully.
When we rebuilt this website, the old contact page lived at an odd URL (/224286-2/) and policies used /privacy-cookie-policy/ and /terms-of-service/. All of them now 301-redirect to the new, clearer URLs, so existing links and bookmarks keep working.
Phase 4: Build and test on staging
- Block staging from indexing with password protection (more reliable than robots.txt alone).
- Crawl staging and compare with the old crawl: titles, meta descriptions, H1s, canonicals, structured data, word counts, internal links.
- Test the full redirect map against staging and confirm every rule returns a single 301 to a 200 page.
- Check Core Web Vitals on key templates.
- Verify analytics, consent management, forms and e-commerce tracking.
- For database migrations: verify serialized data, search-and-replace URLs safely, check character encoding, table prefixes and user roles.
Phase 5: Launch day
- Final backups of old and new environments.
- Deploy, then immediately remove staging protections and any
noindexor “discourage search engines” settings. - Check robots.txt, the XML sitemap and canonical tags on live URLs.
- Run the redirect test against the live site.
- Submit the new sitemap in Search Console and Bing Webmaster Tools; for domain changes, use Google’s Change of Address tool and keep both properties verified.
- Spot-check top landing pages manually on mobile and desktop.
- Ping participating search engines via IndexNow for key URLs.
Phase 6: Monitor and fix (weeks 1–8)
- Daily (week 1): 404 errors, server errors, redirect hits, conversions.
- Weekly: Search Console page indexing, impressions and clicks by page group, Core Web Vitals.
- Compare with your benchmark; investigate pages with large drops first.
- Ask sites with important backlinks to update links to the new URLs.
- Keep redirects in place for at least a year — ideally permanently.
Common migration mistakes
- Redirecting everything to the homepage.
- Forgetting to remove
noindexfrom staging. - Dropping content sections or internal links during a redesign.
- Changing URLs, content, design and domain all at once without testing.
- Letting the old domain expire after a domain move.
Conclusion
A migration is a project, not a deployment. Benchmark, inventory, map, test, launch carefully and monitor. Run a technical SEO audit before and after, and keep security tight during the move (see our hardening checklist). If you would like experienced hands on your next migration, get in touch — it is part of our management and maintenance work.