CONTENT_CTA_001● HighContent
Primary call to action does not say what happens next
By Leakly · Published · Updated
01The problem
The main conversion button uses generic wording, so the visitor cannot predict the result of clicking it.
Unpredictable outcomes create hesitation right at the moment of commitment. A button that names the next step converts better than one that names an action.
02How Leakly detects it
A structural fact counted in the rendered page, or a measurement against a threshold. Confidence ceiling for this detector family: 96%.
The page's own copy, read against the goal — every claim must quote text that resolves in the capture. Confidence ceiling for this detector family: 80%.
03Proof required
- A verbatim quote that must be found again in the captured page.
Without it, the finding is not reported.
04How to fix it
Change the button to name what happens after the click.
- Replace the generic label with the outcome: what the visitor gets, not what they do.
- Keep the same wording on every step of the path so the promise does not drift.
Each audit that finds this leak includes the exact element, a suggested change and, for copy, a rewrite you can paste.