1. Check the enquiry count itself
Test the whole enquiry route on a phone and desktop. Submit the form, check the confirmation and confirm receipt by the person expected to respond. Try a realistic invalid entry and check the error message. Check phone and booking links too.
Compare recorded conversions with actual enquiries. A form-button click is not the same as a delivered enquiry. If the measurement changed recently, establish that before treating an apparent decline as a marketing failure.
2. Separate useful traffic from everything else
Group visits by landing page, source, market and intended task. Existing customers looking for support, people seeking free information and prospects ready to buy may all contribute traffic. They should not be judged against one enquiry rate.
In Search Console, review the queries bringing people to important pages. In analytics, examine the subsequent journey where tracking permits. An informational article can support a sale later, but it still needs a sensible connection to a relevant service.
3. Match the promise to the destination
| Visitor expectation | Useful page response |
|---|---|
| Find a specialist supplier | Clear service, suitable clients, relevant evidence and contact route |
| Understand likely investment | Scope, cost drivers and what is excluded |
| Resolve a technical issue | Specific capability, process and what information to send |
| Compare approaches | Honest trade-offs and next-step criteria |
If an advertisement promises a particular service but the link opens a general homepage, the visitor has to repeat the work of finding it.
4. Remove uncertainty before adding persuasion
Check whether the page explains who the service suits, the problem it solves, what happens next and who does the work. Use evidence relevant to the buyer’s problem. A large client logo alone does not explain your contribution.
Then inspect friction: long forms, unclear required fields, weak mobile layouts, intrusive overlays or an unexpected account requirement. Ask only for information needed at that stage. Explain response expectations only if the business can meet them.
5. Run a controlled improvement
Record a baseline and a hypothesis. For example: “People arriving on the integration service page cannot tell which systems we can connect.” Improve that information and the enquiry brief, then assess qualified enquiries and their quality over a suitable period.
On low-traffic B2B sites, a short experiment may not support statistical claims. Use observed customer tasks, enquiry feedback and operational checks alongside analytics. Avoid changing the offer, traffic sources, page layout and tracking together if you want to understand the result.
Common questions
Should I start with a redesign?
Only if evidence shows the platform or design prevents useful improvements. A messaging, tracking or form problem may need a much smaller fix.
What if the site has very little traffic?
Check whether relevant buyers can find the appropriate service pages. Conversion work and acquisition work may both be needed, but they remain different problems.
What should I measure?
Delivered qualified enquiries, appointments or sales, alongside the traffic and journey evidence that helps explain them.