---
title: CTA label matches the page it leads to | UX guide · Rubric
description: Word the CTA to describe exactly what the destination page is, using the same or closely matching terms — a button labelled "See Plans" leads to a page…
url: https://rubric.design/ux/forms.cta-label-matches-destination
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / [Forms](https://rubric.design/ux/topic/forms) / CTA label matches the page it leads to

# CTA label matches the page it leads to

Usually high · How serious this usually is when it goes wrong. Not a score.

## The guideline

Word the CTA to describe exactly what the destination page is, using the same or closely matching terms — a button labelled "See Plans" leads to a page whose own heading is about plans and pricing, not the general homepage. When a redesign changes a destination page's purpose or URL, audit every CTA that points to it and update the label to match; a stale label is a broken promise even though the link itself still resolves. Where a CTA leads somewhere the visitor has to search the destination page to locate the promised content, that is the same defect as a mislabeled one, even if the words technically matched.

## Common failures

- The CTA label doesn't match the destination — "See plans" leads to the homepage instead of the pricing page.

## Where it applies

### Pages

- Forms

### Disciplines

- Conversion

### Devices

- Desktop web
- Mobile app
- Mobile web

## Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Entered checkout data survives errors and back-navigation](https://rubric.design/ux/checkout.entered-data-persists-through-errors) · Usually high · Preserve every non-sensitive field — name, address, phone, email — across validation errors, session-level failures, and backward or forward navigation within…
- [Slow checkout actions show a status, not a frozen screen](https://rubric.design/ux/checkout.loading-state-feedback) · Usually high · Show a spinner or progress indicator within a fraction of a second of any checkout action that can take more than a couple of seconds — payment submission…
- [Inputs declare their type and autocomplete purpose](https://rubric.design/ux/forms.autofill-and-input-type) · Usually high · Set the type attribute to match the data a field collects (email, tel, number with inputmode, and so on) and add the matching autocomplete token from the HTML…
- [Selecting an option applies it immediately, without a separate Apply step](https://rubric.design/ux/forms.changes-apply-without-a-button) · Usually high · Apply the result of a selection — a radio button, a dropdown, a quantity stepper — as soon as it is made, updating totals, delivery estimates and stock…
- [Required and optional fields are both marked, consistently](https://rubric.design/ux/forms.required-optional-marking) · Usually high · Mark every field's required/optional status explicitly and visibly — not only the required ones, since a form with asterisks on some fields leaves every…
