top of page

Where to put the call to action so people find it when ready

  • 4 days ago
  • 3 min read

Introduction


The usual debate is whether the request belongs at the top of the page or the bottom, and it has no general answer because it depends on something specific: where in the page a reader becomes convinced. Some arrive already decided and want the phone number immediately. Others need the whole argument first. Both exist on every page.

The practical consequence is that the question is wrongly framed. It is not where to put the call to action but where to put them, plural, since the same request appearing at each point where somebody might be ready costs nothing and catches people who would otherwise have to go looking.


1. Where to put the call to action depends on where readers become ready


The organising idea.

Readiness is distributed through the page. A single request assumes everybody becomes ready at the same point, which is not how any page is read. The right number of placements is therefore usually three rather than one, and the debate about top or bottom dissolves.


2. Put one where somebody already convinced would look


The top of the page.

Referred visitors, returning visitors and people who searched your name arrive decided. Making them scroll past an argument they do not need is a small but entirely avoidable loss. This group is small and unusually valuable, because somebody already recommended you.


3. Put one after the main argument


The natural point.

Immediately after whatever does the persuading — the explanation, the proof, the price — rather than several sections later. Placement should follow the persuasion rather than the layout. Find the paragraph that convinces and put the request underneath it.


4. Put one at the end


The completion point.

Somebody who has read the whole page is the most convinced reader you have. A page that ends without a request leaves them to navigate, and some will not. Ending on a footer rather than an action wastes the best-qualified visitor on the page.


5. Repeat the same one rather than varying it


The consistency rule.

The same wording, the same action, at each point. Different requests at different points is a menu rather than repetition, and it produces the competing-actions problem.


6. Put contact details beside the price


The specific high-value placement.

Wherever cost is discussed is where people decide. A request at that exact point captures the moment better than one three screens away.


7. Consider a persistent option on long pages


The mobile consideration.

On a phone, a long page means the request is off-screen almost always. A modest persistent button solves this, provided it does not cover the content.


8. Do not hide it behind navigation


The obvious failure.

A contact page reachable only through a menu adds a step at the moment of intent. Direct routes on the page itself convert better than any menu arrangement.


9. Check where people actually leave


The evidence.

If most readers leave halfway, a request at the bottom is serving a minority. Scroll depth tells you where your requests should be, and it is usually not where they are.

Be careful about placing a request before the page has earned it. On a page whose job is to explain something to a stranger, an immediate demand for contact details reads as impatience and reduces the attention you needed to persuade them.


Conclusion


Place the same request at each point where a reader might be ready.

Put one near the top for people who arrive already decided, one immediately after whatever does the persuading, and one at the end for readers who finished, repeat the identical wording rather than varying it, place a request beside any discussion of price, consider a modest persistent option on long mobile pages, avoid making people navigate to a contact page, and use scroll depth to check that your placements match where people actually are.


Related reading


 
 
 

Comments


bottom of page