How to Write Call-to-Action Buttons That Get Clicked: Wording, Placement and Proof

A call-to-action button gets clicked when it asks for one clear action, names the outcome the visitor will get, and appears at the moment the visitor is ready to take it. That is the direct answer. "Get a Free Quote" works because it says what happens next and what it costs the visitor — nothing, except a short conversation. "Submit", "Click Here", and "Learn More" fail by comparison because they describe the mechanics of clicking, not the benefit of doing so, and they leave the visitor guessing about what happens after the click. If you give every page one primary action, word it as a verb plus a specific outcome, make it visually unmistakable, place it where proof has already been given, and remove the friction around it, more visitors will take the step you actually want — without tricks, pressure, or misleading promises.

Buttons are often treated as decoration: a coloured rectangle added at the end of a page because a template expects one. That is backwards. A button is a decision point, and every decision point should be designed with the same care as the headline above it. Visitors do not click buttons because they like the colour. They click because they understand what they will get, they trust that the next step is safe and easy, and they have just read something that made the step feel worthwhile. Colour, size, and placement support that decision; they do not replace it. A bright button with vague wording will underperform a plain button with clear wording, and a page with six competing buttons will underperform a page with one confident ask, however beautiful the six buttons look.

One primary action per page

Every page should have one primary action, and it should be obvious which one it is. A services page might ask visitors to request a quote. A product page asks them to add to basket or buy. A booking page asks them to choose a time. A guide might ask them to download a checklist or contact the business. Problems start when a page asks for three or four things at once — call us, email us, download this, read that, follow us, subscribe — because the visitor, faced with equal-looking options, often chooses none of them. This is not a theory about attention spans; it is the ordinary result of asking someone to weigh competing choices when they arrived with one task in mind. Choose the action that matches the page's purpose, make it the largest and most contrasting button, and demote everything else to plain text links.

That does not mean a page can contain only one button. A long page will reasonably repeat its primary action two or three times: once near the top for visitors who already know what they want, once after the main proof, and once at the end. Repetition of the same action is helpful. Competition between different actions is harmful. Secondary actions — such as reading a related guide, viewing a gallery, or calling instead of filling in a form — should look secondary: smaller, outlined rather than filled, or rendered as text links. The visual hierarchy should answer, at a glance, the question "If I do one thing here, what should it be?" If a visitor cannot answer that question in two seconds, the hierarchy needs work, however tidy the page otherwise looks.

Verb plus outcome: wording that earns the click

The strongest button wording follows a simple formula: a verb, plus the outcome the visitor wants. "Book a Free Consultation" beats "Submit" because it names both the action and the reward. "Download the Pricing Guide" beats "Click Here" because the visitor knows what file they will receive. "Start Your Free Trial" works for software because it promises a beginning, not a commitment. Notice that none of these examples rely on urgency tricks or false scarcity. They are specific, honest, and matched to the visitor's stage. A visitor who is still comparing options may respond to "See Example Prices" or "Compare Plans", while a visitor who is ready to buy responds to "Buy Now" or "Book Your Visit". Matching the wording to readiness matters more than finding a single magic phrase that works everywhere.

Specificity also means avoiding words that hide the outcome. "Learn More" is the most common offender: more about what, exactly, and what will the visitor have to do to get it? If the button leads to a detailed service page, say "See How Boiler Servicing Works". If it leads to a price list, say "See Typical Prices". If it leads to a contact form, say "Ask for a Quote". The extra words cost nothing and remove a whole category of doubt. Similarly, avoid internal language on buttons. Visitors do not want to "Initiate Onboarding" or "Request a Discovery Call" unless those phrases are already familiar in their world. Use the words they would use themselves when describing the step to a friend, and test the wording on people outside your business, because insiders are the worst judges of whether jargon is clear.

Weak wording	Why it underperforms	Stronger alternative
Submit	Describes the form, not the benefit	Send My Enquiry
Click Here	Gives no clue about the destination	See Example Prices
Learn More	Vague about what comes next	See How It Works
Get Started	Started on what, at what cost?	Book a Free Consultation
Contact Us	Acceptable, but passive	Ask for a Free Quote
Sign Up	Sounds like a commitment	Create a Free Account

Length deserves a brief note. Short buttons are easier to scan, but clarity beats brevity. A four-word button that names the outcome will outperform a one-word button that does not, even though it takes slightly longer to read. Aim for two to five words in most cases, and do not be afraid of a longer label on a key action if the longer version removes doubt. "Get a Free Quote in 2 Minutes" may be longer than "Get a Quote", but if the time promise is honest and the form really is that short, the extra words are doing real work. Never make a time or cost promise on a button that the next page breaks. A button that promises "Free" and leads to a payment form destroys trust faster than a vague button ever could.

