Website traffic but no leads: check the form

A stranger who finds a service site wants one thing first: a sense of the price and whether the firm handles their job. A contact form asks for a name, a phone number, a job size and a timeline before it returns anything. Each field is a small refusal point. A dropdown without the right option forces a wrong answer or no answer at all. A required phone field makes a visitor decide whether they will be called. The visitor who cannot finish the form sends no message, and nothing in the lead count shows that a stranger almost wrote to you.

• Form views against form submits for the same days: where do the two numbers split?
• Required fields: does the form ask for a phone number before a visitor can ask a question?
• Dropdowns: does every answer a stranger could give have an option, including not sure?
• Confirmation message: does it show on a phone without scrolling, and say what happens next?
• Lead inbox: does a test message arrive the same day, and not in spam?

A lead form has three counts that should match and often do not: form starts, form submits and messages that reach your inbox. If your tools record starts, a visitor who starts and never submits is stuck inside the form, so the problem is a field or a step. A visitor who submits and never shows up in the inbox is failing after the form, in the email routing, the spam filter or an address that no longer exists. A visitor who never starts the form has not decided to write yet, so the problem sits on the service page: the price, the proof or the next step is missing.

Each required field is a question the visitor has to answer before they have asked theirs. A budget dropdown with no range that fits a small job, a timeline for someone who has not decided yet, or a company size on a form for a homeowner each stop someone who cannot answer truthfully. Some forms make it worse with a required phone number before the visitor has asked anything. Walk the form as a stranger would, and for each field ask whether they could answer truthfully at that moment. Every field that fails that test should be optional, moved after the first reply, or given a not sure option.

Once the form sends, the visitor expects two things: a message on screen that says it worked, and an email back. The first can fail quietly. A confirmation that appears below the fold on a phone looks like nothing happened, and the visitor presses send again. The second fails in the mail system: a reply address that bounces, a sender that spam filters catch, or an inbox nobody reads. Send a test submission from a phone to an address you control, then check the spam folder and the arrival time. A simulated visitor can confirm the form submitted and showed its confirmation, but the message goes to the inbox the form uses, so check that inbox yourself.

Why no signups

A new service, a new area or a new form field adds a question the stranger has to answer. A field that looks harmless to the owner can stop a stranger who does not know their own answer. Rerun a simulated visitor through the form after each change, and check the confirmation on a phone and your lead inbox each time, since a form that sends without an error can still reach nobody.