Design

How Many Calls to Action Should a B2B Page Have?

Written by
Pravin Kumar
Published on
Sep 9, 2026

How many calls to action should a page on a B2B site actually have?

One primary action, repeated as often as the page is long, plus at most one secondary action for people who are not ready. That is the answer for almost every page I build, and the disagreements about it usually come from counting buttons rather than counting decisions.

A page can carry a request for a demo at the top, again in the middle, and again at the end, and still be a one-decision page. A page that offers a demo, a trial, a newsletter, a download and a chat widget is a five-decision page even if it looks tidier.

Here is the argument for constraint, the honest case against it, and how to decide for a specific page rather than by rule.

Why does adding another option make a page perform worse?

Because choosing is work, and work is what makes people leave. The Nielsen Norman Group states Hick's Law simply: the more choices you present to your users, the longer it takes them to reach a decision. In an article by Katie Sherwin from July 2018, that principle is applied to menus, and it applies just as directly to a stack of competing buttons.

The related effect has a name too. NN/g defines choice overload as too many offerings on a website making it harder for users to make a decision due to analysis paralysis. In a piece by Alita Kendrick from February 2020, the listed consequences are analysis paralysis and struggling to decide, and hasty decisions followed by buyer's remorse.

That second consequence is the one B2B teams underrate. A visitor who books a demo they were not ready for is not a win. They arrive unqualified, they no-show, and your sales team learns to distrust the channel. The upstream version of that problem is in scoring form leads before they reach a human. Choice overload does not only reduce action, it degrades the quality of the action you get.

What is the honest case for more than one call to action?

People arrive at different stages, and a single high-commitment action serves only one of them. Someone comparing three vendors is not going to book a call, and a page that offers them nothing else has not converted them, it has just declined to.

This is a genuine argument and I do not want to wave it away. The resolution is not to add options, it is to make the second option obviously subordinate. One primary action that is visually loud and specific, one quiet alternative for the not-yet, and nothing else competing for the same attention.

What makes this work is that a secondary action of lower commitment does not compete with the primary one. Book a demo and read the technical documentation are not rivals, because nobody who wants a demo is diverted by documentation. Book a demo and start a free trial are rivals, because they serve the same person at the same moment, and now that person has to think.

How does page length change the answer?

It changes how often you repeat, not how many different things you offer. A long page needs the same action available at several points, because a reader who becomes convinced at the two-thirds mark should not have to scroll to find out what to do.

The reading research supports keeping each of those moments brief. Jakob Nielsen, writing for NN/g in 2008 on an analysis of 45,237 page views, concluded that on the average web page users have time to read at most 28 percent of the words during a visit, and that 20 percent is more likely. The same analysis found that users read half the information only on pages with 111 words or less.

That research is old and I flag the date deliberately rather than presenting it as current. But the implication for CTA placement has not weakened: most of your page will be skimmed, so the action has to be legible to someone who is skimming, and it has to appear wherever their attention might land.

What counts as one call to action and what counts as two?

Same destination, same commitment, same words: one. Different destination, different commitment, or different words: two, however similar they look to you.

The wording point matters more than people expect. A page with buttons that say Get started, Talk to sales and Request a demo has three actions, even if all three open the same form, because the reader cannot tell that they are the same. You have created a decision that does not need to exist, and then asked them to make it.

So the first audit of any page is not how many buttons there are, it is how many distinct promises are being made. Count promises. That number should be one, or one plus a clearly lesser one.

Where does the navigation fit into this count?

It counts, and it is the most commonly forgotten source of competition. A header with a prominent Sign up button and a page with a prominent Book a demo button is offering two primary actions on the same screen, and the fact that they live in different components does not help the reader.

The fix is usually to let the navigation carry the site-wide action and the page carry the page-specific one, and then make sure only one of them is visually dominant. If your page is about a specific product and your header is shouting a generic signup, the header is undermining the page it is sitting on.

The same applies to persistent chat widgets, cookie banners, exit intent modals and sticky bars. Each is an interruption that arrives with its own request, and none of them appear in the count when a team reviews a design in isolation. Look at the page as a visitor sees it, with everything running.

What about pages where the reader is not ready to do anything?

Blog posts, glossary entries, documentation. Here the honest primary action is often to read something else, and pretending otherwise produces the sad pattern of a demo request under a beginner explainer.

On those pages I use a contextual link into a more relevant page as the primary action, and a single low-commitment offer at the end. That respects where the reader is, and it keeps the more valuable conversion available for the pages where the reader is closer to deciding.

This is also the version of the argument that saves you from the false comparison. If you measure demo requests per page across a whole site, informational pages will always look like failures, and the instinct will be to add stronger CTAs to them. That is exactly the wrong response. I made the related structural argument in designing an integration page template.

How do you decide for a specific page?

Write down what a reader on this page has just understood, and what the single most reasonable next step is for someone in that state. If two next steps both seem reasonable, the page is probably serving two audiences and should be two pages.

Then check the count against everything actually on screen: header, body, sticky elements, widgets, footer. Across 70 plus projects for 25 plus clients over 6 plus years, the number I find is almost always higher than the team believes, because nobody ever counts the components they did not design that week.

And measure the right thing afterwards. Not clicks on the button, which will always rise when you make a button louder, but completed actions of the quality you wanted. A design that produces fewer, better demo requests is a success that a click-rate dashboard will report as a failure. Getting the tagging right is what makes that distinction visible at all, which I covered in setting up UTM tracking for campaigns.

What should you do next?

Open your most important page on a phone, with everything enabled, and count the distinct promises being made to you. Header, hero, body, sticky bar, chat, exit modal, footer. Write the number down before you look at any analytics.

Then reduce it to one primary and at most one secondary, keep the primary repeated down the length of the page in identical words, and leave it alone for a full sales cycle before judging. Changing the count and the copy and the placement at once tells you nothing about which one mattered.

I design and build conversion-focused pages on Webflow as a Certified Webflow Partner, on fixed fees, with most projects landing between 1,000 and 10,000 dollars. If your pages are busy and your conversion rate is not, reach out and let's chat.

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.