Someone looking for a new accountant may arrive on your website through a Google result for one particular service. They have not seen your homepage or heard your carefully rehearsed introduction. They want to know whether you work with businesses like theirs, what happens next and whether getting in touch will start a sales pitch. A useful website answers those questions in the order they arise.
That sequence is the visitor’s journey. On a service-business website, it usually runs from recognising a relevant problem, through assessing a possible provider, to making an enquiry and receiving a response. It may involve several visits, different devices and an offline conversation. The journey is useful as a design tool because it makes us look beyond individual pages and ask whether one step leads naturally to the next.
Start where the visitor starts
Website owners often picture a visitor opening the homepage, reading the welcome message, then following the menu in order. Search results, shared links and local listings can take someone straight to a service page, article or contact page. Each important entry page therefore needs enough context to stand on its own.
A visitor who lands on a bookkeeping service page should quickly see who the service is for, what help is offered and where to go for more detail. An opening that says only “Welcome to our services” makes them do the work of figuring out whether they have found the right place. A headline that names the service and a short paragraph about the situations it helps are more useful.
This is one reason I look at the whole route to an enquiry, rather than judging the homepage on its own. A strong homepage can orient new visitors; it cannot rescue a service page that leaves them uncertain about the work.
Show enough for someone to recognise a fit
Consider an architect whose site says “bespoke design solutions for every project”. It sounds broad, yet a homeowner planning an extension still does not know whether the practice handles small domestic work, planning applications or projects in their county. A short description of the work, typical project types and geographic area could answer all three questions.
The same issue appears in less visual services. A consultant may describe a methodology in detail while leaving out the business problems that lead clients to call. A therapist may write warmly about their philosophy while a prospective client looks for appointment format, location and practical boundaries. Good content connects the provider’s expertise to the visitor’s immediate decision.
There is no need to publish every detail on the first screen. Give the visitor a credible reason to continue, then organise the supporting detail under clear headings. The Office for National Statistics’ guidance on user needs is a helpful reminder that a page may serve several different needs. On a service page, one person may be checking eligibility while another is ready to ask for a quote.
Make the next question easy to answer
Once someone believes you might be suitable, their questions become more practical. They may want to know how the work begins, what they will need to provide, how long it might take, what affects the price and who will deal with them. These are often the things a business owner explains naturally on the phone, yet the website leaves them implicit.
Imagine a physiotherapy clinic page that describes treatments and has a “Book now” button. A first-time patient may still need to know whether an initial assessment is required, how long it lasts and what happens if they are unsure which appointment to choose. A brief explanation near the booking route can remove a genuine hesitation. It also helps the clinic receive better-matched bookings.
For a web design project, the questions are different. A buyer may want to understand what is included in a quote and why prices vary. My guide to what a professional website quotation should cover gives that decision more room than a service-page paragraph reasonably can. Linking to a useful explanation lets a curious visitor go deeper without forcing everyone through it.
What would a sensible person still need to know before contacting you? Write down the questions you hear in real enquiries. Look for those that repeat. Each one is a clue that a service page, process page or short supporting article could make the journey easier.
Let proof do a specific job
Trust signals are most persuasive when they answer a real concern. A testimonial saying “great service” is pleasant but thin. A description of what was delivered, the type of organisation involved and how the working relationship unfolded gives a reader something to compare with their own situation. Permission, privacy and accuracy matter when describing client work; there is no need to invent a dramatic result.
Photographs can help too, provided they show the people, place or work that a buyer is trying to understand. An independent restaurant benefits from a truthful view of its room and food. A consultant may be better served by a clear portrait and an explanation of how meetings work than by a row of anonymous stock-office pictures. The choice should answer a visitor’s question, not fill a visual gap.
Proof belongs near the decision it supports. A relevant example on a service page can reassure someone considering that service. A detailed case study may deserve its own page. A small business does not need an elaborate evidence library on day one, but it should make whatever evidence it has easy to find and interpret.
Offer a next step that matches the decision
“Contact us” is serviceable when the visitor already knows why they are contacting you. Elsewhere, a more specific invitation can make the action clearer: “Ask about an initial appointment”, “Tell me about your project” or “Request a quotation”. The wording should reflect what happens after the click.
A large commitment may be the wrong first step for an uncertain buyer. If the service requires a conversation before it can be priced, say so. If a fixed booking is appropriate, show the appointment length and the information needed. For a local service with a strong telephone culture, a visible phone number may matter as much as the form. Different routes can coexist when they serve different preferences and the business can manage them reliably.
Put the invitation where it makes sense in the reading flow. An immediate button in the page header gives ready buyers a route. A second invitation after the scope, process and reassurance helps people who needed more information. Repeating the same urgent button after every paragraph can make the page feel pushy without making the decision easier.
The wording and placement are design decisions, not magic conversion tricks. They are most useful when the surrounding content has made the next step feel proportionate.
Keep the enquiry route simple and dependable
The contact form is part of the journey, not a separate administrative detail. Ask for the information needed to respond usefully. A prospective client can often describe a project in their own words before they know its exact budget or technical requirements. A long form may be justified for a complex service, but every field should earn its place.
Labels should be visible and clear, and instructions should explain any unusual request. The W3C’s guidance on labels and instructions describes the accessibility principle behind this. Plain language helps everyone, particularly a visitor using a phone or completing the form between other tasks.
After submission, tell the visitor what happened and when they might hear back. Then test the journey at the business end. A reassuring confirmation on screen is little comfort if the enquiry never reaches an inbox. I have written separately about where contact forms can lose good enquiries; the important point here is that the journey continues after Submit.
That continuation may include an automatic acknowledgement, a human reply, a booking invitation or a request for more detail. Make the promise realistic. A sole trader who replies during working hours should say that plainly rather than imply constant availability.
Check the journey across pages and devices
A website can have well-written individual pages and still feel disjointed. The service page may promise a free consultation, while the contact page asks for a deposit. A button might say “See prices” and lead to a generic contact form. Those inconsistencies create small moments of doubt, especially when someone is comparing several providers.
Consistent navigation and names help people keep their bearings. The W3C’s explanation of consistent navigation addresses a related accessibility requirement: repeated navigation should appear in a consistent relative order. In ordinary design terms, visitors should not have to relearn the site as they move around it.
Check the route on a phone as well as a desktop. A long service page may be comfortable on a large screen yet bury the enquiry action after many small-screen swipes. A sticky button can help in some layouts, though it should not cover the content or compete with an accessibility control. The right answer depends on the page and should be tested in context.
Can someone complete the journey using only their phone? Open the page from a search result, follow the links, read the reassurance, fill the form and check the confirmation. That simple walk-through often reveals more than inspecting each page in isolation.
Map a real route before redesigning anything
You do not need a wall of sticky notes to begin. Choose one important service and one likely visitor. Note their starting question, the page they might land on, what they need to decide and the action you hope they can take. Then follow the route on the existing site as if you knew nothing about the business.
A compact review might look like this:
- Entry: does the landing page say who the service is for and what it offers?
- Understanding: can a visitor find scope, process, location and useful pricing context?
- Confidence: is there relevant evidence and a clear account of what happens next?
- Action: does the button describe the action, and can the form or booking be completed?
- Afterwards: does the visitor receive confirmation, and does the business receive the enquiry?
Watch one or two people unfamiliar with the site try a realistic task if you can. Ask them to find out whether the business handles a particular need and how they would get in touch. Observe where they pause instead of explaining the page to them. GOV.UK’s service design guidance likewise emphasises understanding the whole journey and the different ways people interact with a service. A small business needs a proportionate version of that thinking, not a large research programme.
Analytics can indicate where people arrive and which pages they visit, but it rarely tells you why an individual hesitated. Enquiry emails, phone questions and a careful task walk-through add the missing context. Fix the clearest break first. That might be one paragraph of scope, a clearer page link or a form notification fault rather than a complete rebuild.
The website is part of the service
A useful journey makes a promise that the business can keep. If a page says enquiries receive a reply within a day, somebody must own that inbox. If it invites visitors to book a particular service, the booking process must match the description. The quality of the website’s design depends partly on what happens after a visitor leaves it.
When I review an existing WordPress website, I look at the content, layout and technical route together: how a person arrives, what they learn, where they hesitate and whether the enquiry reaches the business. That diagnosis can lead to a focused repair, a service-page rewrite or a broader redesign, depending on what the journey reveals. If your site gets visits yet makes it hard for suitable clients to take the next step, book a conversation with me and tell me which service you most want the site to explain well.
Sources and further reading
- Office for National Statistics: Understanding your users
- GOV.UK Service Manual: How user research improves service design
- W3C: Labels or Instructions
- W3C: Consistent Navigation
Important note
This article provides general information and professional commentary. It is not advice tailored to your particular business, website or circumstances, and it should not be treated as legal, financial, privacy, accessibility, cybersecurity or other specialist advice. Any opinions are my own professional judgement based on the information available when the article was researched.
Products, prices, services, software and official guidance can change. External links are provided for reference; I do not control third-party websites and cannot guarantee their continuing availability, accuracy or content. A link does not imply endorsement of everything published by that source.
Check current official information before making an important decision. Test technical changes safely, keep a verified backup, and obtain appropriately qualified advice where the consequences warrant it. Any sponsorship, free product, affiliate link or other commercial relationship relevant to the article will be clearly disclosed.
