Why a business website gets visits but few inquiries

The short answer

If people visit your website but rarely get in touch, the cause is usually one (or more) of these:

1. Traffic quality. The visitors are not the people who buy from you, or they are at an early stage of research.
2. Offer clarity. Visitors cannot quickly tell who you help, what you do, and why they should contact you rather than someone else.
3. Page usability. The next step is hard to find, the pages are slow or awkward on a phone, or the form asks for too much.
4. Form reliability. People do try to contact you, but their messages never arrive.

These need different fixes. A new design can help with the second and third, but it will not change who visits, and it can make the fourth worse if nobody tests the form. So it is worth finding out which problem you have before spending money.

Start with the cheapest check: does your form actually work?

It is surprisingly common for a contact form to fail silently. Messages can go to an old mailbox, be blocked as spam, or fail after a plugin update, while the visitor still sees "Thank you".

Test it today:

• Submit your own contact form from a phone and from a computer, using an address outside your organization (a personal email works).
• Confirm each message arrives, in the right inbox, not in spam, and with all fields intact.
• Check who receives it. Is that person still at the organization, and do they check that inbox?
• If you use a form plugin or service, check whether it keeps a copy of submissions. If it does, compare that list with what arrived by email.

If messages are missing, fix that before anything else. The rest of this article assumes the form works.

1. Traffic quality: are these the right visitors?

Visits are not all equal. A page that ranks for a broad question ("what is an ERP?") will attract students and researchers as well as buyers. A page visited mostly from another country may not be relevant to a local service. And a burst of visits from a campaign may be people who clicked out of curiosity.

How to check:

• In your analytics tool, look at which pages people land on, and where they came from (search, social, referral, direct).
• In Google Search Console, look at the search queries that lead to your site. Are they phrases a buyer would use, or general information searches?
• Compare landing pages with the pages that actually lead to inquiries. Often a small number of pages do nearly all the useful work.

What it tells you: if most visitors arrive for informational topics, the fix may be to connect those pages to a clear next step, not to attract more traffic. If buyers are not finding you at all, that is a search and content question, and more design will not help.

2. Offer clarity: can a visitor tell what you do in ten seconds?

A useful test is to show your home page and main service page to someone who does not know your business, for about ten seconds, then ask them:

• Who is this company for?
• What does it do?
• Where is it, or where does it work?
• What should I do next if I am interested?

If they hesitate, your offer is not clear enough. Common causes:

• Generic headlines such as "Innovative solutions for your business" that could belong to anyone.
• Service lists without explanation. A long menu of technologies tells visitors what you know, not what problem you solve.
• No sign of fit. Visitors want to know whether you work with organizations like theirs, of their size and in their area.
• Vague superlatives and unverifiable statistics, which make careful buyers more skeptical, not less.

Google's own guidance on helpful, people-first content points in the same direction. Pages written primarily for people, answering their actual questions, serve both visitors and search engines better than pages written to rank.

3. Page usability: is the next step easy?

Even interested visitors leave when the next step is awkward. Check your key pages on a phone:

• Is there a clear, visible way to get in touch on each service page, not only in the footer?
• Does the page load and settle quickly? Google's Core Web Vitals give reasonable targets for loading, responsiveness and visual stability.
• Is the form short? Every extra required field loses some people. Ask for what you need to reply, and leave details for the conversation.
• Can it be used with a keyboard and a screen reader? Accessible forms, with visible labels and clear error messages, are easier for everyone. See WCAG 2.2.
• Do error messages say what to fix, next to the field that needs fixing?

4. Form reliability: what happens after "Send"?

Beyond the basic test above, a well-built inquiry form should:

• save each inquiry somewhere before showing a success message, so a failed email does not lose it;
• show an honest message if something goes wrong, instead of a false "Thank you";
• prevent the same inquiry being submitted twice by a double click;
• filter spam without making people solve puzzles that exclude some users;
• keep a record you can check against what actually arrived.

A worked example (hypothetical)

A fictional physical therapy clinic in a mid-sized US city notices its website gets steady visits but only one or two contact requests a month. Before commissioning a redesign, it runs the checks above:

• Form test: two of three test messages arrive. The third, sent from a phone, never arrives. A plugin update had broken the form's mobile layout, and the submit button was hidden below a pop-up.
• Traffic: most search visits land on an old blog post about stretching exercises, read by people across the country. Few visits reach the service pages.
• Clarity: the home page headline says "Your partner in wellness". Test viewers could not say where the clinic is or whether it takes new patients.
• Usability: the booking link is only in the footer.

The clinic's priorities become: fix the form and test it monthly; rewrite the home page headline to say what it does and where; add a clear "Book an assessment" link on each service page; and link from the popular stretching article to the relevant local service. A full redesign is postponed until those changes have been measured.

This example is invented to illustrate the method. It does not describe a real clinic or real results.

When a redesign is the right answer

A redesign becomes the sensible option when:

• the site cannot be edited without a developer, so content stays out of date;
• the underlying platform is unsupported or insecure;
• the page structure itself is the problem, such as services buried or merged into one page;
• the mobile experience cannot be fixed without rebuilding templates.

If that is your situation, our website redesign scope and cost guide explains what to decide before asking for quotes.

Checklist: diagnose low inquiries in an afternoon

If you want a second pair of eyes on the results, tell us what you found.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

1. Creating helpful, reliable, people-first content, Google Search Central
2. SEO Starter Guide, Google Search Central
3. Web Vitals, web.dev
4. Web Content Accessibility Guidelines (WCAG) 2.2, W3C

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.