Why your website gets visitors but not enquiries

1. Check the whole journey before changing the design

Start with a page that already attracts relevant interest. Follow the route a customer would take from a search result, advertisement or social post. A homepage visit alone tells you very little about whether a specific service is easy to buy.

• Does the link open the page promised by the search result or campaign?
• Can you quickly identify the service, who it suits and where it is available?
• Is the next step visible and understandable on a small screen?
• Can you complete the form without zooming, guessing or repeatedly fixing errors?
• Does the website confirm the request, and does the business actually receive it?
• Is someone responsible for replying, including when the usual person is away?

Record what happens rather than relying on memory. A short list such as “quote button hard to find”, “required field unclear” and “notification went to spam” gives a developer or marketing specialist something concrete to fix. If the form does not deliver, repair that before trying to increase its use.

2. Work out whether the visitors are suitable

A helpful article may attract people researching a topic months before buying. A service page should make it easier for someone with a current need to assess your business. Those visits have different purposes, so do not judge them as though every reader should request a quote.

Look at the search queries and landing pages involved. Google’s Search Console Performance report shows search clicks, impressions and query information. Use it to investigate whether you are appearing for the services and locations you actually cover. It reports search activity, so you will need other information to connect that activity with enquiries.

For example, a hypothetical removal business offering interstate moves might receive visits from people looking for a same-day local delivery service. More visits from that audience may mean more unsuitable requests. Clear service boundaries, realistic location information and a relevant page title can help people understand the fit.

Advertising has the same requirement. If an ad offers a particular service, send people to a page that explains it. My Meta Ads and digital marketing support connects the creative, landing page and enquiry process so they can be reviewed together.

3. Answer the questions a customer needs to decide

A page that says you deliver “quality solutions” leaves the visitor to work out what that means. Replace vague claims with useful details about the actual service. Explain the work, the customer it suits, the areas covered and what is needed to provide a quote.

Show proof that relates to the decision. A genuine project example with a short explanation can answer questions a decorative image cannot. Use reviews accurately, identify examples clearly and keep information current. Generated editorial images can illustrate an idea, but real work should be represented with real evidence.

Customers often ask the same things before enquiring. Build the most useful answers into the service page. The companion guide, a simple content plan for busy small business owners, shows how to turn those questions into website improvements and helpful posts.

4. Make the next step easier on a phone

Check the page on an ordinary mobile connection. Look for text that is uncomfortable to read, buttons hidden behind a floating banner, oversized images and a navigation menu that covers the contact action. These are practical obstacles even when the desktop version looks good.

Google’s web.dev guidance on Core Web Vitals measures loading, responsiveness and visual stability. Its good-experience thresholds are main-content loading (LCP) within 2.5 seconds, interaction response (INP) of 200 milliseconds or less and layout movement (CLS) of 0.1 or less, assessed at the 75th percentile of visits. These are useful performance references; they do not predict an enquiry rate.

Ask for enough information to start a useful conversation

Every field should have a reason. A name, a suitable contact method and a short description may be enough for an initial discussion. A moving quote may also need locations and dates. Keep the questions your team needs to assess the request, and move detailed intake questions to the next stage when that makes sense.

The W3C Web Accessibility Initiative’s forms tutorial recommends short, simple forms and asking only for information needed for the process. It also covers labels, instructions, validation and success or error messages. Check that people can use your form with a keyboard and understand how to correct a mistake.

Explain what happens after submission. If you cannot promise a reply within a particular time, use an honest description of the next step. Offer a working phone link where calls suit the service. Check that automated acknowledgements and internal notifications still work after website or email changes.

5. Measure useful enquiries and what happens afterwards

Choose a consistent definition of an enquiry before comparing results. A click on a phone number is an expression of interest; it does not confirm that a call connected. A form-button click does not confirm that the message reached your inbox. Keep those actions distinct in your reporting.

Google Analytics documents a recommended generate_lead event for a form submission or information request. It requires setup. Have tracking checked against successful submissions so errors or repeated clicks do not inflate the result. Keep customer names, email addresses and message text out of ordinary analytics events, following Google’s guidance on avoiding personally identifying information.

For a small business, a simple internal record can be enough: date, service requested, source if known, whether it was suitable and the outcome. Handle that record with appropriate access. Compare it with website reporting while allowing for calls, repeat customers, consent settings and other gaps in tracking.

A small number of enquiries can fluctuate considerably. Keep notes about advertising spend, seasonal demand and availability. Change one important part at a time where possible and allow enough activity to make a useful comparison.

A manageable two-week improvement plan

1. Days 1–2: establish the starting point

   Choose one service page. Test the full contact route, note relevant visits and enquiries, and ask your team which customer questions keep returning.

2. Days 3–5: repair the obvious obstacles

   Fix delivery failures, confusing field labels and mobile layout problems. Make the service area, offer and contact action easier to understand.

3. Week 2: strengthen the decision

   Add a genuine project example and the most useful missing answers. Check the revised page and tracking, then record the launch date so later comparisons have context.

4. After launch: review the next useful signal

   Watch enquiry quality and follow-up outcomes over an appropriate period. Keep improvements that help, investigate remaining friction and decide whether more traffic is justified.

If you find a broader visibility or indexing issue, the technical and on-page SEO checklist provides a sensible order for investigating it.