The Redesign Is Usually the Wrong Answer
Key takeaways:
- Companies that audit and fix their existing website typically spend $8–15K and see results in 8 weeks, while full redesigns cost $40–60K and take 6 months, often without proportionally better outcomes.
- A website with solid technical foundations consistently outperforms a visually impressive site built on weak architecture, particularly when search algorithms update.
- The trigger for most redesign decisions is a competitor’s new site, not the business’s own data — and that is almost always the wrong reason to spend $50,000.
When the impulse to start over is costing you the answer
I have been having the same conversation for about fifteen years. A business owner calls, tells me their website is outdated, they need a full redesign, they have a rough budget in mind, and they want to talk timelines. And somewhere in the first twenty minutes, I ask whether they have looked at their analytics recently. The answer is almost always no.
That conversation has happened enough times that I stopped treating it as a quirk of individual clients. It is a pattern, and it tells you something important about how businesses actually make website decisions.
Why do so many businesses default to “we need a full redesign”?
The trigger is almost never data. It is almost always a competitor.
Someone in the leadership team sees that a competitor has launched a new website. It looks impressive. It has a slick homepage video, a modern font, some parallax scrolling. And suddenly the existing website, which was perfectly functional last Tuesday, feels embarrassing. The decision to redesign gets made in an afternoon, usually without anyone opening Google Analytics.
I understand the instinct. Nobody wants to look behind their competitor. But “our competitor launched something impressive” is one of the worst reasons to spend $50,000 and six months of your team’s attention on a website project. It is a vanity trigger dressed up as a strategic decision.
The businesses I see make the best website investments are the ones that start by looking at what their own site is actually doing. Not what it looks like. What it does.
What does fixing an existing site actually involve?
It depends on the audit, but the pattern is consistent. Most websites that have been running for two or more years have accumulated a set of fixable problems that are quietly costing them traffic, leads, or conversions.
I worked with a professional services firm in Singapore a couple of years back. They came to me convinced they needed a full redesign. Their site was four years old, they said, and it felt dated. Before we talked budgets, I asked them to pull their analytics for the previous six months. What we found was a contact form that had stopped submitting correctly nine months earlier. Nobody had noticed because nobody was checking. In those nine months, every person who filled out that form got a success message, and the firm got nothing. No email, no notification, no lead.
That one fix took half a day. The redesign conversation stopped.
That is an extreme case, but the underlying principle is not unusual. A technical audit typically surfaces things like page speed problems that are inflating bounce rates, broken or misconfigured forms, crawl errors that are hiding pages from Google, internal linking gaps that are leaving content stranded, and conversion paths that make sense to the person who designed them but not to the person using them.
Fixing those things costs real money, but nothing close to a full redesign. The work my team at Chillybin does on a focused remediation project typically runs $8–15K and takes six to eight weeks. A full redesign is $40–60K and six months, minimum, if it is run properly.
That is not an argument against redesigns. Sometimes they are genuinely necessary. But the math on “fix first” is hard to ignore.
How does site architecture affect search ranking when Google updates?
This is where the technical side of the “fix versus rebuild” argument gets concrete.
Google runs core algorithm updates several times a year. Each one reshuffles rankings based on how Google’s systems now evaluate quality, relevance, and technical health. The updates are not random. They consistently reward sites with solid technical foundations and penalise sites built on thin content or outdated frameworks.
Earlier this year, we watched a couple of these updates move through and the pattern was exactly what I would have predicted based on two and a half decades of watching this. Sites with clean architecture, proper structured data, fast load times, and content depth held their positions. Sites that had been coasting on historical authority but had neglected their technical foundations took hits.
The point is not that you need to panic every time Google announces an update. The point is that an investment in technical health is not a one-time thing, and a shiny new design does not protect you if the foundation is weak. I have seen beautifully designed sites tank in the rankings because the agency that built them prioritised aesthetics over architecture. And I have seen unglamorous, visually modest sites punch well above their weight because someone took the time to get the technical side right.
A redesign resets your visual layer. It does not automatically fix your technical layer, and if the new build is done by a team that does not understand architecture, it can actually make things worse.
What should a business look at before deciding to redesign?
At minimum, four things.
First, conversion rate. What percentage of visitors are doing what you want them to do? If your site gets two thousand visitors a month and generates three enquiries, the problem is almost certainly not your colour palette.
Second, page speed. Google’s Core Web Vitals have been a ranking factor for a couple of years now. If your Largest Contentful Paint is above 2.5 seconds, you are losing both rankings and users. This is fixable without a redesign.
Third, crawl health. Open Google Search Console and look at your coverage report. Are there pages Google cannot crawl? Errors it is reporting? Most businesses have never looked at this, and most that do look at it find problems.
Fourth, traffic sources and trends. Is organic traffic flat or declining? Over what period? A 30% drop in organic traffic over twelve months is a signal worth investigating before you spend six months and $50K rebuilding something. The new site will inherit the same problems if you do not diagnose them first.
If all four of those look healthy and you still want to redesign, that is a legitimate conversation. Maybe the brand has evolved, maybe the site is genuinely not representing the business well, maybe the content management experience is painful enough to warrant a rebuild. There are good reasons to redesign. “Our competitor did it” and “it feels dated” are not among them.
How long does it take to see ROI from a fix versus a rebuild?
Faster from a fix, almost always.
A full redesign project runs six months in a best-case scenario. That assumes a well-run project with clear scope, decisive client feedback, and no major scope creep. In reality, many redesigns take eight to twelve months by the time you factor in content rewrites, stakeholder reviews, and the back-and-forth that comes with building something from scratch. You are not going to see organic traffic benefits for at least six weeks after launch, and often longer if the migration is not handled carefully.
A focused remediation project is a different timeline entirely. Fix the form, fix the speed, fix the crawl errors, tighten the conversion path. Eight weeks of work. Fixes go live incrementally. You can often see measurable movement within a month of the first changes shipping.
I am not romanticising the fix. Some sites are genuinely too far gone to patch. If the platform is unsupported, if the content management experience is so broken that nobody on the team can update anything, if the site was built on a proprietary system that is locking you out of your own content, then a rebuild is the right call. But those situations are less common than the number of redesign projects being commissioned would suggest.
The bias toward rebuilding exists partly because redesigns are more exciting to talk about, easier to sell, and more visible as a project. A technical remediation is unglamorous. Nobody is going to write a press release about fixing their Core Web Vitals. But the businesses that do that unglamorous work quietly, consistently, tend to be the ones that compound their digital advantage over time while their competitors cycle through expensive rebuilds every three years.
Twenty-five years of watching this industry, and that pattern has not changed. The boring investment usually wins.