Quick Answer
Microcopy is the short functional text inside a product: buttons, labels, hints, empty states, error messages, confirmations and onboarding steps. It is marketing, written at the moment of use, and in most early companies nobody is accountable for it. A microcopy audit is one day of work: list every string a new user meets, group them by moment, mark each one clear, confusing or blaming, and rewrite the blaming lines first.
Open your product and read the first ten strings a new account sees. Somebody wrote them, usually an engineer, usually in a hurry, usually while thinking about the code rather than about the reader.
Nobody reviewed them, because reviewing copy is what the marketing team does to the website. So the surface people read while they are actually trying to get something done is the one surface with no editor.
That is a strange place to be careless, because a reader who is mid-task is paying closer attention than a reader who is browsing. This post covers the one-day audit, the seven moments worth reviewing first, the three ways product copy fails, and the case where rewriting it is the wrong use of the day.
How to Audit the Microcopy Nobody Owns
A microcopy audit is a single day of reading, sorting and rewriting, and it needs no budget, no redesign and no new hire. You collect every string a new user meets, sort them by the moment they appear, grade each one, and rewrite in the order that costs the reader most.
1. List Every String a New User Meets
Create an account in your own product and screenshot every screen from the signup form to the first completed task. Copy each visible line into a spreadsheet, one row per string, with a column for where it appears. Include the transactional email, because a confirmation that lands in an inbox is still your microcopy.
The count is almost always higher than the founder guessed. That gap, between what you think you wrote and what you actually shipped, is the first useful output of the day.
2. Group the Strings by the Moment They Appear
Sort the rows into five moments: signup, onboarding, activation, payment and exit. Each moment asks the reader for a different decision, so a line that reads fine on its own can still be wrong for where it sits.
Grouping also shows the gaps. An empty state with no line on it at all is a row you will only notice once the moments are laid out side by side.
3. Mark Each Line Clear, Confusing, or Blaming
Read every row and give it one of three grades. Clear means the reader knows what to do next without interpreting anything. Confusing means they have to work it out, and blaming means the line puts the fault on them.
Use one reader as the test, not a committee. If you have to explain what a line means, it is not clear, whatever you intended it to say.
4. Rewrite the Blaming Lines Before the Rest
Blaming lines cost the most, so they go first. The GOV.UK Design System states the rule plainly: in the error message, explain what went wrong and how to fix it.
Then take the confusing lines, and leave the merely ugly ones alone. A line that is plain and unlovely is doing its job; a line that is elegant and ambiguous is not.
5. Ship the Fix and Watch One Number
Pick one number before you change anything, so the rewrite has something to be judged against. For a signup error, use the share of people who get past that form. For an empty state, use the share who create their first item.
Give it two weeks and read the number honestly, including the case where nothing moved. A copy change that did nothing is still worth knowing about, because it tells you the friction was somewhere else.
Product Copy Is Marketing at the Moment of Use
Product copy is marketing because it does the same job marketing does, only later. It helps the right person understand what they are looking at, trust it, and take one more step.
What changes is the reader's state. A visitor on your homepage is deciding to care; a user reading microcopy during onboarding is mid-task, with something already invested and a decision in front of them.
Content marketing for tech companies usually stops at the blog, the docs and the site. When Better Marketing rebuilds the page a buyer lands on first, the test on every line is the same one: does this help the reader decide. That test does not expire at the login screen.
Useful words inside the product are the cheapest trust-building asset a founder already owns. Nothing has to be designed, shipped or bought, because a string is changed and deployed with the next build.
Seven Places Where Microcopy Decides What Happens Next
Seven moments carry most of the weight, and most teams have never written them down. Each one asks the reader for a decision, and the microcopy is what they decide against.
- Empty states, which say what a screen is for before there is anything on it
- First-run onboarding, which decides between obvious and demanding
- Error messages, which decide between helpful and defensive
- Permission prompts, which decide between necessary and suspicious
- Billing and cancellation flows, which decide between respected and trapped
- Confirmation screens, which decide between progress and doubt
- Transactional email, which carries the product when the product is not on screen
Read that list against your own product and mark every moment you cannot remember writing. Those are the lines somebody shipped in a hurry, and they are what an audit finds first.
Your support inbox already knows which ones they are. The same tickets that can rewrite a pricing page in your buyer's words also name the screens where people give up.
Bad Microcopy Fails in Three Familiar Ways
Bad microcopy fails by confusing the reader, by blaming them, or by describing the product from the inside. Each failure has a recognizable shape and a short fix.
Two of the three are also accessibility failures. The Web Content Accessibility Guidelines put Error Suggestion at Level AA: where an input error is detected automatically and a correction is known, the suggestion goes to the reader, unless giving it would compromise security.
1. It Confuses the Person Who Is Ready to Act
The reader is willing, and the wording makes them interpret. Invalid input detected tells them a rule exists without telling them the rule.
Write the rule instead: Enter a work email address, because personal domains are not supported yet. The GOV.UK validation pattern goes one step further and asks you to design the question so the error is not needed at all.
2. It Blames the User for the System's Failure
Microsoft's writing-style rules for Windows apps put this in one line: “Even when things break, don't blame the user for any problems.” The product takes responsibility, and then says what to do next.
Something went wrong, please try again names nothing and offers nothing. We could not save this because the file was too large. Try a smaller upload, or compress the image first names the cause and the next move.
3. It Speaks in the Company's Internal Language
This one hides in plain sight, because the sentence is grammatical and accurate. We have enabled advanced workspace governance is a release note wearing a product string.
The reader needs their next step made legible: You can now restrict folders to specific people, which helps larger teams keep sensitive files separate. Feature names belong in the changelog, not in the place where somebody is trying to finish a job.
Site Copy and Product Copy Do Different Jobs
Site copy sells a decision that has not been made yet. Product copy supports a decision already in progress, and that changes who writes it, how it gets reviewed, and how anyone finds out it is wrong.
| Factor | Marketing site copy | Product microcopy |
|---|---|---|
| Reader's state | Browsing, deciding to care | Mid-task, already invested |
| Who usually writes it | Founder or marketer | Whoever was in the file |
| How it gets reviewed | Drafted, edited, approved | Shipped inside a pull request |
| How a failure shows up | A bounce and no reply | A silent drop-off, then a ticket |
| Who can read it | Anyone, crawlers included | Only people who signed in |
The last row is the one that catches marketers out. An AI SEO service works on pages a crawler can fetch, and most product strings sit behind a login where no crawler goes, so they never appear in any report you already read.
That invisibility is why the surface stays unowned, and it is why a website redesign checklist never reaches it. UX writing exists as a discipline precisely because somebody has to answer for text that no dashboard reports on.
Nobody Owns Microcopy Until a Name Is on It
Somebody has to own the strings, and in a company of six that somebody is a name in a document rather than a hire. Ownership means one person reads new strings before they ship and keeps the list the audit produced.
The default owner is whoever wrote the last one, which is how engineers end up writing marketing copy by accident. That is not a failure of engineering. It is what happens when a surface has no editor.
Marketing usually assumes the product is out of scope. A B2B demand generation agency is measured on signups and meetings, and content marketing for tech companies is measured on published pages, so neither brief reaches the microcopy a user reads ninety seconds after signing up.
Write the owner's name into the same document as the grading rule. A surface with an editor stops drifting, because every new string now passes one person who reads it as a reader rather than as its author.
Where a Microcopy Audit Will Not Help You
A microcopy audit does not fix a product people do not want. If the core workflow fails, if the value proposition is vague, or if the job being sold is not a job anyone is hiring for, better words postpone the problem instead of solving it.
It also does not help when the friction is structural. A signup that demands a credit card before showing any value will lose people however kindly the form explains itself.
Three conditions make the day worth spending: the product basically works, people reach it, and they drop out in small avoidable moments rather than at one wall. Miss any of those and the day belongs somewhere else.
An AI SEO service will not reach this surface either, and neither will a new landing page. Onboarding strings are read by people who are already inside, which is a different audience from the one a campaign is built to attract.
Start With the Words Your Users Read Most
You already own a surface your users read every day, and in most companies no one is accountable for it. One day of reading and grading is enough to find the microcopy that confuses, blames, or talks about the company instead of the reader.
Do that before you spend on reaching more people. A B2B demand generation agency fills the top of the funnel, and the words after signup decide how much of it survives.
Better Marketing builds the AI SEO service around pages a crawler can fetch, and the same plain-answer test works on the strings behind your login. Start there, because it costs a day and a text editor.