Conversion and UX

Microcopy

Also called UX writing, interface copy

The small pieces of interface text — button labels, field hints, error messages — that guide a person through a task.

Quick facts: Microcopy

Category
Conversion and UX
Also called
UX writing, interface copy
Level
Intermediate
Affects
Form completion, support enquiries, trust
Where to see it
Session recordings, form analytics, your own checkout on a phone
In this article4
  1. How microcopy works
  2. Why microcopy matters
  3. Where microcopy goes wrong
  4. Getting it right

How microcopy works

Microcopy is the text nobody sits down to write: the label on a button, the hint under a phone field, the message that appears when a card is declined, the line beside a checkbox asking permission to email somebody. It is usually written last, by whoever is building the page, and it carries more weight than the paragraphs above it.

It works by removing doubt at the exact moment doubt appears. A visitor about to type their number wonders who will ring them and when. A visitor about to submit wonders whether this commits them to anything. A visitor who has just seen an error wonders whether their details were lost. Each of those questions is answered, or left hanging, by a handful of words in the space where the question occurs.

Why microcopy matters

The end of a journey is where the expensive traffic already is. Somebody who has read the page, accepted the price and started the form has cost you everything a click costs; losing them to a vague button label is the most wasteful kind of loss there is. Microcopy is also the cheapest thing on a site to change, which makes the ratio of effort to result unusually good.

It carries the brand more honestly than the headline does, too. Anybody can sound helpful in a hero section. How a business speaks when something has gone wrong — a failed payment, an out-of-stock item, a form that timed out — is what people remember, and it is written entirely in microcopy.

Where microcopy goes wrong

Generic labels are the most common fault. A button marked Submit describes what the software does, not what the person gets; Send my enquiry or Get the quote tells them what happens next. Error messages written for developers do the same damage in reverse, telling somebody their input is invalid without saying what a valid one looks like.

Then there is microcopy that manipulates: a decline option worded to make people feel foolish, consent hidden in a pre-ticked box, an urgency line that is not true. These are dark patterns, and they buy a short rise in completions at the cost of complaints, refunds and refused chargebacks later. Missing microcopy is a fault of its own — a phone field with no note about format, on a site taking numbers from several countries, generates support work every day.

Getting it right

Write the questions before the words. Walk the form as a stranger and note every point where you would hesitate, then answer each hesitation in the smallest number of words that will do it. Say what happens after the click, who sees the data, how long a reply takes and what a field expects.

Keep it specific and keep it plain, particularly where visitors are reading in a second language. Test the wording on somebody outside the business, and treat this as part of the writing job rather than a design detail — the same care that goes into copywriting for the page belongs on its buttons. Removing a single confusing label often does more than a redesign, because it removes friction at the point of decision.

Do and do not

Do

  • Label buttons with what the person receives
  • Say who will contact them and how soon
  • Explain in errors what a valid entry looks like

Do not

  • Leave a theme's default placeholder text in place
  • Word the decline option to shame the reader
  • Write error messages in developer language

Questions people ask about this

What should a form button actually say?

Say what the person receives, not what the system does. Get my quote, Book the call and Send my enquiry all describe an outcome; Submit describes a database operation. Where a next step follows, name it, so the label sets an expectation rather than a mystery. Keep it short enough to fit on a phone screen without wrapping.

Does microcopy affect SEO?

Not directly, in the sense that button labels are not ranking factors. It affects SEO indirectly, because a page that fails people is a page they leave quickly and rarely link to or recommend. The clearer benefit is commercial: better microcopy raises the share of existing visitors who finish what they started.

Who should write the microcopy on a site?

Whoever knows what happens after the click, working with whoever builds the screen. In small businesses that is often the owner, and that is fine, because the owner knows how quickly the phone gets answered and what the sales conversation is like. Leaving it to placeholder text in a theme is the outcome to avoid.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.