Deep dive: "CTA above the fold" is conditional on one variable

Deep dive: "CTA above the fold" is conditional on one variable


The rule "always put the CTA above the fold" and the counter-rule "long pages with the CTA at the bottom convert better" are both cited with confidence. They're both right, and the variable that decides between them is the complexity of the decision.

The useful framing comes from a body of A/B testing (Michael Aagaard / Unbounce ran several public experiments on this) showing CTA placement interacts with offer complexity. For a simple, low-commitment, well-understood offer, a high CTA wins — the visitor arrived ready and you shouldn't make them hunt. For a complex or high-perceived-risk offer, the same high CTA can hurt: asking for the click before you've built the case is premature, and a lower CTA after the argument converts better. Aagaard's documented result was a lower-placed CTA outperforming a higher one once the offer required explanation.

The mechanism is decision-readiness. A CTA is a question, and a question lands well only after the visitor has the information to answer it. Place the ask before the case is built and you get a "no" by default (the safe answer to an unsupported request). Place it after, and you get a "yes" from someone now equipped to say it.

This dissolves the debate. The question isn't "how high should the CTA be," it's "how much does this visitor need to know before the ask is fair." Cheap, familiar offer: ask early and often. Expensive, unfamiliar, or trust-sensitive offer: earn the ask first, repeat it after each persuasion block.

For affiliate landers, match placement to commitment. A free tool signup tolerates a top-fold CTA. A "deposit and start trading" offer needs the case built first — and probably the CTA repeated at each natural decision point, not crammed into the hero.

TL;DR
— Placement interacts with offer complexity: simple offers favor a high CTA, complex/high-risk offers often convert better with a lower one after the argument.
— A CTA is a question; asked before the case is built, the default answer is "no."
— Match placement to decision-readiness — cheap/familiar: ask early; expensive/unfamiliar: earn the ask, then repeat it at each decision point.