Button versus link: a hierarchy visitors can read

Buttons and links are not interchangeable. A button says "this is the action I want you to take". A link says "here is somewhere else you can go if you are interested". Use buttons sparingly — one primary, at most one secondary per section — and use text links for everything else: related articles, footer destinations, in-text references, and optional extras. When everything is a button, nothing stands out, and the page starts to look like a control panel rather than a conversation. When only the primary action is a button, the eye goes straight to it, and visitors who want something else can still find it without confusion.

Visual design should reinforce that hierarchy without relying on colour alone. The primary button should be a solid, high-contrast shape with generous padding and readable text, and it should look the same on every page so that returning visitors learn to recognise it instantly. The secondary action can be an outlined button in the same shape, which reads as related but less urgent. Text links should be underlined or otherwise clearly distinct from body text, because a link that only reveals itself on hover is invisible to touch users and to anyone scanning quickly. Check contrast properly: light grey text on a pale button may look elegant in a design tool and be unreadable in sunlight on a phone. If you must choose between elegance and legibility, choose legibility every time.

Placement: above the fold, after proof, and at the end

Placement is about timing. The first button should appear near the top of the page, in the opening section, for visitors who arrived already decided. They searched for a service, they know what they want, and they should not have to scroll through a thousand words of persuasion before they can act. That top button should sit beside or beneath a headline that states the offer clearly, with a short line of reassurance nearby — for example, that a quote is free, or that replies come within one working day. Without that context, even a well-worded button asks for trust the page has not yet earned.

The second placement matters just as much: after proof. Once a visitor has read what is included, seen example work or genuine reviews, and understood the price range, they are ready to decide, and the button should be right there, not three sections later behind a gallery they did not ask for. This is why long pages repeat the primary action rather than saving it for a grand finale. A visitor who is convinced halfway down should be able to act halfway down. The final placement, at the very end of the page, catches the careful readers who needed the whole argument before deciding. Three placements of the same action — top, after proof, end — cover the three kinds of visitor without introducing competing asks.

Friction reducers: make the next step feel safe

Even a clear button can fail if the step behind it feels risky, long, or intrusive. Friction reducers are the small honest reassurances placed near the button that answer the visitor's unspoken objections. "No account needed" tells a visitor they will not be forced to register before they can enquire. "Free, no obligation" tells them that asking for a quote does not commit them to buying. "Replies within one working day" sets an expectation and signals that the form is monitored. "Only three fields" tells them the form is short, provided it really is. These lines work because they are specific and checkable. Vague reassurance such as "We value your privacy" does far less than a concrete statement such as "We never share your details", and only if that statement is true.

Apply the same thinking to the page behind the button. A button that promises a quick quote but leads to a twelve-field form with a mandatory phone number and a captcha puzzle breaks the promise at the worst moment: the visitor has already decided, and the form talks them out of it. Ask only for what you need to reply helpfully — usually a name, a way to reply, and a short description of the job. Make phone numbers optional unless a call is genuinely required, explain why any unusual field exists, and show a clear confirmation after submission so the visitor knows the message arrived. Every extra field, every forced registration, and every surprising charge on the next page is a reason to abandon, and most visitors will not tell you they abandoned. They will simply leave.

Testing honestly: what to test, and what not to claim

Testing buttons is worthwhile, but it is also where small businesses most often fool themselves. Changing a button colour and watching clicks for a week on a site that receives forty visitors a day tells you almost nothing, because the sample is too small for the difference to mean anything. A result based on a handful of clicks can flip completely the following week for reasons that have nothing to do with the button. Honest testing starts with a question that matters — wording, placement, or the friction around the button — and it runs long enough, on enough visitors, to distinguish a real effect from noise. If your traffic is low, qualitative testing with real users, as described in our usability testing guide, will teach you more in ninety minutes than a month of inconclusive split testing.

When you do test, test one thing at a time, keep everything else identical, and decide in advance how long the test will run and what counts as a win. Test wording before colour, because wording changes what visitors understand, while colour mainly changes what they notice. Test placement before size, because a button in the wrong place cannot be saved by making it bigger. And record the result honestly, including tests that showed no difference: "no difference" is useful knowledge, because it tells you to stop chasing that variable and fix something else, such as the offer itself or the proof on the page. Never report a test result as a percentage improvement without stating the sample size and the period, and never borrow another site's claimed uplift as a promise for your own site. Your visitors, your offer, and your traffic are different, and honest numbers protect both you and your customers.

