Loading article…

Table of Contents

Quick Answer: How do you write a call to action that matches the next step?

Write a call to action (CTA) that tells visitors what they can do next. Choose the label after you know what the click opens, submits or commits them to.

  1. Identify the action and its immediate result.
  2. Use a verb and object that describe the actual task.
  3. Put price, timing or required details nearby when they affect the decision.
  4. Follow the click through to the next page or confirmation.

Treat a higher click rate as a diagnostic. Check whether visitors finish the intended action.

Call to action copywriting guide for choosing the next action
Call to action copywriting guide for choosing the next action

“Get started” can open a price list, a signup form or a calendar. Each asks something different of the visitor. Clear CTA copy connects the promise on the page with what the interface will do next.

Follow the Click All the Way Through

Trace the path on the real website. Does the visitor see more information, download a file, send a request, reserve a time or make a payment? Write down the immediate state and anything required after it. Check whether the landing page offer promises the same path.

The GOV.UK Design System recommends button text that describes the action, distinguishing “Continue” from “Save and continue.” [1] Apply that distinction to steps that change a visitor’s state. If a form sends a request and requires a later reply, reflect that in the label and confirmation.

Choose a Verb That Fits the Real Action

Consider a hypothetical installation website. “See installation prices” fits a link to published prices. “Request an installation quote” fits an enquiry path. Use a link labelled “Start a quote request” to open the form and a button labelled “Send quote request” to submit it. If you offer a price list, link to the actual prices. Compare a quote request and a demo booking by what the buyer wants to do, then choose the corresponding label.

WCAG 2.2’s guidance on link purpose says people should generally be able to determine a link’s purpose from the text or its programmatically determined context. [2] Make the label independently descriptive when practical, and use consistent labels for repeated links to the same destination.

Put Commitments Beside the Button

Use a short supporting line for important details. Near “Request a quote,” explain when a reply can be expected and what details the buyer needs to send. Before a payment action, state the actual amount and any recurring commitment. Remove conditions only when they are irrelevant to the visitor’s choice.

If the interface moves between stages, update the language. “Review order” suits a review step. “Place order” belongs where the action submits the order. Use the confirmation state to explain the result and any further steps.

Test What People Expect and What They Complete

Show the page to someone unfamiliar with it. Ask what they expect after selecting the action, then have them follow it. Check whether they can predict the next page, information requested and any commitment. If the answers are wrong, revise the label or supporting copy, then try the path again.

For a live copy comparison, hold the destination, offer, placement, styling and supporting copy constant when the label is the only change. Compare the share of eligible assigned visitors with an accepted quote request over the same period. Use clicks and exits to diagnose where a label attracted attention without preparing people for what followed.

Check Call-to-Action Copy Across Languages

If your WordPress site has multiple language versions, evaluate StagLingo on a few key pages. Check each translated action against the actual destination, form or confirmation.

Explore StagLingo and trial options

FAQs About Call-to-Action Copy

Is “Get started” too vague?

It can be clear when the surrounding text names the process and commitment. Use a more specific label if the next step could be mistaken for a purchase, signup or request.

Should multiple buttons on one page have the same label?

Use consistent wording when the buttons have the same purpose and destination. Use distinct labels when one action reviews a request and another sends it.

Where should you explain cost or a required signup?

Place the information beside the action when it changes the decision to continue. Confirm that the same terms appear at the next decision point.

Sources

[1] GOV.UK Design System. Button

[2] W3C Web Accessibility Initiative. Understanding Success Criterion 2.4.4: Link Purpose (In Context)