The Anatomy of a Landing Page That Actually Converts

A landing page is not a smaller homepage. A homepage serves everyone; a landing page serves one visitor with one problem and offers one next step. Most underperforming pages I audit fail because they forgot that sentence. Here is the structure I build from, in order, and what each section is responsible for.

1. The above-the-fold promise

Within three seconds a visitor should be able to answer: what is this, who is it for, and what do I get. That means a specific headline instead of a clever one. "Bookkeeping for UK e-commerce brands doing £1m+" beats "Financial clarity, delivered." Add a one-line subhead naming the outcome, one primary button, and a single supporting visual.

2. Proof, immediately

Trust decays the further down the page it lives. Put a thin strip of proof directly under the hero — client logos, a review score, a headline result. Not full testimonials yet; just enough signal that this is a real business with real customers.

3. The problem, in their words

Before you explain your solution, show that you understand the situation. Two or three short paragraphs, or a three-item list of frustrations, written in the language your customers use rather than your industry's vocabulary. This is the section that makes people feel found rather than sold to.

4. The mechanism

Now explain how it works, in three or four steps. People buy things they can picture. A numbered process reduces perceived risk more effectively than any feature list, which is why it is the backbone of my own project pages — the same logic I walk through in how a website goes from idea to launch.

5. Benefits framed as outcomes

Every feature needs a "which means" clause. "Built on Next.js" is a feature. "Loads in under a second, which means fewer visitors leave before they see your offer" is a benefit. If you want the numbers behind that specific claim, see the hidden ROI of a fast website.

6. Real testimonials, with specifics

Vague praise is worthless. "Great to work with" persuades nobody. "Our enquiry rate doubled in six weeks and the site has not gone down once" persuades everyone. Chase specifics when you collect them, and include a name, a role, and a photo wherever you can.

7. Objection handling

List the four or five reasons someone hesitates and answer them plainly: price, timeline, lock-in, what happens if it goes wrong, who owns the work. An FAQ block here recovers more conversions than almost anything else you can add, because the alternative is the visitor leaving to find the answer and never coming back.

8. One closing call to action

Repeat the same action from the hero. Not a different one. A page offering a call, a download, a newsletter, and a demo offers nothing — every extra option splits attention. Keep the form short; every field you remove lifts completion. There is a whole post on that: website form UX.

The technical part people skip

None of the above matters if the page is slow or unreadable on a phone. Landing pages get shared on mobile, opened on poor connections, and judged in the first second of loading. Design mobile-first, keep the hero image small, and check your Core Web Vitals before you spend a penny on traffic.

Measure one thing at a time

Pick a single conversion metric, change one section, and give it enough traffic to mean something. Redesigning the whole page tells you that something worked without telling you what.

Want a second pair of eyes on a page that is not converting? Send me the URL — I will tell you what I would change first.