Web Copywriting
Microcopy: The Small Words That Decide Whether a Form Gets Filled
Buttons, field labels, error messages and empty states are written last, by whoever is nearest, and they carry more of the conversion than the paragraphs above them.
Most website copy projects cover headlines, body sections and calls to action, then stop. The words nobody was assigned — the button, the field label, the error that appears when something goes wrong, the screen after the form — get typed by whoever built the page. Those are the words a visitor reads at the exact moment they decide whether to continue.
Buttons Should Name the Outcome
Submit describes what the software does. Get started describes nothing at all and quietly raises the question of how much is being started. What reduces hesitation is naming the result: send my brief, book a 20-minute call, see the price.
The useful check is whether the label would still make sense read out of context, with no surrounding page. If it would not, the button is relying on the paragraph above it, and plenty of readers arrive at the button without having read that paragraph.
Where a commitment sounds larger than it is, the line under the button matters as much as the button. No card required, or takes about two minutes, answers the objection the label itself cannot.
Labels Should Say Why You Are Asking
Every field that is not obviously necessary triggers a small calculation about what you intend to do with the answer. A phone number field on a page that promised an email reply is the classic case, and it costs completions from people who would otherwise have been in touch.
A few words solves it. Phone, only if you would rather we called. Budget range, so we can tell you quickly whether we are a fit. The information is unchanged; the reason for asking is now visible.
- Label above the field, not inside it: placeholder-only labels vanish the moment someone types and are harder to use with a screen reader.
- Mark what is optional, not what is required: on a short form, fewer asterisks read as a shorter form.
- Show the format before it is wrong: a hint under the field beats an error after it.
- Say what happens to the data: one line near the submit button, particularly on anything resembling a signup.
Errors Should Say What to Do
Invalid input tells a reader they have failed without telling them how to stop failing. The three things an error message needs are what went wrong, which field, and what a correct value looks like — and the tone should not imply the visitor was careless, because most errors are the form's fault rather than theirs.
Server-side failures deserve particular care. When a submission does not go through, that is the point at which someone gives up on contacting you entirely, so the message should offer the alternative route: an email address, in the message itself, spelled out.
Confirmation screens are the most wasted surface on most websites. Thank you, we will be in touch tells the reader nothing new at the one moment they are guaranteed to be paying attention. Repeat the response time, say what to look for, and give a fallback if it does not arrive.
Empty States Are Onboarding
Any page that can be empty before someone uses it — a dashboard, a saved list, a search with no results — is showing its least helpful version to its newest user. No results found is a dead end; no results for that term, try a broader one or browse the categories is a route forward.
Write It With the Page, Not After It
Microcopy written separately drifts. A page arguing that the first conversation is relaxed and there is no obligation, ending in a button marked Submit Request, is not one voice — and readers register the mismatch without being able to name it.
The practical fix is to list every string on the page before writing: headings, body, button, labels, hints, errors, confirmation. It takes ten minutes, and it makes the smallest words the responsibility of whoever is responsible for the rest.
Contact forms are where this pays back fastest — see what to put on a contact page. Our website copywriting service treats buttons, labels and confirmations as part of the page rather than as leftovers.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
The small functional text on a page: button labels, form field labels and hints, error messages, empty states, confirmation screens and tooltips. It is usually written by a developer or designer as placeholder text and then never revisited.
It changes them more reliably than headline tweaks do, because the button is the moment of commitment. A label naming what happens next removes the uncertainty that causes hesitation — the effect is small in percentage terms and lands on every visitor who gets that far.
Whoever writes the rest of the page, and at the same time. Microcopy written separately drifts in tone and contradicts the page it sits on — a page promising a relaxed, no-pressure conversation with a button reading Submit Request is a common example.