In plain English
A service-business website needs to explain who you help, what you do, where you work, why a prospect should trust you and what to do next. It also needs clear navigation, accessible enquiry routes, reliable mobile performance and measurement. Start with those essentials before adding animation, extra pages or complex integrations.
What must visitors understand first?
A visitor should quickly identify the service, the customer it suits, the area served and the next sensible action. Write this opening from real customer questions, not internal slogans. If project size, appointment model, availability or geographic coverage affects fit, state that early enough to prevent a promising prospect from building the wrong expectation.
Support the opening with specific, checkable information: named services, a plain explanation of the process, genuine business details and proof the business is entitled to publish. Google recommends useful, reliable, people-first content with a clear site purpose. That is a better foundation than generic claims such as quality, passion or excellence that could describe almost any competitor. For South African businesses, keep currency, service areas, trading details and contact channels consistent wherever those facts appear on the site and approved profiles.
Sources for this section: Creating helpful, reliable, people-first content.
Which customer journeys should the site make easy?
Map the common routes before choosing page layouts. A new prospect may want to compare services, confirm whether the business works in Cape Town or Pretoria, understand the engagement, inspect proof, call from a phone or send a considered enquiry. Each route needs an obvious starting point, descriptive links and a destination that answers the promised question.
Keep the main navigation small enough to scan, but do not hide essential destinations for the sake of visual neatness. Semantic navigation and ordinary links with meaningful text work across keyboards, touch devices, assistive technology and search crawlers. Test the route on a narrow screen and with a keyboard, including focus states, menus, contact links and the journey back to related services. If the menu changes at a breakpoint, confirm the same destinations and reading order remain available.
Sources for this section: Building the main navigation for a website, Link best practices for Google.
How should a visitor be able to enquire?
Offer an enquiry method appropriate to the service and how the business actually responds. That may be a short form, a visible phone number, an email link or a booking route with clear conditions. Do not present a channel as instant, staffed or confirmed when it is not. Explain the expected next step and any information a prospect should prepare. Where urgency matters, place a call option prominently while leaving a non-voice alternative for people who cannot use it.
Every form control needs a visible, meaningful label, useful instructions and an understandable error state. Ask only for fields needed to handle that stage of the enquiry, and make required versus optional fields unambiguous. Test successful submission, failure, duplicate clicks, mobile keyboards, notifications and the internal handoff so an attractive form does not become a dead end.
Sources for this section: Forms Tutorial.
What technical checks belong on the essentials list?
The launch baseline should cover secure hosting, responsive layouts, readable text, image alternatives, page titles, crawlable links, a working error page, backups and a tested contact path. Measure loading, interaction and visual stability with field data where it exists and controlled tests where it does not. Record which method produced each result rather than labelling every score as real-user evidence.
Connect measurement to decisions the business can make. Track form completion, calls or bookings only with approved definitions and privacy controls, then test whether the captured enquiry reaches its owner. A technically fast page that gives the wrong promise is still ineffective; a persuasive page that shifts, stalls or loses submissions is unfinished. Review both content and operation after launch. Schedule these checks again after content, hosting, form, analytics or consent-tool changes reach production.
Sources for this section: Web Vitals.
Official references
- Creating helpful, reliable, people-first content (Google Search Central)
- Building the main navigation for a website (web.dev)
- Link best practices for Google (Google Search Central)
- Forms Tutorial (W3C Web Accessibility Initiative)
- Web Vitals (web.dev)