Seen
Website Refresh vs Redesign vs Rebuild: What Does Your Website Actually Need?
Choose between a refresh, redesign and rebuild by examining what your website actually needs to do better.

Milan Gohil
·
11 min read
A website looking old is not enough reason to replace it. Look at Craigslist. Its current site is still built around a very simple list of locations, categories and postings. People can choose an area, browse jobs, housing, services, items for sale and other categories without the experience trying to look like a modern SaaS website.
McMaster-Carr is another useful example. Its website gives customers access to a large catalogue of industrial products, lets them narrow and compare products, view order history and place orders. McMaster-Carr says 98% of orders ship from stock today. The website is doing serious ecommerce work without depending on the visual style you might expect from a newly launched consumer brand.
Berkshire Hathaway goes even further in the other direction. Its official homepage is essentially a straightforward collection of links to annual reports, shareholder letters, SEC filings, governance information, news and company information. The page is extremely simple, but it directly supports what Berkshire uses that corporate website for.
None of these examples proves that an old-looking website converts better. They show something simpler: How old a website looks does not tell you how much of it needs to change. If your own website feels outdated, don't begin by choosing between a refresh, redesign or rebuild. Open the website and test it.
Start with your own website
Take your phone and laptop and try these yourself.
1. Can you understand the business from the homepage?
Open the homepage as if you know nothing about the company. Without using information you already know, answer:
What does this company do?
Who is it for?
What are the main services or products?
Why would someone choose it?
Where should a relevant visitor go next?
If you already know the company too well to judge this, send the homepage to someone who does not. Ask them what they think the company does. If the answer is wrong or vague, you may have a messaging problem before you have a website problem.
2. Can you find the most important things?
Choose three things a real customer might need. For example:
a particular service
pricing
a case study
product specifications
locations
support
contact information
Start from the homepage and try finding each one. Don't use the website's search unless that is how customers would normally find it. Look at where you hesitate. If information exists but you cannot predict where it will be, the problem may be the sitemap, navigation or page structure. A new colour palette will not fix that.
3. Can someone verify that your claims are real?
Go through your important pages. Whenever the website makes a claim, look for what supports it. If a page says:
We have extensive experience.
Can the visitor see the work? If it says:
Trusted by growing companies.
Can they see the companies, reviews or customer stories? If it says:
We improved the client's performance.
Is there a result, example or case study? Sometimes a website feels weak not because it needs rebuilding, but because it makes too many claims without enough proof.
4. Try becoming a lead or customer
Don't just look at the contact page. Use it. Try the website's main CTA. Submit a form. Open it on mobile. Check confirmation messages. Follow links. Try the phone number and email links. If relevant, test checkout, booking, quote requests or account creation. You may discover that the problem isn't the website design. It may simply be:
a long form
unclear next steps
broken tracking
poor mobile layout
a hidden contact option
a confusing CTA
no explanation of what happens after submission
Those can often be improved without replacing everything.
5. Try updating the website
Now switch from the customer's side to the team's side. Try doing something your business commonly needs:
add a service
create a landing page
publish an article
update a team member
change homepage content
add a case study
create a new location page
update navigation
replace an image
change a form
How much work did that take? Did a marketer handle it? Did you need a developer? Did updating one component affect five other pages? Did you have to duplicate an existing page because creating a new structure was too difficult? If normal business changes repeatedly turn into development projects, the problem may be underneath the visible design.
6. Try adding what the business needs next
Don't test only today's website. Write down five things you expect the website to need over the next two or three years. For example:
more service pages
multiple locations
another language
ecommerce
customer accounts
CRM integration
gated content
better analytics
appointment booking
a resource centre
new product categories
marketing automation
Now ask: Can the current website support each of those without creating another workaround? Something being technically possible does not always mean the current system is the right place to build it.
7. Check what you would lose by replacing the website
Before deciding that everything should be rebuilt, check what the current website already has. Look for:
pages receiving organic traffic
keywords bringing visitors
backlinks
pages generating leads
high-performing landing pages
useful articles
product URLs
images appearing in search
returning-user journeys
integrations
tracking
customer data
existing content your team still uses
The website may look outdated while still holding years of accumulated value. You need to know that before changing it.
Now the difference between refresh, redesign and rebuild becomes easier
You don't need a perfect definition. You need to know where the problem sits. A simple way to look at it is:
What is failing? | What to investigate |
|---|---|
Visual presentation | Refresh |
Messaging/content | Refresh or redesign |
Page structure | Redesign |
Navigation/findability | Redesign |
User journeys | Redesign |
CMS/editing experience | Rebuild or technical restructuring |
Code/components | Rebuild |
Integrations/data model | Rebuild |
Several layers | Combination |
Real projects often cross more than one column. That's normal.
What is a website refresh?
A refresh means most of the current website still does its job. You improve specific parts instead of replacing the system around them. A refresh might include:
updating the homepage
rewriting messaging
improving typography
replacing outdated imagery
improving spacing and consistency
adding recent work
adding stronger proof
updating CTAs
improving selected page layouts
fixing mobile issues
updating outdated content
Imagine a consulting company with a reliable WordPress or Webflow website. Its team can edit it. Important pages already rank. Forms work. The sitemap still matches the services. But the company has grown and the website still looks and sounds like the smaller business it was three years ago. That does not automatically justify rebuilding the platform. Updating the important pages may solve the actual problem with much less disruption.
A practical refresh check
Pick the five pages that matter most to the business. Usually something like:
Homepage
Main service page
Important service detail page
Case study/work page
Contact page
If improving those pages would solve most of what currently bothers you, start by exploring a refresh. If fixing them immediately creates structural problems elsewhere, keep investigating.
What is a website redesign?
A redesign goes deeper. The website technology may still be usable, but the way the site communicates and guides people no longer fits the business. Common situations include:
three services became fifteen
the company entered new markets
different customer groups now need different information
navigation was built around the old company structure
important pages are buried
multiple pages say almost the same thing
the homepage no longer explains the company properly
visitors reach the site but don't know where to go
service pages don't answer the questions customers now ask
conversion paths have grown messy
Here, simply changing typography and colours leaves the real problem untouched. You may need to rethink:
sitemap
navigation
page hierarchy
service structure
homepage content
page templates
internal links
customer journeys
messaging
proof
CTAs
A practical redesign check
Write down five important visitor tasks. For example:
Find whether the company offers Shopify development.
Understand whether the service is suitable for a small business.
See examples of previous work.
Find pricing or understand how pricing works.
Contact the right person.
Now attempt every task on the existing website. If the information exists but the route to it is consistently confusing, you're looking at a stronger redesign signal. This is also why sitemap and navigation testing should happen before drawing a completely new interface.
What is a website rebuild?
A rebuild becomes relevant when improving the experience repeatedly runs into limitations in the underlying setup. That might involve the:
CMS
page builder
theme
component system
codebase
hosting architecture
ecommerce platform
integrations
content model
database
permissions
deployment setup
You might hear things like:
“We can do that, but we'd need another plugin.”
“Don't update this component because it might break those pages.”
“We can't create that page type without custom development.”
“The old developer built that part, so nobody touches it.”
“We have to duplicate this page every time.”
“Changing the CMS field will affect hundreds of pages.”
Those are different problems from an unattractive homepage.
A practical rebuild check
Make two lists. Things the business needs next and What the current website requires to support them If almost every future requirement needs another workaround, dependency or patch, investigate whether continuing with the same foundation still makes sense.
Rebuilding does not mean deleting everything
This is where website projects can create unnecessary damage. You can rebuild the technical system while preserving valuable parts of the existing website. That may include:
URLs
content
metadata
rankings
backlinks
images
product information
page relationships
forms
integrations
analytics
structured data
conversion history
If URLs change during a migration, Google recommends preparing an old-to-new URL mapping, implementing permanent redirects, updating internal links, updating relevant annotations such as canonicals, submitting the new sitemap and monitoring the move through Search Console. Google also notes that ranking fluctuations can occur while significant site moves are recrawled and reindexed. This is why the question should never be: Google: site moves with URL changes.
What can we delete and start again?
It should be:
What is worth keeping?
Don't change URLs just because you're redesigning
A visual redesign does not require URL changes. A CMS change does not automatically require URL changes. Even a rebuild does not mean every useful URL has to disappear. If an existing page:
serves the right intent
already receives traffic
has backlinks
is useful
still belongs in the new website
keeping its URL can reduce unnecessary migration work. When URLs genuinely need to change, map them deliberately. Google recommends direct server-side permanent redirects such as 301 or 308 where appropriate and warns against redirecting large groups of old URLs to an irrelevant page such as the homepage.
A website can need more than one of these
Suppose your CMS works well. You don't need to replace it. But you do need to:
restructure navigation
rebuild the homepage
create new service templates
rewrite content
update the visual system
improve forms
keep current article URLs
preserve existing SEO
Calling the project only a “refresh” or “rebuild” does not make it better. Define the work by what actually needs changing. Another website may be the opposite: The design is acceptable, but the old platform makes content management, performance and new integrations unnecessarily difficult. That could justify technical rebuilding while much of the visible content and structure remains familiar.
What if you are building a website from zero?
Refresh, redesign and rebuild describe changes to something that already exists. If the business has no real website yet, you're planning a new website. You don't have old URLs, existing navigation or legacy technology to preserve, but you still need to make the same kinds of decisions:
What does the business need the website to do?
What should users be able to find?
What pages are needed?
What content belongs on those pages?
What technology supports future requirements?
Who will maintain it?
How will success be measured?
Starting from zero removes migration problems. It doesn't remove planning.
Before you spend money, write this down
You don't need a 40-page website strategy document. Create four lists.
Keep
What already works? Examples:
rankings
URLs
content
customer journeys
CMS
integrations
forms
branding elements
Fix
What is causing problems now? Examples:
unclear homepage
confusing navigation
outdated design
weak service pages
poor mobile experience
low-quality enquiries
Add
What is missing? Examples:
new services
locations
better proof
pricing information
case studies
integrations
language support
Remove
What no longer serves a purpose? Examples:
old services
duplicate pages
outdated messaging
dead integrations
abandoned plugins
irrelevant content
Now compare those four lists. If Keep is large and Fix mostly concerns presentation, start with a refresh. If Fix is dominated by structure, messaging and journeys, investigate a redesign. If Add repeatedly exposes platform limitations, investigate a rebuild. If all four lists are complicated, you probably need a mixed scope.
The useful question is smaller than “Do we need a new website?”
Try this instead: What can't the current website do properly? Then test it. If customers understand the business, find what they need, trust the company and complete important actions, don't replace working parts just because they look older. If the content is weak, improve the content. If people cannot find things, work on the structure. If customer journeys are confusing, redesign them. If the CMS or technical setup repeatedly blocks reasonable improvements, investigate rebuilding it.
And before replacing anything, identify what already creates value. You don't need the biggest website project. You need the amount of change that solves the problems you can actually see—and gives the business enough room for what comes next.
Sources and further reading
All Blogs
All Blogs & Articles
© 2026 Webshunya Studio®. All rights reserved.







