The landing page questions nobody asks

A landing page that is not converting usually gets rebuilt from the outside in. Contrast on the button, whether the hero shows a product shot or a face, how many words belong in the headline. Real variables, and also the smallest ones. A page can get every one of them right and still convert badly, because the decisions that determine the outcome are made before anything is designed.

Those decisions are all about context: who arrives, what they already believe, what they are being asked to give up, and what they expect to happen next. Five questions worth answering on paper before anyone opens a design tool.

How warm is the traffic?

Temperature is how much a visitor knows and trusts before the page loads.

A cold visitor from a paid social ad was interrupted. They did not go looking for you; a targeting model decided they resembled someone who might care. They arrive with no context, low intent, and a thumb resting near the back gesture. Their first question is not "which plan" but "what is this, and why am I still reading".

A warm visitor from a referral, a newsletter, or a branded search has already accepted the premise. Someone they trust vouched for you, or they typed your name. Re-explaining the category wastes their first screen; they want scope, price, and a way to start.

One page cannot serve both well, because the two answers compete for the same space. Establishing the problem bores the warm visitor. Leading with price suits them and loses the cold one, who has not yet seen a reason to care.

A way to reason about it: write down the sentence the visitor was thinking one second before the click. For a cold ad it is usually a symptom, "our invoices keep slipping". For a warm referral it is about you specifically, "someone I trust said these people build exactly this". The top of the page should continue that sentence rather than restart the conversation. When the two sentences are far apart, that is the signal to build two pages.

What single thing should happen here?

A page offering three actions (book a demo, download the guide, join the newsletter) tends to underperform the same page offering one. Not because visitors are lazy. Each option carries a cost estimate the visitor has to compute: how long will this take, how much am I committing to, what happens to my inbox afterwards. Three options mean three estimates plus a comparison between them. That is work, and the cheapest way to finish work is to abandon it.

The cause is usually organisational. Several people each want their ask represented and the compromise is to include all of them, which optimises the page for internal agreement rather than for the person reading it.

A useful test: if this page could report exactly one number to the business, which number would it be? Anything that does not move that number is at best neutral, and a competing button is not neutral. Secondary asks belong in the footer, where they catch the people who already declined the main one.

What are you asking someone to hand over?

Form length has no fixed correct answer. The question is proportionality: does the size of the ask match what is on offer, as the visitor estimates it in that moment?

Nine fields to download a PDF is a bad trade, so people abandon the form or lie in it. The same nine fields to get a quote on a house renovation are reasonable, because the visitor can see the work cannot happen without the detail. Fields feel expensive when their purpose is invisible.

Two things follow. Remove fields you do not need in order to act; job title and company size collected so someone can score the lead are pure cost to the visitor. And where a field is genuinely necessary, say why next to it. "Rough monthly ad spend, so we can tell you quickly whether an audit is worth your time" behaves differently from a bare Budget dropdown, though the data collected is identical.

Phone number is its own case. It reads as an invitation to be called, a far larger commitment than an email address. If it is optional, label it optional.

Where does the doubt appear?

Social proof is usually treated as a quantity problem: more logos, more testimonials, a longer wall of quotes. Placement does more work than volume. Evidence persuades when it arrives at the moment of the doubt it answers, and does close to nothing in a band halfway down the page headed "what people say".

Walk the page section by section and name the objection a sceptical reader raises at each point. Next to a claim about speed: speed at the cost of what? Next to the price: is this sized for a team like ours? Next to the form: what exactly happens if I fill this in? Then put the answering evidence adjacent to the claim, not in a separate testimonial district.

This is also why having no case studies yet is survivable. Evidence and testimonials are not the same category. Working code, a public write-up of a technical decision, a precise description of your method, a demo someone can click: all of these answer doubt, and none require a customer quote. Specificity does the persuading. "Great to work with" convinces nobody; a concrete demonstration convinces with no name attached at all.

What happens after submit?

This is where conversions quietly die. The form is filled in, the button is pressed, and the page swaps in "Thanks, we'll be in touch". A receipt, not a next step.

The interval between submission and first human contact is exactly when doubt returns. The visitor has given something up and received nothing back. If the reply takes a day, that is a day in which they can book someone else or forget the whole thing.

Close the gap with specifics: who will answer, roughly when ("within one working day"), and what the reply will contain ("two or three questions by email, then a call if it makes sense"). Send an immediate confirmation saying the same thing; it proves the address works and gives them a thread to reply into. If your process supports it, offer a calendar link on the confirmation screen, while intent is at its peak.

Verify the mechanics too. A form that fails validation on mobile Safari, a notification that lands in spam, a webhook that silently stopped firing: these cost conversions and produce no signal at all. Submit your own form from a phone, on cellular data, once a month.

The order matters

None of this argues against caring about type, spacing, or the button. It puts them last. A beautifully made page pointed at the wrong temperature of traffic, asking for three things at once, ending in a dead-end confirmation screen, will not be rescued by better contrast.

Answer the five questions first. The visual design then has something to be right about.

---

More on how we build a landing page.