Fix it when the underlying structure is sound and the problems are content, conversion or appearance. Rebuild when repairing the underlying system would cost more than replacing it.
Looking old is not a reason on its own.
An ugly website that ranks and generates enquiries has assets worth protecting. A beautiful website with no traffic has very little.
The rule we work by
If the structure is good, do not demolish the house because you dislike the kitchen.
Many website problems sit below the visual design, in the structure, the content and the search visibility. Those problems do not automatically require a rebuild.
But when several structural things are wrong at once, patching can become false economy, and you end up spending the price of a rebuild while still owning the old site.
The four things we look at first
In this order, before anyone discusses design.
1. What is already working?
Search Console comes before aesthetics.
Does the site rank for anything? Which pages get impressions? Which get clicks? Are there useful backlinks? Are there URLs Google already understands?
A website can look terrible and still have valuable pages underneath it. Those are assets, and a careless rebuild throws them away.
2. Is the structure correct?
We look at whether there is somewhere for each important topic to live.
A page per major service. Location pages where the business needs them. A clear category structure. Internal links that make sense. And no group of pages competing for the same search.
3. Can the current system actually be worked on?
Can we edit templates, improve speed, change headings, control URLs, manage redirects, add structured content, add tracking, and make proper mobile changes?
If every basic change is painful, repairing it stops making financial sense fairly quickly.
4. What does the business need now?
A five page brochure site may have been exactly right years ago.
If the company now has a dozen services, several locations, more than one audience or a second language, the old site has outgrown its original purpose. That is not a failure of the old site. It did its job.
Which way do the signals point?
No single row decides it. The answer comes from the pattern, the platform, and what it would cost to correct the problems together.
| Signals that favour fixing | Signals that favour rebuilding |
|---|---|
| Sensible URLs | Duplicate or confused URLs, pages competing with each other |
| Important services already have their own pages | Important services have no page, and adding one means fighting the platform |
| Google is indexing pages correctly | Pages cannot be indexed properly without structural change |
| Some pages already rank | Nothing ranks except the company name, despite the pages existing |
| The CMS is manageable | The platform fights every change |
| Templates are consistent | Content is hard coded everywhere |
| Mobile is acceptable, or fixable | Mobile cannot be fixed without rebuilding the templates |
| The site can be expanded | Adding pages would require redesigning the navigation |
| The design is dated but not obstructive | Nobody understands how the site works anymore |
| The problems are content, conversion and presentation | Several of the above are true at once |
The right hand column matters most when items combine. A missing service page on a workable platform may be a relatively simple repair. On a platform where adding one means fighting the system, it is a different problem.
One signal worth watching for: navigation labelled Company, Solutions, Expertise, More can indicate that the structure follows internal terminology rather than the way customers search and buy.
What is worth preserving either way
A rebuild should not mean throwing everything out.
URLs. Probably the most important. If a page already ranks, we want a very good reason before changing its address.
Rankings and search history. Which pages rank, for what, which queries bring traffic, where Google already sees relevance. That information shapes the new site.
Good content. Old does not mean bad. If a page contains genuinely useful information, preserve it, improve it, and move it carefully.
Images. Especially real projects, team photos, historical work, before and after shots, product photography. Those often have more value than the new visual design.
Backlinks. If other sites already link to specific pages, that value needs preserving through the same URL or a correct redirect.
The domain. A website rebuild does not normally require changing the domain.
The real danger in a rebuild is the migration
Not the design. The move.
A serious migration mistake is changing URLs without mapping them. An old address disappears, nothing redirects to the new one, and everyone arriving from Google or an old link hits a dead end.
If the rebuild changes URLs, the quote should include URL mapping and a redirect plan. If the URLs are staying the same, confirm that explicitly.
Google’s own site move guidance tells owners to map old URLs to new destinations, use permanent redirects where addresses change, check canonical and robots directives, update internal links and sitemaps, and monitor the move in Search Console. It also warns that significant site changes can cause temporary ranking fluctuations while pages are recrawled and reindexed.
Other things that go wrong on a badly managed migration:
- A noindex tag left switched on after launch
- Canonical tags changed or removed
- Content that was ranking quietly deleted
- Internal links dropped
- Title tags lost
- Structured data broken
- Analytics or conversion tracking not carried across
- Sections blocked in robots.txt
- Sitemap never updated
- Navigation reorganised so important pages become harder to reach
Which is how a website becomes better looking and worse at generating business.
The redesign trap, in both directions
Version one: rebuild everything, lose the traffic
The site looks old, so a new agency replaces the lot. New theme, new navigation, new URLs. Half the old content disappears. Nobody opens Search Console.
Launch day arrives and everyone likes the homepage. After launch, the question becomes why the Google traffic disappeared.
The redesign itself was not necessarily the mistake. Redesigning without understanding what the old site was already doing was the mistake.
Version two: rebuild nothing, change nothing
The new site faithfully preserves all the old content and structure exactly as they were.
So the business pays for a redesign and still has weak service pages, poor search visibility, no conversion strategy and no clear offer. A new coat of paint on the same problem.
What repairs and rebuilds actually cost
We would not frame this as fix equals cheap and rebuild equals expensive. The useful question is different.
What will this website cost you over the next two years?
Spend a bit fixing something now. Then more in a few months. Then more when the next issue appears. You can eventually spend as much as a rebuild while still owning the same underlying system.
The opposite waste is just as real. Rebuilding a workable website because someone dislikes the font is money that would have done more elsewhere.
For reference, our rebuilds start at 30,000 THB. Repair work is quoted, either as a fixed price for a defined cleanup or as a project when content, structure and search visibility all need attention.
The point of a review is to tell you which of those you are actually looking at.
When the website is not the problem
Worth saying, because sometimes the honest answer is that a rebuild will not help you.
Nobody is finding it. Then the problem is visibility, and design does not create traffic. Look at search, Google Business, paid acquisition or market demand first.
Enquiries arrive but few become sales. Look beyond the website as well. Pricing, lead quality, response speed, follow up, availability and the offer itself may all be involved.
There is almost no search demand. Ranking first for something nobody searches will not rescue a business. You need a different channel, not a different website.
The Google Business Profile has been neglected. For an eligible local business, the profile may be worth checking before spending money on a serviceable website.
The business itself is not defined yet. If nobody has decided what is being sold, to whom, at what price, and which services matter, a redesign is premature. You risk paying for a polished site built around an offer that changes shortly afterwards.
What we would do first, in your position
Open Search Console and look at the last six months. Then ask three questions.
Is anything ranking? If yes, you have assets and they need protecting through whatever you do next.
Does every important service have its own page? If no useful page exists for an important service, that is a structural problem worth addressing.
Can the site be changed without a fight? If every small edit needs a developer, the platform is costing you money every month.
If you want a straight answer rather than a quote for a rebuild you may not need, that is what a paid review is for. Sometimes the conclusion is fix it. Sometimes it is rebuild. Occasionally it is that the site is fine and the problem is somewhere else, and we will tell you that too.
The 15 minute call beforehand is free.
