Skip to main content
Buttons and links are critical navigation elements that enable users to take action. Effective button and link text clearly communicates what will happen when clicked.

​
Purpose

Buttons and links should:
  • Enable users to take action
  • Clearly communicate the result of clicking
  • Use specific, descriptive verbs
  • Match user mental models

​
The pattern

Follow this simple pattern for button labels: 
[Verb] [object]

​
Examples

Good examples

  • Save changes
  • Delete account
  • View details
  • Download report
  • Send message

Avoid

  • OK
  • Submit
  • Click here
  • Continue
  • Proceed

​
Format guidelines

1

Use active imperative verbs

Start with a strong action verb that describes what happens.
  • Good: “Delete account”
  • Avoid: “Account deletion”
2

Include the object

Tell users what they’re acting on.
  • Good: “Save changes”
  • Avoid: “Save”
3

Use sentence case

Only capitalize the first word (unless it’s a proper noun).
  • Good: “Create new project”
  • Avoid: “Create New Project”
4

Keep it concise

Aim for 2-4 words, maximum 6 words.
  • Good: “Export to CSV”
  • Avoid: “Click here to export your data to CSV format”

​
Link text

Links require special attention for accessibility and clarity.

​
Screen reader friendly

Screen readers often list all links on a page out of context. Your link text should make sense on its own.
Users with screen readers often navigate by pulling up a list of all links. If your links say “click here” or “learn more,” the list becomes useless:
  • Click here
  • Click here
  • Learn more
  • Read more
Instead, descriptive links create a useful list:
  • Read our privacy policy
  • View pricing details
  • Download the guide
  • Contact support

​
Link best practices

Use descriptive text that tells users where they’re going
Make links long enough to click easily (at least 2-3 words)
Avoid “click here” or “read more”
Don’t repeat the same link text for different destinations

​
Examples

ContextBadGood
Privacy policyClick here for more informationRead our privacy policy
Help docsLearn more about this featureView the integration guide
ContactClick here to contact usContact support
DownloadDownloadDownload the onboarding checklist

​
Context-specific patterns

​
Primary actions

Primary buttons should clearly state the main action:
  • Sign up screens: “Create account” (not “Get started”)
  • Checkout: “Place order” (not “Submit”)
  • Forms: “Save changes” (not “Save”)

​
Secondary actions

Secondary buttons can be slightly less specific:
  • “Cancel”
  • “Go back”
  • “Skip for now”

​
Destructive actions

For irreversible actions, be explicit:
Use clear, serious language for destructive actions. Users should never accidentally delete data.
  • Good: “Delete account permanently”
  • Avoid: “Remove” or “Clear”

​
Confirmation buttons

Confirmation dialogs should repeat the action: 
Dialog: "Delete this project? This can't be undone."
Button: "Delete project" (not "Yes" or "Confirm")

​
Quick reference

Do

  • Start with an action verb
  • Include the object being acted on
  • Use sentence case
  • Be specific about the action
  • Keep it under 6 words
  • Make links descriptive

Don't

  • Use generic labels (OK, Submit)
  • Say “click here” in links
  • Use title case
  • Leave out the object
  • Make links too vague
  • Rely on context alone

​
Related resources

Accessibility

Learn more about writing accessible link text

Voice and tone

Adapt button copy to your brand voice

Quality standards

Apply the four quality standards to buttons

Build docs developers (and LLMs) love

Get started for freeTalk to us