In short
Upgrading makes sense when you can fix the problems and fit the site to what your business needs within the existing setup. A rebuild is worth considering when the structure, the design, and the way the site is managed all need broad changes, or when the site has become hard to keep developing. Before you decide, look at what works, what's holding the business back, and what each option takes in budget and time. Even in a rebuild, you can keep your content, your photos, and your page URLs.
When I decided to rebuild my studio’s website, the first thing I wanted was to get things in order.
I built the first version when I was just starting out. Since then I’ve learned a lot, the studio has grown, and projects, articles, and changes have piled up. I wanted to clean up the structure and give the site a better foundation for what comes next: a clear place for services, projects, and content, and an easy way to add and update things.
I wanted to move forward on design too: a more modern feel that fits the work I do today and the way I want to present the studio.
This time I was both the builder and the client. All the feedback went to the same person.
The decision to rebuild came out of all of that together. I wanted to change the structure, make the site easier to manage, and develop a new visual language. I’ve already written separately about how I rebuilt the studio’s website, but the question that came before it is one a lot of business owners face.
You have a website. You’ve already put money and time into it. You feel something needs to change, but you can’t tell whether that means a few fixes, a major upgrade, or a whole new project. To decide, you first need to know what you want the change to solve.
What’s actually bothering you about your site?
“I need a new website” can be shorthand for several very different problems.
Sometimes the design no longer fits the business. Sometimes it’s hard to tell what a service includes. Sometimes the site looks fine on a computer, but on a phone the menu is awkward and the images cover the text. And then there’s the part the owner knows all too well: how much hassle it takes to change one sentence or add a new project.
Start with a few simple questions:
- Does the site show the services you offer today and the kind of work you want to get?
- Can someone who doesn’t know your business understand what you offer and who it’s for?
- Is it easy to read, find your way around, and get in touch on a phone?
- Can you update the site and add content without getting tangled up?
Try to describe the problem in a way you can check. “The site feels dated” is a start. “Our latest projects aren’t on it, our main service is buried at the bottom of the page, and the gallery is a pain to update” already points to the work that needs doing.
And what if the site just isn’t bringing in leads?
Then you also need to look at what happens before anyone gets in touch. Are people reaching the site? Where do they come from? Are they looking for the service you offer? And what do they see when they land?
If there’s almost no traffic, the question is how people are supposed to find you. If the right people are visiting but few get in touch, look at the content, the way the service is presented, and the path to contacting you. Send a test form too, and make sure the message actually arrives.
The review may lead to a change on the site. It may also turn out that the content, the SEO, or the advertising needs work. A lack of leads doesn’t, by itself, mean you have to rebuild everything.
When can you improve the site you have?
When the site’s structure still fits the business and the existing system is workable, there’s a lot you can improve within it.
You can rewrite the service pages, show recent work, reorganize the menu, deal with heavy images, and fix the areas that don’t work well on a phone. Sometimes even a broad design refresh can be done inside the existing site.
Say you’ve added a new service. If you have an easy way to create a page for it, add it to the menu, and connect relevant projects to it, that may be exactly the job to do right now. A change in the business is no reason to assume the whole site has to be replaced.
One example from my own work is the Digitaler website. Ofer Teller came to me to improve its performance, and a review turned up things that were slowing down the load, including large images and components that loaded as soon as the page opened. The work covered optimizing the images and the way the site loads, all within the existing site.
When the work was done, I wrote to Ofer that we’d gotten good results, and that going beyond them would take major changes to the site. That’s an important point in this decision: knowing what you can achieve within the current setup and what calls for a different scope of work.
Even with an upgrade, define up front what you want to achieve. For example, a smoother load on phones, or a way to add a project without designing a new page every time. Then at the end you can check whether the work solved the problem that got you started.

