Build the page around one offer
A landing page argues for one thing: one offer, one action, one reader. Where a homepage has to serve a visitor who might want anything from pricing to a careers page, a landing page is built for someone who has already read an ad, clicked a link in an email, or followed a search result promising a specific outcome, and the page has to keep that promise without distraction.
Take a worked example: a one-day online workshop that teaches small shop owners how to set up an online shop, priced at a fixed fee, promoted through a paid social campaign. The weak version of this page tries to do three jobs at once: it sells the workshop, mentions the company's other training courses, and links off to a blog post about e-commerce trends. The reader arrives ready to decide about the workshop and is handed a menu instead. The stronger version drops everything that is not the workshop. One offer, described once, argued for the length of the page.
Remove the navigation
A landing page built for a campaign carries no header menu, no footer links to other services, and no path back to the rest of the site. Every link on the page is a door the reader can walk through before they have finished reading the argument, and a door out is a door away from the decision you are asking them to make.
This is not true of a homepage, where navigation is the point, and it is not true of a product page sitting inside a wider catalogue. It is true specifically of a page built to argue for one offer to a reader who arrived via one ad or one email. If the workshop page above still carries a link to "Our other courses" in the corner, that link will take a share of the clicks that the workshop button was supposed to get, and the page will never know how many readers left through it instead of buying.
Decide between long-form and short-form copy
The right length depends on how far the reader has to travel before they say yes. A reader who has clicked an ad offering a free download needs very little convincing: the offer is low-risk, the commitment is small, and a short page with a clear headline and one CTA (call to action) will outperform a page that makes them wade through six sections of reasoning they did not ask for.
The workshop, by contrast, asks for money and a day of the reader's time, so it earns a longer page: enough space to explain what is covered, who it is for, what the reader will be able to do afterwards, and what happens if they cannot make the date. A considered purchase needs a considered argument. The rule is straightforward: match the length of the page to the size of the decision. The copy length reference tables set out typical ranges by format if you want a starting point rather than a guess.
Use trust signals the reader can check
A trust signal only works if it is specific enough to be checked. "Trusted by businesses across the UK" tells the reader nothing, because it cannot be verified and could be true of almost any company selling almost anything. A trust signal that names who runs the session, what they have actually done, which platforms the workshop covers, and in what order, gives the reader something to weigh.
On the workshop page, that might mean stating plainly what the day covers session by session, and naming the platforms taught. Vague reassurance and vague enthusiasm are the same move pointed in opposite directions: both ask the reader to be impressed without giving them a reason to be. Specificity is what persuades, because it is what a sceptical reader can test against what they already know.
Answer objections before the reader has to ask them
Every landing page is read by someone looking for a reason not to buy, and the objection they are holding rarely appears anywhere on the page unless it is put there. For the workshop, the likely objections are the price against the value, whether the content applies to a shop that is not yet trading online, and what happens if the reader cannot attend on the date advertised. A page that ignores these leaves the reader to answer them alone, usually by leaving.
The stronger version of the page states the objection in the reader's own words and answers it directly, close to the button that asks for the decision: a line addressing whether the workshop suits someone starting from nothing, a line addressing what happens if the date does not work, placed where the reader is deciding. Writing the objection down before writing the answer is the discipline that makes this work. The guide to writing a call to action covers how to phrase the decision itself once the objections around it are cleared.
Map the structure before you write a line
A landing page has a sequence, and each block in that sequence does one job. Laid out as a structure rather than a page of running text, the workshop example looks like this:
- Headline: states the offer in the reader's own words, matching the wording of the ad that brought them here, positioned above the fold (the part of the page visible before scrolling).
- Subheading: names who the offer is for, in one line.
- Primary CTA: the button or link asking for the decision, repeated near the top, again partway down, and again at the end.
- The problem: a short statement of the situation the reader is in, without dramatising it.
- The offer explained: what is included, and what the reader will be able to do afterwards.
- Trust signals: specific, checkable detail.
- Objections answered: the two or three reasons a reader might hesitate, addressed by name.
- Second and final CTA: the same decision, asked again, because a reader convinced by paragraph six should not have to scroll back up to act on it.
Each block earns its place by moving the reader one step closer to the decision. A block that does not (a company history, an unrelated testimonial, a link to the blog) is not neutral filler. It is a pause in an argument that was supposed to run straight through. Before publishing, the general pre-publish checklist is worth a pass to catch anything that has crept back in.