A rebuild proposal has a line for discovery, a line for design, a line for build, and a line for content migration.
It does not have a line for the thing it actually costs you, which is a year of not being able to tell what worked.
That is the argument against most rebuilds, and it has nothing to do with the money. You are about to change two hundred things at once on the only asset where you can measure anything, which means that whatever happens next, you will not know which change caused it.
So the answer is usually no, and the useful version of the answer is a sequence. Find out which page is failing, using data you already have, in about an hour. Fix that. Rebuild only when you can name the specific thing the current site physically prevents you from doing.
There are three cases where the answer is genuinely yes, and I will get to them.
Which page is failing
Almost nobody commissioning a rebuild can answer this, which is remarkable given the price.
Your problem is in one of three places, and they have completely different fixes.
Not enough people arrive. Sessions are low on the pages that are meant to sell. This is not a website problem at all. A new site with the same number of visitors converts the same number of people, and you will have spent the budget on the wrong department.
People arrive and leave. Decent traffic to a page, almost nobody goes further. Now you have a page problem, and it is usually a copy problem rather than a design problem. The page does not say who it is for, or what happens next, or what it costs.
People convert and nothing comes of it. Forms get filled and the pipeline is still thin. That is a follow-up or a qualification problem and a rebuild cannot touch it.
Pull up the last ninety days. Landing pages by sessions, then the conversion rate on the three that are supposed to do the work. You will know which of the three you have inside an hour, and in my experience it is the second one far more often than people expect, which is the cheapest of the three to fix.
A rebuild is the only remedy that costs the same regardless of which problem you have. That is why it gets sold.
Changing everything at once buys no knowledge
Here is the part that gets skipped, and it is the real cost.
Say you rebuild. New structure, new copy, new design, new platform, new forms. Six months later inquiries are up 20%.
What caused it? You cannot say. Not approximately, not with effort. The variables moved together and there is no counterfactual, because the old site no longer exists to compare against.
Now the worse version. Six months later inquiries are down 20%. Was it the copy, the navigation, the lost rankings, or the market? You cannot say that either, so you cannot fix it, and the honest options are to wait or to change more things.
Compare the alternative. Rewrite one page. Watch it for six weeks against its own history. Keep it or revert it. You end the quarter knowing something true about your buyers, and you spent almost nothing.
The rebuild converts money into a new website. The sequence converts money into knowledge about what your customers respond to. Only one of those is still worth something next year.
And if you do rebuild, the traffic side has its own failure modes that have nothing to do with design, which I have covered separately in how to redesign without losing your Google traffic.
“The site is slow” is usually not the reason
This is the most common technical justification put in front of owners, and it deserves a straight answer, because somebody has probably shown you a Lighthouse score in the forties.
Google’s own page experience documentation is unusually direct about this. Core Web Vitals are used by its ranking systems, and there is no single page experience signal. But it also says that good scores in Search Console or third-party tools do not guarantee your pages will rank at the top, that beyond Core Web Vitals other page experience aspects do not directly help you rank higher, and this line, which I would put in front of anybody selling you a rebuild for speed:
Trying to get a perfect score just for SEO reasons may not be the best use of your time.
It goes further. Search “always seeks to show the most relevant content, even if the page experience is sub-par.”
You will also see a figure quoted, Core Web Vitals being 1% to 3% of ranking weight. I went looking for the source and could not find Google saying it anywhere. Treat it as somebody’s estimate that acquired a decimal point on the way round.
Which leaves speed as a conversion argument rather than a ranking one, and as a conversion argument it is often real. A page that takes six seconds on a phone on cellular loses people. But that is a reason to fix the images and the scripts on your four important pages, which is a week of work, not a reason to replace the site.
The three times the answer is yes
Each of these has the same shape: the current site physically prevents something specific, and you can name it in a sentence.
The platform blocks something nameable. Not “it is limiting us”. You need multi-location pages and the platform allows one address. You need to take payments in a currency it does not support. You need a booking flow the builder cannot express. If you cannot finish the sentence with a concrete capability, this is not your reason.
Nobody can change the site without a developer. This is the one I would weigh most heavily, and the least discussed. If publishing a page requires a ticket and a two week wait, you will stop publishing pages. The compounding cost of that over two years is larger than any rebuild quote, and it is invisible because it shows up as things you never did.
Accessibility or legal exposure. A genuine obligation rather than a vague worry, and often fixable without a rebuild, which is worth establishing first. I went through what actually applies to a small business in website accessibility and ADA compliance.
Notice that none of these is about how the site looks.
Dated and untrustworthy are different things
In fairness to the people who raise appearance, they are not always wrong. They are usually imprecise.
A site can look unfashionable and still convert perfectly well. Fashion in web design moves faster than buyers do, and your customers are not comparing your typography to anybody’s.
What costs you money is anything that reads as abandoned. A copyright line ending in 2021. A layout that breaks on a phone. Team photographs of people who left. A contact form that errors. Those are not aesthetic complaints, they are signals that nobody is home, and they are fixable in an afternoon without touching the architecture.
So when somebody says the site looks old, ask which of those two they mean. One is a taste conversation and the other is a trust problem with a cheap fix.
Where I come out
Spend the first hour finding out which page is failing, then spend a month fixing that one page and watching what happens.
If after that you can still name the specific capability the current site denies you, rebuild it, and you will brief it far better for having learned something first.
Most people who do the hour do not end up rebuilding. That is not because rebuilds are never right. It is because the hour usually finds something smaller, and smaller is the only kind of change you can actually learn from.
If you’d like a second opinion on which of the three problems you’ve actually got before you commit the budget, drop me a line on email, WhatsApp, phone or LinkedIn and we can have a quick chat, and my notes on SEO cover the traffic side in more detail. I’m taking on a small number of contracts at the moment, so I’ll tell you straight whether it’s something I could help with.