Microcopy

What microcopy is

Microcopy is the writing that lives inside the interface rather than in the body content: the label on a button ("Start free trial" vs. "Submit"), the hint under a form field ("We’ll never share your email"), the message when something goes wrong ("That code has expired — request a new one"), the text of an empty state ("No projects yet — create your first"), tooltips, placeholder prompts, confirmation toasts, and the fine print beside a checkbox. Each piece is tiny, often just a few words, but it appears at the exact moment a user has to decide or act.

Because it is functional, microcopy is judged by whether it helps: does the button say what will happen when you click it, does the error explain how to recover, does the hint remove a hesitation. Good microcopy is clear, specific, and human; weak microcopy is vague ("Error"), generic ("Submit"), or absent where reassurance was needed.

Why it matters for website copy

Microcopy carries a lot of weight for its size, and it is also where copy quality most often quietly breaks. It is written piecemeal, frequently by developers rather than writers, and scattered across components, so it is the copy least likely to get a careful editorial read. That is exactly where leftover defaults survive ("Button text", "Lorem ipsum" in a tooltip), where placeholder strings ship, and where tone and capitalization drift out of step with the rest of the site.

For proofreading, microcopy is just copy — short copy in small components, but subject to the same issues as any other text: typos, awkward phrasing, inconsistent style, and leftover placeholder defaults. Because Verant reads the rendered page, the microcopy a visitor actually sees — button labels, hints, and messages built into the live DOM — is checked alongside the body copy for the same six kinds of issue. The one caveat is that a check reads what is rendered at scan time: a microcopy string that only appears after a specific interaction (an error that fires on a failed submit, say) may not be on the page when it is read.

Common mistakes

The most common mistake is treating microcopy as not really "content" and skipping it in the editorial pass, so it ships with typos, vague labels, and leftover defaults the body copy would never get away with. Another is inconsistency — "Sign up" on one button, "Register" on another, "Create account" on a third, all for the same action. A third is generic error and empty-state text that names a problem without telling the user what to do about it. The fix is to treat microcopy as first-class copy: write it deliberately, keep it consistent, and proofread it like everything else.