A website can look perfectly acceptable and still fail to bring enquiries — which is why the problem survives so long. There is rarely one magic broken button; there is a chain from search to enquiry, and it fails at the weakest link. The productive move is diagnosis before treatment: work out whether the site has no visitors, the wrong visitors, or visitors who arrive and leave — because each failure has completely different fixes. This guide walks that diagnosis first, then the six most common leaks in order of how often we find them, with the specific fix for each.
Diagnose first: no traffic, wrong traffic, or no conversion?
Ten minutes in your data tells you which problem you actually have. Open Search Console and analytics and answer three questions. How many people visit per month? Under a couple of hundred, you have a traffic problem — the site is invisible, and improving the contact form is rearranging furniture in an empty shop. What searches bring them? If visitors arrive for terms unrelated to what you sell, you have a wrong-traffic problem. Do visitors view service pages and then leave without contact? That is a conversion problem, and the sections below are your list. Most low-enquiry sites have a blend, but one problem usually dominates — fix that one first.
Under ~200 visits/month: traffic problem, fix visibility first
Visitors from irrelevant searches: intent problem
Visits without contact: conversion problem — read on
One problem usually dominates; sequence the fixes
The offer is not clear enough
The most common conversion leak is at the very top: a visitor lands and cannot answer, within ten seconds, what you do, who it is for, where you work, and why you over the next tab. Vague headlines ('Quality solutions for your business'), welcome-message openers, and service lists hidden below decorative sliders all fail this test. The fix is unglamorous and powerful: a headline that names the service and the area, a subline that names the customer and the promise, and proof within the first screen. Read your own homepage as a stranger in a hurry — or better, ask an actual stranger and watch where their eyes stall.
Ten-second test: what, for whom, where, why you
Headline names service and area — no slogans
Proof visible in the first screen
Watch a real stranger read it; note where they stall
Trust signals are missing at the decision moment
Enquiring means risking wasted time on an unknown business, and visitors de-risk by scanning for signals: real reviews, photos of actual people and work, a physical trace (address, service area), consistent phone and email, company details in the footer, accreditations. When those are missing or stocky, hesitation wins — the visitor keeps your tab open, checks a competitor with forty Google reviews, and enquires there. The fix is proof-gathering, not design: request reviews from your best recent customers this week, photograph real jobs, and surface both next to every point where you ask for contact.
Buyers de-risk by scanning: reviews, photos, address, footer details
Stock imagery reads as absence of the real thing
Surface proof adjacent to every contact prompt
This week's fix: ask five happy customers for reviews
The contact path asks visitors to work too hard
Every extra step between interest and enquiry sheds real percentage points. The classic frictions: contact hidden in the nav's last item, forms demanding ten fields where three would do, no phone number for people who would rather call, no hint of what happens after submission, and — quietly deadly — forms that error on mobile or send enquiries to an unwatched inbox. Fix by shortening: a visible enquiry action on every service section, forms asking only name, contact, and a message box, tap-to-call on mobile, and a confirmation that sets expectations ('we reply within one working day'). Then test your own form from your own phone, this week.
Enquiry action visible on every key section
Three fields: name, contact, message — resist additions
Tap-to-call for the phone-first half of your audience
Test the form from your own phone; check where it lands
Mobile is fighting the visitor
Most local, buying-intent searches happen on phones — and many sites that look polished on the designer's monitor punish the phone visitor: text needing zoom, menus needing precision, images pushing the offer three screens down, forms with fields too small to hit. The visitor does not file a complaint; they thumb back to the search results. The test costs nothing: on a mid-range phone, over mobile data, try to get from a Google search to a submitted enquiry in under a minute. Every point of friction you hit, they hit — and where your patience frays as the site's owner, theirs already ended.
Phone visitors bounce silently — no complaint, no enquiry
Test: search → submitted enquiry in under a minute, on 4G
Readable text, thumb targets, offer above the imagery
Your friction threshold is higher than theirs; fix what annoys you
The site targets searches nobody makes — or loses the ones they do
Two intent failures starve sites of the right visitors. First, pages named internally ('Our Solutions') rather than the way buyers search ('boiler repair Leeds'), so Google has nothing to match. Second, targeting vague giant terms ('plumbing') where page one is unreachable, instead of specific service-plus-area and question searches where a small business genuinely competes. The fix is one page per real search intent: specific titles and headings, copy that answers what the buyer asks at that moment, and supporting guides that catch question-searches early and link to the money pages. Specific beats vague at every step of that path.
Name pages the way buyers search, not the org way
Service + area and question searches: winnable ground
One page per intent, guides feeding money pages
Vague head terms are where small-business SEO goes to die
Speed and technical drag are shedding visitors silently
Slow pages lose visitors before your offer is ever read — especially on mobile data, where a heavy hero image or a pile of scripts turns into a blank screen the visitor does not wait through. Beyond speed, quiet technical faults kill conversion invisibly: forms that error without saying why, links that 404, pages Google has silently stopped indexing. Run the free checks quarterly: PageSpeed Insights for Core Web Vitals, Search Console for indexing and errors, and a manual pass submitting every form. None of this needs a developer to detect — only to fix — and detection is the step most low-enquiry sites have never done.
Heavy pages = blank screens on mobile data = silent exits
Broken forms and 404s convert nobody, report nothing
Quarterly: PageSpeed Insights + Search Console + form tests
Detection is free; most sites have simply never looked
Common questions
Frequently asked questions
Why is my website not getting enquiries?
Diagnose before treating: it is either a traffic problem (too few visitors), an intent problem (the wrong visitors), or a conversion problem (visitors arrive and leave). Conversion leaks concentrate in five places — unclear offer, weak trust signals, contact friction, hostile mobile experience, and slow or broken pages. Fixing enquiries means fixing the dominant leak first, not repainting the whole site.
Will a redesign help my website get more enquiries?
Only if it fixes the actual leak. A redesign that clarifies the offer, surfaces proof, shortens the contact path, and repairs mobile and speed will move enquiries. A prettier version of the same unclear message, with the same ten-field form, will not — and if the real problem is traffic, design changes nothing at all.
What should I fix first on a low-enquiry website?
Check the data first: if traffic is under a couple of hundred visits a month, work on visibility before conversion. If traffic exists, fix in order of leverage — homepage offer clarity, trust proof beside contact prompts, then the contact form itself. Those three moves cover most cases.
How many visitors should convert into enquiries?
For UK local service businesses, something in the region of 2–5% of relevant visitors enquiring is a healthy working benchmark — a site with 300 relevant monthly visitors should produce enquiries weekly. Well below that with real traffic means a conversion leak; use the diagnosis to find which one.
Do Google reviews really affect website enquiries?
Strongly, twice over: they influence whether searchers click through to you at all, and they are the proof visitors scan for before contacting an unfamiliar business. Requesting reviews from recent happy customers and surfacing them on the site is routinely the highest-return hour available to a low-enquiry business.
How do I know if Google is even showing my website?
Search Console answers it for free: it shows the searches your site appears for, your position, and how many click through — plus indexing problems that silently remove pages. If you have never connected it, that half hour is diagnosis step zero.