How do I write button labels that make the next step clear?
Quick answer
Describe the action a button starts with a concise verb and a specific object or destination. Then check that the next page or process matches what the label suggests. For example, use “View available plans” to open a plans page, but “Choose a plan” only if visitors can make that choice next. If the result is uncertain or conditional, label the immediate action rather than promising an outcome.
The question, the details, the next step.
I’m revising buttons on a website. How can I tell whether a label makes the next step clear?
Write down three things for each button: the action it starts, where it takes the visitor, and what the visitor can expect to do or see there. The label should describe that actual next step, not the eventual goal of the whole journey.
For example, if a button opens a page showing different plans, “View available plans” sets a clearer expectation than “Get started.” If it submits a request, “Send request” may be more accurate than “Learn more.” The right wording depends on what happens after selection, so check the destination or process before choosing a label.
What should I write down when I check the destination?
Use a small worksheet and keep each part concrete:
- Action: What does selecting the button initiate? For example, it might open a page, download a file, or submit entered information.
- Destination: What page, screen, file, or next step appears?
- Expected result: What can the visitor do or see immediately afterward?
- Label: What concise wording describes that action and result without claiming more?
A useful test is to read only the label and ask, “Would a visitor be surprised by the next screen?” If yes, revise the label or make the destination match it. Don’t use a more attractive promise just because it sounds persuasive.
Could you show me how to apply that? Suppose my button opens a page with a form to request a callback.
Assuming the button opens the form and does not itself send a request, fill in the worksheet like this:
Action: Open the callback-request form. Destination: A page containing that form. Expected result: The visitor can enter details and submit a request. Possible label: “Request a callback” if that is the form’s purpose and it’s clear that the request still needs to be submitted. “Open callback form” is more literal if you want to emphasize the immediate step.
Avoid “Get a callback” at this point: it can sound as though selecting the button itself schedules or guarantees one. Make the form’s next action and any relevant conditions clear in the surrounding content. The button label cannot explain details that have not been established.
How short should the label be, and what if I have several buttons on the page?
Aim for the shortest wording that still identifies the action. A verb plus a useful object or destination often works: “Download the guide,” “View locations,” or “Save changes.” Use these only if they match what your buttons actually do.
When a page has several buttons, compare their labels side by side. Make different actions sound different, and avoid giving unrelated buttons the same vague label, such as “Continue.” If a label needs a long explanation to avoid misleading someone, consider whether the next step or nearby explanatory text needs clarification. Don’t imply a purchase, submission, appointment, download, or completed result unless that is what the visitor can reasonably expect from selecting it.
Can you give me a reusable check before I publish?
For every button, complete this copyable worksheet:
Button label: [draft wording] Selecting it starts: [specific action] It takes the visitor to: [destination or next screen] The visitor can then: [immediate expected result] Possible gap or overpromise: [anything the label suggests that does not happen] Revised label: [short, accurate wording]
Then read the revised label without the surrounding page and predict what happens next. Compare that prediction with the actual destination or process. If they differ, adjust the label or the experience. When you cannot confirm the destination or outcome, mark it for verification rather than guessing.
A practical checklist
Record what selecting the button actually starts.
Name the destination or immediate next screen.
Describe what the visitor can do or see next.
Choose concise wording that fits the action.
Remove wording that implies an unconfirmed or guaranteed result.
Compare neighboring buttons to make their actions distinguishable.
A few more useful answers
Is “Submit” always a bad button label?
No. It can fit when the action is clearly a submission, but a more specific label such as “Send request” may better identify what is being submitted. Choose wording that matches the actual action.
Should every button start with a verb?
A direct action word is often useful for making the next step apparent. The important test is whether the complete label accurately describes what selection does, not whether it follows a rigid formula.
What if the button’s outcome depends on what the visitor enters?
Label the immediate action, such as “Check availability,” rather than promising a particular outcome. Explain relevant conditions near the button when they affect what happens next.