What to test	Why it matters	Caution
Button wording	Clarity changes understanding	Keep the destination page identical
Button placement	Timing changes readiness	Test top versus after proof, not ten positions at once
Form length behind the button	Friction kills completed enquiries	Count completed enquiries, not just clicks
Friction-reducer line	Reassurance answers objections	Only promise what you actually deliver
Button colour	Contrast affects visibility	Test last; wording matters more

Measure the right outcome. Clicks alone can mislead, because a button can attract curious clicks that never become enquiries, especially if its wording overpromises. Track the full journey: how many visitors clicked, how many completed the form or booking, and how many of those became genuine enquiries rather than spam or accidental submissions. A button that gets fewer clicks but more completed, qualified enquiries is the better button, even though a clicks-only report would call it a failure. If you cannot track completions, ask new enquirers how they found you and what nearly stopped them. That conversation is slower than a dashboard, and it is often more truthful.

Mobile tap targets and accessibility

On a phone, a button must be easy to tap with a thumb, without zooming, and without accidentally tapping the link beside it. Make buttons tall enough to tap comfortably, with generous spacing between adjacent actions, and keep the label readable without squinting. Avoid placing two different buttons side by side on a narrow screen where a thumb can easily hit the wrong one; stack them instead, with the primary action first. Check that buttons remain usable when text size is increased, when the page is viewed in landscape, and when a visitor uses a keyboard or screen reader. A button that is only recognisable by colour fails visitors who cannot perceive that colour, so pair colour with shape, label, and position, and ensure the button's text contrast passes a basic readability check.

Accessibility also covers the words around the button. Screen reader users often navigate by jumping from link to link, hearing button labels out of context. "Learn More" heard in isolation tells them nothing, while "See Boiler Servicing Prices" tells them everything. Write every button label as if it will be read alone, because for some visitors it will be. The same rule helps search engines and helps anyone scanning a page quickly. Finally, make sure buttons are real buttons or links in the page code, not styled text that looks clickable but cannot be activated by keyboard. A beautiful fake button is worse than a plain real one, because it promises an action it cannot deliver.

Mistakes that quietly kill clicks

The most common mistakes are quiet ones. A page with no button at all, ending in a paragraph that assumes the visitor will hunt for the contact page, loses the visitors who were ready but not motivated enough to search. A page whose button leads to a generic homepage instead of the promised quote form breaks trust in a single click. A page that repeats the same button with different wording — "Get a Quote" at the top, "Contact Us" in the middle, "Enquire Now" at the end — confuses visitors about whether these are the same action or three different ones. Keep the wording consistent wherever the same action repeats, so visitors learn to recognise it and do not have to re-decide at every scroll position.

Other mistakes are about tone. Buttons that shout in all capitals, buttons that guilt-trip visitors with "No, I hate saving money" as the decline option, and buttons that hide the decline option in tiny grey text may increase clicks in the short term and damage the relationship in the long term. Visitors remember being manipulated, and they are less likely to return, recommend, or trust the next offer. The sustainable approach is less dramatic and more effective: one clear action, honest wording, proof before the ask, and a next step that is as easy as the button promised. If you would feel tricked by your own button as a customer, rewrite it before you publish it.

Frequently Asked Questions

How many buttons should a page have?

One primary action, repeated in two or three places if the page is long. Secondary actions should be text links or outlined buttons, so the primary action remains unmistakable at a glance.

Is "Learn More" always a bad button label?

Not always, but it is usually too vague. If the destination is a specific page, name it: "See How It Works", "Read Customer Reviews", or "See Typical Prices" all tell the visitor more than "Learn More" does.

Should buttons be above the fold?

Yes, for visitors who arrive already decided, but not only above the fold. Repeat the same button after proof and at the end, so visitors who need the full argument can act when they are ready.

How long should I run a button test?

Long enough to gather a meaningful number of visitors and completed actions, not just clicks. On a low-traffic site, a qualitative test with real users will usually teach you more, faster, than a split test that never reaches a reliable sample.

Does button colour matter?

Contrast and visibility matter; a specific "best" colour does not exist for every site. Choose a colour that stands out from the page, passes contrast checks, and stays consistent across the site, then test wording and placement first.

What makes a good mobile button?

A tall tap target, a readable label, space from neighbouring actions, and a position reachable with a thumb. Stack competing buttons on narrow screens rather than squeezing them side by side.