When people talk about microcopy they usually think of a button label or an error message. UX writing is that same craft applied to the entire website: what each menu section is called, how a form step is explained, what the site says when something goes wrong, what tone it uses when everything is fine. It is design, done with words instead of pixels, and it determines whether a visitor understands at a glance what to do next or hesitates and leaves.
Why words are a design decision, not just a writing task
It is easy to assume the "text" gets decided afterwards, once the visual design is already locked. In practice, that separation is exactly what causes most problems: a button designed first and filled in afterwards with the word "Submit" because it fit, instead of thinking from the start about which exact word reduces the user's uncertainty at that specific moment. "Submit" says nothing about what happens next. "Book my free consultation" does, and that nuance changes how many people click.
Good UX writing gets thought through alongside the visual design, not after. When a designer and a writer (or the same person wearing both hats) work together from the initial sketch, the result is a flow where every word has a reason to exist, not a gap to be filled.
Clarity before cleverness
It is tempting to want to sound witty in a button or heading, and sometimes it works, but the general rule in UX writing is that clarity almost always beats cleverness. If a user has to stop and think about what a clever line means, you have already lost some of the momentum that was carrying them toward acting. "Start free" communicates faster than a punchy slogan, however charming that second option sounds in an internal meeting.
Tone should match who you are, not who you wish you were
An accounting firm should not sound like a dating app, and a skate shop should not sound like a law office. The common mistake is copying the tone of an admired brand (usually a large one with a very different budget) without asking whether it fits your own business and, above all, what the real customer expects to find. A tone misaligned with expectations creates a vague sense of distrust, even if the visitor cannot pinpoint exactly why.
Error messages are an opportunity, not a formality
"Error 400" or "Invalid field" are messages that inform a developer, not a customer. A good error message explains what happened in human language ("That phone number looks incomplete, could you check it?") and, when possible, how to fix it. The forms that convert worst are usually exactly the ones that punish the user with technical jargon right at the moment they were about to complete the action.
Empty state copy matters more than it seems
When a customer opens their private account for the first time and has no orders, invoices or history yet, the screen they see at that moment (the so-called "empty state") is a chance to guide them toward the next step, instead of simply showing a blank space with a sad icon. "Your orders will appear here once you place the first one. Want to browse the catalogue?" does more work for conversion than any banner.
Terminology consistency: do not call the same thing "basket" on one page and "cart" on another
It sounds like a minor detail, but switching terms for the same thing (basket on one page, cart on another; "account" in one place, "profile" in another) creates unnecessary doubt: is this the same thing or something different? Keeping your own glossary, even an informal one, of two or three key words and using them consistently across the site avoids that invisible friction.
How to start auditing your own website's UX writing
A simple, free exercise: walk through your website as if you were a new customer who knows nothing about your business, and on every screen ask yourself "what am I supposed to do here, and does the text tell me clearly?" Note down every button, heading or message that makes you hesitate even for a second. That list, even if it only has ten items, is often more valuable than a full visual redesign.
How to review UX writing as a team without it turning into an endless debate
Reviewing copy as a group can easily degenerate into an endless argument over personal taste, with everyone proposing their preferred version with no objective criteria to settle the conversation. It is more productive to define two or three clear criteria in advance (clarity, brevity, consistency with brand tone) and evaluate each proposed text against those specific criteria, instead of simply asking the group "which one do you like best" with no shared frame of reference.
UX writing in confirmation messages: the customer's moment of highest attention
Right after completing an important action (a purchase, a booking, submitting a form), the customer pays more attention than at almost any other point in their visit, because they want to confirm everything went well. That confirmation message is a wasted opportunity on most websites, which settle for a generic "Thanks" when they could reinforce trust with useful information: what happens now, when they will hear back, who to contact if something looks off.
Adapting tone to the stage of the relationship with the customer
Tone does not have to be identical at every touchpoint. A first welcome message can afford a bit more warmth and enthusiasm than a notification about a technical problem, where the priority shifts to clarity and reassurance above everything else. Thinking about tone based on the customer's likely emotional state at each moment, not just the brand's general personality, noticeably improves how each message is perceived.
The cancel or back button: copy that often gets neglected
UX writing attention usually focuses on positive action buttons (buy, confirm, submit), leaving cancel or back buttons aside, which often keep the system's generic default text. Yet this button matters just as much: a blunt "Cancel" can feel punitive right when the user simply wants to double-check something, while text like "Go back without saving" clarifies exactly what will happen, avoiding the anxiety of losing something by accident.
Legal and consent text: clarity without losing validity
Text related to legal terms or data consent is usually written in a register very different from the rest of the website, full of legal jargon necessary for the document's validity but incomprehensible to most users. Adding, alongside the full legal text, a brief plain-language summary of what that consent actually involves improves real understanding without compromising the underlying document's legal validity.
How to involve customer service in reviewing UX writing
The customer service team has, by virtue of their position, direct knowledge of which texts generate the most confusion, because they are the ones receiving the enquiries that confusion creates. Involving them periodically in reviewing key website copy (forms, error messages, confirmations) brings a perspective grounded in real data that the design team, without that direct contact, can hardly replicate on its own.
Frequently asked questions
Is UX writing the same as copywriting?
They are related but have different goals. Copywriting aims to persuade and usually lives in sales copy (ads, landing pages). UX writing aims to guide and clarify, and lives inside the product or website itself: buttons, forms, menus, system messages.
Do I need to hire someone who specialises in UX writing?
For a small business, a dedicated role is usually not necessary. It is enough for whoever designs or develops the website to keep these principles in mind, or to bring in a writer with a usability eye for a one-off review before launching major changes.
Do short pieces of text really affect conversions?
Yes, measurably. Changing a button's wording or clarifying an error message are among the cheapest adjustments there are, and in A/B tests they often move the conversion needle more than their implementation cost would suggest.
How do I choose the right tone for my website if I have no writing experience?
Start by describing your ideal customer with three adjectives and ask yourself how you would speak to them in person if they were standing in front of you at the counter. That register, adjusted to read well in writing, tends to be a more honest starting point than copying another brand's tone.
Does UX writing also apply to the automated emails my website sends?
Yes, and it is one of the most neglected areas. An order confirmation email with a generic subject line and a cold body copy is a missed opportunity to reinforce trust right when the customer is paying the most attention to your brand.
What is an "empty state" and why should I care?
It is the screen a user sees when there is no content to show yet (an empty order history, a search with no results). Designing it with useful text instead of leaving it blank turns a potentially frustrating moment into a chance to guide the next step.
How do I objectively evaluate whether a piece of UX writing is good?
By checking whether it meets three basic criteria: whether a new user understands what to do without hesitating, whether it uses the vocabulary the customer themselves would use (not internal jargon), and whether it is consistent with the rest of the website's copy. If it meets all three, it is probably good copy.
Should error messages always include a solution?
Whenever possible, yes. A message that only reports the problem with no suggested next step leaves the user stuck; even a partial suggestion ("try checking the phone number format") reduces frustration considerably compared to a plain "invalid field."
Is it worth customising cancel or back buttons too?
Yes, even though they are often neglected. Clear text on these buttons ("Go back without saving" instead of a generic "Cancel") reduces the user's anxiety about exactly what will happen when they press it.
How can the customer service team help improve the website's UX writing?
By providing direct information about which texts generate the most enquiries or confusion, since they are the ones receiving those doubts firsthand. Involving them in periodic reviews of key copy brings a perspective the design team does not always have on its own.