Redesign or rebuild? And how to do either without losing your Google rankings

A redesign changes how the site looks and is organised on the same platform; a rebuild moves it to a new platform or starts the code again. The right one depends on whether the current site’s problems are skin-deep. Either can lose you rankings, and when it happens it is almost never because of the design — it is because the old addresses stopped working and nobody mapped them to the new ones. That part is entirely preventable.

Which one you need

Redesign if the site works, ranks, and is simply dated: the platform is fine, the content is roughly right, it just looks like 2018. Rebuild if the platform is fighting you — a builder that has become slow and inflexible, a theme nobody can maintain, a site that cannot pass Core Web Vitals no matter what is tuned, or a stack you cannot hire for. A useful test: if three separate people have told you “that’s a limitation of the platform”, it is a rebuild.

The honest answer is sometimes neither. If the site ranks well and only looks tired, a design refresh on the same platform costs less than either and risks nothing.

Why redesigns lose traffic

Google ranks addresses, not websites. Every page that ranks has a URL, and Google’s trust in that page is attached to that exact URL. When a redesign changes /services/plumbing-repair/ to /plumbing/ and the old address returns a 404, Google’s trust in it evaporates over a few weeks. Multiply by fifty pages and the traffic graph falls off a cliff a month after launch — by which time everyone has decided the new design is to blame.

The checklist that prevents it

Before anything is built: export every URL the current site has (from the sitemap, from Search Console, from the analytics “top pages” report), and note which ones actually get traffic or rank. This list is the most valuable document in the project.

During the build: for each old URL, decide the new URL. Where possible keep them identical. Where they must change, record the pair.

At launch: every changed URL gets a permanent (301) redirect to its new home — not to the homepage, to the equivalent page. Titles and descriptions carry over. Structured data carries over. The sitemap is regenerated and submitted. Nothing is left returning 404 that used to return a page.

After: watch Search Console’s coverage report for two weeks for 404s and “redirect errors”, and fix anything it finds. Traffic may wobble for a few weeks; it should not fall off a cliff.

Moving platforms

Coming off Wix, Squarespace or a builder onto WordPress follows the same rules with one extra: the old platform’s URL structures are often odd (/blog-1/post-title, dates in strange places), so the redirect map is longer and it has to be built by hand. Content moves; comments and some embedded features may not. Plan the map before the design, not after.

What it costs

Our redesign and migration service starts at $2,000 and includes the full URL map and 301 redirects, content migration, speed and accessibility improvements, the new design, and a Search Console check after launch. If the redesign grows into a full rebuild, that is a business website from $3,500. Either way you get a fixed written quote after a free call, and the URL list is the first thing we ask for.