Rebuild or Repair? How to Tell What Your Cayman Website Actually Needs

Someone has told you that you need a new website. Maybe it was a designer who looked at it for thirty seconds at a Chamber mixer. Maybe it was a cold email from overseas. Maybe it was your niece. And you genuinely cannot tell whether they are right, because the only person who could tell you is the same person trying to sell you the rebuild.

That is an awkward position to be in, and it is the reason a lot of businesses in Cayman either rebuild a site that did not need it, or nurse a site that has been dead for two years. This article is a way to work out which situation you are in, on your own, before you talk to anybody.

A dated site and a broken site are not the same problem

This is the distinction that saves people the most trouble, so it goes first.

A dated site is one that looks like it was designed a while ago. Rounded buttons that went out of style, a stock photo of a handshake, a slideshow at the top that nobody scrolls past. It is an aesthetic problem. It might be costing you enquiries, because people do judge, but it is not on fire. You can live with it for another year and nothing bad happens.

A broken site is one where the machinery underneath has failed. Nobody can log in. The software has not been patched since the last hurricane season. Your opening hours have been wrong since Boxing Day and you cannot change them. Google is showing a warning next to your name. This is not an aesthetic problem, and it does get worse on its own.

Plenty of ugly sites are perfectly healthy. Plenty of handsome sites are quietly rotting. The two conditions have almost nothing to do with each other, and only one of them is urgent. If someone tells you your site “looks tired” and jumps straight to a rebuild, they have diagnosed the one that does not matter as much.

Run this ten-minute diagnostic before you talk to anybody

You need your phone and, for one step, a second person. No tools, no logins to buy, no developer.

1. Open your site on your phone, on mobile data, with the office wifi turned off. Count the seconds until you can actually read something. Google’s own Core Web Vitals guidance treats 2.5 seconds as the line for the main content appearing. If you have time to look away and look back, you have your answer. Test it the way a visitor on roaming data would experience it, not the way you experience it on the office fibre.
2. Check your opening hours in three places. Your website, your Google Business Profile, your Instagram bio. Do all three agree? Do they agree about public holidays? If you closed early for a storm or changed your Sunday hours, did the website ever find out?
3. Try to change one word yourself. Pick something harmless — a phone number, a line of text on the about page. Time yourself. Note whether you found it, whether you were afraid to press save, and whether anything else moved when you did.
4. Write down who holds the keys. Three separate things: the domain name registration, the hosting account, the website admin login. Name a person for each. “The guy who built it” is not a name if you cannot reach him.
5. Open your menu or catalogue the way a customer would. On the phone. Is it a PDF that downloads? A photo of a printed menu? Can you select the text with your finger, or is it just a picture of words?
6. Look at the address bar, then search your own business name. Is there a padlock, or does it say “Not secure”? In the search results, is there anything like “This site may be hacked” under your listing? Do any results point to pages you did not create?
7. Hand your phone to someone who has never used your site. Ask them to find your phone number, or book, or order. Do not help them. Just watch. Ten seconds of watching someone fail tells you more than any report.

Keep your seven answers. The next two sections sort them.

Symptoms that are repairs, not rebuilds

Every one of these can be fixed on the site you already own, without touching the design, without changing your address on the web, and without losing anything.

