Your website feels dated, the bounce rate looks bad, and a competitor just launched something slick. The obvious move is a full redesign — burn it down, start fresh, hire an agency. For most businesses that instinct is wrong, and it's expensive in a way that's hard to undo once the project starts.
The takeaway up front: a redesign and a refresh solve different problems, and most "we need a redesign" feelings are really refresh problems in disguise. A refresh updates the look and fixes weak spots on the site you have. A redesign rebuilds the structure, content, and often the platform underneath — so it costs several times more and ships in months, not weeks. The whole website redesign vs refresh decision comes down to one thing: is your problem skin-deep or structural? Diagnose that honestly and you'll either save a large budget or spend it on the right thing.
Refresh vs. redesign: what each one actually is
These two words get used interchangeably, which is exactly how businesses buy the wrong project. They are not the same scope.
A refresh keeps your site's structure, navigation, and platform, and improves what sits on top: updated colors and typography, better photography, sharper copy, a rebuilt homepage or a few key pages. The information architecture — how pages are organized and how people move through them — stays put. It's cosmetic by design.
A redesign changes the bones: new structure, reorganized navigation, rewritten content, often a new platform underneath. You're replacing the site, not improving it — which is why it risks losing hard-won SEO and breaking links. A refresh asks how do we make this site better? A redesign asks should this site exist in its current form at all? — and most businesses asking the first accidentally pay for the second.
The signs you actually need a full redesign
These are the redesign signs that actually justify a rebuild — each is structural, something a new coat of paint won't reach:
- The site can't do something the business now needs. You've added a product line, a booking flow, a members area, or a second market, and the current structure has no sensible place to put it. Architecture, not aesthetics, is the blocker.
- The platform is a dead end. You've outgrown your builder or CMS — it can't support the integrations, page types, or performance you need. Changing the foundation is a rebuild.
- Navigation has become a maze. Pages were bolted on for years with no plan, and analytics show people landing and giving up. When the organization is broken, restyling won't save it.
- The site misrepresents the business. Not "it looks a bit old" — it positions you as something you no longer are, or undercuts your credibility with the customers you want now. That's a strategy problem, and strategy lives in structure and content.
The thread through all of these: the limitation is in the foundation. If you'd have to tear up the structure to fix it, you're in redesign territory.
The signs you only need a refresh
Far more often, the real problems are these — and every one is a refresh, not a rebuild:
- It just looks dated. Old fonts, tired stock photos, a color palette that screams its age. This is the most common reason businesses think they need a redesign — and new visuals on the existing structure get you most of the perceived upgrade for a fraction of the cost.
- One or two pages underperform. The homepage doesn't convert, or a landing page loses people. You don't rebuild a whole site to fix two pages — you redesign those pages.
- The copy is weak or off-message. Confusing headlines, no clear next step, jargon. Rewriting content is a refresh; the structure that holds it is fine.
- It's a little slow. Performance problems are usually fixable in place — images, scripts, hosting — without touching architecture.
- The branding shifted. New logo, colors, or voice. Rolling a brand update across the existing site is a refresh, even when it touches every page.
A useful test: if you can name what's wrong and none of it requires changing how the site is structured, it's a refresh.
How to decide: the one-question framework
Strip away the feelings and the competitor envy, and the decision reduces to one question: is the problem in the foundation, or on the surface? Work it in three steps:
- Name the actual problem. Not "it feels old" — the specific, observable issue. "Our booking flow has nowhere to live." "The homepage converts at half what it should." A named problem earns a budget; vague dissatisfaction doesn't.
- Ask whether the structure has to change to fix it. Could a competent designer solve this by updating visuals, rewriting copy, fixing a few pages, or tuning performance on the current structure? If yes, it's a refresh. If the only real fix is reorganizing the site, changing the platform, or rebuilding how pages work, it's a redesign.
- Count the structural problems. One isolated issue might be solvable in place. A pile of them — outgrown platform, broken navigation, wrong positioning, plus the dated look — is the case for starting over. Redesign when the problems cluster, not when a single surface gripe is loud.
When you're unsure, default to the refresh: cheaper, faster, lower-risk, and it preserves the SEO and links a rebuild can endanger. If it doesn't move the numbers, you've learned the problem really is structural — the evidence that justifies the bigger project.
Whichever way you lean, get clear on what good design is doing before you scope the work — the principles in our web design guide apply whether you refresh or rebuild.
FAQ
How do I know if my website needs a redesign?
You need a full redesign when the problem is structural — the site can't support something the business now needs, the platform is a dead end, the navigation is genuinely broken, or it misrepresents who you are. If you can fix what's wrong by updating visuals, rewriting copy, improving a few pages, or tuning speed on the existing structure, you only need a refresh. Name the specific problem first; "it feels old" is almost always a refresh.
What's the difference between a website refresh and a redesign?
A refresh keeps your site's structure and platform and improves what's on top — design, photography, copy, and a few key pages. A redesign rebuilds the foundation: new structure, reorganized navigation, often a new platform. A refresh is cosmetic and surgical; a redesign is a replacement, which is why it costs several times more and takes months rather than weeks.
Can I just refresh my homepage instead of the whole site?
Yes, and you often should. If one or two pages underperform while the rest works, redesigning just those pages is the right-sized fix. Page-level work is a core refresh activity precisely because it gets results without the cost, time, or SEO risk of a full rebuild.
Will a redesign hurt my SEO?
It can, which is a reason not to redesign casually. Rebuilds risk losing rankings and breaking links when URLs change, content gets dropped, or redirects are mishandled. A refresh that leaves the structure intact carries far less of that risk. If you do redesign, plan it to preserve URLs, redirect old pages, and keep the content that earns your traffic.
How often should a business redesign its website?
There's no fixed schedule, and "we redesign every few years" is usually a way to spend money on a refresh problem. Redesign when a structural need appears — an outgrown platform, a real shift in what the business does, navigation that no longer works. In between, keep the site current with refreshes.
Next step
Before you greenlight anything, write down the specific problem you're solving. If you can't name one — or the ones you can name are all surface-level — you need a refresh, and you'll get most of the upgrade for a fraction of the budget. If the problems are structural and they cluster, a redesign is the right call, planned so you don't lose the SEO and links you've earned. The expensive mistake isn't choosing wrong once; it's never asking whether the problem is in the foundation or on the surface. Want a second opinion on which one your site needs? Talk to us at whelex.com.
