Redesign when the structure is right and the site just looks its age. Rebuild when the structure is wrong, the platform has become a liability, or nobody at the business can change a sentence without calling someone. The visual is almost never the real reason for either.
Owners usually arrive asking for a redesign because the site looks old, and old is the symptom they can see. Underneath, the actual complaint is usually one of three things: it does not bring in work, it cannot be updated, or it is broken on phones. Only the first of those is reliably fixed by how it looks.
What counts as a structure problem?
No page for a service you sell. A single services page listing eight things in a bulleted list. Navigation that reflects how the business is organized internally rather than how a customer thinks. Ten pages about the company and one about the customer.
None of that is fixed by new colors. You can put a beautiful skin on a site with no page for your most profitable service and it will still not be found by anyone searching for that service. That is a rebuild of the information, whether or not the code gets replaced.
When is the platform itself the problem?
When updating it is risky, when nobody can log in, when the plugins have not been touched in two years, or when the person who built it has moved on and nobody knows how it works. All four are common and all four get worse with time.
WordPress specifically ages badly when it is unattended. It is a fine platform and we work with it, and an unmaintained install with a dozen abandoned plugins is a genuine liability rather than an inconvenience. If you cannot say when it was last updated, treat that as a finding.
Not sure which one you are looking at?
Send us the address of your current site. We will tell you which side of the line it falls on and what it would take either way.
Get a free website and marketing auditHow do I tell the difference in ten minutes?
| If this is true | You probably need |
|---|---|
| The structure is right, it just looks dated | A redesign |
| You have a real page for every service you sell | A redesign |
| You can edit a page yourself today | A redesign |
| There is no page for your most profitable service | A rebuild of the structure |
| Nobody can log in or update the platform safely | A rebuild |
| It was never really built for a phone | A rebuild |
Score it honestly. Two or more on the rebuild side and a redesign will not save you, because you will spend the money and still be unable to add a service page next spring.
Is rebuilding always more expensive?
Not always, and that surprises people. Working inside somebody else's inherited build, with its conventions and its undocumented decisions, can take longer than starting cleanly. We have quoted both ways on the same site and had the rebuild come in lower.
What is reliably more expensive on a rebuild is the content and the migration, because that is where the real hours are. If the copy survives and the URL structure stays the same, a rebuild is mostly a build. If neither survives, it is a build plus a writing project plus a redirect map, and the quote should say so in three lines rather than one.
Can I do it in stages?
Often, yes, and it is underrated. Fix the structure first: add the missing service pages, fix the navigation, sort out the phone experience. Live with that for a season and see what the numbers do. Then do the visual work, with real evidence about which pages matter.
This is slower and it is a better use of money for a business that is not sure. It also removes the worst outcome in this whole category, which is spending your entire budget on the look and discovering the problem was somewhere else.
What about the content you already have?
Read it before you throw it away. Owner written copy from six years ago is often clumsy and often contains a specific detail that no rewrite will recover, because it came from a job somebody actually did.
Our habit now is to read every page of an old site before quoting, and to keep the sentences that carry real knowledge even when the paragraph around them gets rewritten. The alternative is what happens on most redesigns: the old site is treated as a problem to be replaced, and a small amount of genuine expertise is quietly deleted along with the bad layout. You cannot get that back from a brief, because the person who wrote it has forgotten the detail.
What we would tell you not to do
Do not rebuild because it has been three years. Age is not a reason. Some of the best performing local sites we look after are five years old, unremarkable to look at, and structurally right, and we would not touch them except to keep adding content.
And do not rebuild without the old URL list in hand. It is the one part of this that is very painful to fix after launch, and it is the part most likely to be missing from a cheap quote.
If you want an honest read on which side of the line your site sits, send us the address. We will tell you plainly, including when the answer is that it needs neither and your problem is somewhere else entirely. What each route involves is on the Growth Engine page, what it costs is on the pricing page, and the contact page is the fastest way to start.