When is a rebuild worth considering?
A rebuild becomes a reasonable option when several of the changes you need are tied to one another and are hard to carry out cleanly within the existing site.
Say the business now works in several areas, but the site was built around a single service. The service pages need to be reorganized, the work needs a different way of being shown, and the navigation has to change. If the system you manage the site with also makes those changes hard and the design needs extensive work, it’s worth weighing the two options side by side.
Another case to look at is a site where every change has to be made in several places. If updating one detail of a project means manually editing the project page, the home page, and several service pages, it’s time to think about how the content is organized. Sometimes that can be improved in the existing system; sometimes the right move is to rebuild that part.
In my case, wanting to clean up the structure and build a foundation that’s easy to work with going forward was a big part of the decision. I wanted to add projects and articles through a clear system, and give them a place inside a design that fits the studio today.
What will you want to add to the site later?
Think about the needs you can already see coming: a service you plan to add, a growing portfolio, content you’ll want to publish, or a connection to a system your business uses.
For example, if you plan to post projects regularly, you’ll want an organized way to enter photos, a description, and details. If your services are aimed at different audiences, each one may need its own page and its own explanation.
You don’t need to build every idea you might get to five years from now. You do want to know that the current plan lets you keep going with the things that already matter to the business.
Does your current platform fit those needs?
The platform is part of the review too. If your site is on Wix or Squarespace, find out whether the changes you need can be made there and how much work they involve. When the platform puts a real limit on something the business needs, a move to WordPress is worth considering.
I work in WordPress because it lets me fit the content structure, the editing interface, and the code to the business, on hosting the business chooses. That flexibility can be useful when the site needs to grow or needs special features. It also comes with responsibilities: maintenance, updates, and backups.
The move takes planning. Wix doesn’t let you export the complete site to run on other hosting, and Squarespace lets you export some of the content, while the design and some content types have to be handled separately. So you check what can be moved and what has to be rebuilt. Wix’s help page and Squarespace’s export guide lay out the options.
How do you compare the cost of an upgrade with the cost of a new site?
To compare two options, you need to understand what you’ll have at the end of each.
A quote for upgrading the home page and a quote for rebuilding the whole site cover different work. Even if the first is cheaper, some of the problems may remain. Then again, it may solve exactly what matters to you right now, and everything else can keep working as it is.
Check what each option includes in content, design, mobile, and the back end; which limitations will remain; and what it’s likely to take to make the next change you’re planning.
Your time is part of the math too. Preparing copy, choosing photos, reviewing mockups, and checking the result are all part of the project. The comparison should also include the relevant ongoing costs, such as hosting, licenses, and maintenance.
We’ve already invested in the site. What happens to that investment?
That’s a completely fair question, especially if you’ve invested in writing, photography, and a portfolio.
Some of that material can come with you: good photos, useful articles, service descriptions, and projects. In a rebuild, too, you go through what’s there, decide what fits, and put it in the right place. You don’t have to produce everything again.
Take the existing investment into account, and at the same time look at what’s needed from here on. Sometimes the right call is a focused upgrade within the current budget, with room to expand later.
This table can help you sort it out. The actual direction depends on a review of the site:
| What’s happening on the site | What to check | Possible direction |
|---|---|---|
| The content and photos no longer represent the business | Whether the structure and the editing system suit the new content | A content update and a visual refresh |
| The site is slow or hard to use on a phone | What’s causing the problem and how many parts of the site need work | A focused fix or a broad upgrade, depending on what you find |
| The services have changed and adding content has become cumbersome | Whether the structure and the back end can be changed within the existing setup | A comparison between a major upgrade and a rebuild |
| Almost no leads | How much traffic there is and how relevant it is, how the service is presented, and whether the contact path works | Work on whatever cause you find; the traffic sources may need work too |
What should you keep when you change the site?
Before touching the site, find out what’s already working. A page that brings in visits from Google, an article that answers an important question, a project people ask to see, a link from another website: all of these belong in the plan.
When you have access to search, traffic, and lead data, use it to spot the pages and actions that are important to keep. Alongside the data, go through the content itself. Sometimes a site has good material that just never got a clear place.
In a rebuild, you can usually keep the same domain and keep the page URLs that still fit. When a URL changes, plan a permanent redirect to the relevant page, so anyone coming in through an old link lands in the right place. If pages are merged or removed, each case is decided by the page’s content and what it does.
The switch itself needs planning too. The new site can be prepared in a separate staging environment while the existing site stays live. Before the switch, check the pages, the menus, the forms, and how it all looks on a phone. If the site handles bookings, purchases, or sign-ups, you also need to plan how to keep the information that comes in while the work is underway.
After launch, check again that inquiries come through, that links work, and that search engines can reach the pages. Keep watching the data to catch anything that needs attention.
This kind of planning lowers the risk of hurting your presence on Google. A major change can still cause some fluctuation, which is why the checking continues after the new site is live. You can read more in Google’s guidelines for moving a site with URL changes.

How do I approach this decision with a business owner?
I want to understand what the business does today, which customers it wants to bring in, and what it needs to add or change on the site. Then we go through the site itself and the data that’s available, and see what can be done with the existing setup.
That’s my starting point in web design projects for businesses. The goal is to arrive at a clear scope of work: you can see what it includes and how it connects to the needs that came up in our conversation.
When I look back at the decision I made for my own site, what tipped it was wanting to bring together a cleaner structure, easier management, and a modern design. For another business, the review might lead to a content update or work on a few key pages.
If you’re trying to figure out what to do with your site, we can start with a conversation about your business and what you’d like to change. It’s a good way to find out what’s worth checking before you decide on your next project.
Frequently asked questions
Is there an age when a website needs to be replaced?
No set number of years means a site has to go. What matters is whether it still represents the business accurately, is easy to use, runs on a platform and plugins that are still maintained, and can be updated and expanded. An older site can keep serving a business well, and a fairly new one may need major changes.
Can I refresh the design without rebuilding everything?
Yes, depending on how the site is built. Sometimes colors, typography, images, and page layouts can be changed within the existing system. If the redesign also means reorganizing the content, the menus, and the editing interface, check the scope of the work before you decide.
Can a new website hurt my Google rankings?
Yes. Changes to URLs, content, or links can affect rankings, and so can problems that keep pages from being crawled and indexed. Mapping the pages, keeping what matters, setting up the right redirects, and testing before and after launch all help reduce the risk. No one can promise there won't be fluctuations.
Can I upgrade the site in stages?
Yes, when the site's structure and the way the changes depend on each other allow it. You can start with the problems that get in visitors' way or with the pages that matter most to the business, and go from there. It's worth making an overall plan up front, so the stages fit together and you don't end up redoing work later.
Does a rebuild mean switching platforms or domains?
No. You can rebuild on the same platform and keep the same domain, as I did with my studio's site on WordPress. A move to another platform is weighed against what the business needs and the limits you've run into. Even when you switch platforms, you can usually keep the domain and plan how the content and URLs move over.



