EyeCaptain

CTA Button Text: How to Write Buttons That Get Clicked

How to write CTA button text that converts: the verb plus outcome formula, specificity, the first person test, microcopy, and before and after examples.

Dimitris Andreadakis

8 min read
55 views
CTA button textcall to action button copyCTA examplesbutton microcopyfirst person CTA

Good CTA button text pairs a verb with the outcome the visitor gets, such as "Get my quote" or "Book a table," instead of generic words like "Submit" or "Learn more." Make it specific to the offer, check that it reads naturally after "I want to," and add one line of microcopy under the button that removes the main worry.

Why does CTA button text matter so much?

Button text matters because it is the last thing a visitor reads before committing, and it tells them what will happen when they click. Vague text makes people guess. Guessing creates hesitation, and hesitation at the button is where a lot of visitors leave.

The button is also one of the few pieces of copy almost everyone reads. Visitors skim headlines and skip paragraphs, but they look at the button to find out what to do next. That makes two to five words of button text some of the most valuable copy on the page.

Button text works with button design, not instead of it. A clear label on a button nobody notices still fails. If your button blends into the page, fix its contrast and size first; our article on color and conversions covers that side.

What is the verb plus outcome formula?

The verb plus outcome formula means the button names an action and the thing the visitor gets from it. "Get my free quote" has a verb (get) and an outcome (a free quote). "Submit" has a verb but no outcome, so it describes your form instead of the visitor's benefit.

Some useful verbs by intent:

  • Getting something: Get, Download, Claim, Grab
  • Starting something: Start, Try, Create, Build
  • Reserving something: Book, Reserve, Schedule
  • Buying something: Add to cart, Buy, Order
  • Seeing something: See, Compare, Check, Find

Avoid stretching the formula into a sentence. "Get my free quote" works. "Click here to get your personalized free quote today" is too long to scan and too long to fit on a phone without wrapping.

How specific should button text be?

Button text should be specific enough that the visitor knows exactly what happens next, and short enough to read at a glance. Specific beats clever every time.

Compare "Get started" with "Start free trial." The first could mean a sign up form, a demo booking, or a pricing page. The second tells the visitor they are starting a trial and that it is free. Compare "Download" with "Download the checklist (PDF)." The second sets expectations about what lands on their device.

Specificity also means the button must match what happens after the click. If a button says "See pricing" and opens a contact form, the visitor feels tricked. Either change the button or change the destination.

What is the first person test for buttons?

The first person test checks whether the button text completes the sentence "I want to..." from the visitor's point of view. "I want to get my free quote" works. "I want to submit" sounds odd, and "I want to start your trial" sounds wrong, which tells you the wording is written from the company's side.

The test has two uses. First, it catches company centered wording such as "Request a consultation with our team." Second, it helps you choose between "your" and "my." Many teams find "my" ("Start my trial") reads more personally on the button itself, while "your" works in surrounding copy. Neither is a rule; treat it as a variant worth testing on a high traffic page.

What microcopy should go under the button?

Put one short line under the button that answers the biggest worry at that moment. The button says what happens; the microcopy says what does not happen, or what it costs in time or effort.

  • SaaS trial: "No credit card required. Cancel anytime."
  • Lead form: "We reply within one business day. No spam."
  • Ecommerce: "Free returns within 30 days."
  • Booking: "Free cancellation up to 24 hours before."
  • Newsletter: "One email a week. Unsubscribe in one click."

Only write what is true. If a card is required, do not imply otherwise. For more on short helper text in forms, see our guide to form microcopy.

What are before and after examples by site type?

The table below shows weak button text and a stronger rewrite for common site types, with the reason each rewrite is better. Use it as a starting point, then adapt the outcome to your own offer.

Site typeBeforeAfterWhy it is better
Online store, product pageBuyAdd to cart, $48Confirms the action and the price in one glance
Online store, cartProceedGo to secure checkoutNames the next step and adds reassurance
Lead generationSubmitGet my free quoteNames the outcome instead of the form action
SaaS homepageGet startedStart free 14 day trialStates what starts, that it is free, and for how long
SaaS enterpriseContact usBook a 20 minute demoSets the commitment and format
Booking siteContinueCheck availabilityDescribes what the visitor sees next
RestaurantReserveBook a tablePlain wording that matches how people talk
Content siteSubscribeSend me the weekly guideTells readers what arrives and how often
AgencyLearn moreSee client resultsPromises a specific page instead of a vague one

How do you rewrite a CTA button step by step?

Rewrite it by starting from what the visitor gets, not from what your system does. These steps work for any page.

