Writing microcopy that reduces friction, not just fills space
Microcopy is the small interface text — button labels, hints, error messages, confirmations — that quietly decides whether people finish what they started. Write it specific, human and reassuring, and most friction disappears without touching your layout.
Most redesigns focus on the big things: layout, imagery, the headline. Microcopy rarely gets a second look, which is strange, because it's the text people actually read at the exact moment they decide whether to continue or bail. A button that says "Submit" instead of "Get my quote" is a small thing. Multiply it across every form, error and confirmation on your site and it adds up to a meaningfully worse experience.
Microcopy is cheap to fix. You don't need a redesign, a developer, or a new template — you need fifteen minutes and a willingness to reread your own site the way a stranger would.
What counts as microcopy
Microcopy is every small piece of interface text that isn't a headline or a paragraph: button labels, form field hints, placeholder text, error messages, success confirmations, tooltips, empty states, and the fine print under a checkbox. None of it is long. All of it is read at a decision point, which gives it outsized influence relative to its length.
| Location | Example | Job it does |
|---|---|---|
| Button label | "Start my free trial" | Sets the expectation for what happens next |
| Form hint | "We'll only use this to send your quote" | Removes a reason to hesitate |
| Error message | "That email doesn't look complete" | Tells the visitor exactly what to fix |
| Success message | "You're in — check your inbox in a minute" | Confirms the action worked and what's next |
| Placeholder text | "jane@yourcompany.com" | Shows the expected format before they type |
Generic microcopy creates hesitation
The default text most forms ship with is vague on purpose — it was written to work everywhere, which means it's tailored to nowhere. "Submit" doesn't tell anyone what they're submitting or what happens after. "Invalid input" doesn't tell anyone what was wrong or how to fix it. Vague copy doesn't stop people cold, but it adds a half-second of doubt at exactly the moment you need none. Doubt at a decision point is where conversions leak.
Rewriting buttons: name the outcome, not the mechanism
"Submit" describes the mechanism — a form gets sent to a server. Nobody cares about the mechanism. They care about the outcome. Naming the outcome on the button removes ambiguity and, often, adds a small reassurance at the same time.
| Generic | Specific | Why it's better |
|---|---|---|
| Submit | Get my free quote | States what actually happens next |
| Sign up | Start my 14-day trial | Sets expectations and reduces perceived risk |
| Send | Send my message | Confirms the action in the visitor's own words |
| Continue | Continue to payment | Removes uncertainty about what step is next |
| Download | Download the checklist (PDF) | Confirms format before the click, not after |
Rewriting form hints: remove the reason to hesitate
People pause before filling in fields that feel risky to share — email, phone number, payment details. A one-line hint next to the field can remove that hesitation before it forms. The best hints answer the unspoken question a visitor is already asking themselves.
- 1Identify the unspoken questionNext to a phone number field, the question is usually "will I get spam calls?" Next to an email field, it's "will this get sold to a list?"
- 2Answer it in one short line"We'll only call if there's a question about your order" answers the fear directly instead of ignoring it.
- 3Keep it under the field, not above itHints read right before the input are more likely to be seen than instructions buried at the top of a long form.
- 4Skip the hint if the field is truly optionalFor genuinely low-risk fields, a hint just adds visual noise. Save hints for the fields people actually hesitate on.
Rewriting error messages: say what's wrong and how to fix it
"Invalid input" is the single worst phrase in interface design. It tells the visitor something is wrong without telling them what, which means they're now guessing at a fix while also feeling mildly blamed for a mistake they can't identify. A good error message names the field, states the problem plainly, and — where possible — shows the expected format.
| Vague | Actionable |
|---|---|
| Invalid input | That phone number needs 10 digits |
| Error | This field can't be empty |
| Something went wrong | That email is missing an @ — mind checking it? |
| Field required | We need your zip code to calculate shipping |
Confirmations and empty states deserve the same care
The moment right after someone completes an action is a trust-building opportunity that gets skipped constantly. "Thank you" tells someone their action registered. It doesn't tell them what happens next, and that gap is where anxiety creeps in — did the email actually send? Will someone actually call back? A confirmation that names the next concrete step closes that gap. The same logic applies to empty states: a search with no results, or a dashboard with nothing in it yet, is a place to guide the visitor forward, not just report an absence.
Repeat this on every button, hint and error on the page — it's the whole method.
How to audit your own site in one pass
Open your most important form or checkout flow and read every piece of small text out loud, in order, as if you'd never seen the page before. Anywhere you'd naturally pause and think "wait, what does this mean" is a microcopy problem. Anywhere the text could apply to literally any website is generic and worth sharpening. This takes under twenty minutes for most sites and needs no design or development help — it's a writing pass, not a rebuild.
- ✓Microcopy is the small text — buttons, hints, errors, confirmations — read at decision points.
- ✓Generic copy like "Submit" or "Invalid input" adds hesitation exactly when you need none.
- ✓Name the outcome on buttons instead of describing the mechanism.
- ✓Answer the unspoken question a field raises, right next to that field.
- ✓Error messages should say what's wrong and how to fix it — never just "error".
- ✓Confirmations should state the next concrete step, not just say thanks.