Rebuild or repair: how we decide what to do with an existing site

761 VenturesAugust 7, 20264 min readDelray Beach, FL

An owner with an existing website usually asks the same question first: do we have to start over? Often not. The answer depends on a handful of things we can check in an afternoon.

Short answer

We decide between repairing a site and rebuilding it by checking whether we can edit the pages, control the redirects, add schema, fix the speed, and get out of the platform later. If the platform allows those, repair usually wins and the money goes into content. If the platform blocks them, a rebuild pays for itself, because every fix on the old site is temporary.

The questions we ask first

A rebuild is disruptive, and a site that has been online for years has earned standing with Google that a careless rebuild throws away. So the default is to repair. We only move to a rebuild when the platform itself is the problem. These are the checks:

Content versus plumbing

The second thing we do is sort the site's problems into two piles. Content problems: thin pages, a single Services page, no area pages, no questions and answers, stock photos, no posts. Plumbing problems: slow hosting, missing schema, broken redirects, two addresses for every page, no sitemap, a locked platform.

If the pile is mostly content, repair wins. The platform is fine, the site just does not say enough. The money goes into writing service pages, area pages and posts, and into photographing real work. That is where the visitors come from anyway.

If the pile is mostly plumbing and the platform allows the fixes, repair still wins. A few days of work on images, scripts, schema and redirects, and the site is sound.

If the pile is mostly plumbing and the platform does not allow the fixes, that is when a rebuild pays for itself. Every repair on a locked platform is temporary. You pay for it now and again at the rebuild. Better to do the rebuild once.

When repair wins

The repair cases usually look alike. A site on a common platform where pages are editable, redirects work, and schema can be added. It is slow because of photos, and it has no pages for its services or its towns. We do not rebuild that. We fix the images, add the schema, write the pages, and start the posts. The site stays where it is and starts doing its job.

When a rebuild pays for itself

The rebuild cases look different. A site on a builder that cannot add schema, cannot redirect, and loads a thick layer of code on every page. Or a site where the only person who could edit it has left, and the login went with them. Or a site on a platform that is being discontinued. In each case, the fixes the site needs are fixes the platform will not allow, so the choice is between a rebuild now and a rebuild later with wasted repair money in between.

When we do rebuild, the old site's standing comes with it. Every old address is mapped to a new one and forwarded. The pages that were ranking keep their content and their headings. The analytics history stays in the client's account because the account was always theirs. A rebuild done this way is a renovation, not a demolition.

How the conversation usually ends

We send the owner the list of checks, with an answer next to each, and the two piles. Then we say which way we lean and why. Most of the time the owner already suspected the answer. What they wanted was to see the reasoning laid out so the decision was theirs rather than ours.

This is the first conversation we have with every business that comes to us with a site already standing, whether it belongs to a painter or a permit company.

Questions people ask

Does a rebuild mean we lose our Google ranking?

Not if it is done carefully. Every old page address is mapped to a new one and forwarded, the pages that were ranking keep their content and headings, and the analytics history stays in your account. A rebuild done this way keeps the standing the old site earned.

How can we tell if our platform is locked?

Try to add a redirect, add schema to a service page, and export the site's content and code. If any of those is impossible or costs extra, the platform is working against you. Those are the checks that usually decide between repair and rebuild.

When is repair the right answer?

When the platform allows the fixes and the site's real problem is that it does not say enough. Thin pages, no area pages, no questions and answers, and stock photos are content problems, and the money is better spent on content than on moving the site somewhere new.

Share
Written by the 761 Ventures team

Operators in Delray Beach, Florida who build websites, CRMs, AI assistants and automation for businesses like yours, then write down what worked.

Want this done for your business?

Two minute intake. A real person reads every one and replies within a business day.

Start a project
OlderWhat your Google Business Profile and your website need to agree onNewerYour domain, your email, your analytics: what you should own and why

Keep reading