What a Website Redesign Should Actually Change

A redesign gets requested for all kinds of reasons: a rebrand, a new hire who does not like the old look, a competitor whose site looks newer. Almost none of those reasons say anything about what the site should actually do differently once it is finished.

That gap matters because a website redesign is expensive to get wrong twice. The visual refresh is the easy, visible part. The part that decides whether the new site performs better is content structure, page speed, and whether the pages are built around what customers actually search for.

Start with what the old site got wrong

Before any design work starts, list the specific problems: pages that do not convert, content that is out of date, a CMS nobody on the team can use, load times that lose mobile visitors. A redesign brief built from that list produces a site that fixes something. A brief built from "make it look more modern" produces a site that looks different and performs about the same.

Protect what is already working

It is common to lose organic traffic after a redesign simply because URLs changed and nobody set up redirects, or because a page that ranked well got merged into a broader one and lost its focus. Audit which pages already bring in traffic or leads before touching the site structure, and treat those as fixed points the redesign has to preserve, not casualties of a fresh sitemap.

Decide what "better" means before you start

Faster load times, a CMS the team can actually use, more enquiries from the same traffic, easier editing for non-technical staff — pick the two or three that matter most for this project and hold the finished site to them. Without that, "we redesigned the website" is the only outcome anyone can point to, and it is not one that shows up on a balance sheet.