Rebuild a website when the business's position has changed, when the structure works against how buyers decide, or when the platform keeps the site from being fast and accessible. Repair it when the message and structure are sound and the problems are local: weak copy, a few poor templates, slow pages, or missing structured data. The age of the site and how dated it looks are poor guides. The decision should come from a diagnosis of what the site says, how it is organized, and what it is built on.
What is the difference between a website redesign and a refresh?
A rebuild, often called a redesign, starts again from the foundation. It means new architecture, new copy, new design, and often a new platform. A repair, often called a refresh, keeps the foundation and fixes what sits on it. It might mean rewriting key pages, redesigning a few templates, fixing speed problems, or adding accurate structured data.
There is a third option that we advise against: a new visual style laid over the same structure and the same words. It costs real money, looks different for a while, and leaves the actual problems in place. If the site was saying the wrong thing in the wrong order, it will keep doing so in a new color.
How do you know if a website needs a redesign?
We look at three things, in this order. Each one points toward a rebuild on its own.
Has the company's position changed?
If the business now serves different buyers, offers different work, or competes on different grounds, the website is describing a company that no longer exists. The first job is to rebuild the message, not the site. We settle who the company serves and why it is the right choice, as we explain in Positioning Is Not Marketing. Only then is it clear whether the existing site can carry the new message. Sometimes new copy on the existing pages is enough. More often, a changed position means different pages, in a different order, for a different reader.
Does the structure fight the buyer?
Buyers arrive with questions in a predictable order. They want to know what the company does, whether it serves people like them, how the work proceeds, and what happens next. A site built around the company's internal departments, or around whatever pages were added over the years, answers those questions out of order or not at all.
Signs of a structure problem include important services buried two or three clicks deep, pages that overlap or contradict each other, navigation that lists everything with equal weight, and no clear path from interest to contact. A site that serves two audiences, such as referral partners and the clients they send, needs a separate path for each. When the structure is wrong, fixing individual pages helps little. The architecture has to change.
Does the platform block speed or accessibility?
Speed and accessibility can be measured, so this question has firmer answers. Google's Core Web Vitals give clear targets. A good Largest Contentful Paint, which measures loading, is 2.5 seconds or less. A good Interaction to Next Paint, which measures responsiveness, is 200 milliseconds or less. A good Cumulative Layout Shift, which measures visual stability, is 0.1 or less. Google recommends measuring these at the 75th percentile of page loads, across mobile and desktop.
For accessibility, the current W3C guideline is WCAG 2.2. It became a W3C Recommendation on October 5, 2023, and an updated version was published on December 12, 2024. We build to its AA level as a target.
If a site misses these marks because of a few heavy images or a handful of template errors, that is a repair. If it misses them because of the platform itself, such as a page builder that loads the same heavy code on every page or a theme that controls markup you cannot change, repairs will not hold. Each fix is undone by the next update.
When should you change website platforms?
Change platforms when the platform, not the content, is the limit. We look for a few patterns. Every small change needs a workaround or a developer. Plugins pile up to add features the platform should handle, and each one adds weight and risk. The markup cannot be controlled well enough to meet accessibility targets. Pages cannot be served as complete HTML, so the content depends on scripts to appear.
A platform change is a larger project than a redesign on the same platform, because content must be moved and URLs may change. It is worth doing when it removes a limit the business would otherwise pay for on every future change.
When is a refresh enough?
A refresh is enough when the position is current, the structure follows the buyer, and the platform can meet speed and accessibility targets. In that case the work is focused and usually faster. Typical repairs include:
- Copy. Rewriting the home page and key service pages so they answer the buyer's questions directly.
- A few templates. Redesigning the page types that matter most, such as service pages or the contact page.
- Speed fixes. Compressing images, removing unused scripts, and fixing layout shifts.
- Structured data. Adding accurate schema.org markup that matches what each page visibly says.
- Accessibility fixes. Correcting contrast, headings, form labels, and keyboard access.
- Internal links. Connecting related pages so readers and crawlers can follow the thread.
Repairs like these also improve how the site is read by machines, as we describe in How Search Engines and AI Assistants Read Your Website.
Will a redesign hurt search rankings?
It can cause a temporary dip, and careful work keeps the risk small. Google's documentation on moving a site with URL changes is plain about it: "Expect temporary fluctuation in site ranking during the move." The same page says that for medium-sized websites, it can take a few weeks or more for Google to start showing the new URLs instead of the old ones, and longer for larger sites.
Google's guidance on doing it well is also clear. Map every old URL to its new URL. Use server-side permanent redirects, such as 301 or 308, from the old URLs to the new ones. Avoid chains of redirects and send each old URL straight to its final destination. Update sitemaps with the new URLs. Google also states that 301 and other permanent redirects do not cause a loss in PageRank.
We add one rule of our own: keep good URLs where they are. If a page already has a clean, sensible address, a rebuild does not need to change it. Fewer changed URLs means fewer redirects and less to go wrong.
None of this guarantees a position afterward. Google's own guidance says no one can guarantee a #1 ranking on Google. What a careful move does is preserve what the old site earned and give the new one a fair start.
How does CATORI make the call?
We diagnose before we recommend. We read the site as a buyer would, from the first page to the contact form. We measure speed with real-user data where it exists and test accessibility against WCAG 2.2. We crawl the site to list every URL and see how pages connect. Then we compare what the site says with what the business now is. The recommendation follows from those findings, and it is often smaller than the client expected. The full sequence is set out in our approach.
What to do next
Start with the three tests above: whether the position has changed, whether the structure follows the buyer, and whether the platform can meet speed and accessibility targets. A changed position, a structure that fights the buyer, or a platform that cannot meet the targets points toward a rebuild. If the answers point the other way, a focused repair is likely the better use of money.
If you want a clear answer for your own site, our website design and development practice starts with exactly this diagnosis and recommends rebuild or repair based on what it finds.