How to move a website without losing important visitors

Define the move before touching URLs

A website move can mean several different things: changing design, platform, hosting, domain, URL structure or all of them together. Write down exactly what will change. A redesign on the same domain has different risks from moving to a new domain with new page addresses. The clearer the scope, the easier it is to choose the right tests and to explain responsibilities to everyone involved.

Make a list of the pages, features and integrations that the business cannot afford to lose. Include enquiry forms, booking flows, payments, analytics, email notifications, customer logins and important downloads. Decide whether the old site will remain available during preparation and who can approve the final launch. Migration problems often begin when technical work starts before the business has agreed what success means.

Keep a decision log for unusual cases, such as pages with strong links but no current equivalent. This makes the migration deliberate and gives the team a record to revisit if visitors or search data reveal a different need after launch.

Inventory the current website

Export or record the current URLs, page titles, important headings, canonical settings, indexation rules, media files and internal links. Use analytics and Search Console to identify pages that attract relevant visitors, generate enquiries or receive links from other sites. Do not judge a page only by its last month of traffic; seasonal or low-volume pages can still matter.

Include URLs that are not obvious from the main navigation. Old campaigns, PDFs, help articles, location pages and bookmarked forms may still bring visitors. Check server logs or search data when available. The inventory becomes the evidence for decisions about keeping, updating, combining or redirecting pages instead of relying on memory.

Capture a baseline before the move: important landing pages, enquiries, conversions, rankings and errors. Without a baseline, the team may mistake normal variation for a migration problem or miss a gradual decline that needs attention.

Map every important old URL

Create a redirect map with one row for each old URL and a clear destination on the new site. Send a page to its closest relevant replacement, not automatically to the new homepage. If several old pages become one stronger page, map each old address to that page and record the reason. If no useful replacement exists, decide deliberately whether a not-found response is more honest than an irrelevant redirect.

Avoid chains and loops. An old URL should ideally point directly to the final destination, and the new page should link to the correct current URLs. Keep the map available to the people managing the server or platform. It is both a launch tool and a reference for investigating lost visits later.

Use the destination page to preserve the visitor’s purpose. A person looking for a specific service should not arrive at a generic page that forces another search. Relevance is more valuable than making every redirect point somewhere that technically loads.

Preserve content and customer journeys

Compare old and new pages for meaning, not just word count. Keep information that helps visitors choose, prepare, contact, buy or return. A shorter page can be better, but removing service details, FAQs, examples or location context may make it less useful. Check that headings, links, images, forms and downloads still support the same decisions.

Walk through real journeys as a customer. Submit a form, make a test booking, try a payment, open an important document and check confirmation messages. Test on a phone and with keyboard navigation. A migration is not complete when the homepage loads; it is complete when important visitors can still reach a useful outcome.

Pay attention to forms that send notifications through several systems. A successful test should confirm not only that the form submits, but also that the right recipient receives the message and that the visitor receives an understandable confirmation.

Test before and during launch

Build a test version that search engines should not index while the team checks it. Test internal links, redirects, canonical tags, robots rules, sitemap output, structured data, page speed, forms, integrations and error pages. Compare representative old and new URLs. Keep a launch checklist with an owner and a clear pass or fail result for every critical item.

At launch, apply the redirect map, remove temporary blocking rules when appropriate, submit the new sitemap and confirm analytics collection. Change DNS or hosting settings carefully and record the exact time of the switch. Keep the old environment available for a planned period if possible, so unexpected differences can be investigated without guessing.

Keep a copy of the redirect map and launch settings outside the website platform. If the new environment becomes unavailable, the team still needs to know what changed and which settings must be restored or investigated.

Monitor the weeks after moving

Check Search Console for indexing issues, crawl errors, security warnings and changes in search performance. Review analytics for traffic by landing page, device and channel. Watch enquiries, bookings, payments and support questions, not just sessions. A traffic change may be seasonal, but a sudden cluster of missing pages or failed forms needs immediate investigation.

Keep a list of errors and resolve them by impact. Fix broken redirects, missing high-value pages, incorrect canonical settings and blocked resources first. Update external partners or important directories when their links point to retired URLs. A successful migration is a managed transition, not a single launch moment, and the monitoring period is part of the work.

Compare results over several weeks rather than reacting to one day. The first days may contain crawl fluctuations, campaign changes or incomplete indexing. A clear monitoring routine helps separate temporary noise from a real issue.

Sources

• Site moves and migrations · Google Search Central
• Search Console overview · Google Search Console

Frequently asked

How long should redirects remain after a website move?

Keep important redirects for as long as they receive visitors or links, and avoid removing them simply because the new site has launched. Review logs and search data before changing them.

Will a redesign automatically hurt search traffic?

No. Risk depends on what changes and how carefully URLs, content, redirects, technical settings and measurement are handled. A well-planned redesign can improve usefulness and performance.

Should every old page redirect to the homepage?

Usually not. Redirect each useful old URL to the closest relevant new page. A homepage redirect that does not answer the original need can confuse visitors and search systems.