Microcopy: Small Words, Big Conversions

Quick Summary

• Microcopy is every small UI string: button labels, placeholder text, error messages, tooltips, empty states
• Expedia removed one field label and gained $12M in annual revenue
• MailChimp lifted CTR 18% by changing "Submit" to "Send Campaign"
• Baymard Institute (2024) found 31% of top ecommerce sites still lack live inline validation
• The principle: microcopy reduces friction by replacing user anxiety with clarity and confidence

What Is Microcopy?

Microcopy is the short, functional text woven into a user interface: button labels, form field hints, error messages, confirmation notices, empty-state prompts, tooltips, and placeholder text. It is not the headline or the hero paragraph. It is everything else, the words users read when they are deciding whether to act.

Because it is small, microcopy is routinely written last, delegated to developers, or left as placeholder defaults ("Submit", "Error", "No results"). That neglect is expensive.

Why Microcopy Moves Metrics

The Expedia $12M Field Label

Travel researcher Jared Spool documented how Expedia removed a single form field, "Company Name", from its booking flow. Users were filling it in with their bank's name instead of leaving it blank, which caused payment failures. Removing the field (and its label) recovered $12 million in annual revenue from abandoned transactions.

The copy was not wrong. The field's presence created a question users did not know how to answer correctly.

MailChimp's Button Experiment

MailChimp tested renaming their campaign send button from "Submit" to "Send Campaign." The outcome-specific label produced an 18% lift in click-through rate. "Submit" describes what the button does to a form. "Send Campaign" describes what happens to the user's work.

Baymard Institute 2024 Benchmark

The Baymard Institute's 2024 checkout usability benchmark reviewed the top 100 ecommerce sites and found that 31% still do not implement live inline validation on form fields. Users who encounter validation errors only after submitting a form abandon at significantly higher rates than users who receive field-level feedback in real time.

The Four High-Impact Surfaces

1. Button Labels

The default button label is "Submit." It is also the worst. "Submit" is system-centric: it describes what happens inside the software. Outcome-centric labels tell users what they will receive.

Michael Aagaard, a conversion researcher at ContentVerve, documented a 17.18% conversion lift by switching button copy from a generic action verb to a first-person outcome phrase. The pattern is: "Get / Start / Send / See + [what the user receives]."

2. Form Fields

Every form field has three layers of microcopy opportunity:

1. Label, tells users what to enter (never use placeholder text as a substitute for a label)
2. Helper text, explains why the field exists or what format is expected
3. Reassurance text, reduces anxiety about how the data will be used

The Expedia case above failed at layer 1. The field label was not wrong, it was present when it should not have been.

A stronger example is checkout forms that include the line "We'll only contact you about your order" beneath an email field. Bohme, a women's fashion retailer, saw measurable checkout completion improvement after adding brief reassurance strings to its email and phone fields because users were hesitant to share contact information without knowing how it would be used.

3. Error Messages

Default error messages fail on two dimensions: they are technical ("Invalid input") and they are not actionable ("Please try again"). A good error message has three parts:

1. What went wrong, in plain language
2. Why, optional but helpful
3. How to fix it, specific next step

Inline validation, showing errors at the field level as the user moves to the next field rather than after form submission, reduces abandonment. The Baymard 2024 data confirms that 31% of top sites still do not do this, which means fixing inline validation is a competitive advantage for those who add it.

4. Empty States

Empty states appear when a user has no data yet: an empty inbox, a dashboard with no campaigns, a shopping cart with nothing in it. The default response is to display nothing or a generic "No items found."

A strong empty state does two things: it explains the state and it prompts the next action.

Slack's empty channel state reads: "This is the very beginning of the [channel name] channel." It then shows a button to invite people. The copy is warm, it establishes context, and it moves the user forward.

The Decision Framework

Six Common Microcopy Mistakes

1. Using "Submit" as a default button label, it describes server behavior, not user outcome
2. Placeholder-only forms, no visible label once the user starts typing
3. Page-level error messages, showing all errors only after the user clicks submit
4. Vague error text, "Invalid input" with no explanation of what valid looks like
5. No reassurance on sensitive fields, email and phone fields without a one-line privacy note
6. Empty states that display nothing, missing the opportunity to guide the user to a next step

How to Audit Your Own Microcopy

1. Walk every form and button in your product with a fresh eye, read every label aloud
2. List every error state your product can produce, check whether each one is actionable
3. Check your empty states, do they explain context and suggest a next step?
4. Test your most important CTA button label against an outcome-centric alternative
5. Add inline validation to any form field that currently only validates on submit