In brief
A website redesign or migration does not have to cost you search traffic — traffic is lost when page addresses change without redirects, when content that was earning visits is thinned or removed, when the new site loads more slowly, or when the change is made in one leap with nothing watching it. The safe method is mechanical: export every existing URL and note which ones bring visitors in, keep those addresses wherever you can, map each retired address to its closest new equivalent with a 301 redirect, carry the earning content across unchanged, then monitor for errors and coverage drops for the four to eight weeks after launch. Done that way, most sites hold their visibility or improve; the drops people blame on "the redesign" are almost always drops caused by a missing redirect or a page that quietly disappeared.
The traffic you have is attached to addresses
Search visibility is not stored in a website as a whole. It sits on individual addresses: the page that ranks for a phrase, the article that keeps collecting enquiries, the guide other sites have linked to. When those addresses change and nothing tells search engines where they went, the work behind them starts again from zero. That is why a migration plan begins with an inventory rather than a design.
Pull every URL your site currently has — from the sitemap, from a crawl, and from your analytics and search console reports — and mark the ones that bring visitors in. That short list of earning pages is the thing you are protecting. Anything that cannot be mapped to a new equivalent should not be deleted quietly; it should be redirected to the nearest useful page and mentioned in the launch review.
Design changes are cheap, structure changes are not
A new look is the least dangerous part of a move. Keeping the same URLs, the same page names and the same hierarchy while rebuilding the interface usually passes without a visible dent in traffic. What costs visibility is re-architecting at the same time: merging pages, renaming sections, dropping a blog, or moving content from a subfolder to a subdomain. Each of those decisions moves ranking signals and has to be paid for with redirects and time.
So the discipline is to separate the two changes. If the structure genuinely needs to change, change it once, deliberately, with the mapping written down before development starts — one old address to one new address, chosen because the content matches, not because the page name happens to be similar. A redirect that sends a service page to a homepage is technically a redirect and practically a loss.
The checks that decide whether the move holds
Before launch, the earning content has to be present in the new build in full: the copy that answered the query, the headings, the images with their descriptions, the structured data, and the internal links that connected related pages. Content shortened for the sake of a cleaner layout is one of the quietest ways to lose a page that had been working for years.
Then the mechanical checks: no accidental noindex on staging, the XML sitemap regenerated and submitted, robots.txt not blocking the new site, canonical tags pointing at the live addresses, internal links updated to their final form rather than following redirect chains, and load speed measured on the pages that matter. Speed deserves particular attention because a design that is heavier than the one it replaces can undo a perfectly executed redirect map.
Launch is the start of the monitoring period
In the days after go-live, watch for 404s, crawl errors, and coverage changes in search console, and compare rankings and enquiries on the previously earning pages against their pre-launch figures. Missing redirects surface here — a page nobody thought to map, an old blog post that was still bringing people in, a filtered URL that started returning errors. Each one found and fixed is visibility recovered.
Blacktide International plans and delivers website migrations, redesigns and platform moves for service businesses in Glasgow and across the UK, United States and Europe — with a URL inventory, a one-to-one redirect map, content carried across intact, and a monitoring period after launch so a migration is judged on what it preserved rather than on the day it shipped.