A redesign can improve trust and conversion while quietly damaging search visibility if URLs, redirects, metadata and measurement are treated as launch-day details.
Website migration is not only a technical transfer. It changes the routes customers and search engines use to reach valuable information. Whether you are changing domain, platform, page structure or hosting, the safest approach is to inventory what works, map every important URL, test before launch and monitor after release.
Define exactly what is changing
Start by naming the migration type. A hosting move with unchanged URLs has different risks from a domain change, CMS replacement or full redesign. If possible, avoid changing the domain, content architecture, design and technology simultaneously. Google recommends changing one major thing at a time where practical because layered changes make problems harder to diagnose.
Document the reason for the project, desired business outcomes, launch window, stakeholders, rollback plan and success measures. Include organic landing-page traffic, enquiries, revenue, indexed pages and priority rankings, but do not make rankings the only measure.
Create a complete URL inventory
Crawl the current site and combine the results with XML sitemaps, analytics landing pages, Search Console data, backlink reports and server logs. Include HTML pages, PDFs, images and campaign destinations. Mark pages with traffic, enquiries, external links or strategic value.
This inventory prevents the common mistake of migrating only pages visible in the main navigation. Older guides and campaign pages may still attract customers or hold valuable links even when staff rarely visit them.
Decide what to keep, improve, merge or retire
Every old URL needs an intentional outcome. Keep useful pages at the same URL when possible. Improve outdated material without discarding the topic’s value. Merge overlapping pages only when the new destination genuinely satisfies the same intent. Retire content that no longer serves customers and has no suitable replacement.
Do not redirect every removed page to the homepage. Google warns that irrelevant mass redirects can confuse users and may be treated as soft 404s. When no relevant replacement exists, return a true 404 or 410 and provide a helpful error page.
Build a one-to-one redirect map
Map each changing URL to the closest relevant new URL. Use permanent server-side redirects for permanent moves, avoid chains, and test both the initial and final response. Preserve query parameters only when they remain useful and safe.
Keep redirects for at least a year; in many cases keeping them indefinitely benefits customers with old bookmarks and websites with outdated links. Update high-volume internal and external links so users do not rely on redirects unnecessarily.
Preserve search and social signals
Carry across unique titles, meta descriptions, headings, body copy, image alternative text and structured data where they are still accurate. Every new page should have a self-referencing canonical URL. Update hreflang annotations on international sites, Open Graph metadata for social sharing, and schema identifiers that contain URLs.
Check that robots directives do not retain staging-site noindex rules. Confirm robots.txt allows the content that should be crawled. Generate a clean XML sitemap containing canonical, indexable URLs that return successful responses.
Protect analytics and conversion tracking
Record the current analytics, consent, advertising and call-tracking setup before the migration. On staging, verify page views, form submissions, phone clicks, bookings and thank-you states without polluting production reports. Preserve campaign parameters and configure cross-domain measurement when journeys span more than one domain.
Take screenshots or exports of important reports before launch. A migration may appear successful while lead tracking is broken, leaving the team unable to distinguish a traffic problem from a measurement problem.
Test the new site as a customer
Run technical crawls, but also complete real tasks on physical phones and desktop browsers. Call phone links, submit forms, navigate with a keyboard, check confirmation messages and verify notification delivery. Test priority pages on slower connections and review image quality, layout shifts and interactive responsiveness.
Include legal, privacy and cookie experiences. Confirm that essential forms remain usable when optional tracking is declined. Test the custom 404 page and a representative sample of redirects.
Plan the launch sequence
- Freeze non-essential content changes shortly before launch.
- Take verified file and database backups.
- Reduce DNS time-to-live before a domain or host change where appropriate.
- Deploy during a lower-traffic period with the responsible team available.
- Enable redirects, canonical tags and production indexability together.
- Run smoke tests immediately and retain a clear rollback threshold.
Monitor the first hours, weeks and months
Immediately verify priority URLs, redirects, forms, analytics and server errors. Submit the new sitemap in Search Console and use URL Inspection for representative pages. When changing domains, use the Change of Address tool after all verified variants and redirects are ready.
During the following weeks, monitor crawl errors, indexed-page counts, canonical selections, organic landing pages and lead volume. Some fluctuation is normal while search engines recrawl a moved site. Investigate patterns rather than reacting to a single day.
Compare performance by page group and query intent. If one service section declines while others remain stable, inspect its redirects, content, internal links and rendering. Keep a migration log so every correction is documented.
Common migration failures
- Launching without a URL inventory or redirect map.
- Replacing useful service copy with visually impressive but thin content.
- Leaving staging noindex rules or blocked resources in production.
- Changing internal links but forgetting canonical and hreflang URLs.
- Publishing an XML sitemap full of redirected or non-canonical URLs.
- Testing forms visually without verifying actual email or CRM delivery.
Key takeaway
A safe migration protects the routes that already produce visibility and enquiries while improving the experience around them. Inventory first, map deliberately, test real journeys and monitor long enough to catch delayed indexing or tracking issues.
Planning a redesign or platform move?
RATdeck combines website strategy, technical SEO, responsive testing and post-launch checks in one migration plan.