Most of the words on a website are in headings and paragraphs, and that is where most of the writing effort goes. But visitors make their decisions on much smaller pieces of text: the label on a button, the hint under a form field, the message that appears when something goes wrong. That small, functional text is called microcopy.
Good microcopy is almost invisible. It answers the question a visitor has at that exact moment, then gets out of the way. Poor microcopy creates hesitation, errors and abandoned forms. This guide explains where microcopy matters most on a business website and how to write it well.
The short answer
Microcopy is the short text that helps people use an interface: buttons, links, form labels, hints, error messages, empty states, confirmations and tooltips.
Good microcopy is:
- clear: says exactly what will happen;
- specific: “Send enquiry” rather than “Submit”;
- helpful at the moment of need: answers the question the visitor has right now;
- consistent: the same action always has the same name;
- in your voice: friendly and calm, never blaming.
Where microcopy matters most
| Place | What it does | Example |
|---|---|---|
| Buttons and calls to action | Tells visitors what happens when they click | “Get a fixed quote” |
| Navigation labels | Helps visitors find the right page | “Pricing” rather than “Investment” |
| Form labels and hints | Explains what to enter and why | “Phone (optional, if you prefer a call)” |
| Error messages | Explains what went wrong and how to fix it | “Please enter an email address, like name@example.com” |
| Confirmations | Reassures that an action worked | “Thanks, we’ll reply by tomorrow afternoon” |
| Empty states and 404 pages | Helps visitors recover | “We couldn’t find that page. Try our services or search” |
| Cookie and privacy notices | Explains choices in plain language | “Only essential cookies are used” |
Writing buttons
Buttons are the most important microcopy on a business site, because they sit at the point of decision.
- Start with a verb that describes the result: “Book a call”, “Download the price list”, “Send enquiry”.
- Be specific. “Submit”, “Click here” and “Learn more” say nothing about what happens next.
- Reduce perceived risk where it helps: “Get a free audit” or “See pricing” feel less committal than “Buy now” for a service.
- Keep it short, usually two to five words.
- Match the page. If the page promises a free audit, the button should say so.
Our guide to call to action best practices covers buttons in more detail.
Writing form labels and hints
- Always use a visible label above each field. Placeholder text inside the field disappears when people start typing, and many screen readers treat it inconsistently.
- Say why when a field might feel intrusive: “Phone, so we can call if email doesn’t reach you.”
- Mark optional fields rather than every required one, if most fields are required.
- Give examples for formats people might get wrong, such as dates or phone numbers.
See our guide to web form design for structure and layout.
Writing error messages
Error messages are where tone matters most, because the visitor is already frustrated.
- Say what happened in plain words.
- Say how to fix it, next to the field concerned.
- Don’t blame the visitor. “Please enter a date in the format DD/MM/YYYY” is better than “Invalid input”.
- Keep what they typed. Clearing a form after an error is one of the fastest ways to lose an enquiry.
The W3C’s guidance on error identification explains why errors must be described in text, not only shown with colour.
Writing confirmations
After an action, visitors want to know it worked and what happens next:
- confirm clearly: “Your message has been sent.”
- set expectations: “We reply within one business day.”
- offer a next step if it helps.
Our guide to thank-you pages covers confirmations after enquiries.
Empty states and 404 pages
An empty state is what visitors see when there is nothing to show: a search with no results, an empty basket, a page that no longer exists. These moments are easy to forget and easy to get wrong, because the default message is often technical, such as “404 Not Found” or “No items”.
Good microcopy turns a dead end into a route forward. Say plainly what happened, without blame, then offer two or three useful links: the home page, the main services and a way to contact you. A short, calm message such as “We couldn’t find that page, but these might help” keeps the visitor on the site instead of sending them back to the search results.
Consistency matters
Choose one name for each action and use it everywhere. If the button in the header says “Start a project”, the contact page shouldn’t call the same thing “Begin your journey” and the footer “Get in touch”. Keep a short list of standard labels alongside your tone of voice guidelines.
Microcopy in more than one language
Microcopy is short, which makes it easy to translate badly. A button label that fits neatly in one language may be too long in another and break the layout. A friendly phrase may sound odd when translated literally.
- Translate microcopy in context, with screenshots, rather than as a list of isolated strings.
- Allow space in designs for longer translations.
- Keep labels consistent within each language.
- Check error messages and confirmations in every language, not just page content.
Accessibility
- Links and buttons should make sense out of context, because screen reader users often navigate by a list of links. “Read more” repeated ten times is unhelpful; “Read more about website maintenance” works.
- Icon-only buttons need an accessible label, such as “Close menu”.
- Errors should be announced to screen readers when they appear.
How to test microcopy
- Read it out loud. If it sounds like a system or a legal notice, rewrite it.
- Watch someone use the page. Hesitation over a button or a field usually points to unclear words.
- Check analytics for forms with many abandoned starts.
- Review the whole journey: button, form, error, confirmation and follow-up email together.
Small wording changes can make a noticeable difference, but test them one at a time so you know what helped.
Frequently asked questions
Is microcopy the same as UX writing?
UX writing is the broader practice of writing for interfaces. Microcopy is one part of it: the small pieces of text attached to specific elements and moments.
Should buttons use first person, such as “Get my quote”?
Either first or second person can work. What matters most is clarity and consistency across the site.
How long should an error message be?
As short as possible while still saying what went wrong and how to fix it. One sentence is usually enough.
What to do next
Go through your enquiry journey from the first button to the confirmation email, and list every piece of microcopy. Replace anything generic, such as “Submit” or “Click here”, with words that describe what will happen.
When we build a site through our website design and development service, buttons, labels and messages are written and tested in every language, not left as defaults. For campaign pages, our landing pages service focuses each page on one clear action.