Fix low enquiries with smart checks: Check if traffic matches visitor need using GA4 landing page reports; Ensure form labels and feedback meet W3C guidelines for clarity; Verify completed requests actually reach the receiving team
Image: Lead Generation Desk

Lead Reporting

Part of Improving an underperforming lead funnel

Diagnosing traffic with few enquiries

Check visitor intent, page promise and the completed enquiry route before changing a page with traffic but few requests.

Desk Funnel Measurement · · 3 min read

When a page gets visits but few enquiries, check whether its arrival routes bring people with a relevant need and whether a completed request reaches the team.

Then inspect the page promise, action and form. The enquiry rate alone cannot show which part failed.

Establish what the traffic represents

Separate arrival routes by the question they appear to answer. A guide used for early research should not be judged by the same immediate enquiry expectation as a page inviting a project discussion.

Compare similar routes and periods, and show the visit count beside a rate; a small denominator can make a change look dramatic.

If GA4 is configured, consult its Landing page and Traffic acquisition reports as starting points for reviewing traffic. These views do not, by themselves, reveal a visitor's complete need or prove that a page caused a later enquiry. Read the page and the requests that actually arrived.

For Google Ads traffic, compare the ad and keywords with the destination page. If an ad promises a particular service but the page opens with a broad company message, treat the mismatch as a possibility to check against the actual requests, not an established cause.

Traffic Source Comparison: Intent vs. Enquiry Rate

  • Informational Route (e.g., research guide)
  • Transactional Route (e.g., project discussion invitation)

Walk one enquiry route

  1. Answer:Does the page explain the service, whom it suits and a limit that could change the decision?
  2. Invitation:Does the action say what the visitor can request and what response follows?
  3. Form:Are the questions understandable and proportionate to the first reply?
  4. Completion:Does a successful request show confirmation and reach an accountable recipient?

W3C form guidance calls for labels that identify controls and understandable feedback on success or errors. Also check whether a request actually reaches the team. A button click or form start is not a received enquiry.

Diagnosing Traffic with Few Enquiries

  • AnswerDoes the page explain the service, whom it suits, and any limits?
  • InvitationDoes the action clarify what can be requested and the expected response?
  • FormAre questions understandable and proportionate to the initial reply?
  • CompletionDoes a successful request show confirmation and reach an accountable recipient?

Identify the failure before changing the page

Informational visitors may finish reading without needing to enquire. If people with a defined service need reach the form but do not complete it, inspect the fields, validation and any recorded failures.

If requests submit successfully but never reach the receiving team, repair delivery first. Avoid calling a departure from the form abandonment unless the tracking can distinguish a form start from a page view and a successful submission.

Read completed requests too. Requests about the described service may indicate that the route is useful despite modest volume. Repeated requests for unavailable work call for a check of the arrival promise and service boundary. That is a different diagnosis from a broken form.

Choose a change that matches the evidence. Record the affected route and compare completed enquiries with the receiving team's ability to answer them. More submissions alone do not establish an improvement.

Key Metrics for Enquiry Route Health

  • Page Visits
  • Completed Enquiries (form submissions)
  • Enquiries Reaching Team

More from Lead Reporting