Landing page design best practices that actually move conversions

Most advice about landing pages is written by people who have never had to explain to a client why the page they paid for isn't converting. It's a list of tactics — add urgency, use contrasting buttons, put a video in the hero — with no account of which ones matter and which are noise.

These are the practices I actually apply, in rough order of how much difference they make. At the end there are three popular ones I've stopped using, and why.

One page, one job

A landing page that offers a visitor three things to do converts worse than one that offers a single thing — reliably, and by a margin that dwarfs every colour and copy tweak you might make afterwards. Every additional option splits attention and gives someone a reason to defer the decision.

In practice this means: one primary action, repeated as many times as the page is long. Strip the site navigation, or reduce it to a logo. Remove the footer link farm. If the page's job is booking a consultation, then "download our brochure" is not a helpful secondary option — it's a way for someone who was ready to book to do something cheaper instead.

The most common version of this mistake is sending paid traffic to a homepage. A homepage is built for people who don't yet know what they want. Ad traffic already knows. You're paying per click for the privilege of showing them a menu.

Earn the scroll in five seconds

The first screen has one job: make the visitor decide the page is about them. Three things have to be legible without scrolling:

• What this is. Plainly. "Flat-fee divorce, handled online" beats "Redefining the modern legal experience."
• Who it's for. Naming the audience out loud costs you nothing and disqualifies the wrong visitors, which is a benefit, not a loss.
• What to do next. The primary action, visible without scrolling, on a phone.

A useful test: show the first screen to someone unfamiliar with the business for five seconds, then hide it and ask what the company sells. If they can't answer, no amount of persuasion further down the page will be read, because they won't get there.

Write about them, not about you

Count the instances of "we" and "our" in your first two sections, then count "you" and "your". If the first number is higher, the page is a brochure.

The mechanical fix is to convert each feature into the thing it lets the reader do. "Fifteen years of experience" becomes "you won't be the project where we learn this." "Cloud-based platform" becomes "nothing to install, and it works from your phone." The feature isn't wrong — it's just not what the reader is shopping for.

This is also where specificity pays. Numbers, timeframes and constraints read as true; adjectives read as marketing. "Most projects go live in three weeks" earns more trust than "fast turnaround," precisely because it's falsifiable.

Answer objections in the order they occur

Structure isn't decoration; it's the argument. A page should answer questions in the order a real person thinks of them:

1. What is this, and is it for me?
2. What exactly do I get?
3. Why should I believe you?
4. What does it cost me — money, time, risk?
5. What happens if it goes wrong?
6. What do I do now?

Most underperforming pages get this out of order: proof before the offer is understood, or price before value has been established. If you're unsure of the order for your own page, listen to a sales call. The sequence customers ask about on the phone is the sequence the page should follow.

Proof that isn't decorative

A row of logos nobody recognises proves nothing. A five-star rating with no source proves less. Proof works when it's specific enough that inventing it would be obvious:

• Named testimonials with a photo, a role and a company — and, ideally, quoting a result rather than an adjective.
• Numbers you can stand behind: orders shipped, clients served, years in business, average response time.
• Before and after, where the work is visual. This is why it's the strongest section on most clinic and trades pages.
• Third-party ratings linked to the source, so it's checkable.

Placement matters as much as content: proof belongs immediately after each claim that needs it, not quarantined in a testimonials section at the bottom that nobody reaches.

The form is the product

Everything above the form exists to get someone to the form, and then people put eleven fields in it. Each field is a decision the visitor can lose interest during.

Ask only for what you need to have the next conversation. For most service businesses that's a name, a way to reply, and one line about what they need. Budget ranges, company size and "how did you hear about us" can wait until you're talking to a real prospect rather than deterring one.

Beyond field count, the details that matter:

• Labels above the fields, not placeholder text that vanishes when you start typing.
• Errors shown next to the field, in words, not a red outline and a shrug.
• A submit button that says what happens: "Get my quote," not "Submit."
• A real confirmation state — a page or panel that acknowledges the send and says when they'll hear back.
• One line under the button on what you'll do with their data. It costs nothing and removes a real hesitation.

Speed is a design decision

Load time is treated as a technical afterthought, but on paid traffic it's a conversion factor with a hard edge: people who leave before the page renders never see any of your persuasion. A hero video, three web fonts and a chat widget can cost you more visitors than a weak headline ever will.

The usual culprits are boring and fixable — uncompressed images, fonts loaded in formats nobody needs, marketing scripts stacked from years of experiments, and a page builder shipping CSS for widgets the page doesn't use. Test on a mid-range phone on mobile data, not on your desktop over office wifi. That's the device your traffic is actually using.

Design the phone version first

If most of the traffic is mobile — and for paid social it's nearly all of it — then the desktop layout is the variant, not the design. Designing desktop-first and squashing it down produces the usual symptoms: a hero where the CTA sits below the fold, a two-column comparison table that becomes unreadable, and forms that require zooming.

Things that only show up when you check on a real device: tap targets too close together, sticky headers eating a third of a small screen, autocorrect fighting the email field, and CTAs that land exactly where the browser chrome sits.

Instrument it or you're guessing

A landing page without tracking is an opinion. Before launch:

• GA4 with a conversion event on the form submission, not just pageviews.
• Meta and Google pixels if you're running paid traffic, tested with the browser extensions rather than assumed.
• UTM parameters carried into the form submission, so a lead in your inbox can be traced to the campaign that produced it.
• A test submission from a phone, end to end, before you spend a euro on ads.

Then leave it alone long enough to collect real data. Judging a page on forty visits is how teams talk themselves into rebuilding something that was working.

Three practices that don't hold up

Fake urgency. Countdown timers that reset on refresh and "only 3 spots left" that is always 3. It works once on the people it fools and permanently damages trust with everyone who notices. Real deadlines are fine; invented ones are a tax on your credibility.

"Never make them scroll." Cramming everything above the fold produces a claustrophobic page and a visitor who hasn't been given a reason to believe anything. People scroll happily when the first screen tells them the page is relevant. Length isn't the enemy; irrelevance is.

Exit-intent popups on every page. They measurably capture some emails and they measurably annoy people, and on mobile the trigger barely works. On a page whose job is a considered purchase, interrupting someone reading your proof section to offer them a discount code is a strange trade.

FAQ

How long should a landing page be?

As long as it takes to answer every objection, and no longer. Low-commitment offers need little — a short page with the offer and a form often outperforms a long one. High-value or high-risk decisions need length, because the reader has more questions and each unanswered one is an exit. Let the objection list set the length, not a word count.

Should I use a video in the hero?

Only if the video explains something words can't, and only if it doesn't delay the page. An autoplaying background video that pushes your headline down and costs two seconds of load time is a net loss. A thirty-second explainer behind a click, below the fold, is often genuinely useful.

How many CTAs should a landing page have?

One action, repeated. Repetition isn't the problem — competing options are. A long page should offer the same button after the offer, after the proof and after the FAQ, because different readers become ready at different points.

Do I need a separate page for each ad campaign?

If the campaigns speak to different audiences or offers, yes — the match between the ad and the first screen is one of the strongest conversion factors there is. If they're variations on the same message, one page with dynamic headline text is usually enough.

The short version

One action per page. Say what it is in the first screen. Write about the reader. Answer objections in the order they arise. Prove claims where you make them. Keep the form short. Make it fast, design it for a phone, and measure it — then change one thing at a time and keep what wins.