Back to blog
Websites

Your site has visits but no enquiries. What should you check?

Published: 2026-07-279 minKrzysztof Jaroński

Traffic without enquiries does not automatically mean you need a redesign or a bigger ad budget. First separate three questions: are the right people arriving, do they understand the offer, and can they take the next step comfortably? Without data it is easy to fix the wrong thing. A new look rarely fixes poor traffic quality, a broken form or an unclear offer.

Contents

Traffic vs conversion

First check whether the problem is acquisition or action. A small amount of well-matched traffic may not create enough contact opportunities, but a large volume will not help either if it attracts people looking for something else than the company offers. Session count alone does not prove that visitors are potential clients.

Then compare entry pages, channels and actions. Do people from search results read a service page, or do they land on a generic article? Does the campaign promise match the view after the click? Are phone and form used, and if not, are they even noticeable? This analysis does not need artificial benchmarks — it should show a concrete gap in the path.

Traffic quality

Visits “exist” when:

  • someone is looking for instructions or free knowledge and has no buying intent;
  • traffic comes from a mismatched keyword or campaign;
  • bots and accidental hits inflate session counts;
  • the user lands on an article without a clear bridge to the offer.

Before you change colours, check sources, landing pages and queries (Search Console / campaign reports). If most sessions are educational content without a CTA to a service, the path may be the problem, not an “ugly design”.

Offer and intent

The most common issue is not missing decoration, but an unclear answer to “what exactly do you offer?”. A headline such as “comprehensive solutions for business” can fit almost any company. A visitor needs to see the service, who it is for, which problem it solves, and what happens after contact.

The page should also match the intent of the traffic. A person looking for instructions does not have to be ready for a sales call, and a person looking for a contractor does not want to wade through a generic article to find the service scope. Linking informational content to service pages is helpful, but it does not replace a separate, well-described offer.

Review the first screens of the most important pages: without scrolling, is it clear what the company does, for whom, and where to go next? Does the language match the words customers use for the problem, rather than only internal names?

CTA and trust

A CTA does not have to be aggressive, but it must be concrete. “Contact us” is useful when it is clear what the conversation is about. Messages that describe the next step often work better, for example “Describe the project”, “Book a scope call” or “Ask about availability”. The CTA should be visible where the user decides, not only in the footer.

Lack of trust has a similar effect to a weak CTA. Depending on the industry, a visitor may need to see the team, the process, experience, examples of scope, company details, contact rules or answers to doubts. Do not invent claims or publish testimonials without consent. Specific, credible information is better than a generic slogan.

Mobile and forms

A large share of visits happens on a phone, so start diagnosis on a real device, not only a browser simulation. Check whether the header hides content, the menu can be used with a thumb, the phone number is tappable, buttons are reachable, and the form does not require pinch-zoom.

Speed matters, but the whole diagnosis should not collapse into a single lab score. What matters is real experience: whether key copy and the CTA appear quickly, whether images shift the layout, and whether scripts block basic interaction. A wider explanation of slow loading is in slow company websites.

The form should ask for a minimum of data at the first step, use clear labels, and show a send confirmation. Also check delivery: a working interface does not guarantee that the enquiry reached the inbox or CRM.

Measurement

Before you conclude there are “zero enquiries”, verify measurement:

  1. Does the form event count a successful send, or only a button click?
  2. Does the cookie consent setup block analytics without you noticing gaps?
  3. Are email / phone enquiries outside the form recorded at all?
  4. Are you comparing the same period and the same conversion definitions?

Sometimes “no enquiries in the report” means a broken configuration, not a lack of customers. An end-to-end test submission is mandatory.

SEO and analytics

SEO content is useful when it answers real questions from people who may later need the offer. Writing articles on random popular topics can grow traffic without growing valuable conversations. For each page, define intent: informational, comparison, local, service or navigational. More on the visibility foundation: a pretty site is not enough.

Technically, confirm that key pages are indexed, internal links are correct, and there are no accidental blocks or 404s. Google's get on Google guidance helps you understand what a search engine must be able to find and read.

Redesign

Redesign makes sense when layout, copy and components actually make the offer hard to understand or hard to use on a phone. It does not automatically fix:

  • traffic from mismatched keywords;
  • an offer the company cannot describe;
  • a sales process where nobody picks up enquiries;
  • missing measurement;
  • hosting or indexing problems.

Diagnose first, then decide: fix the path, modernise, or build a new site. The comparison new site or modernisation helps.

Diagnosis plan

  1. Define what counts as an enquiry and where it should be recorded.
  2. Check channels, entry pages and devices instead of only total traffic.
  3. Walk the key path as a customer on phone and desktop.
  4. Compare the promise of the ad, search result or referral with the landing page.
  5. Collect questions from sales and support to see what the site is missing.
  6. Check forms, notifications, analytics and technical indexing.
  7. Ship a few high-impact changes and re-check the data.

Priorities

Do not change the site from a random list of suggestions. Collect problems in one place and for each write: who it affects, which page, which step it blocks, how it can be verified, and who owns the fix. Then score impact versus effort. A broken form on the main service page outranks footer cosmetics, even if the latter is easier to spot in a review.

A good order is: remove blockers, then clarify the offer, then polish messaging. Blockers include a broken form, a wrong phone number, a page unusable on a phone, unreadable contrast, an error with no next step, or an unsafe redirect. The second group is information gaps: missing service scope, missing audience, unclear collaboration process, or a mismatch between the ad and the page. Only once those are in order should you test button copy, section order or extra materials.

Talk to the people who receive enquiries. Sales, support and people who run first meetings know which questions appear before a decision and which contacts turn out to be a mismatch. Write down the wording, but do not publish confidential details. If clients keep asking about the operating area, minimum scope or sequence of work, that is a signal to update the site, not only to write a better email reply.

Channel consistency also matters. A person looking for a specific service should land on a service page, not a blog post that only mentions the topic. An article can help earlier in the journey and should link naturally to the offer. A visitor from a local campaign must recognise the location or area of work. A referral from a partner needs a page that confirms competence and how to get in touch. These paths do not require a separate page for every user, but they do require a deliberate architecture.

Before you change anything, record the baseline: whether the form works, how many confirmed submissions there are, which pages lead to contact, whether there are mobile bugs, and which questions appear in conversations. After launch, watch the data for a reasonable period, allowing for seasonality and small sample sizes. Do not conclude from a button click when there is no form success. At the same time, do not wait for a perfect report before fixing an obvious functional bug.

If the problem is still unclear, run a controlled review with someone outside the project. Ask them to find a specific service and get in touch with no hints. Watch where they stop, but do not immediately explain what a section “was supposed to mean”. That simple test often reveals the gap between company language and customer language. After the diagnosis, pick a small set of changes, assign owners and return to measurement.

30-day plan

In week one, fix operation and measurement: forms, tappable contact, the worst mobile issues and analytics events. In week two, tighten headlines, offer scope and CTAs on the most important pages. In week three, add missing trust elements, answers to real concerns, and links between content and services. In week four, review data, test submissions and user behaviour, then set the next priority.

For foundation work see website development or tell us what your site needs. Before accepting a build, use the acceptance checklist.

Related materials