When to redesign a website, and when not to
Most redesigns are commissioned because a site “looks old”. That is a real cost — people judge quickly — but it is rarely the biggest one, and a rebuild is an expensive way to fix a problem that might be cheaper to solve directly.
Here is how to tell which situation you are in. Prices and scope for the work itself are on the web design page.
Four reasons a rebuild is justified
The structure is wrong for what you now sell. You have added three services since the site was built and they are all crammed into one page. No amount of restyling fixes a structure that has no room for the business.
It cannot be edited. If changing a phone number requires a developer, you are paying rent on your own website, and the site will drift out of date because updating it is a task rather than a moment.
It is not usable on a phone. Not “it shrinks” — usable. If most of your traffic is mobile and the mobile experience is a compromise, the site is failing for the majority of the people who see it.
The platform is a liability. Unsupported, unpatched, or dependent on plugins that stopped being maintained. This one has a deadline attached whether you set it or not.
Four reasons to fix instead
It is slow. Compressing images, removing unused scripts and fixing caching often transforms a site without touching the design — see what a slow website costs you.
Your Google profile is unverified or thin. For a local business this frequently produces more enquiries than the website. It costs nothing and takes an afternoon: getting found on Google Maps in Riyadh.
Key pages have almost nothing on them. A service page with two paragraphs will not rank or convert regardless of how it looks. Writing them is cheaper than rebuilding around them.
Only the homepage is dated. Sometimes that really is all it is, and one page is a fraction of the cost of a site.
The expensive mistake: losing your URLs
This is the part that actually costs money, and it is invisible until traffic drops six weeks after launch.
Every page that has ever ranked or been linked to has an address. Change the addresses without redirecting the old ones and you discard that history. Google finds a 404 where a ranking page used to be, and the pages you rebuilt start again from nothing.
Before any rebuild:
- Export every existing URL, from your analytics and from Search Console
- Map each one to its equivalent on the new site
- Redirect them all, with a 301, on launch day — not later
- Check them after launch, because the ones that were missed do not announce themselves
A redirect pointing at a page that does not exist is worse than no redirect at all: the crawler follows the hop and finds nothing, and the old URL is spent for nothing.
Do it in stages if you can
Rebuilding the highest-value pages first — usually the homepage and your top two service pages — lets you see the effect on real enquiries before committing the rest of the budget.
It also avoids the launch where six things change at once and, when the numbers move, nobody can say which change did it.
How to decide
Write down the specific job the site is failing at, in one sentence, with a number attached if you have one. If you cannot, the honest answer is usually that the site needs content and speed work rather than a rebuild — and what a website costs sets out what each of those is worth paying for.