Should I rebuild my website or just fix it?
“The website needs redoing” is one of the more expensive sentences in small business, partly because it is often true and frequently not.
These are the tests we use, and you can run most of them yourself before speaking to anyone.
Test one: can you edit it?
Open the site and try to change a paragraph and add a page.
If you can do both without a developer, the site is maintainable and probably worth keeping. If every change requires paying someone, the ongoing cost compounds indefinitely and eventually exceeds a rebuild. That is the strongest single argument for replacement.
Test two: is the content actually in the page?
Open any service page, view the page source, and search it for a sentence you can see on screen.
If the text is there, search engines and AI crawlers receive it in the initial response, and the site is structurally sound in the way that matters most. If the source is mostly script tags and your content is absent, the page is assembled in the browser.
That was the situation with the previous version of this site: roughly 1.6KB of HTML, no sitemap, everything rendered client-side. It is a genuine reason to rebuild, because it cannot be tuned away.
Test three: where does the slowness come from?
Run the site through a performance tool and look at what is heavy.
If the answer is oversized images, several typefaces, and a stack of third-party scripts, that is a repair. Those are the usual causes and they are fixable in place for a fraction of a rebuild.
If the platform itself generates enormous markup on every page regardless of content — some page builders and heavy themes do — then the ceiling is structural, and Google’s thresholds may not be reachable without replacing it.
Test four: can the structure hold the pages you need?
Write down every service you want to be found for. Then check whether the site could hold a proper page for each, organised sensibly, without fighting the navigation.
If yes, you have a content problem rather than a website problem, and content is cheaper.
If the platform forces everything into one page, or the navigation cannot express a hierarchy, the structural limit is real.
Test five: does it work on a phone in bad conditions?
Load the site on a phone, on mobile data, outdoors.
If the phone number is not immediately tappable, if text is unreadable, if buttons are too small for a thumb, those are usually fixable. If the whole layout collapses, it may be older than its appearance suggests.
Scoring it
Repair when the site is editable, the content is in the page source, the slowness traces to assets rather than the platform, and the structure can hold the pages you need. That covers most sites, and the money is better spent on content and rankings.
Replace when you cannot edit it, when content is rendered client-side, when the platform prevents acceptable performance, or when the structure cannot support a page per service. That is a rebuild, and if the current site has rankings worth protecting it is specifically a migration rather than a fresh start.
The decision nobody makes but should
There is a third option that gets overlooked: change nothing about the website and spend the budget on visibility instead.
If your site is adequate — editable, indexed, reasonably fast, with a visible phone number — the constraint on your business is probably not the website. Rebuilding an adequate site is a comfortable way to spend a marketing budget without changing anything about how many people find you.
Call 734-747-3922 or request a free audit, and we will run these tests on your site and tell you which category it falls into.
Back to the service this covers: Web Design from the start.