Keep + optimize
The foundation works. Improve what customers and Google already respond to.
Free 5-minute decision tree
Answer up to 10 yes-or-no questions. Get a direct verdict: keep it, refresh the copy, tune up the technical foundation, rebuild it, or start from zero.
Diagnose before you redesign
A quiet phone does not automatically mean you need a new website. The problem may happen before anyone reaches the site: weak map visibility, the wrong Google Business Profile category, too few reviews, or a service page that does not rank. A rebuild cannot repair demand that never arrives.
But the opposite is also true. Sending more traffic to a slow, confusing, or untrustworthy site wastes the attention you already earned. A local customer usually wants fast answers: Do you provide the service I need? Do you work in my area? Can I trust you? What should I do next? If the site hides those answers, the design is not merely old. It is creating sales friction.
Start with ownership. If an old agency controls the domain, login, hosting, or analytics, recover those assets before paying for cosmetic changes. Then test the site on a real phone, preferably away from fast office Wi-Fi. Check whether the main page loads quickly, the phone number works, the form submits, and the service information is readable without pinching or hunting.
Next, separate copy problems from technical problems. A healthy site with vague headlines and no service-area proof often needs a focused conversion and content refresh instead of demolition. A clear, credible site that loads slowly or disappears from Google may need a technical tune-up. When weak ownership, broken technology, embarrassing design, stale information, and zero leads pile up together, a rebuild is usually the more honest use of money.
This decision tree recommends the smallest fix that matches the evidence. It does not protect the feelings of an old website, and it does not push every visitor into a new build. Use the verdict as a scope: fix the listed issues, measure calls and forms, and only move to a larger project when the current foundation cannot support the work.
Before any rebuild, save the useful parts of the current site. Record the URLs that receive traffic, pages that rank, forms that produce leads, customer reviews, photos, analytics history, and links from other websites. A careless redesign can erase working assets while making the home page prettier. The new version should preserve earned value, redirect replaced pages, and improve a short list of measurable problems.
Judge the result after launch by qualified calls, forms, booked work, and the searches that produce them. Page views and design compliments are supporting signals, not the final outcome.
Website rebuild decision tree
Five honest outcomes
A rebuild is one possible answer, not the default. Every verdict includes three specific next steps and a relevant destination.
The foundation works. Improve what customers and Google already respond to.
The site functions, but the message is not turning attention into calls.
The offer is credible, but speed, indexing, access, or basic function is holding it back.
Too many structural failures have accumulated for another patch to be responsible.
No site yet. Build the minimum useful foundation in the right order.
Website Sprint
Strategy, responsive build, local and answer-ready copy, technical SEO, schema, analytics, sitemap, and launch.
Want a human second opinion?
Send the URL. I’ll identify the first three priorities and the smallest sensible scope.