Best text for a call to action button (not Submit)
The best text for a call to action button names what happens after the click. See rewrites of Submit, Click here and Learn more.
On this page 5 min read
Key takeaways
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
Someone fills in your contact form. Name, email, a few lines about their project. Then they reach the button, and it says "Submit".
Submit what, and to whom? Will they get a reply, a call, a newsletter they never asked for? The button doesn't say, so they have to guess. Some people guess and click. Some people leave.
Here's the fix. A button should name the result of clicking it. That's usually a verb plus an object in two to four words: "Send message", "Book a call", "Create account". Labels like "Submit", "Click here" and "Learn more" make people guess what happens next.
What should a button say instead of "Submit"?
Say what the person gets or what happens when they press it. Look at what the form does, then write that on the button.
- A contact form sends a message. The button says "Send message".
- A quote form asks for a price. The button says "Get my quote".
- A signup form makes an account. The button says "Create account".
- A booking form reserves a time. The button says "Book a call".
Here's a before and after for a contact form.
Before: the heading says "Contact us". The button says "Submit". After the click, the page reloads and nothing else happens.
After: the heading says "Tell me about your project". The button says "Send message". Under it, one small line: "I reply within a day."
The form has the same fields. The second one tells you what you're doing and what comes next. If you're unsure about the fields themselves, the post on placeholder vs label in forms covers the boxes above the button.
Why is "Submit" a problem?
It describes what the computer does. It says nothing about what the person gets.
"Submit" is a developer's word. The form submits data to a server. That's true, and no visitor cares.
The visitor is at the last step. They've done the work of filling everything in, and now they have to commit. A vague button gives them a reason to stop and wonder.
There's a second problem. "Submit" fits every form on the internet, so it tells you nothing about this one. If you can paste a label onto any button on any site and it still works, it's too generic.
A quick test: cover everything on the page except the button. Can you still tell what will happen when you press it? "Send message" passes. "Submit" doesn't.
What's wrong with "Click here" and "Learn more"?
They describe the click or promise nothing specific, so the reader has to read around them to know where they go.
"Click here" tells people how to use a mouse. They know. The useful part is where the click leads, and that's the part you left out.
It's also a problem for people who use a screen reader. The W3C's guidance on link purpose notes that assistive technology can give users a list of the links on a page. Pulled out of the page like that, a row of "Click here" and "Learn more" sounds like the same link repeated ten times.
"Learn more" is a little better, but learn more about what? Name the thing.
- "Click here" becomes "Download the price list".
- "Learn more" becomes "See pricing" or "Read the case study".
- "Get started" becomes "Start free trial".
- "Continue" becomes "Go to payment".
How long should button text be?
Two to four words is the usual range. Go longer only when the extra words remove a doubt.
One word is rarely enough. "Send" is fine in a chat app where the context is obvious. On a form, "Send message" is clearer and costs you one word.
Four or five words can work when the short version would leave a question open. "Send my quote request" is longer than "Submit", and it's better, because it tells you that you're asking for a quote and nobody is charging you yet.
Past five words, the button starts doing a sentence's job. Move the extra detail to a small line under the button instead. "Create account" on the button, "Free, no card needed" under it.
Start with the verb. "Book a call" reads faster than "Call booking".
How do I write good button text for my own site?
Finish the sentence "I want to..." from the visitor's side, and put the ending on the button. This is the routine I'd use on any page.
- Finish the sentence. "I want to... book a call." "I want to... see pricing." If the ending sounds odd, the label is wrong. Nobody says "I want to submit".
- Match the page that comes next. If the button says "See pricing", the next page should be the pricing page, with "Pricing" at the top. A label that promises one thing and delivers another costs you trust.
- Use the same words everywhere. If the header button says "Book a call", the one at the bottom of the page shouldn't say "Schedule a consultation". People will wonder if those are two different things.
- Name the scary ones clearly. A delete dialog with "OK" and "Cancel" makes people stop and reread. "Delete project" and "Keep project" are much harder to misread.
- Answer the worry under the button. One short line is enough: "No card needed" or "Takes two minutes". Only write it if it's true.
What does this look like on a whole site?
The same rule everywhere: the button names the result. Here's a made-up example.
Say you run a bookkeeping service. Your homepage has a header button that says "Get started", a hero button that says "Learn more", and a contact form at the bottom that ends in "Submit". Three buttons, three vague promises.
Rewrite them around what a visitor actually wants. The header and hero buttons both become "Book a free call", so people know there's one way in and what it costs them. The pricing link becomes "See monthly prices". The form button becomes "Send message", with "I reply within a day" under it.
Nothing about the design changed. The colours, the layout and the fields are the same. But every button now answers the question a visitor has right before they click: what happens next? If the page still isn't getting enquiries after that, the post on why your landing page is not converting looks at the rest of it.
If you'd like a second pair of eyes on your landing page, buttons included, book a call. Send me the link and I'll tell you what I'd change first.
Questions
-
It's better than "Submit", but it's still vague. If you can name the first real step, like "Start free trial" or "Create account", use that.
-
Both work. "Start my free trial" reads as the visitor speaking, and "Start your free trial" reads as you speaking. Pick one and keep it the same across the site.
-
They do different jobs. Colour and size get the button noticed. The words tell people what they're agreeing to.
Read next
View all postsConsistent icon style in UI: why mixed sets look cheap
Mixed icon sets make a UI look stitched together. How to spot it, why emoji fail as icons, and how to pick one family and weight.
How to design a website without content (no lorem ipsum)
Copy not written yet? You can still start designing. Use rough draft copy instead of lorem ipsum. Here's how, step by step.
How many pricing tiers should a SaaS have? Fewer
How many pricing tiers should a SaaS have? Fewer than you think. When two plans are enough, when three make sense, and when to add one.
Have a project in mind?
Book a short call. We'll talk through what you're building, and I'll tell you how I can help.
- Length
- 15 minutes
- Where
- Cal Video
- Time zone
- Metro Manila