“The site looks dated” is the reason people give. It is almost never the actual problem. The actual problem is usually that the site cannot do something the business now needs, and the dated look is what you notice while being annoyed about it.
Those are two different projects with two different price tags. Here is how to work out which one is in front of you.
Signs you need a redesign
A redesign keeps the structure and changes the surface: type, color, spacing, photography, maybe the layout of a few templates. The pages stay where they are and the URLs do not move.
This is the right project when:
- The pages you need already exist and are roughly right.
- Your team can edit the site and does.
- Traffic is steady and the search results you care about are holding.
- The site is fast enough on a phone.
- What is wrong is that it looks like it was made in 2014, because it was.
A redesign is cheaper, faster, and lower risk. If this describes you, do not let anyone talk you into more.
Signs you need a rebuild
A rebuild changes what the site is. New page structure, new templates, often a new content management system, and a redirect map from the old addresses to the new ones.
This is the right project when:
- You cannot edit meaningful parts of the site without calling someone.
- Pages have been added over the years with no plan, and nobody can say what half of them are for.
- The services you sell today are not the services on the site.
- It is slow on a phone and nobody can tell you why.
- Adding a booking form, a portal, or a real service page means fighting the template.
- The platform is no longer supported, or updates keep breaking things.
The tell is usually the third one. If the site describes a business you stopped being two years ago, no amount of new typography fixes it.
The middle case nobody names
There is a third project that gets skipped: keep the site, fix the content. New words, new photos, a page list that matches what you sell, better titles, real service pages. Same design, same platform, same URLs.
It is the cheapest of the three and it is often the one that moves the phone. A tired-looking page that clearly states what you do and where beats a beautiful page that makes a visitor guess.
If you are not sure, try this first. You will learn what your site actually needs to say before you pay anyone to design around it.
Questions that settle it
Answer these honestly and the project usually names itself.
- When did you last change something on the site yourself? If the answer is “we ask the guy,” the structure is the problem, not the look.
- What do people call you about that the site never mentions? That is a content gap, not a design gap.
- Which pages bring in work? Check before you touch anything. Businesses rebuild sites every year and quietly delete the one page that was earning.
- What is on the site that you would not sell today? Old services still bring calls you have to decline.
- Does the site have to do anything new? Booking, accounts, quoting, payments. Any yes means a build, not a facelift.
What a rebuild must include
If a rebuild is the answer, three things are not optional, and they are the ones most often left out of a cheap quote.
A page list agreed before design starts. Every page, what it is for, and what a visitor does on it. Without this you are decorating.
A redirect map. Every old address pointed at its new home, then tested against the live site. This is how you keep the search traffic you already have. Skipping it is the single most expensive mistake in a rebuild, and it does not show up for about six weeks.
A content plan with names on it. Who writes what, by when. Content is what delays website projects. Not design, not code. Content.
What to do this week
Open your analytics and list your ten most visited pages. Open your phone and load the site off wifi. Write down the three questions customers ask you most often and check whether the site answers them.
If the pages that earn are fine and the answers are there, you need a redesign. If the list surprises you and the answers are missing, you need to fix the content first and then decide.
