Website redesign: how to rebuild a site without losing what already works

The word redesign makes people think of colors and layouts. Those matter. But in most of the rebuilds I've done, the real problems were structural: pricing nobody could find, a phone number that didn't exist, a news section where every link went to the same page. A new coat of paint wouldn't have fixed any of them.

Refresh, redesign, or restructure?

These three get used interchangeably, and they're different jobs with different costs. Picking the right one is the first decision.

If you can't tell which one you need, that's what the audit is for. Restructuring is the one that overlaps most with website architecture, so it's worth reading that page before changing a single URL.

Signs a site needs a redesign

• The menu has a More tab. That's usually where the plan ran out.
• Important information lives on a page nothing links to. Bella Passion Creations had a genuinely good pricing breakdown sitting under an unrelated URL, reachable from nowhere.
• Several pages compete for the same search. Search Console shows them trading places, and neither ranks well.
• Visitors can't take the next step. No phone number, a broken form, a checkout that goes nowhere.
• The brand says different things in different places. NewsBeauty's company name, brand name, and domain had blurred together across bios, flyers, and the old site.

One sign that looks like it belongs on this list and doesn't: a low-value content warning. DryOutHub got one, and the fix wasn't a redesign at all. It was a robots.txt setting blocking crawlers. Rule out technical causes before rebuilding anything. Here's how that one played out.

Audit before you redesign

Every rebuild I've done started with an audit, page by page, before touching any code. It's the least glamorous step and the one that decides whether the redesign fixes anything. Two audits run side by side.

The output is a simple spreadsheet with one decision per page: keep, merge, rewrite, or remove. That spreadsheet becomes the redirect map later, so it's worth doing carefully.

The website redesign process

Six steps, in this order. The order is the strategy: structure before visuals, protection before launch, measurement after.

1. Audit what exists

   Run both audits and write down what the site is failing to do, in plain sentences. Visitors can't find pricing. Two pages fight over the same keyword. Those sentences become your success criteria.

2. Decide what stays

   Pages that rank and convert are assets, even if they look dated. Keep their URLs. Merge thin pages that cover the same question. Remove only what has no traffic, no links, and no purpose.

3. Rebuild the structure

   Draft the new hierarchy and navigation before any design work. For Bella Passion Creations, services became rentals, tiered packages, and event bundles, because that's how she actually sells.

4. Redesign the experience

   Now the visuals. Pull the palette and imagery from the business itself, not a template. Check contrast with real math, not your eyes, and test on a real phone.

5. Protect search equity

   Map every old URL that changes to its closest new page with a 301 redirect. Update the sitemap. Check robots.txt, canonicals, and internal links before launch day, not after.

6. Launch, then measure

   Watch Search Console coverage and queries for the following weeks. Compare against the sentences from step one. A redesign is done when those problems are gone, not when the site looks finished.

Protecting search traffic during a redesign

This is where redesigns lose rankings they took years to earn. The fix is boring and reliable: a redirect map built from the audit spreadsheet.

OLD URL                        →  NEW URL                    ACTION
/pricing-copy-2/               →  /packages/                 301
/our-services/                 →  /services/                 301
/services/grab-and-go/         →  /services/grab-and-go/     keep
/blog/post?id=12               →  /blog/knotless-braids/     301
/old-promo/                    →  (no equivalent)            410

Two launch-day lessons from my own mistakes. First, check that the deploy actually landed in the web root. A NewsBeauty upload extracted one folder too deep, the domain showed a 404, and a search bot crawled it while it was broken. Second, test pages reached through URL rewrites. On this site, every post briefly rendered with no styling because relative paths resolved differently once a rewrite made the URL look deeper than the file was. Absolute paths fixed it.

The search-side reasoning behind all this, how hubs and internal links carry authority, lives on the SEO site architecture page.

UX redesign and navigation redesign

A UX redesign isn't about making things prettier. It's about removing the moments where someone gets stuck. The ones I see most often:

• A contact path on every page. A real phone number and one clear action, not a buried email link.
• Fewer, clearer menu items. Group by what visitors want to do, and move everything else to the footer.
• Real destinations behind every card. If a card looks clickable, it should lead somewhere specific.
• Mobile tested on an actual phone. A client's screenshot caught a footer overflowing off-screen that my own testing never did.

Journeys, flows, and content hierarchy get a fuller treatment on UX and information architecture.

Website redesign checklist

The short version I run before calling a redesign ready to launch:

What went wrong in real rebuilds

These are the ones I'd warn anyone about before they start.

Real rebuilds

Each of these went through some version of the process above.

Website redesign FAQ