A redesign changes how your website looks. A rebuild changes what it is made of. Agencies rarely explain the difference, partly because “redesign” is the easier sale — and a redesign on a broken foundation produces a better-looking site with all the same problems underneath.
Here are seven signs the problem is structural rather than visual, a ten-minute self-check you can run without buying anything, and an honest look at when living with what you have is the right answer.
Redesign or rebuild: the difference
| Redesign | Rebuild | |
|---|---|---|
| What changes | Layout, colours, typography, imagery | Code, data structure, CMS, hosting |
| What stays | Underlying code and structure | Content and, usually, URLs |
| Typical duration | 2–4 weeks | 4–10 weeks |
| Fixes appearance | Yes | Yes |
| Fixes speed | Rarely | Usually |
| Fixes “we can’t do that” | No | Yes |
| Fixes security exposure | No | Usually |
The test is simple: if your complaints are about how the site looks, redesign. If they are about what it does, how fast it is, or what you cannot change, rebuild.
The seven signs
1. Pages take more than three seconds to load
Test on a phone on mobile data, not on office wifi. If pages take several seconds, that is costing you visitors and rankings.
What makes it structural: if the delay is in server response time rather than images or scripts, no amount of visual redesign fixes it. Look at time to first byte specifically. Under 600 milliseconds is healthy; several seconds means something is wrong beneath the surface — hosting, database, plugin bloat, or occasionally something malicious.
2. You cannot make changes without a developer
If adding a page, updating a price or publishing a post requires paying someone, your CMS is not configured for the people who use it. That friction compounds: updates get postponed, content goes stale, and the site slowly stops reflecting the business.
This is a structural problem. The fix is content modelling — fields shaped around your actual content — not a new colour scheme.
3. It breaks on mobile in ways that are not just cosmetic
Not “it looks a bit cramped” but forms that cannot be submitted, navigation that cannot be opened, tables running off screen, buttons too small to hit. Most of your visitors are on phones. If core functions fail there, the site is not doing its job.
4. Nothing you publish appears in search
If pages have been live for months and still do not appear, something structural is likely wrong: pages blocked from indexing, near-duplicate templates Google declines to index separately, or a site so slow it is crawled rarely.
Diagnose before rebuilding — sometimes it is a single setting. We cover the full sequence in why isn’t my website showing on Google.
5. It has been hacked, or you do not know that it hasn’t
A compromised site is not fixed by a redesign. If your site has been compromised, or runs on an abandoned theme and plugins years out of date, you are carrying known vulnerabilities.
Worth knowing: modern SEO-spam malware deliberately hides from logged-in administrators. Everything looks fine while you browse your own site, while search engines are shown injected links or redirects. Unexplained slowness is often the only visible symptom.
6. Adding anything new is disproportionately expensive
Every quote for a small change comes back surprisingly high, or the answer is “the theme cannot do that.” This is what technical debt feels like from the client side. When the cost of change is consistently out of proportion to the size of the change, the foundation is the problem.
7. The site no longer matches the business
Before assuming this needs a rebuild, check whether it is really a copy problem rather than a structural one — that is a far cheaper fix.
You have changed what you sell, who you sell to, or how you sell it — and the site describes the business you were three years ago. If the information architecture is wrong rather than the styling, restructuring is a rebuild, because the content model has to change.
Check your own site in ten minutes
- Speed: run your homepage through PageSpeed Insights on mobile. Note the score and the server response time.
- Indexing: search
site:yourdomain.com. Roughly the number of pages you expect? - Mobile: on your phone, complete your main conversion action — submit the enquiry form, or buy something.
- Editing: try changing one sentence yourself. How long did it take?
- Updates: in WordPress, check Dashboard → Updates. Anything years out of date?
- Links: click through your main navigation. Anything broken or empty?
Two or more failures suggests a rebuild. One failure is usually a fixable problem, not a reason to start over.
What it costs to rebuild versus living with it
A rebuild for a typical business website costs in the same range as a new build — roughly NPR 60,000 to 150,000 depending on scope, as broken down in what a website costs in Nepal.
The cost of not rebuilding is harder to see but real: enquiries lost to a slow or broken mobile experience, staff time spent working around a CMS nobody can use, developer invoices for changes that should be trivial, and the risk of a compromise on unmaintained software.
A rough way to think about it: if a slow site is costing you even one enquiry a month, and your average project is worth more than a few thousand rupees, the arithmetic gets clear quickly.
When to leave it alone
Rebuilding is not always right.
If the site works and you simply dislike it, a redesign is cheaper and sufficient.
If it has one specific problem, fix that problem. A slow site caused by unoptimised images needs image optimisation, not a rebuild.
If your business is about to change significantly, wait. Rebuilding now and restructuring in six months means paying twice.
If you cannot maintain what you build, a new site will decay exactly as the current one did. Budget for maintenance as part of the decision, not as an afterthought — what that actually covers is worth reading first.
Frequently asked questions
How often should a website be rebuilt?
There is no schedule. Well-built and maintained sites last many years; poorly-built ones need replacing in two or three. Rebuild when specific problems justify it, not because of a date.
Will rebuilding hurt my search rankings?
Only if done carelessly. Map every old URL to its new equivalent with 301 redirects, keep your content, and preserve your page structure where it already works. Done properly, rankings usually improve because speed and structure improve. Done without redirects, you can lose years of accumulated authority overnight.
Can I keep my design and rebuild underneath?
Yes, and it is a common approach. The visual design is reproduced on a new, cleaner codebase. Visitors see no change; you get speed, maintainability and the ability to extend it. Useful when the brand is fine and the foundation is not.
How do I know if my slow site is a hosting problem or a code problem?
Look at time to first byte versus total load time. Slow TTFB with fast rendering points at the server or backend — hosting, database, a heavy plugin, or malicious code. Fast TTFB with slow rendering points at the front end — images, scripts, fonts.
What should I ask an agency before agreeing to a rebuild?
Ask them to show you the diagnosis first. Which specific problems are they solving, and how did they determine that? An agency recommending a rebuild without auditing what exists is selling rather than advising.
Can I rebuild in stages?
Sometimes. Splitting by section — rebuilding the blog first, then the main site — works when the parts are genuinely separable. It costs a little more overall and spreads the expense, which for many businesses is the right trade.
Not sure which you need?
The honest answer usually comes out of an audit rather than a conversation. Run the ten-minute check above; if it points at structural problems, get a second opinion before committing to either path.
Our SEO packages include a free technical audit that covers speed, indexing and structure, and will tell you plainly which category you are in. If you already know it is a rebuild, custom website development sets out how we scope one — or just describe the problem and we will tell you whether it warrants starting over.
