<b>"Always put the CTA above the fold" — the data says it depends on commitment level</b>

<b>"Always put the CTA above the fold" — the data says it depends on commitment level</b>

Deep dive: A persistent rule says the call-to-action must sit above the fold. Tested across enough cases, the rule breaks — and the exception reveals the underlying principle.

A frequently cited case from CXL/Conversion-rate testing: moving the call-to-action <i>below</i> the fold, after a longer explanatory page, beat the above-fold version on a high-commitment offer. Other A/B sets show the opposite for low-commitment offers. The contradiction resolves once you stop thinking about position and start thinking about <i>readiness to act</i>.

The mechanism is the match between information needed and information consumed at the moment of the ask. A call-to-action should appear when the visitor has enough information to say yes. For a $9 ebook or a free trial, that's almost immediate — above-fold CTA wins because waiting just adds friction. For a $2,000 course or a complex SaaS, asking above the fold is asking before the case is made; the visitor isn't ready, so a premature button underperforms a button placed after the argument.

Michael Aagaard's testing put it well: the CTA isn't "too low" or "too high" — it's placed at the right or wrong point in the visitor's decision journey. Position is a proxy for journey stage.

For affiliate landers, set CTA placement by offer complexity and traffic temperature. Cold traffic on a considered purchase needs the case before the ask. Warm traffic on a cheap offer wants the button immediately — and repeated down the page.

TL;DR:
— Above-fold CTA wins for low-commitment offers; below-fold can win for high-commitment ones
— Place the ask where the visitor has enough info to say yes — position proxies journey stage
— Calibrate by offer complexity and traffic temperature, not a fixed rule