What is a call to action?
A call to action is the element on a page that asks the visitor to take a specific next step, usually a button or link such as "Start free trial", "Book a demo" or "Download the guide". It's where the page turns attention into a measurable action. Everything else on a landing page exists to make that click feel like the obvious thing to do.
The term covers more than the button. A complete CTA includes the label, the line of reassurance under it, the form it opens and the page that confirms it. For a plain-English definition with examples, see our explainer on what a CTA is. This guide is the practical version: how to write, place and design calls to action on a landing page, and where to go deeper on each part.
What makes an effective call to action?
An effective call to action has four qualities: it offers a clear next step, it describes what the visitor gets, it appears at the right moment, and it's visually the most obvious thing to click. Most weak CTAs fail on one of the four, and the fix depends on which one.
Quality | What good looks like | Common failure |
|---|---|---|
Clear next step | One primary action per page | Three equal buttons asking for different things |
Specific value | "Get my pricing breakdown" | "Submit" or "Learn more" |
Right moment | After the reader has the information to decide | A demo ask before the product is explained |
Visual priority | Highest-contrast element in its section | A button styled like every other link |
Low friction | Short form, reassurance under the button | A ten-field form with no explanation |
The thread running through all five is that a CTA is a promise. The visitor is deciding whether the thing behind the button is worth what it costs them: time, an email address, a sales call. Your job is to make the value obvious and the cost feel small.
How do you write CTA copy that gets clicked?
Write CTA copy that names the outcome or the next step in the visitor's terms, not the action of clicking. "Submit", "Click here" and "Learn more" describe mechanics. "See it on your data", "Get the checklist" and "Book a 20-minute walkthrough" describe what happens, and they let the visitor judge whether it's worth it.
- Start with a verb that matches the offer: start, get, see, book, try, download, join.
- Name the thing: "Start your free trial" is clearer than "Start now".
- Match the commitment to the page: a cold visitor from an ad is more likely to watch a demo than book a call.
- Use first person when it reads naturally: "Send me the guide" can read better than "Send the guide", but test it rather than assuming.
- Keep it short: two to five words on the button, with any detail in the line under it.
The one hard data point in this area is a widely cited Optimizely test in which "Watch a Demo" converted at 1.59% against 0.91% for "Get Started". The lesson isn't that one phrase always wins. It's that a specific, lower-commitment ask beat a vague one. Practitioners consistently rank "Request a demo" and "Submit" among the weakest labels for the same reason: they describe effort, not value.
- Conversion rate for 'Watch a Demo' in the Optimizely CTA test
- 1.59%
- Conversion rate for 'Get Started' in the same test
- 0.91%
If you want copy to lift directly, our list of CTA button text examples is organised by offer: trial, demo, waitlist and download. And because the button label only works if the headline set it up, pair it with our guide to writing a landing page headline.
Where should you place a call to action on a landing page?
Place a call to action wherever a reader could reasonably be ready to act: in the hero, after the key proof, and at the end of the page. The rule "always above the fold" is half right. The hero should carry the CTA for visitors who arrive ready, but visitors who need convincing will only click after the section that convinced them.
In the hero
For visitors who already know what they want. The headline and subheading must explain the offer well enough that the button makes sense here.
After the product explanation
Once the visitor understands what the product does, repeat the primary CTA. This is often where the first real clicks happen on complex products.
After the strongest proof
Testimonials, case studies and numbers lower risk. A CTA straight after them catches the visitor at their most convinced.
After pricing or the FAQ
Objections are answered here, so a CTA placed right after removes the need to scroll back up.
At the end of the page
A final, full-width CTA section for readers who read everything. Restate the offer in one sentence.
On long pages, a sticky header button or a slim sticky bar on mobile keeps the action in reach. Those help when they don't cover content and don't appear before the visitor knows what the offer is. Our guide to sticky CTAs and exit-intent popups covers when they help and when they cost trust or speed.
How many calls to action should a landing page have?
A landing page should have one primary call to action, repeated as many times as the page length needs, and at most one clearly secondary option. Repeating the same CTA isn't the problem. Competing CTAs are: when "Start trial", "Book demo", "Download whitepaper" and "Follow us" all carry equal visual weight, the visitor has to choose, and many choose nothing.
A secondary CTA earns its place when it serves visitors who aren't ready for the primary one, such as "See pricing" next to "Start free trial", or "Watch a two-minute demo" next to "Book a call". Style it as a text link or an outline button so the hierarchy is obvious. Our full guide to how many CTAs a landing page should have covers repeated vs competing CTAs and how to set the hierarchy.
How should a CTA button be designed?
A CTA button should be designed to be the most visually obvious interactive element in its section, with enough contrast, size and space that nobody has to look for it. Color matters only relative to the rest of the page: the "best button color" is whichever one stands out from your palette, not a universal winner.
- Contrast: the button should contrast clearly with its background and with nearby buttons. Check text contrast against the button fill too, using the WCAG contrast guidance on w3.org.
- One accent color: reserve the button color for primary actions so it trains the eye. If links, badges and icons share it, it stops signaling anything.
- Size and tap area: large enough to tap easily on a phone, with space around it so it isn't mistaken for neighbouring links.
- Clear states: a visible hover, focus and pressed state, and a loading state after clicking so nobody clicks twice.
- It looks like a button: solid fill, readable label, no ghost buttons for the primary action.
Whitespace is the underrated tool here. A button surrounded by space reads as important even in a muted color, while a bright button jammed between paragraphs and icons gets lost. Design the section around the button rather than dropping the button into a finished section.
Hypothetical example: rebuilding a cluttered hero CTA
For example, suppose a SaaS hero has the headline, a subheading, two buttons of equal size ("Get Started" and "Contact Sales"), an app store badge, a newsletter field and a row of social icons.
The rebuild keeps the headline and subheading, replaces "Get Started" with "Start your 14-day trial" as a solid primary button, turns "Contact Sales" into a text link reading "Talk to sales", adds a reassurance line under the button, and moves the newsletter field and social icons to the footer. Nothing new was added; the hierarchy was simply made obvious. This is an illustrative scenario, not a measured result.
What happens after the click?
After the click, the call to action continues into the form, the confirmation and the thank-you page, and each one can lose the conversion the button won. A visitor who clicks "Get my audit" and meets a twelve-field form has been misled by the button. A visitor who submits and lands on a bare "Thanks" page has nothing to do next.
The form
Ask only for what changes who follows up or how. Every extra field costs completions, and fields like phone number often get fake answers anyway. Our guide to landing page form design goes field by field on what to keep and cut. If the form must be long, splitting it into steps can help, though the famous "300% more conversions" claims don't hold up, as our comparison of multi-step vs single-step forms explains.
The microcopy
The small line under a button or field often decides the click: "No credit card required", "Takes 2 minutes", "We'll reply within one business day". It answers the last-second doubt the button can't. Our guide to conversion microcopy has examples by situation.
The thank-you page
The confirmation page is where a lead becomes a meeting or an activated user. Embed the scheduler, show what happens next, or point to the most useful first step. Our guide to thank-you pages shows how to make it the next step instead of a dead end.
Which CTA fits which offer?
The right CTA depends on what the visitor is being asked to commit to and how ready they are. A free trial suits self-serve products a buyer can evaluate alone. A demo suits complex or sales-led products. A download or waitlist suits visitors who are early in research or products that aren't available yet.
Offer | Good fit when | Example label | Reassurance line |
|---|---|---|---|
Free trial | Product shows value in a first session | Start your free trial | No credit card required |
Demo or call | Product is complex or priced per deal | See it on your data | 30 minutes, no slides |
Recorded demo | Visitors are interested but not ready to talk | Watch the 3-minute demo | No signup needed |
Waitlist | Product isn't open yet | Join the waitlist | We'll email you once, at launch |
Lead magnet | Visitor is researching | Get the checklist | Instant download, no sales call |
Pricing view | Buyer wants cost before committing | See pricing | Plans from day one, no call needed |
Lead magnet CTAs need their own page design, because the value of the download has to be shown before anyone hands over an email. Our guide to lead magnet landing pages covers that. For AI and technical products, where the offer is harder to explain, our guide to explaining AI products shows how to set up the ask.
How do you test and improve a call to action?
Test and improve a call to action by changing the thing most likely to matter first: the offer and the commitment, then the label, then the placement, and the color last. Swapping "Book a demo" for "Watch a demo" changes what the visitor is agreeing to, which can move results. Swapping green for orange rarely does.
- Check tracking: make sure clicks and completions are recorded separately, so you can tell a button problem from a form problem.
- Watch recordings: see whether visitors notice the button, hover and leave, or click and abandon the form.
- Write a hypothesis: tie the change to something you observed. Our A/B test hypothesis guide has a template.
- Change one meaningful thing: the offer, the label or the position, not all three at once.
- Measure completions, not clicks: a label that wins clicks but loses form submissions hasn't helped.
Low-traffic pages can't run valid tests on small changes, so treat CTA work there as research-led fixes: ship the change, watch the funnel and the recordings, and keep notes. If the CTA keeps underperforming after a few rounds, the problem is usually upstream: the value proposition isn't clear enough for anyone to want the next step, and that's a homepage or landing page rewrite, as our guide to homepage-only redesigns discusses.
What should you read next on CTAs and forms?
Use this list to go deeper on whichever part of your call to action is weakest. Each guide covers one piece of the flow from button to confirmation in detail.
If you need to fix | Read this |
|---|---|
The button wording | |
Too many buttons | |
Form fields | |
Long forms | |
Doubt at the last second | |
Sticky bars and popups | |
What happens after submit | |
Download offers |
If the issue is positioning rather than the CTA itself, our positioning statement template is the place to start, because a clear position makes every call to action easier to write.
