Conversion and UX

Button Copy

Also called CTA copy, button label, button text

The wording printed on an action button, which should name the outcome the visitor gets rather than the system operation.

Quick facts: Button Copy

Category
Conversion and UX
Also called
CTA copy, button label, button text
Level
Beginner
Affects
Click-through, form completion, enquiry quality
Where to see it
GA4 click events, session recordings, any A/B testing tool
In this article4
  1. How button copy works
  2. Why button copy matters
  3. Common mistakes with button copy
  4. How to act on it

How button copy works

The label on a button is the last thing a visitor reads before they commit, and it is doing two jobs at once. It has to name the action clearly enough that nobody is guessing, and it has to describe that action in terms of what the visitor gets rather than what your system does.

The difference between weak and strong labels is usually specificity. “Submit” names an operation on a database. “Send my enquiry” names the thing the visitor actually wants to happen. “Learn more” describes nothing at all, whereas “See what is in the audit” tells someone precisely what the next page holds. Good labels tend to be short verb phrases, written from the reader’s side, and they answer the quiet question every button raises: what happens if I press this?

Why button copy matters

Uncertainty stops people. If a visitor cannot tell whether a button will send their details, open a form, start a payment or simply scroll them further down, hesitation costs you the click. That hesitation is worst at the moments that matter most — a lead form, a checkout step, a phone call.

It is also the cheapest thing on the page to change. Rewriting a label costs minutes, touches no design and needs no development. That makes it one of the few pieces of microcopy worth revisiting regularly, and a sensible first experiment in any programme of conversion rate optimisation.

Common mistakes with button copy

Vague verbs are the first problem: Submit, Continue, Go, Learn More, Click Here. Each one leaves the visitor to work out the consequence. The second is overselling — a label promising a transformation that the following page does not deliver, which reads as a trick and loses the trust the rest of the page built.

Length is the third. A label that wraps to three lines on a phone stops looking like a button. Language mixing is a fourth issue for Nepali sites: a page written in Nepali with an English button, or the reverse, forces a small mental switch at precisely the wrong moment. Finally, several buttons on one page reading identically but leading to different destinations leaves people unsure which one they already pressed.

How to act on it

Write the label as the visitor would finish the sentence “I want to…”. Send my enquiry. Book a call. Download the checklist. Start the free audit. Read it back and ask whether a stranger could predict the next screen from the label alone.

Then match the label to what actually follows. If the button opens a form rather than sending anything, say so. If a call is being placed, put the number or the word call in the label. Keep the primary action worded the same way everywhere it appears on the page, and word secondary actions differently and more quietly, so the two are never confused. When you change a label, note the date, because otherwise a later shift in enquiry volume has no explanation attached to it.

Do and do not

Do

  • Name the outcome the visitor gets, not the system action
  • Keep the label to one line on mobile
  • Word the same primary action identically across the page

Do not

  • Use Submit, Continue, Go or Learn More
  • Promise something the next page does not deliver
  • Give two different destinations the same button label

Questions people ask about this

What is wrong with a Submit button?

Submit describes what the software does, not what the visitor gains, and it carries a faintly bureaucratic tone. Replacing it with the outcome — send my enquiry, book my call, get the quote — removes the guesswork at the exact moment somebody is deciding whether to hand over their details. It costs nothing to change and needs no design work.

How long should button copy be?

Long enough to name the outcome and short enough to sit on one line on a phone screen. Two to four words covers most cases. If a label needs more than that, the extra explanation usually belongs in a line of supporting text beneath the button, where it can reassure without making the button itself look like a paragraph.

Should the button say I or you?

First person often reads better because it echoes the visitor's own thought: send my enquiry rather than send your enquiry. It is a small effect and not worth arguing over. What matters far more is that the verb is specific and the outcome is honest, so test the wording on your own audience instead of copying a rule from elsewhere.

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.