Your website receives visits, but few enquiries reach the business. Before increasing spend or commissioning a redesign, establish what is happening between the landing page and the person who handles new requests.
Start with one important service, one landing page and one contact route. This diagnostic helps you check whether suitable visitors understand the offer, can contact you successfully and receive a useful response. The aim is a specific next action, supported by evidence and assigned to an owner.
First, define what “no leads” actually means
A campaign dashboard and a sales inbox can tell different stories because they count different things. Agree on these four stages before judging performance:
- Contact interaction: someone taps a phone number, opens a form or follows a WhatsApp link
- Received enquiry: a request reaches your business through a working form, an incoming message or a connected call about your service
- Qualified enquiry: the request meets your agreed criteria, such as service fit, location and project requirements
- Commercial outcome: a booking, accepted proposal or another outcome your business recognises
Keep spam, duplicate requests and test submissions separate. A real enquiry can still be unsuitable; that is a different problem from a contact form that sends nothing.
Google Analytics distinguishes form interactions and outbound clicks in its enhanced measurement documentation. The practical implication is that a WhatsApp link click does not establish that a message was sent or received. Likewise, test whether your form events correspond to accepted submissions and actual delivery. Do not assume the event name proves the whole journey worked.
Rule out a broken contact route before changing the campaign
Open the landing page on a phone and make a clearly labelled test enquiry. Check the confirmation shown to the visitor, the receiving inbox or customer relationship management system (CRM), and the notification received by the person responsible.
Try an invalid field, correct it and submit again. Test the phone and WhatsApp links on a device that can use them. A button can look right while opening the wrong number, hiding behind a sticky banner or failing after validation.
If an enquiry is accepted but disappears before anyone receives it, fix delivery first. If it arrives but is not assigned or answered, fix the handoff. Neither problem needs an experiment with button colours.
Use the first confirmed signal to choose where to investigate next. These are starting points, not diagnoses.
| What you can observe | First check | Who should investigate |
|---|---|---|
| A labelled test request does not arrive | Delivery, receiving address and notifications | Website or email administrator |
| Contact clicks are recorded, but receipt is unconfirmed | What each event counts; whether requests reach the business | Measurement owner and enquiry handler |
| Genuine enquiries arrive but are unsuitable | Recorded reasons for poor fit, then audience and offer alignment | Campaign owner and service manager |
| Suitable enquiries arrive but do not progress | Assignment, replies, quotations and the next agreed action | Sales or service manager |
One business may have several of these problems at once. Confirm the fault you can reproduce, then investigate the remaining uncertainty.
1. Check whether the traffic fits the service
Total visits mix together people with very different intentions. A student researching a process, a job applicant and a purchasing manager requesting a supplier quote may all visit the same industrial website.
Review the landing page, traffic source, target location and language together. Where available, inspect the search terms behind paid clicks and the search queries associated with organic visits. Then compare those intentions with what the page actually offers.
A useful diagnosis sounds like this: “The campaign promotes installation, but the searches we can see are largely about buying spare parts.” That gives the campaign owner something to investigate. “We need better traffic” does not.
For businesses serving Egypt or several MENA markets, check service availability rather than assuming every visit from the region is relevant. Can you deliver in that city? Does the page explain the market and language you support? Treat those as audience questions, not regional stereotypes.
When the mismatch begins with customer searches and page selection, search intent and SEO priorities may need attention. When it begins with paid targeting or messaging, investigate the campaign before rewriting the entire website.
2. Follow the promise from the ad to the page
Read the ad or social post, then open its destination without using the navigation. Can you find the same service, relevant details and promised next step?
A hotel campaign offering meeting-space enquiries should lead to information about meeting spaces and how to request availability. A general homepage that opens with a room-booking offer introduces a new decision at exactly the point the visitor expected an answer.
Google Ads guidance on landing pages recommends matching the destination to the ad and its call to action. Apply that as a consistency check, not a promise that a matching headline will produce sales.
Write down the promise, the destination and the action in three short sentences. If they describe different offers, agree which one the campaign is meant to support. This is where campaign planning and landing-page readiness need a shared brief.
3. Find the unanswered buying question
A page can describe a company accurately while leaving the buyer unsure whether to contact it. Read the page from the perspective of someone comparing providers:
- What specific problem does this service solve?
- Is it suitable for a business or project like mine?
- What is included, and what needs a separate discussion?
- What evidence can I inspect?
- What happens after I enquire?
Use evidence you can substantiate: relevant work you have permission to show, a clear process, accurate specifications or genuine customer feedback. If you cannot publish a project, explain your approach without inventing a case study.
For a bespoke service, pricing may require a conversation. Explain what information is needed to prepare a quote rather than leaving the visitor with a vague “Contact us”. For a standard package, make its scope and exclusions understandable.
Ask a colleague unfamiliar with the page to explain the offer back to you. Their uncertainty is a clue to investigate, not proof that every visitor shares it. Fix the missing answer before adding more claims.
4. Test the effort required to enquire on mobile
Work through the real task with the keyboard open. Can you read the labels, correct an error and reach the submit button? Does a floating contact button cover the consent control or the last form field?
Question each required field: does the business need this information to respond usefully at this stage? An industrial quote may need a specification or drawing. An initial professional-services conversation may not need a full billing address. Removing every field is not the goal; requesting appropriate information is.
Google Analytics’ lead-generation guide separates visits, form views, starts and submissions. Use those stages to locate a drop-off, then investigate the cause. Abandonment alone does not tell you whether the problem was form length, an error, weak intent or an interruption.
Check loading and responsiveness too, especially on the devices and connections your audience uses. web.dev explains why lab and field measurements differ: controlled tests and real-user experiences cover different conditions. A speed score helps investigate performance; it does not establish whether an enquiry reached the inbox.
5. Trace the enquiry after it reaches your business
Choose a small, recent set of genuine enquiries and trace what happened. Was each assigned? Did someone respond? Did the reply address the requested service? Was the next action recorded?
Agree who covers each contact route, including absences and enquiries outside normal working hours. Set a response expectation your team can meet. Do not put an instant-response promise on the website if nobody can honour it.
If enquiries arrive but most are unsuitable, record why. Wrong service, unsupported location, insufficient project detail and budget mismatch suggest different remedies. A clearer qualification prompt might help one problem; a targeting change might help another.
If suitable enquiries arrive but sales do not follow, investigate quoting, follow-up, availability and offer competitiveness. Website traffic is too far upstream to explain that outcome on its own.
Keep one diagnostic record for each suspected problem
Use the following fields in a shared document. Keep observations separate from explanations so a plausible theory does not become an accepted fact.
- Observation: what actually happened, on which page, device or contact route?
- Evidence: which test, report or business record supports it?
- Hypothesis: what might explain the observation, and what remains unknown?
- Baseline and review context: record the dates, relevant traffic segment, enquiry definition and approximate volume, alongside material changes during the review
- Action and owner: what will change, and who is responsible?
- Review measure: what would show that the change worked, and what else could affect the result?
Fix reproducible faults directly. For uncertain improvements, make a focused change with a clear reason and preserve the previous version. Avoid changing targeting, copy and the form together if you want to understand which change mattered.
A hypothetical industrial-service example
Imagine a maintenance supplier receiving visits to its emergency-repair page but few recorded enquiries. This is an illustrative scenario, not an ADAMS client result.
A labelled mobile test shows that the form displays a success message, but the request never reaches the service inbox. The evidence is a failed delivery test; the initial priority belongs to the website or email administrator. The completion check is a repeat test that reaches the correct recipient once, with a usable reply route.
After delivery is restored, the business discovers that several genuine requests concern cities it does not cover. That is a separate audience-and-offer question. The campaign owner and service manager should review location settings and page wording. Repairing delivery did not establish that targeting was correct.
Finally, suppose the analytics dashboard still reports more contact actions than received requests. The measurement owner should check what each event counts, including repeated clicks. Relabelling all interactions as qualified leads would hide the difference.
Choose the next investment from the evidence
Fix confirmed contact or delivery faults first. Then rank the remaining issues by evidence, commercial impact and effort. That protects the route a potential customer is already trying to use while keeping the next investment tied to what you know.
A focused website improvement may be enough when the problem is confined to one page. A rebuild becomes a more reasonable discussion when the existing structure repeatedly prevents essential changes across services, languages or contact journeys. Increasing media spend is a separate decision that needs evidence about traffic relevance, enquiry quality and business capacity.
Review comparable traffic segments and record campaign changes, seasonal effects and sales delays. Low-volume businesses may need more observation before drawing conclusions. A short before-and-after comparison can suggest a direction without proving that your change caused the result.
The useful outcome of this diagnostic is a decision you can explain: what is failing, what evidence supports that view, who owns the fix and how you will check it.
Discuss the next step with ADAMS
Send ADAMS the page you want to improve, its main traffic source and the action you want visitors to take. Include any confirmed delivery fault or recurring reason an enquiry is unsuitable. These details give us a useful starting point for discussing the right scope across your website, messaging and campaigns.