A CTA's click rate measures visibility. Whether that click converts depends on whether the copy promised what the destination delivers.
TL;DR
- A CTA fails for one of two reasons: the user doesn't see it (visibility failure) or sees it and reads it as something else (intent failure).
- Visibility failures are loud — low CTR, low scroll engagement on the CTA region. Most teams catch these.
- Intent failures are quiet — _high_ CTR, _low_ click-to-conversion rate, bounce-back from the destination. Most teams miss these.
- The diagnostic is per-source-page click-to-conversion rate. If clicks from pages where audience intent doesn't match the destination dominate, the CTA copy is pulling the wrong audience.
- Fixing it: change the verb to predict the destination, or suppress the CTA on source pages where the audience can't be the intended one.
The two failure modes, mapped
Most CTA test reports tell you whether you're in the top half (visible) or the bottom half (not visible). They rarely tell you whether the click came with the right intent.
| Copy clear about destination | Copy unclear or mismatched | |
|---|---|---|
| Visible CTA | ✅ Real win. Healthy CTR + healthy click-to-conversion. Conversion grows. | ⚠️ The intent trap. Healthy CTR but low click-to-conversion. Users bounce from the destination. |
| Hidden / buried CTA | ⚠️ Visibility problem only. Low CTR but healthy click-to-conversion when clicked. Fix with prominence. | ❌ Compound failure. Low CTR AND low click-to-conversion when clicked. Fix both. |
The standard CRO playbook fixes the bottom half — visibility. Make the CTA bigger, brighter, sticky, above the fold. It does almost nothing for the right column — copy and destination misalignment. Most "we shipped the CTA test" failures live in the top-right cell. The CTA was visible. Users clicked. The clicks didn't convert because the copy promised one thing and the destination delivered another.
How to tell which cell you're in
Pull two metrics for the CTA in question:
| Metric | What it tells you |
|---|---|
| Click-through rate (CTR) | Visibility / placement / visual treatment |
| Click-to-conversion rate | Whether the click came with the right intent |
| If CTR is... | And click-to-conv is... | Failure mode | Fix |
|---|---|---|---|
| Healthy (>baseline) | Healthy (~baseline or above) | None — real win | Ship |
| Healthy | Low (<half of baseline) | Intent failure (top-right cell) | Change copy or suppress on wrong-intent pages |
| Low | Healthy | Visibility only | Make CTA more prominent, sticky, above-fold |
| Low | Low | Compound failure | Diagnose visibility first, then re-examine copy |
The intent failure is the cell most teams skip. It looks healthy at first glance because the click numbers are up. The diagnostic that exposes it is per-source-page breakdown.
In my experience reviewing navigation and landing-page tests, teams reach the copy diagnosis faster when the report groups source pages by user intent before anyone looks at button color or size.
The "Sign Up" trap: an illustrative composite
This synthetic composite represents a recurring navigation pattern rather than a named company or attributable test. A button says "Sign Up" and routes through a modal to a commercial selection flow. The aggregate looks positive; the source-page breakdown tells a different story.
| Source-page class | Click volume | Click-to-next-step rate | Audience intent |
|---|---|---|---|
| Help and billing content | Largest share | Low single digits | service or billing |
| Signed-in account surfaces | Meaningful share | Low single digits | account management |
| Commercial entry surfaces | Smaller share | Low twenties | evaluate or purchase |
| Total | Several thousand | Mid-single digits | mixed |
A large minority of clicks came from service and account pages. On those surfaces, the click-to-next-step rate was a fraction of the rate on commercial entry pages. The CTA fit the commercial context but created an intent mismatch on account-service surfaces, where users could read "Sign Up" as account access.
The CTA was visible. The clicks happened. The conversions did not — because the click was placed by a user looking for something the destination doesn't provide.
Three rules for CTA copy that binds intent to destination
| Rule | Bad | Good |
|---|---|---|
| The verb predicts the destination | "Continue", "Submit", "Next" | "View Plans", "Get Quote", "Apply Now" |
| The noun sets a specific expectation | "View" | "View Plans" or "View My Quote" |
| Avoid phrases with strong existing associations elsewhere | "Sign Up" (= account creation in most contexts) | "Shop Plans", "Browse Plans", "Get Started" |
If the click promises shopping, the destination must show shopping. If the click promises account access, the destination must show account access. Mismatched verbs are the most common copy-intent failure.
When you cannot rewrite the copy
Sometimes the CTA copy can't change. Brand approval, global navigation owned by another team, six-week deploy timeline. The cheaper fallback is per-page suppression: hide the CTA on source pages where the audience cannot be the intended one.
In the composite above, one candidate fix is suppressing "Sign Up" on service and account pages while keeping it on commercial surfaces. Per-page render conditions can be simpler than a global copy change, but the team should still measure whether suppression improves the pre-specified business outcome.
What user research keeps saying
Across many qualitative studies, these are useful hypotheses to test:
- Users want to know what happens after the click. Generic copy ("Next", "Continue", "Submit") is unsatisfying because it doesn't preview the destination.
- Action-oriented copy can outperform generic copy when it sets a clearer expectation. "View Options" tells users more about the next step than "Next."
- Benefit-led copy can pre-qualify a click when the benefit is accurate and supported. It should be tested against a clear action label rather than assumed to win.
- A promise-destination mismatch should be visible in path data. Look for rapid returns, abandonment after the click, and weaker downstream completion.
This is consistent with Jakob's Law: users bring expectations learned elsewhere. Familiar vocabulary can reduce uncertainty, but only a controlled comparison can establish what it changes on a particular product.
The behavioral mechanism
A click is a curiosity event. A conversion is a commitment event. The two are correlated when the path between them is well-designed and the copy sets accurate expectations. They decouple when:
- The verb / noun in the CTA implies a different destination than what the user lands on.
- The user's intent on the source page doesn't match the destination's audience.
- The destination has new friction (modal, form field, redirect) that wasn't implied by the CTA copy.
Each of these creates the same signature in the data: healthy clicks, broken conversion. The diagnostic per-placement breakdown catches all three.
Bottom line
Most CTA tests measure visibility. A CTA's value depends on visibility _and_ intent match — and intent failures show up as healthy click rates with broken conversion rates. Pull per-source-page click-to-conversion rate when the path spans multiple intent classes. If a high-volume source materially underperforms an intent-matched comparison, investigate copy and destination fit before shipping.
Visibility is the easy half. Copy intent is the half that determines whether a CTA test ships a real win or a cosmetic one.
FAQ
How do I know whether copy or prominence is the problem?
Read click-through and click-to-next-step together. Low clicking with healthy downstream completion points toward discovery or prominence. Healthy clicking with weak downstream completion points toward intent, routing, or destination friction.
Should every button use an action verb?
Use labels that predict the result of the action. The GOV.UK Design System's button guidance recommends clear action language, while W3C guidance on labels and instructions explains why controls need usable context.
Is per-page suppression better than rewriting the CTA?
It depends on ownership, intent mix, and implementation risk. Suppression can remove a clear mismatch quickly; a copy change may create a more coherent global experience. Test the option that addresses the diagnosed mechanism and preserves the pre-specified outcome.