Why Your Website Gets Traffic but No Enquiries (and How to Fix It)

Before you change a single word on the page, check whether the enquiries are actually missing, or just invisible to you. This is the step almost every guide on this topic skips, and it is the one that regularly changes the diagnosis.

On our own site we define a lead in three ways only: a WhatsApp message, a phone call, or a contact form submission. Those three actions are the ones we track as key events in analytics. Run the same test on your site. Can you see, for the last 30 days, how many people tapped your WhatsApp button, how many called from the website, and how many submitted the form? If any of the three is not being counted, your problem may be measurement, not conversion, and no redesign will fix a number you cannot see.

Then check the unglamorous places enquiries go to die. Open the inbox the form sends to and search the spam folder for your own test submission. Submit the form yourself, on your phone, and time how long the confirmation takes to arrive. Call the number shown on the site and see who answers, and how fast. We say this because the pattern is common: a business concludes its website does not convert, hires someone to rebuild it, and discovers afterwards that enquiries were arriving all along, into a mailbox nobody was watching.

Only when all three routes are counted, delivered and answered does the honest question begin: people are arriving, the routes work, and still nobody writes. That is a page problem, and it has five usual causes. If your problem is the opposite one, no visitors at all, start with our guide to why your website is not showing on Google instead, because the fixes there come before everything in this article.

Traffic is not one thing. A visitor who searched for a definition and a visitor who searched for a company to hire both appear as one session in your reports, but only one of them was ever going to enquire. When the first kind dominates, the site can look busy and stay silent.

Look at the searches and pages bringing people in. Informational visits land on guides and articles, read, and leave informed; that is their job, and a good guide still earns its keep by making the next visit a branded one. Buyer visits land on service and city pages, and those pages should be converting a visible share of their visitors into enquiries. If your service pages get the traffic and produce nothing, the problem is on those pages, which is what the rest of this article is about. If nearly all your traffic is informational, the problem is upstream: the site ranks for questions but is invisible for the searches people make when they are ready to buy.

That second problem is a search problem, not a design problem. It is fixed by building and supporting pages for the services and cities you actually sell in, which is the slow, unglamorous work behind our SEO services in Dubai. The mistake to avoid is redesigning a converting page layout to chase a traffic-quality problem, or buying more traffic to feed pages that were never built to receive a buyer. Diagnose which of the two you have before spending on either.

Give a stranger five seconds on your busiest service page and ask what they would say the business does, who it does it for, and what happens if they get in touch. If the honest answer is a shrug, you have found the most common cause of all. Pages fail this test in predictable ways: a headline that could belong to any company in any industry, services listed as nouns with no outcome attached, and no mention of the place the customer is actually in.

Clarity is specific. A Dubai business reading a page wants to know that the service covers Dubai, what the work actually includes, roughly how it is priced or at least how the price is worked out, and what the first step looks like. None of that requires clever copywriting. It requires the page to answer, in order, the four questions every buyer silently asks: Do you do the thing I need? Have you done it for someone like me? What will it cost me to find out? What exactly happens when I contact you?

Our opinion, from building and fixing pages like these: vague pages are rarely vague by accident. They are vague because the business has not decided what it wants to be chosen for. A page that tries to be the safest choice for everyone ends up the memorable choice for no one. Pick the work you most want, say it first, and let the rest of the site carry the rest.

In the UAE, the first conversation about almost any service starts on WhatsApp. Buyers here message first and fill in forms later, if at all. Yet a surprising number of business websites still offer exactly one route: a contact form asking for a name, an email, a phone number, a company, a budget range and a paragraph, on a phone screen, in portrait. Every extra field is a small tax on a stranger’s goodwill, and most strangers decline to pay it.

The fix is to make the easiest route the most visible one. On mobile, the WhatsApp button should be one tap away without scrolling; our own site keeps it floating on mobile screens for exactly this reason. The number, the tap target and the response behind it all have to work: a WhatsApp button that opens a chat nobody answers is worse than no button, because it converts a maybe into a confirmed bad experience. If your message volume grows past what one phone can handle, that is what WhatsApp Business API setups exist for.

Keep the form, but demote it to the second route and shorten it to what a first reply genuinely needs: a name, a way to reach the person, and one line about the project. Everything else can be asked in the conversation. And make the call option real on mobile, as a tap-to-call number, not a number rendered as an image. When you are ready to send people somewhere, send them to a contact page that offers all three routes side by side and lets the visitor choose, instead of a page that makes the choice for them.