EyeCaptainEyeCaptain
Conversions Booster

Your visitors leave without converting

Most websites lose 97% of their traffic without a single conversion. Our AI scans 200+ CRO elements to find exactly where visitors drop off.

Hero CTA missing

  1. Write down what happens after the click. Be literal: "a form opens," "the item goes to the cart," "a PDF downloads."
  2. Name the outcome the visitor cares about. A quote, a booked table, a trial, a guide.
  3. Pick a verb that fits. Use the list above.
  4. Combine them in two to five words. Read it aloud. Check that it fits on one line at 390 px width.
  5. Run the first person test. Does "I want to..." plus your text sound natural?
  6. Add one line of microcopy. Answer the main worry: cost, commitment, time, or spam.
  7. Check the accessible name. WCAG 2.2 success criterion 2.5.3, Label in Name, requires that a control's accessible name contains its visible text, so update any aria label to match.
  8. Test it. On a page with enough traffic, run an A/B test of the old and new text.

What does a rewrite look like on a real page?

Here is a worked example for a hypothetical bookkeeping firm that offers small businesses a fixed monthly price. Its homepage hero has the headline "Bookkeeping for small businesses" and a gray button reading "Submit inquiry." Under the button is nothing. The form asks for name, email, company, and monthly revenue.

Going through the steps: after the click, the visitor's details go to the sales team, who reply with a price. The outcome the visitor cares about is knowing the price. The rewrite becomes "Get my monthly price," with the microcopy "Fixed price, reply within one business day, no sales calls unless you ask." The button keeps its position but switches to the brand's accent color so it stands out from the form fields.

Lower on the page, a second button reading "Learn more" under the services list becomes "See what's included," which matches the page it opens. For more ideas specific to forms and quote requests, see our page on lead generation pages.

How do you test CTA button text?

Test it with an A/B test on a page that gets enough conversions to reach a reliable result, and change only the text in that test. If you change text, color, and placement at once, you will not know which change mattered.

Decide your sample size before starting and do not stop the test early because one version looks ahead. Our post on the peeking problem in A/B testing explains why. On low traffic pages, apply the principles in this article directly; clear, specific text is a safe default. A free CRO audit on EyeCaptain reviews the main CTA on one page and suggests a rewrite with a before and after.

Key takeaways

  • Combine a verb with the outcome the visitor gets: "Get my free quote," not "Submit."
  • Be specific about what happens after the click, and make sure the destination matches.
  • Use the "I want to..." test to catch company centered wording.
  • Add one line of honest microcopy under the button to answer the main worry.

Frequently asked questions

How many words should a CTA button have?

Two to five words covers most good buttons. That is enough for a verb and an outcome, such as "Book a table" or "Start free trial," and short enough to fit on one line on a phone. If you need more words to explain the offer, put them in the headline or in microcopy under the button, not in the button itself.

Is "Learn more" a bad CTA?

"Learn more" is not wrong, but it is vague. It does not say what the visitor will learn or where the click leads. It works as a secondary link in a list of features, but as a main call to action it usually loses to text that names the destination, such as "See pricing" or "Compare plans."

Should a CTA button say "my" or "your"?

Both can work. "My" reads as the visitor speaking, which fits a button they press, while "your" reads as the company speaking. Use the first person test: if "I want to start my trial" sounds natural, "my" fits. Treat it as a test on high traffic pages rather than a fixed rule, and keep it consistent.

Should the CTA text be the same on every page?

Keep the main conversion button consistent across pages that lead to the same action, so visitors recognize it. Change the text when the action changes. A pricing page button for a specific plan can say "Start Pro trial," while the homepage says "Start free trial." Consistency of action matters more than identical wording.

Does button text matter more than button color?

They do different jobs, so you need both. Color and contrast make the button noticeable; text makes the click feel safe and worthwhile. A bright button with vague text gets noticed and then ignored. A clear label on a button with poor contrast gets missed. Fix visibility first, then refine the words.

Enjoyed this article?

One short email a week with practical CRO and UX tips

No spam. Unsubscribe anytime.

Find what stops your visitors from converting

EyeCaptain is an AI-powered CRO & UX audit tool that automatically scans your pages, identifies UX issues, and gives you actionable optimization suggestions to increase conversions. Try it for free, no card, no commitment.

Free CRO Audit
Share this article
LinkedIn X

About the author

Founder of EyeCaptain. Writes about conversion rate optimization, UX analysis and the neuromarketing behind pages that actually sell.

More articles by Dimitris Andreadakis