Redesigning or moving a website without losing search traffic

List existing pages, useful content, incoming links and important customer actions before choosing what changes. A new visual design should not accidentally remove the pages customers rely on.

A new site can look better while dropping the content people came for. An old service page disappears. A useful guide is replaced by a short generic paragraph. Old links lead to errors. A test-site noindex setting remains after launch. The enquiry form appears to work but never delivers. These are different failures and need separate checks.

Changing a website can affect how Google crawls, understands and ranks it. A change of design alone is different from changing content, URLs, platform and domain together. Where practical, avoid combining unrelated major changes without a reason. Preserving every address does not guarantee unchanged traffic: demand, competition, content relevance and search systems can also change.

Start an inventory with the CMS, sitemap and known public pages. With access, add useful landing pages, search clicks, incoming links and enquiries. Keep dated evidence. Include valuable files and image addresses where they matter; a list made only by clicking the menu can miss them.

Illustrative example: page inventory (partial)

URL	Reader task	Evidence	Decision (pending)
/services/old-offer	Understand the previous service	Incoming links, search clicks, enquiries	Review and redirect
/guides/website-migration	Read the full guide	Search clicks, internal links	Keep and update
/downloads/price-list.pdf	Download price list (PDF)	Incoming links, external references	Check and keep
/contact	Send an enquiry	Form submissions (verify delivery)	Test and confirm
/images/hero-product.jpg	View product image	Used on key pages, external links	Keep

Give each existing page a documented decision. Keep useful content and an address when they still fit. Improve a page when its job remains but the answer is weak or outdated. Combine pages only when a useful replacement genuinely covers the same needs. Move a page when the new structure calls for a different address. Retire material when it is no longer useful.

A changed address usually needs a direct permanent redirect to its closest relevant replacement. A genuine consolidation can redirect several old pages to the combined page. Do not send every deleted URL to the homepage: it often fails the visitor’s original task. Where there is no useful equivalent, a real 404 or 410 response may be appropriate. Record the reason rather than hiding it behind an unrelated redirect.

Treat the status of a page separately from its content quality. A page that returns 200 but no longer answers the question has not been preserved meaningfully. A redirect that reaches the wrong service has not solved the problem either.

A usable map records the old address, existing reader task, planned action, final address or response, content requirements, business priority, owner and test evidence. The destination must be agreed before redirects are implemented. Keep old and new URLs exact; similar-looking paths are easy to confuse.

This is an example plan, not a record of completed tests. Add the date, status and evidence as tests are run.

Test real representative URLs even when redirect rules are generated from patterns. Check for loops, unnecessary chains and destinations that still point to staging.

Review useful content as well as the visual design. Test the paths from an entry page to an enquiry or order. Check forms end to end, including delivery, mistakes and retry behaviour. Check important layouts on an actual phone. Agree who can authorise the switch and who can reverse it if a serious problem appears.

For pages intended to be indexed, verify that the live destination can be crawled and returns the intended response. Intended indexable pages normally identify their new preferred address with a canonical; duplicate variants identify that preferred page. No public page should accidentally name a staging or old address. Internal links and sitemap entries should agree.

Where the domain or hosting changes, preserve the required DNS and email records, verify access and plan the relevant transition. These checks are not identical for every redesign. Mark each task as applicable or deliberately not applicable rather than using a checklist blindly.

1<head>2  <link rel="canonical" href="<em>https://example.com/services/bookkeeping</em>" />3</head>4...5<a href="../../services/bookkeeping">Bookkeeping</a>

Launch checklist

• Live site online
• Key pages checked
• Redirects working
• Indexing settings confirmed
• Forms and tracking tested
• Customer journey complete
• Issues logged and assigned

Test the actual public site after publication; a staging test does not prove the live server behaves the same way. Open valuable old URLs and verify the final page and response. Confirm public indexing settings, important links, form receipt and measurement triggers. Test the main customer journey again. Record defects, affected URLs, owners and repairs.

Google advises monitoring both old and new URLs during a move. Rankings may fluctuate as pages are recrawled and processed. Compare like-for-like periods and channels, and account for seasonality, consent and tracking changes. A drop in analytics sessions alone does not prove search rankings fell. Search Console clicks, page-level evidence and live tests help separate causes.

Monitoring responsibility and duration should be written into the project scope. Redirects need to remain for a meaningful period; Google recommends at least a year for site moves. A launch agreement should say who maintains them and the domain. Do not remove working redirects simply because the new design has been signed off.

First rule out measurement changes and obvious launch faults. Test a valuable old address, inspect the destination and its indexing signals, and check whether useful content is still present. Fix confirmed blockers promptly and record what changed. Several faults can coexist. Separate necessary repairs from discretionary content experiments and give search processing time without treating waiting as a substitute for diagnosis.

On Shopify, an unpublished theme can support a redesign while the current theme remains active. Check theme-specific content, app displays and analytics integrations separately from the store’s product data. Redirect handling has platform limits, so test changed addresses on the live store. A move from another platform also needs export and content checks; changing the theme does not perform that migration for you.

This guide reduces avoidable migration mistakes. It cannot guarantee traffic, rankings or enquiries, and it does not diagnose a particular site without evidence.

Each task needs an owner, evidence of completion and an applies-to condition. Save the completed map with the handover so the next person can understand it.