“Visits are not the same as decision-ready enquiries: diagnose the gap between discoverability, relevance, and a form experience people can complete.
Diagnosis
A property site can attract attention yet lose intent when the landing page does not answer the query, the mobile version omits important content, or the enquiry form asks for effort without clear feedback. Treat “no qualified enquiries” as a journey problem, not proof that traffic is worthless. Separate search visits, property-detail engagement, form starts, successful submissions, and the information sales teams can actually use.
Decision framework
First ask whether the page matches the visitor’s language and property intent. Next check whether the same useful content and primary actions are available on mobile. Then inspect the form: every control needs an understandable label, and a submission should produce a clear success or error notification. Only after those checks should you change acquisition or judge lead quality.
Explicitly hypothetical property example
Implementation and measurement
Create an intent-to-page matrix for location, unit type, and buying purpose. Review a sample of mobile sessions, then instrument property views, form starts, validation errors, successful submissions, and handoff fields. Compare these stages by language and landing page. Read submitted enquiries for completeness, and use errors and abandonment to prioritize editorial or interface fixes rather than assuming more traffic is the answer.
Put it to work
- Map three priority intents to dedicated landing pages.
- Label every enquiry control and document success and error states.
- Report the funnel by language, device, and landing page before changing campaigns.