Design

Where should the second call to action go?

Written by
Pravin Kumar
Published on
Sep 27, 2026

Where should the second call to action go?

Immediately after the section that answers the reader's biggest doubt. Not at a fixed depth, not halfway down, and not at the end because that is where CTAs go. The correct position is wherever the page has just finished earning the ask.

Most pages get this wrong in the same way. There is a button in the hero, then a long run of content, then another button at the bottom. The reader becomes convinced somewhere in the middle and then has to scroll to the end to act, which is a small friction applied at the exact moment it costs the most.

So the useful question is not how many buttons to add. It is where belief actually happens on your page.

Why does one call to action at the top not work?

Because it asks before the reader knows what they are agreeing to. A hero CTA converts the people who arrived already convinced, which is a small and valuable group, and does nothing for everyone else.

That is not an argument against the hero CTA. It should be there, because the pre convinced visitor should not have to hunt. It is an argument against treating it as the page's only ask.

The people you are losing are the ones who needed three more paragraphs. They read, they became interested, and then the page kept explaining. Interest decays, and a page that has nothing to offer at the moment of peak interest is wasting its best content.

What makes a reader ready to act?

Having their specific objection answered. Readiness is not a function of scroll depth, it is a function of doubt resolution, and different readers arrive with different doubts.

In practice there are usually two or three dominant objections on any page. Will this work for a business like mine, can I afford it, and how much work is it to get started. Each of those has a section on the page that answers it, and the end of that section is a moment of readiness.

That is why a single fixed CTA position cannot be right. If your page answers three objections, you have three natural moments, and which one a given reader hits depends on which doubt they walked in with. This is the same reasoning behind deciding how much a page should explain before it asks.

Should the second call to action be the same as the first?

Usually yes, in wording and destination. Varying the ask feels creative and reads as indecision. If the primary action is booking a call, every primary CTA on the page should say something close to booking a call.

What can change is the framing around it. The hero CTA sits under a promise. The mid page CTA sits under a resolved objection, so the sentence next to it can acknowledge that. Same button, different context.

Where people go wrong is inventing a new offer for the second position because repeating themselves felt lazy. Now the reader has two different things to evaluate, which is more cognitive work at precisely the wrong moment.

Where exactly on the page?

After the proof, not before it. If your page has a section that demonstrates the thing works, the CTA belongs immediately below it, because that is the highest belief point on the page.

The second best position is after the pricing or scope section, because a reader who has just accepted the cost is briefly decisive. Waiting until the end means asking after they have had time to think of a new reservation.

What I would avoid is placing it between two explanatory sections with no logical break. A CTA in the middle of an argument interrupts the argument, and interrupted arguments do not persuade. Proof placement follows the same logic, which I have written about in where to put testimonials so they get read.

What about a sticky call to action?

It solves the availability problem and creates an attention problem. A persistent bar means the ask is always reachable, which is genuinely useful on long pages. It also occupies screen space permanently, which matters most on the devices where space is scarcest.

If you use one, make it quiet. A slim bar with the same wording as your primary CTA, appearing after the reader has scrolled past the hero, is unobjectionable. A large floating panel that covers content is a tax on every reader to catch a few.

My own preference is in page CTAs placed well over a sticky element, because a well placed CTA is a design decision and a sticky bar is often a substitute for one. If you cannot decide where belief happens on your page, a sticky bar hides that problem rather than solving it.

How many is too many?

Three primary asks on a long page is comfortable. Five starts to feel like pressure. The number matters less than whether each one sits at a moment that earned it.

A useful test is to read the page and ask, at each CTA, what the reader has just learned. If you can name it, the CTA is placed. If the answer is "nothing in particular, it had been a while", delete it.

Across more than 70 projects for more than 25 clients over more than six years, the pages that converted best were rarely the ones with the most asks. They were the ones where each ask arrived right after something had been proved.

For the reader who is not ready to buy, offer a smaller, honest next step, and only one. Something genuinely useful on its own rather than a gate designed to capture an email address.

The distinction matters. A page that offers a real answer to a real question earns the right to ask for contact details. A page that hides ordinary information behind a form teaches the reader that you will trade their inconvenience for your metrics.

Keep the secondary ask visually subordinate. If the primary and secondary CTAs look equally important, you have asked the reader to make a decision about which decision to make, which is the one thing a call to action is supposed to remove.

Does any of this change for readers arriving from an AI answer?

Yes, because they arrive mid thought rather than at the top. Someone who followed a citation is looking for the specific thing they were promised, and they may land on a section rather than reading from the start.

That argues for CTAs that make sense out of sequence. A button labelled with the action rather than with "get started" survives being encountered cold, because it does not depend on the sentence above it for meaning.

It also argues for each section being self contained enough to stand alone. I have gone into what that means for page structure in designing a page for visitors who arrive from an AI answer.

How do you tell whether it is working?

Compare which CTA gets used, not just how many conversions you got. If the bottom one does all the work, your page is too long before the first real ask. If the mid page one dominates, you have found where belief happens and you should consider moving proof earlier.

Give it long enough to mean something. Small differences in CTA performance on low traffic pages are noise, and reacting to noise is how pages end up redesigned every quarter with no cumulative improvement.

What I would measure above all is whether the people who arrive through the second CTA are better qualified. Volume is easy to move by asking more often. Quality tells you whether the page is persuading or just nagging.

What should you do next?

Open your most important page and mark the end of each section that resolves a real objection. Those marks are your candidate positions. Put one primary CTA at the strongest of them and leave everything else alone for now.

Then read the page from the top as a sceptical stranger and notice where you first felt convinced. If there is no ask within a screen of that point, you have found the change worth making this week.

If you want a second opinion on where the belief moments are on a page you are working on, reach out. It is much easier to see from outside than from inside.

Get found, cited and the back office automated

Let's make your site the source AI engines quote and wire up the systems behind it.

Contact

Let's get your website found and cited by AI

Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.

Got it, thanks. I read every message personally and reply within 1-2 business days.
Oops! Something went wrong while submitting the form.