The short answer
If people visit but rarely get in touch, the cause is usually one or more of four: traffic quality (not buyers, or early in research), offer clarity (unclear who you help and why you), page usability (hard next step, awkward on phones, long form) or form reliability (messages never arrive). A redesign helps the second and third, not who visits, and can worsen the fourth if untested. Diagnose first.
Start with the cheapest check: does your form actually work?
Forms often fail silently: messages go to an old mailbox, get blocked as spam or break after a plugin update, while the visitor still sees "Thank you". Test it today:
- Submit twiceFrom a phone and a computer, using an outside address.
- Check arrivalRight inbox, not spam, all fields intact.
- Check recipientStill at the organization, and checking that inbox?
- Compare recordsIf the form service keeps submissions, match them against email.
A personal email works as the outside address. 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?
A page ranking for a broad question ("what is an ERP?") draws students and researchers as well as buyers; visits mostly from another country may not suit a local service; a campaign burst may be curiosity clicks.
How to check: in analytics, see landing pages and sources (search, social, referral, direct); in Google Search Console, whether queries are buyer phrases or general information searches. Compare landing pages with pages that lead to enquiries: often a few do nearly all the useful work.
What it tells you: mostly informational visitors means linking those pages to a clear next step, not more traffic. If buyers do not find you at all, that is a search and content question; design will not help.
2. Offer clarity: can a visitor tell what you do in ten seconds?
Show your home and main service page to someone who does not know your business for about ten seconds, then ask:
- Who is this company for?
- What does it do?
- Where does it work?
- What should I do next?
If they hesitate, the offer is not clear enough. Common causes:
Generic headlines
"Innovative solutions for your business" could belong to anyone.
Unexplained service lists
A menu of technologies shows what you know, not the problem you solve.
No sign of fit
Visitors want to know you work with organizations like theirs, their size, their area.
Vague superlatives
Unverifiable statistics and superlatives make careful buyers more sceptical, not less.
Google's guidance on helpful, people-first content agrees: pages answering people's actual questions serve visitors and search engines better than pages written to rank.
3. Page usability: is the next step easy?
Interested visitors still leave when the next step is awkward. On a phone, check:
- A visible way to get in touch on each service page, not only in the footer.
- Fast loading and settling. Google's Core Web Vitals give reasonable targets for loading, responsiveness and visual stability.
- A short form. Every extra required field loses some people: ask for what you need to reply.
- Keyboard and screen reader use. Visible labels and clear errors make forms easier for everyone (WCAG 2.2).
- Helpful errors that say what to fix, next to the field.
4. Form reliability: what happens after "Send"?
Beyond the basic test, a well-built enquiry form should:
Save first
Store each enquiry before showing success, so a failed email loses nothing.
Honest errors
A real message if something fails, not a false "Thank you".
No duplicates
A double click does not submit the same enquiry twice.
Fair spam filtering
No puzzles that exclude some users.
A checkable record
Compare it against what actually arrived.
A worked example (hypothetical)
A fictional physiotherapy clinic in northern Ontario 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 North America. Few visits reach the service pages.
- Clarity: the 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.
Its 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 makes sense when the site cannot be edited without a developer (so content stays out of date), the platform is unsupported or insecure, the page structure itself is the problem (services buried or merged into one page), or the mobile experience cannot be fixed without rebuilding templates. Our website redesign scope and cost guide explains what to decide before asking for quotes.
Checklist: diagnose low enquiries in an afternoon
Form reliability
- Form submitted from phone and computer; both arrived in the right inbox.
- The recipient still works here and checks that inbox.
- Submissions are stored somewhere besides email, and the two lists match.
Traffic quality
- Listed the ten top landing pages and where visitors come from.
- Search Console queries checked; they include phrases a buyer would use.
- Identified which pages actually lead to enquiries.
Offer clarity
- In ten seconds, a stranger can say who, what, where, next step.
- Each service page explains the problem it solves and who it suits.
- Unverifiable claims and generic slogans have been removed.
Usability
- Every service page has a visible next step.
- Key pages load and settle quickly on a phone.
- The form asks only for what is needed to reply.
- The form works with a keyboard, and errors are clearly explained.
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.
- Creating helpful, reliable, people-first content, Google Search Central
- SEO Starter Guide, Google Search Central
- Web Vitals, web.dev
- 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.