Website redesign and migration — keeping what a site earned

A website is not only the thing visible in a browser — over years it also accumulates something invisible: search engine trust, indexed pages, inbound links, and a track record Google has built up about the domain. A redesign or a platform migration can discard all of that in an afternoon if the underlying URLs change without a redirect plan, and it is entirely possible to do so while believing the project went well because the new site “looks great”.

Why this redesign and migration cluster exists

This is the “Live-with” verb — commissioning a website is not a single event, it is followed by years of maintaining, occasionally redesigning, and sometimes migrating it, and this part of the journey carries real demand that the rest of this site’s structure had, until this cluster, never addressed. “Website redesign” and “website migration” each measure 32 AI-assistant prompts nationally; “website migration” also carries 70/mo of genuine, separately measured Google volume at essentially zero difficulty (research/outer-volume-au.json) — real, low-competition demand sitting unaddressed.

What redesign and migration guides are here

When a website actually needs replacing and redesign or rebuild set the decision frame before any project starts. What to keep from the old site covers the content audit that should precede any brief.

Redesigning without losing rankings covers the single highest-risk technical mistake in this entire process — the named bridge into search engine optimisation as a discipline. Content migration: the work nobody quotes and moving between platforms cover what a platform change actually carries across and what it does not.

Moving hosts without downtime and changing domain names cover the two infrastructure changes with the sharpest technical risk. What a migration checklist contains and running the old and new sites in parallel cover the practical sequencing around a launch.

What a rebrand does to a website and measuring whether the redesign worked close out the cluster with the identity side of a redesign and the honest evaluation of whether it achieved anything.

The one idea that runs through the whole redesign and migration cluster

A redesign changes how a site looks and how it is built. It should not, by default, change what the site is at — its URLs, its accumulated links, its indexed history — unless that change is deliberate and mapped. Conflating “we’re redesigning the site” with “every URL is up for grabs” is the single most common and most expensive mistake covered across these pages.

Website migration, site migration and CMS migration: what changes and what doesn’t

Website migration and CMS migration cover two different things people mean by the same phrase. A site migration might mean moving hosts on the same platform with the same URLs — a low-risk, largely invisible change. Or it might mean a full CMS migration: moving the content itself from one platform to another, which is a development project in its own right, not a configuration change. Either way, the migration process depends entirely on a redirect plan: every URL that changes needs a form of redirect mapped to its replacement before the old one goes offline, not after. A team that says it can migrate a site without discussing redirects at all has not actually done this before, whatever the rebuild website quote says it includes.

What to do next before a redesign or migration

If a redesign or a CMS migration is being considered at all, start with when a website actually needs replacing before briefing anyone — a genuine redesign need and a maintenance backlog dressed up as one are different problems with very different price tags, covered on what drives the cost of a website. For where redesign sits inside web design as a whole, start with web design in Australia.