A rebuild needs a reason
An older website can still explain a business well. A new website can still leave buyers confused. The age of the design tells you very little about the information available on it.
Before approving a rebuild, ask your agency to show the specific limitation. Can you edit titles and page copy? Add a useful page? Link to it from the menu? Fix redirects and indexing settings? If those jobs are straightforward, improving the current site is a sensible first move.
We would rather improve five useful pages than launch fifty vague ones. The work should earn its cost through clearer information and a better buying experience.
Make one service page useful
Open your main service page on your phone. Imagine a prospect reading it between meetings, with one thumb and little patience.
Can they find what you do, whether it fits their situation and how to contact you? Use that as your first review. Below is an illustrative rewrite for an accounting firm, not a claim about a District10 client.
“Your trusted partner for business success.”
“Monthly bookkeeping for Singapore ecommerce sellers. We reconcile marketplace payouts and prepare management accounts.”
The second version gives a buyer something to assess. Follow it with the practical details: what is included, what you need from the customer, how the work happens and what affects the quote.
Add a real example where you have permission to publish it. Show the problem, the work and the observed outcome. Leave unsupported percentages out.
Check access before adding more content
Your developer should check the important pages for accidental indexing blocks, broken links and content hidden behind a login. Ask for findings at page level, with a proposed fix for each issue.
Google’s AI search guidance says supporting pages must be indexed and eligible for a search snippet. It also says there is no special AI markup or extra machine-readable file required for these features. Read Google’s requirements.
For ChatGPT search, OpenAI identifies OAI-SearchBot as its search crawler. Its controls are separate from GPTBot, which concerns model training. Allowing a training crawler is therefore a different decision from allowing search access. See OpenAI’s crawler documentation.
Access is a prerequisite to check, not proof that a particular page will be recommended. Keep a record of the changes so later tests have a useful baseline.
Keep the business details consistent
Check the company name, services, operating locations and contact details across your key pages. Remove retired offers and correct outdated team information. If you serve a market remotely, explain that instead of implying you have a local office.
Connect related information. A service page can link to a relevant project example; that example can link back to the service. The reader should be able to follow the relationship without returning to Google.
Use our readiness checklist to turn unknowns into a short list of checks for your team. Complete the checks before treating the answers as confirmed.
When starting fresh makes sense
A new build becomes reasonable when the current platform prevents routine improvements, depends on unsupported components, or is costly to maintain. A confusing page structure may also need a substantial redesign.
If you rebuild, keep a list of existing URLs and their replacements. Plan redirects, preserve useful content and test important forms on a phone before launch. A better-looking homepage is a poor trade if customers lose the pages they were using.
Send us your current URL on WhatsApp. We can review the work it needs and whether the existing site can support it.