what is a CTA button? call to action, explained with the ones that actually get clicked

design · Oct 6, 2026 · 5 min read

cta stands for call to action, and the cta button is the button you most need clicked: "book now", "get a quote", "reserve a table". it is the sentence your whole page was built to make happen — everything above it is argument, and the button is the ask. every page has a job (how do i make a website makes you name that job first); the cta is the job, as a button.

why so many buttons die

the generic cta fails for a reason that is easy to feel: "submit" asks the visitor to spend something they cannot see. submit what? to whom? what happens after? the visitor's hesitation is not laziness, it is an unanswered transactional question — what do i give, what do i get. the buttons that get clicked answer it:

  • "submit" → "get my free quote" — says what arrives and what it costs (nothing).
  • "send" → "book a 20-minute call" — says the size of the commitment.
  • "learn more" → "see the menu" — says exactly what the click opens.
  • "download" → "get the price list (pdf)" — format and content, no surprise.

specific verbs beat abstract ones because specificity is a trust signal — the same argument made in what makes a website look trustworthy, applied to four words instead of four paragraphs.

the placement rules

  • one primary cta per screen. a page can serve several jobs across its scroll, but each screen's hierarchy should name its one next step. two equal buttons side by side are a question you asked the visitor to answer for you — "which one am i supposed to want?"

  • above the fold, and at every decision point. the visitor ready at second three and the one convinced at second ninety both need the button available; neither should hunt.

  • where the eye already goes. after the offer, after the proof, at the natural end of the argument. the awkward button floating mid-paragraph loses to the button that arrives exactly when the argument does. deciding where buttons go is its own discipline — the placement decisions i actually use are in ux design tactics i use on my website.

  • the mobile test. a cta is a thumb target: on a phone it needs to be reachable one-handed, big enough to hit without precision, and never placed where the browser's own chrome sits. the layout context is in what is responsive design.

    what the button itself needs

  • to look like the most important thing in its area. this is the accent color's actual job — the scarcity argument from how many colors should my website use exists so that the one action color points at the one action.

  • to promise, not demand. "start free", "get", "see", "try" — the verbs of receiving. "register", "provide", "enter" are the verbs of paperwork. compare the two lists next to your own buttons and feel the difference.

  • to keep its promise. the fastest trust-killer on a site is a button that says "get instant quote" and opens a 14-field form. the click sets an expectation; the page after the click must honor it, or the lesson learned is that your buttons lie.

  • a quiet secondary. "not ready? see how it works" beside the main button catches the not-yet visitors without competing with the ask. secondary means visually quieter, or it means two primaries.

    the metric that settles every argument

cta debates end with data, not taste: the site already has the measuring stick — how many people click, and whether they finish what follows. that is conversion tracking, and the plain-language version — what a conversion is, and how a form submit becomes a countable event — is in what counts as a conversion for my site. change one word at a time, measure, keep the winner.

FAQ: the questions i actually get

can i have several ctas on one page?

several across the full scroll, yes — one per screen of it. the failure is several competing on one screen. one primary, one quiet secondary, nothing else that shouts.

what about the sticky button that follows the scroll?

on a phone, for a single-action site (call, book, order), it is honest ergonomics and earns its place. on a desktop page with many goals it is noise. judge by the number of jobs, not by the trend.

how long should the button text be?

two to five words, verb first. "get my free quote" is the ceiling of good; past that it stops reading as a button and starts reading as a sentence to skip.