Follow the enquiry beyond the click.

Define a qualified enquiry in operational terms

Write a short definition that the people answering enquiries can apply consistently. It might include a supported service, a workable location and enough information to begin a relevant conversation. Keep this separate from whether the person ultimately becomes a customer. A genuine request can be qualified even when timing or capacity prevents the sale.

Agree on a small set of lead outcomes, such as awaiting review, suitable enquiry, outside coverage, duplicate or spam. Use neutral descriptions and avoid collecting personal information that is not needed for follow-up. A consistent review process helps identify a content problem when the site repeatedly attracts requests for something the business does not offer.

Keep visibility, interaction and receipt separate

Search Console reports impressions, clicks and other search metrics. Analytics events describe website interactions. A lead management record confirms that submitted details reached the intake system. Those measures are useful together, but they should not be reported as the same thing. A person opening chat or pressing a submit button has not necessarily sent a complete enquiry.

Define the conversion event at the point the application has a confirmed receipt. Record earlier interactions separately so they can help diagnose abandonment. If the request is saved but temporarily awaiting delivery, tell the visitor what happened and preserve a reference. That makes the customer experience more reliable and reduces the chance of counting repeated attempts as separate opportunities.

• Search visibility: the page appears or receives a search click.
• Website interaction: a visitor explores chat or begins a form.
• Confirmed enquiry: the intake system returns a valid saved reference.
• Lead quality: the team reviews suitability and the next step.

Preserve useful context without private event data

The first landing page, selected service and intended market can help explain an enquiry. Keep that context alongside the lead where appropriate and label it accurately. A city selected in a form is the requested market, not proof of the visitor’s physical location. A referrer or campaign label is useful context, not a complete account of every interaction that influenced the decision.

Google Analytics prohibits sending information it can recognize as personally identifiable, including email addresses and personal phone numbers. Check URLs, page titles and event parameters as well as visible forms. Keep names, private messages and contact details in the appropriate lead system. Analytics collection should follow the website’s disclosed consent choices and configuration.

Compare pages around the job they perform

Group pages by their purpose before comparing outcomes. A guide may help someone understand a problem, while a service page supports a direct enquiry. Review each group’s relevant search visibility and how people move toward the next useful page. Avoid judging every informational article by the same immediate contact rate as a high-intent service page.

For city pages, inspect the requested service and the suitability of incoming enquiries. A page receiving more traffic but mostly out-of-area requests may need clearer coverage information. A lower-traffic page generating appropriate conversations may be doing valuable work. Include the reporting period, the number of observations and important business changes so small differences are not overstated.

Use the report to choose a specific improvement

A practical monthly review can begin with three questions: What changed? Which evidence supports that observation? What should we check or improve next? If visibility grows but relevant enquiries do not, examine the page’s promise, service fit and form journey. If recorded enquiries fall suddenly, verify intake and notification delivery before assuming search demand disappeared.

Keep a record of significant changes so the next review has context. Consent choices, browser behaviour, delayed decisions and cross-device journeys can leave gaps in attribution. Treat the lead system and human review as important companions to website reporting. The aim is an increasingly useful account of demand, not a claim that a dashboard can explain every customer decision.