A visitor decides whether to trust a page before they finish reading it, and the evidence they look for is boring: real work, real names, real outcomes, and prices that are not hidden. When the proof sits three clicks away on a separate page, most visitors never see it. They do not distrust the business; they simply never encounter the reason to trust it.

Move the proof next to the decision. The strongest place for a case study link is beside the claim it supports, not in a gallery. Our Travel Trek Tourism case study sits where it does because a tourism business weighing a website needs to see a tourism website, not a testimonial about one. Reviews work the same way: a handful of specific, named reviews beside the enquiry button outweigh a page of anonymous praise.

Price transparency is part of the same trust test, and it is the part businesses resist most. You do not have to publish a price for everything. You do have to remove the fear that asking will waste the visitor’s time or invite a sales call they cannot escape. On our own pricing pages the website packages are published with the scope written out, starting at AED 999 for the Starter package, precisely so a visitor can self-qualify before enquiring. The enquiries that arrive after published pricing are fewer and better: the visitor already knows the shape of the deal, and the first conversation starts at scope, not at suspicion.

Most of your visitors are on phones, on mobile connections, in the gaps of a working day. A page that loads in a patient desktop test can still be the page a buyer abandons in a car park in Al Quoz. Speed is not a technical vanity metric here; it is the door of the shop, and a slow door quietly caps every other fix in this article.

We can put a number on this from our own site, because we did the work on it. Our homepage’s official mobile PageSpeed score went from 57 to 94 through unglamorous changes: removing a heavy script framework the design did not need, serving the page’s own compiled styles instead of generating them in the browser, and self-hosting the fonts. No redesign, no new content, and no change to what the page says. The full account, including what the slowness was costing, is in our guide to what page speed actually costs a Dubai business.

Test your money pages the way your customers meet them: on a phone, on mobile data, with the official PageSpeed tool, and look at the mobile score for the service page that should be producing enquiries, not just the homepage. If it is slow, fix the causes your developer can name, and re-test. If it is fast, speed is not your problem and you can strike this cause off the list with confidence, which is its own kind of progress.

Resist the urge to change everything at once. If you alter the headline, the buttons, the form and the layout in the same week, and enquiries rise, you will not know why; if they fall, you will not know what to undo. Work in this order, one layer at a time, and give each layer enough traffic to judge.

First, measurement: count the WhatsApp taps, calls and form submissions for one clean month, so every later change has a before picture. Second, the next step: WhatsApp one tap away on mobile, a short form, a working tap-to-call number. This is the cheapest layer and usually the most productive, because it removes friction for the visitors you already have. Third, clarity: rewrite the first screen of each service page so the five-second test passes. Fourth, proof: case studies and reviews moved beside the claims and the buttons. Fifth, speed: the mobile fixes, tested page by page. Traffic quality, the upstream cause, runs in parallel throughout, because it is the slowest to change and the first one whose results you will want later.

Notice what is not on the list: a redesign. A redesign resets everything, including the parts that were working, and it is the most expensive way to run an experiment. Most silent websites need surgery on two or three layers, not a new body. If, after working the list, the honest conclusion is that the site’s structure itself blocks every fix, that is a different conversation, and we have written the redesign-versus-new-website comparison for it. But start with the list. It is cheaper, faster, and it teaches you what your customers actually respond to.

Sometimes the audit ends with an uncomfortable finding: the website is doing its job. Enquiries arrive, and then they wait. A WhatsApp message answered the next morning, a form reply sent after the weekend, a missed call never returned; each one is a buyer who did the hard part, raised a hand, and was met with silence. By the time the reply lands, the competitor who answered in ten minutes has the job.

Treat response as part of the website’s performance, because the visitor experiences it that way. Decide who owns first response during working hours, set a simple standard for it, and route the three channels somewhere a named person actually watches. This is also why the measurement in the first section matters twice: the same tracking that counts enquiries can show you the gap between an enquiry arriving and anyone noticing.

None of this is glamorous, and none of it requires a new website. Which is, in the end, the point of this guide. Traffic without enquiries feels like a verdict on the site, but it is usually a short list of fixable breaks between a visit and a conversation. Find the breaks in order, fix the cheapest first, and measure like you mean it. The visitors you already have are the cheapest growth you will ever buy.