• Slow because of images. The most common cause of a slow small-business site is photographs uploaded straight off a phone or a camera at full size. A hero image meant to be a few hundred kilobytes is often several megabytes. Resizing and converting those images changes nothing about how the site looks and a great deal about how it feels on cellular data. This is an afternoon, not a project.
• No structured data. Structured data is a block of machine-readable information in the page that states your name, address, hours, phone number and, for a restaurant, your menu. It is invisible to humans and it is how search engines and AI assistants read your details without guessing. Adding it does not require rebuilding anything. It is code added to the pages you already have.
• Your menu or catalogue is trapped in a PDF or a JPEG. A PDF is a picture of a document. Software can sometimes extract text from it, often badly, and a photo of a printed menu it usually cannot read at all. If your dishes, services or stock only exist inside a file, they are effectively invisible to anything that is not a human squinting at a phone. Moving that content into real web pages is content work, not construction. On 26 August 2026, searching “why can’t AI read my menu” returned a Google AI Overview that used our own two-second test and listed toctoc.ky as a source alongside Apple — worth noting only because AI Overviews vary by phrasing, location and date, and that same search may not produce the same result for you.
• Wrong or inconsistent hours. Fixable in minutes, assuming you can log in. If you cannot log in, that is a different symptom and it belongs in the next section.
• Nobody ever tested it on a phone. Text overflowing, a button you cannot press with a thumb, a form that will not scroll. These are usually a handful of styling fixes, not a foundation problem.
• The words are out of date. You stopped doing the thing on the homepage two years ago. That is a writing job.

Note what all of these have in common: the site can still be worked on. Someone has access, the software still runs, changes stick. That is the definition of repairable.

Symptoms that mean the foundation is gone

These are different in kind. They are not things you fix on the site; they are reasons the site can no longer be trusted to hold anything you build on it.

• Nobody has the login. Not the admin password, not the hosting, and in the worst version not the domain — it sits in the personal account of a developer who left the island, or an ex-staff member’s email. Everything else on this list can be worked around. This one cannot. Before anything else, find out whether you actually control your own domain name.
• The theme or plugins are abandoned. Website software gets security patches the same way your phone does. If the theme was bought once in 2019 from a marketplace and the seller has since vanished, or the plugins show update notices that nobody has clicked in years, the site is unpatched. Unpatched sites get broken into eventually, and the break-in is usually invisible to you and very visible to Google.
• Every edit breaks something else. This is the page builder problem. Change a heading, and the spacing collapses on mobile. Fix the spacing, and the contact form disappears. If your site has reached the stage where routine edits require undoing yesterday’s edits, keeping it going takes more out of you every month. We build our client sites as custom WordPress themes without page builders — around 24 live sites now — specifically so that a text change is a text change.
• You cannot change a word without hiring someone. A site you cannot edit is a site that will drift out of date, guaranteed, because nobody schedules a developer to correct Sunday hours.
• Security warnings. Browser warnings, an expired certificate nobody can renew because nobody has the hosting login, “this site may be hacked” in the search results, pages in another language you did not create, or a host that has suspended the account. Treat these as urgent regardless of how the site looks.
• No backups and no way to make one. If nobody can produce a copy of the site, then any repair is being performed without a safety net.

One item from this list does not automatically mean rebuild — a lost login can sometimes be recovered through the registrar or the host, and that is the first thing to try. Three or four items from this list, together, usually does.

The grey area, and how to think about it

Most sites are not clean cases. A typical one: it looks dated, it is slow because of images, the menu is a PDF, and it was built with a page builder that still works but that you personally will not touch. Nothing here is fatal. Nothing here is fine either.

The question that resolves it is not “is this site good?” It is: can the next two years of changes be made on this foundation without fighting it? If yes, repair, and put your effort into the things that actually change outcomes — real content, correct hours, structured data, photographs of your own place instead of stock.

If no — if every small change needs a specialist, or a break-in is one unpatched plugin away — then a rebuild is not vanity. It is maintenance you deferred, arriving all at once.

There is a third case worth naming: the foundation is sound and the design is genuinely hurting you. A restaurant whose site looks abandoned reads as closed, and a visitor deciding between two places will pick the one that looks open. That is a redesign — new appearance on the existing structure — and it is not the same undertaking as a rebuild.

Questions to ask anyone who recommends a rebuild

An agency that recommends replacing your site before looking inside it has not diagnosed anything. Rebuilds are the easiest thing for an agency to sell and the easiest thing to specify. That does not make them wrong, but it does mean the recommendation should survive some questions.

