Lorixen.
EN

Button labels: what to write instead of "Submit"

Short answer: A good button label tells people exactly what happens when they press it: "Send my quote request", "Book a 30-minute call", "Download the price sheet". Generic words like "Submit", "Click here" or "Go" make visitors guess, and guessing at the last step is where forms get abandoned. Keep one main action per screen, make the label match what follows, and make sure icon-only buttons still have a name that screen readers can announce.

Most small-business websites in New Zealand put real effort into headlines and photos, then finish the page with a button that says "Submit". It is the single most-read piece of text at the moment of decision, and it is often the least considered. The fixes are cheap: a few words in a page builder or a template. Below are the mistakes we see most often, why each one costs you, and what to write instead.

Mistake 1: Labels that describe the machine, not the result

"Submit", "Send" and "Process" describe what the website does with the data. The visitor cares about what they get. Compare "Submit" with "Get my free measure-up" on a curtain installer's form. The second label repeats the promise of the page, so pressing it feels like collecting something rather than handing something over.

Write instead: a verb plus the outcome, from the visitor's side. "Request a callback", "Check availability", "Reserve my table", "Start my free trial". If the outcome has a useful detail, include it: "Book a 15-minute call" sets an expectation that a vague "Book now" does not.

Mistake 2: "Click here" and other labels that only work in context

"Click here", "Learn more" and "Read more" rely on the text around them. People scanning a page jump between headings and buttons, and screen reader users often pull up a list of links or buttons on their own. A list of five "Learn more" items tells them nothing.

Write instead: labels that make sense when read alone. "See wedding packages", "Compare plans", "Read the drainage case study" (only if it exists). On touch screens "click" is also the wrong verb, so leaving it out makes the label better on every device.

Mistake 3: Two or three buttons shouting at once

A hero section with "Get a quote", "Call us", "Browse services" and "Follow us" in matching bright colours gives the visitor four decisions instead of one. Usability researchers at Nielsen Norman Group have long argued that primary commands belong on buttons, while secondary options can be presented as plainer links with more room for explanation.

Write instead: decide the one action that matters most on each page and give it the strong button. Make the others visibly quieter: an outlined button, a text link, or a line further down. A plumber's homepage might use "Book a plumber" as the main button and "Or call 09 xxx xxxx" as a text line beneath it (illustrative only).

Mistake 4: A label that promises something the next step does not deliver

If the button says "See prices" and the next page is a contact form, people feel tricked, and they leave. The same goes for "Instant quote" leading to "we'll be in touch within two business days".

Write instead: a label that matches what actually happens. If the next step is a form, say "Ask for a price". If it is a booking calendar, "Pick a time". When a step takes longer, say so near the button: "We reply the same working day" is more honest, and more reassuring, than a fast-sounding label that the process cannot keep.

Mistake 5: Changing labels inside one process

A three-step booking flow that uses "Next", then "Continue", then "Proceed", then "Confirm" makes people wonder whether each button does something different. Inconsistent wording is a small irritation that adds up over a long form.

Write instead: pick one word for moving forward ("Continue") and keep it until the final step, where the label changes to the real commitment: "Confirm booking" or "Pay $… and book" if money is taken at that point. The change of word itself signals that this is the final button.

Mistake 6: Arguing about button order instead of labels

Should "Cancel" sit left or right of "Save"? Jakob Nielsen's view is that following the platform's convention matters more than optimising a single dialog, and that either order is defensible. The bigger risk is two buttons that look the same and carry vague labels like "Yes" and "No" under a confusing question.

Write instead: labels that answer the question on their own. Under "Remove this item from your cart?", the buttons "Remove item" and "Keep item" cannot be misread, whatever order they appear in. Style the destructive option so it does not look like the default.

Mistake 7: Icon-only buttons with no name

A magnifying glass, a cart icon, a hamburger menu, a small cross on a pop-up: these are buttons too. MDN's documentation on the HTML button element notes that buttons showing only an icon do not have an accessible name, which is the text assistive technology reads out. Without it, a screen reader may simply announce "button".

Write instead: give every icon button a name in the markup, for example with visually hidden text inside the button or an aria-label such as "Open menu" or "Close newsletter pop-up". Ask whoever builds your site to check this; most page builders have a field for it, but it is often left empty. MDN also points out that icons can be interpreted differently by different people, so for important actions a visible word next to the icon helps everyone.

A quick rewrite exercise

Take your three most important pages and list every button on them. For each, answer three questions:

  1. Could someone guess what happens next from the label alone?
  2. Does the next screen deliver exactly that?
  3. Is this the one action we most want on this page, and does it look like it?

Illustrative example: a Christchurch dog groomer (hypothetical) changed "Submit" on the booking form to "Request a grooming slot", turned "Learn more" under each service into "See what's included", and moved "Follow us on Instagram" from a big button into the footer. No new design, just clearer words and a calmer page.

FAQ

Should button text be in first person, like "Start my trial"?

Both "Start my trial" and "Start your trial" work. First person can feel more personal on sign-up and download buttons. What matters more is that the label is specific and that you use one style consistently across the site.

How long can a button label be?

Long enough to be clear, short enough to fit on a phone without wrapping awkwardly. Two to five words usually covers it. If you need more explanation, put a short line of supporting text next to or under the button rather than stuffing it into the label.

Does button wording affect SEO?

Not directly in any way you should plan around. Clear labels help visitors complete actions, and descriptive link text helps people and search engines understand where a link goes, so the two goals point in the same direction.

If your forms and buttons still say "Submit" and you would like them to say what customers actually get, tell us which pages matter most and we can rework the wording and markup together.

Sources

WhatsAppLet’s talk