No migration can guarantee unchanged traffic. You can reduce avoidable risk by retaining useful URLs, documenting necessary changes and testing content, redirects and enquiry forms before launch. A new design is not, by itself, a reason to change every address or shorten valuable service explanations.
Start with an evidence-backed inventory
Combine sitemap URLs, crawl discoveries and available search and conversion exports. Record language, intent, links, performance and the proposed disposition. Unavailable data stays unavailable; it must not become zero or a reason to delete a page.
Review pages with enquiries or external links before removing them. Low traffic does not necessarily mean low value, especially for a specialised buyer question. Similar titles do not prove identical intent: inspect the content and intended next action.
Build a testable migration map
| Decision | Action | Acceptance |
|---|---|---|
| Content remains useful | Retain its URL | 200 response and equivalent useful content. |
| Address changes but intent remains | Permanent redirect | One hop to a relevant destination. |
| Genuine overlap is consolidated | Reviewed merge and redirects | Preserve useful material and update links. |
| Removed with no equivalent | Appropriate 404 or 410 | No blanket homepage redirect. |
Update internal links to their final destinations. Redirects support old external references; they are not a substitute for fixing navigation. Include downloads and images when they have independent public URLs.
Check rendering, language and conversion
Inspect server-delivered HTML for titles and main content, then verify canonical links, language alternates and sitemaps. Keep staging protected and ensure its indexing restrictions are not accidentally deployed to production. Blocking crawling does not ensure a crawler can read a page’s noindex instruction.
Complete an enquiry on mobile and with a keyboard. Exercise validation and repeated submission. Measurement should distinguish a CTA click from a server-accepted enquiry and must not send personal form content to analytics. Compare before and after using the same event definitions.
Launch with a recovery plan
Name the release owner, cutover window and rollback conditions. Retest important old and new URLs immediately after the authorised release, then monitor errors, indexation and enquiries over subsequent weeks. Separate seasonal changes and measurement failures from migration effects; a short fluctuation proves neither success nor failure.
Include these checks in corporate website development. The vendor handover checklist and project brief help establish what must be preserved before design work begins.
Sources and editorial status
- Google: site moves with URL changes.
- Google: redirects and Search.
- Original contribution: migration disposition and enquiry-acceptance matrix. No ranking guarantee.
