Website visits but few enquiries? Audit the customer journey

Check the journey between a visit and a useful enquiry

If your website gets visits but few suitable enquiries, investigate the audience, page content, evidence, contact process and business handoff before changing the design at random. The problem may be wrong-fit traffic, an unclear offer, an awkward form or an enquiry that never reaches the team.

Use this audit on one important service page first. Keep notes of what you find and change a small number of things you can evaluate.

First, check that the measurement means something

Define a useful enquiry for your business. A request outside your service area is different from a suitable project; a spam submission is different again. Record those distinctions without collecting unnecessary personal information in analytics.

Agree which actions you count and how you check them. A form-start event, a button click and an enquiry saved in WordPress are three different things. Where possible, connect the measurement to what the team actually receives.

Google’s Search Console performance report can help identify the searches and pages bringing visitors from Google. Compare that context with your own enquiry records. Do not assume every visit represents a potential buyer.

Check whether the page matches the visitor’s need

Look at the search query, referral link or campaign that led to the page. Does the page answer the question implied by that route?

Someone researching how to clean a patio may be looking for a guide, while someone asking for a local cleaning quotation needs service coverage, evidence and a contact route. Both audiences can be valuable, but their next steps are different.

For a fictional landscaper seeking larger projects, attracting more general gardening traffic could increase visits without improving lead suitability. The useful change may be clearer positioning and project examples rather than a bigger advertising budget.

Ask someone unfamiliar with the site to try it

Give them a realistic task: find the relevant service, decide whether the business looks suitable and start an enquiry. Watch what happens without explaining the interface for them.

• Can they identify the service and the customer it suits?
• Can they find real work and understand what it demonstrates?
• Can they establish whether you cover their area?
• Can they find what happens after contacting you?
• Do they get distracted, blocked or asked to repeat themselves?

The point is to discover specific hesitation. “Make the website more engaging” is difficult to test; “people cannot find the project enquiry button on mobile” gives you a concrete problem.

Review trust without inventing proof

Check for accurate business details, relevant projects, clear service boundaries and a straightforward explanation of the process. Use genuine qualifications, memberships and approved feedback where available.

If a result is not measured or a testimonial is not approved, leave it out. A small, well-explained project can be more informative than an impressive number without a source. Our portfolio shows the sort of context that can support a visitor’s assessment.

Test the form and the handoff

Complete a labelled enquiry on a phone. Try optional fields in the way a customer would, including entering a website as example.com. Check that errors are useful and entered details survive a failure.

If your site includes a chat guide, confirm that it closes when navigating and that project information carries into a form the visitor can review. Keep a direct contact route available for people who do not want to chat.

Then inspect the saved record and the notification. Check the recipient, the project details and who owns the reply. A success message is only one part of the journey.

Prioritise one fix and one outcome

Write a small test statement: “If we explain which projects this service suits and show two relevant examples, we expect more suitable enquiries from this page.” Decide how you will assess suitability and which other changes need to stay steady during the test.

Compare periods carefully. Small enquiry counts fluctuate, and a difference between a handful of visits is not strong evidence of a design improvement. Record uncertainty as well as the result.

Does every page need a contact form?

No. Some pages need a clear route to a suitable next step. Adding forms everywhere can create clutter without answering the visitor’s earlier questions.

Should I remove the AI chat if enquiries are low?

First check whether people understand it and can complete their task. Test the ordinary navigation and contact route too. Keep features that help, and improve or remove those that demonstrably get in the way.

Explore our enquiry journey improvement service or send us the page you want to review.