Lead Form Best Practices: Fields, Spam, Thank-You Page

Why a lead form beats "call us"

A phone number on a landing page asks the visitor to do the hardest thing first: talk to a stranger, right now, during business hours. A lead capture form asks for thirty seconds and lets the visitor stay in control. That is why a remodeling contractor with a form hears from the homeowner who browsed at 11 p.m., and one with only a phone number does not.

The form also gives you a record: every submission arrives with a timestamp, the page it came from, and the campaign that brought the visitor, if you tag your links. After a month you can see which campaign produces contracts and which one produces "just curious" calls; conversion tracking in GA4 is built on that record. Keep the phone number anyway, for the burst pipe and the toothache, as the alternative for people who cannot wait.

Contact form fields: the minimum, and when more earn their place

The minimum is two fields: a name and one way to reach the person. Ask for the channel you will actually use: a dental clinic that confirms appointments by text asks for a phone number, a bookkeeper who sends proposals as PDFs asks for an email. Asking for both when you need one loses submissions for no reason.

Every extra required field gives a share of visitors a reason to stop, and the more personal the question (budget, address, company size), the larger that share. The trade is fewer leads for better-sorted leads, worth making only when the answer changes what you do next.

Two habits keep forms short. Make everything after the contact field optional, and say so in the label. And move qualifying questions to the reply: the contractor selling a $30,000 kitchen remodel does not need the square footage in the form, because the estimator asks on the first call. If you truly need more answers, split the form into two steps, easy questions first and the contact second.

Where to place the form on a landing page, and how many

A landing page has three natural places for a form, and each catches a different visitor. The first screen catches people who arrived knowing what they want, usually from a search ad. A full form there competes with the headline, so use two fields and a button, or a button that scrolls down. The middle, after cases and reviews, catches people who needed convincing. The end catches the careful readers who went through the price and the FAQ; this is the main form, with the headline, the "what happens next" line, and the privacy note. The landing page structure guide shows where each block sits.

Two or three forms per page is normal; ten is noise. The alternative is one main form and every button on the page scrolling to it. Whatever the count, keep the fields, the button text, and the promise identical everywhere: "Get a quote" in the header and "Contact us" at the bottom read as two different offers.

Headline and button copy: what to write instead of "Submit"

The form has three pieces of text: the headline says what the visitor gets, the button says the action in the visitor's words, and one line under the button says what happens next.

The headline restates the offer as a next step, not a form title: "Contact form" describes the widget, "Get a fixed-price estimate for your kitchen" describes the reward, and for a clinic, "Book a consultation this week." A number (minutes, days, dollars) makes it credible.

The form button text finishes the sentence "I want to…". "Submit" and "Send" describe what the button does to the data; "Get my estimate," "Book my visit," and "Send me the price list" describe what the visitor gets. In our observation, this swap is the cheapest form conversion rate improvement there is: two minutes of work that never hurts. Keep it under four words so it fits on a phone.

The line under the button removes the last doubt: "We'll call you back within an hour on business days, no sales pressure." Say when and how, and promise only what you keep.

Consent and the privacy notice

A short line with a link to your privacy policy covers the ordinary case of using the contact to reply: "By sending this form you agree to our privacy policy." If you plan to send marketing emails or text messages afterward, add a separate, unchecked checkbox for that: a pre-checked box is not valid consent under GDPR and UK rules, and a bad practice everywhere else. Keep the wording plain, and if your visitors are in the EU, the UK, or a US state with its own privacy law, ask a lawyer whether it needs specifics.

Spam protection for web forms that actually works

The day the page gets traffic, the form gets bots: dozens of "SEO services" and "crypto" submissions a week, with the real leads drowning in them. Three methods handle most of it without bothering a real visitor.

A honeypot is a hidden field that a person never sees, but a bot filling every field does; any submission with it filled is dropped. Rate limiting caps how many submissions one address can send in a period: a person sends one form, a script sends two hundred. Empty and junk filtering drops submissions with no contact field or with a "name" that is a URL. What gets through is occasional hand-typed spam, marked as junk and forgotten.

A CAPTCHA (the "select all the traffic lights" box, or invisible checks such as reCAPTCHA and Turnstile) stops more bots and also some people, especially on older phones and in browsers with strict privacy settings. Put it on when the first three methods are not enough, not before.

If the page is built with Pageo, all of this runs on its own: a hidden trap for bots, a limit on submission frequency from one address, and a filter for empty submissions, with nothing to configure (forms and the thank-you page). Stray spam can be marked as low quality in the leads list so it does not mix with real clients.

The thank-you page: what to write, and why analytics needs it

After the click, the form either shows a message on the same page or sends the visitor to a separate thank-you page. A message is fine for a newsletter box; for a lead form the page is better, for a reason unrelated to copy: it has its own URL.

A URL is the simplest thing an analytics tool can count. When a visitor arrives at /thanks, you mark that page view as a key event in GA4, Google Ads imports it, and other ad platforms fire their own pixel on the same URL. Without it you are counting button clicks, including the ones that ended in a validation error; with it you see the cost per lead by campaign and turn off the ads that only bring visitors.

