LanderKit

Templates written in French — fully translatable in minutes

Form microcopy: the small words that change completion rates

Published on 24 July 2026 · 7 min read

There is a lot of talk about a form's field count and the choice between one step or several. Those are important structural decisions, but they don't tell the whole story: two forms that are structurally identical can show very different completion rates depending on how they are written. That writing — labels, placeholders, contextual help, error messages, button text — has a name: microcopy. It's the least visible part of a form in a mockup, and the most decisive one at the moment a visitor hesitates, makes a mistake, or closes the tab.

Label or placeholder? The trap of the field that disappears

The most common choice — and the most problematic one — is to skip a label above the field entirely and rely on a greyed-out example text inside it (the placeholder). The form looks cleaner, but the moment the visitor starts typing, the hint disappears: if they come back to that field a few seconds later, or fill the form out of order, they no longer know what was being asked. This is a usability problem that hits mobile visitors especially hard, since it's easy to jump between fields, and screen-reader users, since a placeholder doesn't carry the same semantic weight as a real label for assistive technology — a point covered in our article on landing page accessibility. The safest rule remains a label that stays visible above the field at all times, with a placeholder reserved for a format example ("jean.doe@email.com") when the expected format isn't obvious.

Help text: before the error, not after

Contextual help text — a discreet line under the field, shown before any input — prevents an error rather than fixing one after the fact. "We never share your email" under an email field, or "format: (555) 123-4567" under a phone field, answer a hesitation before it turns into an abandoned form. This matters most on fields asking for sensitive or unusual information: on the property valuation template, stating right under the address field that the estimate is free and comes with no obligation removes an objection the visitor might never have voiced out loud, but that would have made them close the tab.

Error messages: what the research shows

Error messages are the most studied piece of form microcopy. A study by Bargas-Avila and colleagues, published in 2007 in the journal Interacting with Computers, compared two ways of flagging an input error: showing it immediately, as soon as the visitor leaves a badly filled field, versus waiting for full form submission to list the fields to fix. Across two experiments (77 and 90 participants), immediate validation — despite being the practice recommended by the ISO standards of the time — performed worse: more errors made and more time spent fixing them than when feedback arrived after the whole form was completed (study on Google Scholar). The explanation is interruption: cutting the visitor off mid-input breaks their concentration, even when the interruption flags a real problem.

A broader study by Seckler, Heinz, Bargas-Avila, Opwis and Tuch, presented at the CHI conference in 2014, empirically tested a set of form design guidelines — including placing the error message right next to the affected field rather than at the top or bottom of the form — and confirmed their positive effect on error rate and completion time (study on Google Scholar). In practice, for a landing page: validate when the visitor moves to the next field rather than on every keystroke, show the message directly under the affected field, and phrase it as an instruction rather than a rebuke — "Add your country code" converts better than a plain "Invalid field".

Button text: the last line of microcopy

"Send" or "Submit" describe a technical action, not a benefit. Button text should complete the sentence "I want to…" in the visitor's head: "Get my free estimate", "Book my discovery call", "Join the waitlist". It's the same principle as any call to action — see our 12 CTA examples that convert for the full method applied to buttons outside a form.

The reassurance line under the CTA

A discreet line under the button clears the last silent objections: "No credit card required", "Unsubscribe in one click", "We never sell your data". On a contact or booking form, like the one on the coach consultant template, reminding visitors that filling out the form commits them to nothing reduces friction for someone still deciding between submitting and closing the tab. It's also the natural place for the minimal GDPR notice required by law — what it needs to contain is covered in our article on GDPR-compliant forms.

Microcopy mistakes that cost conversions

  • No visible label, only a placeholder that disappears on the first keystroke.
  • Validation on every keystroke, flagging an error before the visitor has even finished typing.
  • A generic error message ("Invalid field", "Error") that doesn't say what to fix.
  • A "Submit" button that reminds no one of the benefit or of what happens next.
  • No reassurance under the CTA on a form asking for sensitive information (email, phone, address).
  • Help text that arrives too late, only after a first mistake, when it could have prevented it.

Microcopy doesn't replace a sound form structure — field count and step breakdown still matter just as much. But with structure held equal, it's often the only lever left to gain a few conversion points without cutting anything from the form. LanderKit's templates ship with this microcopy already thought through — visible labels, contextual help, sensible validation — ready to receive your content.

FAQ

Frequently asked questions

Should a form field be validated while the user is typing, or only afterwards?

Research leans toward a middle ground: validate when the visitor leaves the field (on blur), not on every keystroke. A study by Bargas-Avila and colleagues (2007) found that immediate, character-by-character validation produces more errors and a longer completion time than waiting until the user finishes a field.

Where should an error message be placed in a form?

Directly next to the affected field, not in a summary at the top or bottom of the form. A study presented at the CHI conference in 2014 (Seckler et al.) empirically confirmed that this placement reduces error rate and completion time compared to a centralised message.

Can a placeholder replace a field label?

No, in most cases. The placeholder disappears the moment the user starts typing, which is a problem if they return to the field later or fill the form out of order — and it doesn't carry the same weight for screen readers. A label that stays visible above the field at all times remains the safest choice; the placeholder can supplement it with a format example.

Does the text on a form's submit button really make a difference?

Yes. A generic label like "Send" or "Submit" describes a technical action without reminding anyone of the benefit. Text that completes the sentence "I want to…" in the visitor's head ("Get my free estimate", "Book my call") generally converts better, on the same principle as any landing page CTA.

Read next

Related articles