More visitors do not automatically mean more customers. A service business can attract the wrong audience, make its offer difficult to understand, lose messages after submission or receive suitable enquiries that never reach a quotation. Each problem needs a different response.
Before commissioning more content or a redesign, follow one important service from its landing page to the person responsible for replying. The aim is a repair brief supported by evidence, rather than a list of guesses about why the website is not working.
1. Separate the stages before judging performance
Keep search exposure, website visits, contact actions, received enquiries and customers in separate columns. A click on a phone link shows an attempted action; it does not establish that a useful conversation happened.
Google Search Console reports search impressions, clicks and average position. Google Analytics traffic acquisition helps identify session sources. These reports describe different parts of the journey; their totals should not be treated as interchangeable.
A useful working record has these stages:
- Relevant service page visited.
- Contact action attempted.
- Enquiry received in the business's chosen register.
- Enquiry reviewed and considered suitable.
- Quotation or proposal sent.
- Work agreed.
Only record a later stage when there is evidence for it. Google's recommended lead events also distinguish lead generation, qualification and conversion. An analytics event should represent the stage its name describes.
2. Choose a small, relevant page sample
Start with the main service page, one supporting article that attracts potential buyers and the contact route. Add another page only if it represents a different service or audience. Comparing the whole site's visits with its total messages can hide the actual problem.
Write the buyer's likely question for each page. Someone reading a beginner's explanation may be researching; someone checking service scope, delivery and support may be evaluating suppliers. Their immediate next steps can differ.
Record the reporting dates and known internal tests. Check the same pages over comparable periods. Small totals, consent choices and incomplete records make confident percentage claims unreliable.
3. Use an evidence-led diagnosis table
| What you observe | What to inspect next | A sensible response |
|---|---|---|
| Search appearances without many visits | Query, page, position and search purpose | Review visibility and relevance before blaming the contact form |
| Visits arrive mainly at unrelated articles | Landing pages and the route to relevant services | Connect suitable content to the buyer's next question |
| Buyers cannot tell whether the service fits | Scope, service area, exclusions and examples | Clarify those decisions on the service page |
| Contact actions occur but no message is recorded | One labelled submission and the destination record | Investigate delivery or storage |
| Messages arrive but concern unsuitable work | Actual enquiry categories | Explain the work you do and do not take on |
| Suitable enquiries receive few proposals | Assignment and follow-up records | Review the business process after receipt |
These are investigation routes, not universal explanations. For example, a page may have both weak relevance and an awkward form.
If the issue is being found, start with Google visibility checks. If a service page leaves buyers unsure, use the service-page improvement checklist.
4. Test the contact journey as a customer would
Use a phone, open the selected service page and find the contact route without relying on knowledge of the menu. Check that the page explains what happens after an enquiry and that any response-time statement reflects what the business can deliver.
Submit one clearly labelled test through the agreed route. Confirm the saved record and intended recipient, then mark the test as internal. A visible success message is one check; receipt by the business is another. W3C's form guidance recommends understandable success and error feedback.
Do not send repeated tests without checking the first result. If a request times out, inspect the destination before trying again, so you can distinguish a failed delivery from a duplicate.
When the form works but staff lack the details needed to quote, use the quote-request form specification. That is a different task from repairing a message that never arrives.
5. Turn the finding into a repair brief
Use this copyable record for each issue:
| Page or process | Buyer task | Observed obstruction | Evidence | Owner | Change | Retest |
|---|---|---|---|---|---|---|
| Selected service page | Decide whether the service covers this job | To be recorded | URL, date and observation | Named person | Agreed repair | Same task and outcome |
Here is a completed example for a fictional decorating business. It illustrates a repair decision, not a Nolixia customer finding or a reported increase in leads.
| Record | Fictional example |
|---|---|
| Buyer task | Decide whether decorating can be arranged while the premises remain in use |
| Observation | The service page lists decorating work but does not explain arrangements for occupied premises |
| Evidence to retain | The reviewed page version and the business owner's confirmed operating conditions |
| Bounded change | Publish only the arrangements the business actually offers, then link to the relevant enquiry route |
| Acceptance check | A reviewer can find those conditions on a phone; one labelled enquiry can be located by the receiving team |
| Outcome status | Proposed repair and retest; no customer or revenue result has been established |
If the evidence points beyond a small change, use the repair-or-redesign decision checklist before agreeing a wider rebuild.
Choose work that removes a confirmed obstruction, then retest. Use the existing SEO measurement guide to keep outcomes separate from activity.
Ask for a focused website review
Contact Nolixia with your website address, the service you want to sell and the action you want visitors to complete. We can discuss whether a focused repair or a wider website upgrade is the appropriate scope. Please do not send passwords or private customer records in the initial message.
