Rebuilding is justified when the foundation is the problem — the platform, the structure, the ownership situation, or the technical condition underneath. If the foundation still works, a redesign or a handful of targeted improvements is usually the better spend. That’s the whole decision, and it’s worth resisting anyone whose answer is always “start over,” including us.
There are four honest options, not two:
Keep and improve. The structure stays; specific weaknesses get fixed — clearer headline, better photos, a working form, corrected information. Cheapest per fix, fastest to ship.
Redesign. New appearance and layout on the same platform and largely the same content. What visitors see changes; what’s underneath doesn’t.
Migrate. Move the site to a different platform while keeping its content — because the current platform, not the current design, is the constraint.
Rebuild. New foundation, new structure, new build — typically keeping only the content worth carrying over.
The foundation questions
Answer these before choosing. They separate presentation problems (cheap to fix) from foundation problems (worth a rebuild).
Can you actually change it? If routine edits require a developer you can no longer reach, an account you don’t control, or a platform version nobody supports anymore, the site is functionally frozen. A frozen site fails the foundation test no matter how it looks.
Do you own and control it? If the domain, hosting, or files sit in someone else’s account and you can’t get them, you have an ownership problem before you have a design problem — and it changes the plan, because a site you can’t access can’t be incrementally improved, only replaced. What you actually own breaks down how to check.
Does the structure fit the business anymore? A site built when you offered two services, now stretching to cover six, has an architecture problem. Depending on how the site was put together, restructuring inside it can be more labor than rebuilding cleanly — where that’s the case, it’s the most legitimate everyday reason rebuilds win.
Does it fundamentally work on phones? There’s a difference between “the mobile layout needs polish” (improvable) and “this was built before mobile mattered and shrinks a desktop page onto a phone screen” (foundation). The second is sometimes retrofittable and often isn’t — it depends on how the site is built, which is worth establishing before assuming a rebuild.
Is the content still true? Wrong services, dead links, old pricing — that’s not a redesign problem at all; it’s editing, and it’s the cheapest fix on this page. Don’t buy a rebuild to fix sentences.
The website self-audit runs these foundation checks alongside the visitor-facing ones and prioritizes what it finds.
Symptom → usual path
| What’s actually wrong | Usual answer |
|---|---|
| Looks dated, but accurate, editable, fine on phones | Redesign — or less |
| One or two specific failures (form, photos, headline) | Keep and improve |
| Content wrong or stale, everything else works | Edit it — nobody needs hiring |
| Platform limits what you need next (fees, lock-in, missing capability) | Migrate — and check what exports first |
| Can’t edit it, can’t reach who built it, don’t control accounts | Rebuild, and fix ownership in the process |
| Structure no longer matches the business | Rebuild — if restructuring in place would cost more than starting clean |
| Pre-mobile-era foundation | Rebuild — usually, unless it can be practically retrofitted |
Two things the table can’t capture: problems compound — “dated and wrong and awkward on phones” tips toward rebuilding even though each alone wouldn’t; and boredom isn’t a symptom. You see your own site a hundred times more often than any customer does. If it’s accurate, usable, and representative, your restlessness with it is not a business case.
The migration fine print
Two facts to hold before choosing the migrate path. Moving off a hosted builder generally means rebuilding the site’s design regardless — Wix documents that sites can’t be exported to run elsewhere, and Squarespace’s export carries limited content and none of the styling. So “migrate” from a builder is really “rebuild, keeping the words and images.” Budget accordingly.
And any project that changes your page addresses — redesign, migration, or rebuild — carries a manageable detail that’s easy to mishandle: map each old URL to its closest new equivalent and set those up as server-side permanent (301) redirects. Done that way, people following old links still land in the right place, and the signals those pages earned are helped across to the new addresses. Some ranking fluctuation is normal for a period after addresses change, and it typically settles; leaving the redirects out is what turns a routine move into an avoidable loss. It’s standard practice, it’s cheap to do at build time, and it’s one of the specific things to ask any provider about before work starts. If a site currently gets real traffic from search, treat redirects as part of the project’s definition of done.
Sequencing the money
A sensible order when budget is tight: fix falsehoods first (free-to-cheap, immediate), then the worst conversion failure, then decide the structural question with real information. Improvement spending on a sound foundation compounds; improvement spending on a broken foundation is rent. That’s also the argument against dripping money into a frozen site — several rounds of paid patches on something that ultimately gets rebuilt anyway can easily cost more than deciding once.
If you’re not yet sure the site is even the problem, diagnose before spending anything: why your website isn’t getting leads separates visibility problems from conversion problems — a redesign fixes neither of the first kind.
Where TruePoint sits
We build new foundations — that’s the product, and the bias that comes with it is exactly the one this guide warns about, so here’s the counterweight in writing: if your foundation passes the questions above, we’d tell you to keep it. A redesign-scale project on a sound platform, or a short list of targeted fixes, is a better outcome bought from someone else than a rebuild you didn’t need bought from us.
When a rebuild is the answer, ours start from the structure question — what the business sells now, what the site needs to do — with the scope agreed before anything is billed, redirects included when addresses change, and ownership set up correctly from day one. The packages page shows what each scope covers; if you’d rather just describe the state of your current site, the project form takes a few minutes, and “keep what you have” is a real possible answer.