The page itself answers "did it work, and what now?" Four lines are enough: confirm that the request was received; name the next step and its timeframe ("Sarah will call you within an hour from (512) 555-0134, so you recognize the number"); suggest what to do while waiting (look at three cases, take photos of the room); and give a phone number for the impatient. Exclude the page from search and do not link to it from the site, so nobody lands on it without submitting and inflates your conversions.

In Pageo the setting sits in Site settings → Delivery → Thank-you page: enter a page of this site, such as /thanks, or any other link; leave it empty and the visitor stays on the page and sees the form's message. On every submission Pageo also sends the generate_lead event to GA4, which you mark as a key event (analytics and goals), a second count independent of the page. The page is hidden from search with the "Show in search" switch in the indexing settings.

Where do form submissions go

The question decides whether the lead gets a reply. A submission should land in at least two places: a permanent list you can search a year later, and a notification that reaches the person who replies within minutes. The list is your record; the notification is your response time.

• The builder's inbox or a CRM. The permanent list: every submission with its date, fields, source, and campaign. A CRM adds stages and reminders; the inbox is enough for a one-person team.
• Email. The default notification: a message per lead to one or several addresses.
• A messenger such as Telegram or Slack. The fastest notification: it lands on the phone of whoever is on duty, with a sound.
• A spreadsheet such as Google Sheets. A row per lead, for the colleague who never opens the builder.
• A webhook. The form sends the data to a URL, and an automation tool (Zapier, Make, or your own script) does the rest.
• An email marketing tool such as Mailchimp. For newsletter signups rather than sales leads: the contact joins a list and a welcome sequence starts.

In Pageo every submission is saved in the Leads list of your account, with the traffic source and any UTM tags, and is sent to every channel you connect in Site settings → Delivery. Email notifications switch on in your profile; Telegram, Google Sheets, and a webhook are paid-plan integrations, as are the CRM connections (amoCRM and Bitrix24) and Mailchimp. Connect channels one at a time and save before testing; the delivery guide covers the Telegram bot token and the webhook format (a POST with the form data as JSON). The free plan caps submissions per month, so check the leads list and the plan limit before ad traffic starts.

Whatever the tools, decide who replies and by when. A lead form without a named person on the other end is a suggestion box: for a two-person remodeling company that person is the office manager; for a clinic, the front desk, with the notification on their phone.

Test the form before running ads, and the mistakes that survive the test

Before the first dollar goes to ads, submit the form yourself, from the published page, on a phone, with a note like "Test 1" in the message field. Then follow the lead to every place it should reach: list, email, messenger, analytics. A green "connected" light on a settings page says the credentials are valid, not that the lead arrives; only a submission does. Check what the visitor sees, too: the error on an empty phone field, the thank-you page, and whether its phone number dials on a tap. A draft form does not accept submissions, so publish the site first, and republish after every later change.

The test catches broken plumbing; these mistakes survive it because they are habits, not bugs:

1. No "what happens next." The visitor sends the form into silence and starts filling out a competitor's. One line under the button and a thank-you page fix it.
2. Notifications in the spam folder. The lead arrived; nobody saw it. Whitelist the sender, add a messenger channel, and check the list once a day regardless.
3. Nobody replies for two hours. By then the homeowner has talked to two other contractors. A Harvard Business Review study of lead response found that companies reaching out within an hour were about seven times as likely to qualify the lead as those that waited even one hour more.
4. Seven required fields. Each had a good reason, and together they turn away the people who would have answered all of them on the phone.
5. A CAPTCHA on day one. It went up before any spam existed and has cost real submissions every day since.

FAQ

How many fields should a lead form have?

Two to four. Name and one contact channel are the floor; a service dropdown and an optional message are the common additions. Ask a fifth question only if its answer changes who replies or what they say.

Should I ask for a phone number or an email?

The one you will use to reply. A contractor who calls back asks for a phone; a consultant who sends a proposal asks for an email. If you truly need both, make one optional and label it so.

Do I need a separate thank-you page, or is a message enough?

A message works for a newsletter box. For a lead form, a separate page with its own URL gives analytics and ad platforms a clean conversion to count and gives the visitor a place to read what happens next.

Is a CAPTCHA necessary on a contact form?

Not at first. A honeypot, a limit on submissions per address, and a filter for empty submissions stop most bots without bothering anyone. Add a CAPTCHA only if hand-typed spam keeps coming through, and use the invisible kind.

Key takeaways

• The form is the main action of a landing page; the phone number is the alternative for people who cannot wait.
• Start with a name plus one contact channel, and add a field only when its answer changes what you do next.
• A short form or a button in the first screen, the main form at the end, and the same fields and button text everywhere.
• The button says what the visitor gets ("Get my estimate"), and one line under it says when and how you will reply.
• A thank-you page with its own URL gives you a conversion to count; a honeypot and rate limiting handle spam; a real test submission before ads proves the whole path.