• What did you actually look at? The public pages only, or the admin, the plugin list, the hosting?
• Which of my problems cannot be fixed on the current site, and why? A straight answer sounds like “the theme is abandoned and the child theme was edited directly, so updating it would wipe the changes.” A vague answer sounds like “it’s outdated.”
• What happens to my existing page addresses? If your pages have been indexed by Google for years and the new site puts them at new addresses with no redirects, that history is discarded. Ask for the redirect plan in writing. This is the most common quiet damage done by a rebuild.
• Who owns the domain, the hosting and the logins when this is finished? The answer should be you, in your own accounts, with your own email on them.
• Can I edit my own hours, text and details afterwards, without calling you? If the answer is no, you are buying the same trap in a newer style.

What nobody can tell you from the outside

We should be straight about the limits of this. From the public side of a website, anyone can see that it is slow, that the menu is a PDF, that there is no structured data and that it behaves badly on a phone. Nobody can see from outside whether the theme is abandoned, whether the plugins are patched, whether backups exist, or whether the last developer edited files in a way that makes updating impossible. Those four things decide the rebuild question, and all four live behind a login.

So if someone diagnoses your site without asking for access, they are guessing. Including us. Including a checker tool — ours or anyone else’s. A tool can tell you what a visitor experiences. It cannot tell you what the plumbing looks like.

Questions we get asked

My site looks old-fashioned. Isn’t that reason enough to replace it?

Usually not on its own. Looking dated and being broken are separate conditions, and a fresh appearance on a rotten foundation buys you a nicer-looking version of the same problem. The exception is when the design is actively costing you — a site that looks abandoned makes people assume you are closed. Even then, a restyle on the existing structure is often enough.

Everyone tells me WordPress is insecure. Should I move to something else?

The risk in practice is rarely WordPress itself. It is abandoned plugins, marketplace themes whose sellers have disappeared, and nobody applying updates. Moving to a different platform without changing that habit relocates the problem. We build custom themes with very few plugins because there is less to go wrong and less to patch, but any platform that nobody maintains ends up in the same place.

Do I need structured data, llms.txt and all the AI things?

Structured data earns its keep if you are a business with a physical location, opening hours and things you sell — it is how machines read your details without inferring them. The AI-specific side is less settled, and we say so: no AI company has publicly committed to reading llms.txt, so anyone selling it as a guarantee is overselling. What we can say is that in a session recorded on 21 August 2026, ChatGPT named two of our clients, Uncle Liu and Coconut Room, when asked where to eat on Seven Mile Beach. AI answers are non-deterministic and change with phrasing, location and date, so treat that as one recorded session and not a promise. We have influenced AI-generated local recommendations; nobody can promise you a position in them.

All my business comes from Instagram and word of mouth. Do I need to do anything at all?

You probably do not need a rebuild, and possibly not a redesign either. But keep two things true: your site should load, and your hours and phone number should be correct everywhere. Those details are what Google, Apple Maps and AI assistants read when somebody asks about you, and they read them whether or not you think of your site as important.

Can you tell me over the phone whether I need a rebuild?

No, and we would rather say so. We can tell you in five minutes what a visitor sees. Deciding between repair and rebuild needs a look at the admin, the plugin list and the hosting. If a diagnosis arrives without anyone asking for access, it is a sales position, not an assessment.

If you want a starting point, run your own address through our free checker at toctoc.ky/seo-checker. It scores what a visitor and a search engine can see — speed, structured data, AI visibility — and it drafts an llms.txt file for you. It will not tell you whether your foundation is sound, because nothing from the outside can. But it will tell you which of the repairable symptoms you actually have, and that is usually enough to know whether the person recommending a rebuild has looked at your site or just at your industry.

And if the diagnosis comes back saying the foundation really has gone, that is the work we do: website design and development in Grand Cayman, built as custom themes rather than page builders, and custom web development for Cayman businesses when the site has to do more than sit there — a booking flow, a catalogue, a point of sale that talks to the website. From George Town, for businesses on this island.