What your call to action button should say. Stop winging the words

Alex · Founder of Magpie AI
Published · 6 min read

In short
Your call to action button should say what the visitor gets or what happens next, in a few plain words like "Get my free report" or "See pricing". Labels such as "Get started", "Learn more" and "Submit" fit any goal, so they mislead people who wanted something else. Keep one main button, and put the last doubt in a short line under it.
Contents
Six of eight people on one meal delivery site pressed "Get Started" because they thought it would tell them about the company. It didn't. It dropped them into a sign-up flow, and that's from a study Nielsen Norman Group wrote up in 2017, which is still the clearest picture I know of what a vague button does to the people who press it.
So write the words on your button as if the visitor will hold you to them. Say what they'll get, or the step they're about to take, and use as few words as that needs.
Why "Get started" and "Learn more" cost you#
They fit every goal. That's the trouble with them.
In the same study, some people on a second site saw "Get Started" sitting above the fold and decided the details they were after weren't on the page at all, so they never scrolled to find them. The researchers called the label "ambiguous" because it "can apply to almost any goal that a user might have", and I'd go a bit further. Even a sharp-eyed visitor can't tell from those two words whether a price, a menu or a form is waiting on the other side.
You still get the click in your analytics, of course. You just don't get much from someone who wanted a price and found a form.
"Learn more" has a second problem, and it's one most people never see. Someone using a screen reader often hears a page's links read out as a list, stripped of the sentences around them, so five links all saying "Learn more" turn into five identical sounds in a row (try telling those apart). WCAG 2.4.4, at level A, which is the lowest bar the accessibility guidelines set, asks that a link's purpose be clear from its own words, or from its words with the text right around them.
Name what the visitor gets#
Use a verb and the thing itself, in the words a buyer would use. Take a made-up plant care app at fernly.example:
| Vague | Says what happens |
|---|---|
| Get started | Start watering reminders |
| Learn more | See how reminders work |
| Submit | Send me my plant plan |
| Sign up | Create my free account |
| Request a demo | Book a 20-minute walkthrough |
The right-hand column is longer, and I don't think that matters much. Each one tells you what you're agreeing to before you agree to it. It also sorts the clicks for you, because whoever presses "Book a 20-minute walkthrough" already knows a call is coming and isn't going to be annoyed when it does.
Match the words to where the button leads#
If "See pricing" opens a contact form, the visitor notices. Fair enough if they leave. When the next step is a quiz, say quiz, and when it asks for an email, "Email me the guide" is honest about that. NN/g's fix for a fashion site in the same study went the same way, swapping "Get Started" for "Take Our Style Quiz".
This means opening your own next page and reading it as a stranger would, which is easy to skip when you built both pages and know exactly where they go. Magpie's full report does it for you. It follows the main button one step (opening a link or pressing a plain button, never a form's) and reads the button's words against the page it lands on.
One main button, and the same words each time#
"Start free" and "Book a demo" side by side, the same size and colour, make the visitor stop and pick. Some pick neither. I'd make one of them the clear main button and turn the other into a plain link beside it.
Buttons that go to the same place should be birds of a feather, too. A header button saying "Get started" and a hero button saying "Start free trial" might lead to one page, but the visitor has no way of knowing that, so choose one label and use it in both. Repeating the main button in the header is pretty much always fine, by the way, since it keeps the action in reach as people scroll down.
The headline and the line under it matter as much as the button itself. I go through both in what a landing page's first screen should say, with a made-up page to show each change.
Put the last doubt in the line under it#
The few words under a button can do as much work as the button. Right at the moment of clicking, the doubt is usually about cost, a card, time, or what happens afterwards. Answer whichever one your buyers ask most often:
- No card needed
- Takes about a minute
- Cancel any time from your account
- Free for up to five plants
Only crow about "No card needed" if the sign-up really asks for none (whether a free trial should ask for a card at all is a separate argument). Someone who was ready to go and then hits a card form has just learned that your site says things that aren't true, and I doubt they'll read the rest of it kindly.
When the doubt is "does this work for people like me", a named customer's quote near the button does better than anything you write yourself.
What colour should the button be?#
Whichever one stands out most from what's around it. I'd love a firmer answer, but there isn't one. Andrew Elliot's 2015 review of colour research found the field still young, a lot of its studies too small, and every effect it did find tied to its context. What we do know is that a button catches the eye by standing apart from its surroundings, and no single colour has been shown to do that on its own, so pick yours for contrast and spend your testing time on the words. (Where eyes actually land is a separate thing, covered in where visitors look first.)
Size matters more for thumbs than colour does. WCAG 2.5.8 puts the smallest tap target at 24 by 24 CSS pixels, and a main button on a phone wants to be comfortably bigger than that. Check it's still on the mobile first screen, too, since a tall picture above it is the usual reason it slips out of view.
Questions people ask#
Should it say "my" or "your"?#
Honestly, whichever reads more naturally on your site. The tests people usually quote for "Start my trial" over "Start your trial" are company case studies that don't publish a sample size, so I wouldn't choose on the strength of them. Saying what happens next matters far more than the pronoun.
How long should the label be?#
I'd aim for two to five words. If it won't fit in five, the extra detail probably wants to live in the line underneath instead.
Is "Get started" ever fine?#
Sometimes, yes. If the words right around it already say exactly what starts, and the page is only offering one thing, I don't think it does much harm, though I've not found a study either way. I'd still swap it. Naming the thing ("Start my free check") costs you nothing, it reads better to anyone on a screen reader, and it means the label still makes sense when someone copies your button into a different part of the site six months later and forgets what the paragraph above it used to say.
Sources
- Nielsen Norman Group, Get Started Stops Users (Aurora Harley and Kim Flaherty, 2017) (opens in a new tab)
- Nielsen Norman Group, Learn More Links: You Can Do Better (Katie Sherwin, 2015) (opens in a new tab)
- W3C, Understanding WCAG 2.2: Link Purpose (In Context) (opens in a new tab)
- W3C, Understanding WCAG 2.2: Target Size (Minimum) (opens in a new tab)
- Elliot, Color and psychological functioning (Frontiers in Psychology, 2015) (opens in a new tab)

About the author
Alex · Founder of Magpie AI
Alex founded Magpie AI and writes about what turns a landing page's visitors into customers, drawing on what its audits find on real sites, from the first screen to the checkout


