Techkeeping

Home / Articles /

New Website or Fix the One You Have: How to Tell

The question usually arrives late at night, after a customer could not find the booking page, or the site comes up on your own phone looking far older than the business. Rebuilding feels like the honest answer. It is also the expensive one, and much of the time it is the wrong one.

We run websites for small businesses on Oahu and on the East Coast. Some we repaired in place. Some we rebuilt from the ground up. The difference was never how old the site looked. It was whether the platform underneath could still do what the business needed.

Most website problems are fixes

Here is the split we see in practice:

The problem Fix or rebuild
Titles Google cuts at about 60 characters Fix
Pages with no main heading Fix
No description, so Google picks random text to show Fix
Images with no alt text Fix
No analytics counting visitors Fix
No business markup telling Google what and where you are Fix
Slow pages from oversized images Usually a fix
You cannot change a page without a developer Rebuild
The platform cannot do what the operation needs Rebuild
The site undersells what you actually sell Often a rebuild

Everything in the top half lives in the pages, not the platform. It can be repaired on the site you already have, usually in days, while the site stays up and the address stays the same.

A site that read like a rebuild and was not

A Honolulu office technology dealer came to us with a WordPress site built years earlier by an agency that knew the industry. Of its 120 pages, 111 had no main heading, 45 page titles ran longer than Google displays, and no analytics was counting visitors.

On paper that reads like a site beyond saving. It was not. Within five days the header was repaired on every page, the homepage went from four main headings to one, and the first business markup went in. The site never moved.

That is the pattern with most sites we check: the faults are in the pages, and pages can be fixed. An old site with good bones costs far less to repair than to replace.

When a rebuild is the right call

A rebuild makes sense when the problem is the platform, not the pages. We rebuilt two charter sites, and each one earned it a different way.

An Oahu fishing charter had a Squarespace site that was never set up properly and made a premium trip look ordinary. No amount of title fixes changes that. The site had to show the boat, the water, and the trip well enough to justify the price, so we rebuilt it around original photography and video.

A charter on the East Coast, one boat for twenty-five years, sat on a booking platform that could not reschedule a trip, issue a refund, or resend a confirmation without someone logging in to handle it by hand. When the platform cannot do what the operation needs, you are no longer fixing pages. That site was rebuilt too, with booking software shaped around one boat.

So the rule is simple. Fix when the pages are wrong. Rebuild when the platform blocks the business.

The one thing a rebuild must not lose

Every page on your site has an address, and Google has a history with each one: which searches it has shown the page for, and which other sites link to it. That history is the most valuable thing an old website owns, and a careless rebuild throws it away by changing every address.

Google's own site move documentation says that when addresses change, it can take a few weeks or more for a medium-sized site before Google starts showing the new ones. Its redirects documentation says a permanent redirect passes along the value the old address earned, and Google advises leaving redirects in place for at least a year.

The better answer is to not change the addresses at all. Both charter rebuilds went live with the old page addresses intact, so Google never had to relearn the site. Over the twelve months that followed, the Oahu charter's appearances in Google results grew to 5.1 times the level from when we started, and it now sits above a booking platform that once sat above it.

If a builder quotes you a rebuild, ask about the old addresses before you ask about price. You want either the same addresses on the new site or a written redirect map: every old address, and where it will point. It is the least visible part of a website design and migration, and the part a cheap rebuild skips.

How to decide tonight

Open your site on your phone and try to do what a customer does: find the price, find the phone number, book or ask. Then look at the top half of the table above. Titles, headings, descriptions, alt text, markup, and analytics can all be read from outside in about ten seconds, no login needed.

Three questions settle most cases. Can you update a page yourself today? Does the platform handle what the business needs, whether that is deposits, reminders, or a shop? Does the site present the work at the level you charge for it? Three yeses mean fix it. A no on either of the last two is the strongest case for a rebuild.

One warning either way: a rebuild does not excuse the upkeep. The office dealer's site had a professional build behind it and still reached us with 111 pages missing a main heading. A new site that nobody watches ends up exactly where the old one is now.

Answer the three questions for your own site. Then run the free homepage check and see how much of what it finds already sits in the fix column.

Back to articles