Landing page sections are not a template to fill in. They are the order of an argument. A visitor arrives with one question, decides whether the page is about them, wants to see how it works, looks for evidence, checks what it costs, raises a doubt, and then acts or leaves. Seven sections answer those moments in sequence: hero, problem, mechanism, proof, offer, objections, close. For each one below you get its purpose, a copy pattern to write against, and the way it usually fails.
Key takeaways
- Seven sections, in order, because that is the order the visitor's questions arrive.
- Proof belongs above the offer, not in the footer.
- Objections get answered on your page, or on somebody else's.
Why the order matters more than the sections
A landing page is one page, one audience, one action. The sections are the steps a visitor needs before they will take it.
Put them out of order and each one works against the next. An offer before the mechanism looks like a price with no product attached. Proof before the problem reads as boasting about something the visitor has not yet agreed they need.
Not every page needs every section at full length. A free waitlist can compress the offer into a line; a high-ticket service may need long objections. The lengths change; the sequence holds.
1. Hero: the promise in one screen
Purpose. Answer "what is this, and is it for me?" before the visitor scrolls. Nielsen Norman Group's eye-tracking research found that most viewing time is spent above the fold, so the first screen has to make sense without the second.
Copy pattern. Headline: the outcome, in the visitor's words. Subline: who it is for and how it works, in one sentence. One button: a verb and a noun, such as "Join the waitlist" or "Book a call". One piece of evidence beside or beneath it: a named quote, a real product screen, a client the visitor will recognise.
Failure mode. A clever headline that needs the subline to explain it, and a subline that needs the third paragraph. If a stranger cannot repeat what you offer after five seconds, the hero has failed. The second failure is two equal buttons: a decision the page declined to make, handed to the visitor.
2. Problem: the situation in their words
Purpose. Let the visitor recognise themselves. This is where they decide whether the page is about them or about someone else.
Copy pattern. Describe the situation, then the cost of leaving it alone. "You are doing X because of Y. It costs you Z." Use the words they would use in an email to a colleague, not the words in your pitch deck.
Failure mode. A feature in disguise: "Struggling without automated scheduling?" Nobody describes their own problem using your product category. The other failure is exaggeration. A problem drawn bigger than the visitor feels it makes the page sound like it is talking to someone else.
3. Mechanism: how the promise is delivered
Purpose. Move the promise from hopeful to plausible. The visitor has accepted the problem. Now they need to see how the outcome actually happens.
Copy pattern. Three steps, each a verb and a result: "Connect your calendar. Pick your hours. Share one link." Or show the product doing the thing: a short loop, a working calculator, a real screen. If the product can be used for five seconds on the page, that beats any description of it.
Failure mode. A feature grid. Twelve icons with two-word labels tell the visitor what exists, not how their problem gets solved. A mechanism is a sequence. A grid is an inventory.
4. Proof: evidence before the ask
Purpose. Answer "does this work, and for people like me?" before asking for anything.
Copy pattern. Named quotes with a role and a company, specific enough to check. Real screenshots. Recognisable clients, with context rather than a bare logo. Any number carries its source and its date.
Failure mode. Anonymous praise ("Great service! J.") and logo walls without names, which prove that companies exist rather than that the product worked. The positional failure is just as common: proof parked in the footer, after the ask, where it reads as a formality.
5. Offer: exactly what you get
Purpose. Remove any doubt about what happens if the visitor says yes.
Copy pattern. What is included, what it costs or starts from, what happens next and how long it takes. If there are tiers, keep them few and make the recommended one obvious.
Failure mode. Vagueness that pushes the question onto a sales call: "Pricing tailored to your needs." Sometimes that is true, but then say what the price depends on and give a starting point. Every unanswered question about the offer is a reason to postpone the decision.
6. Objections: the hesitations, answered plainly
Purpose. Deal with the doubts that stop a visitor who is otherwise convinced. They nearly always fall into five groups: price, time, risk, fit and trust.
Copy pattern. A short FAQ built from real questions: what prospects ask on calls, what support hears, why people cancel. One question, one direct answer, no marketing voice. Where you can, reduce the risk instead of arguing with it: a trial, a refund policy, a clear way out.
Failure mode. Fake questions that are really features: "Why is our platform so easy to use?" The other failure is leaving out the hard question, usually price or lock-in, because the honest answer feels uncomfortable. If you do not answer it, the visitor will look for the answer somewhere else.
7. Close: one action, repeated
Purpose. Give the visitor who has read everything a clear place to act, without scrolling back to the top.
Copy pattern. Restate the promise in one line. Repeat the same button, with the same label as the hero. Add one line that lowers the cost of clicking: what happens next, how long it takes, whether a card is needed. Any alternative is a plain link.
Failure mode. A new, different ask at the bottom ("Subscribe to our newsletter"), a footer offering twenty exits, or a close so quiet the visitor cannot tell the argument has ended.
The seven landing page sections at a glance
| Section | Question it answers | Copy pattern | Failure mode |
|---|---|---|---|
| Hero | What is this, and is it for me? | Outcome headline, one subline, one button, one piece of evidence | A clever line that needs explaining; two equal buttons |
| Problem | Is this about my situation? | The situation and its cost, in their words | A feature disguised as a problem |
| Mechanism | How does it actually work? | Three steps, or the product in use | A feature grid |
| Proof | Does it work for people like me? | Named, specific, dated evidence | Anonymous quotes; proof in the footer |
| Offer | What do I get if I say yes? | Inclusions, price, next step, timing | "Tailored pricing" with no starting point |
| Objections | What is stopping me? | Real questions, direct answers | Fake questions; the hard one left out |
| Close | Where do I act? | The promise, the same button, what happens next | A new ask, or twenty exits |
What to cut
Most landing pages get better by losing things, not gaining them. Each item below is a cost the visitor pays before reaching the button, and none of them moves the decision forward.
- Full site navigation. Every link in the header is an exit. Keep the logo and, at most, one link.
- A second primary button. Demote every alternative to a text link.
- The feature list that repeats the mechanism. If three steps explain it, twelve icons are not needed.
- Carousels and rotating headlines. They hide the message behind timing.
- Form fields you will not use yet. Baymard Institute's checkout research found that most forms ask for more than they need. If nothing happens with an answer this week, remove the field.
- Sections that exist because a template had them. A "meet the team" block on a product waitlist is padding, not proof.
One test for every block: if it disappeared tomorrow, would the visitor have one fewer question answered? If not, it goes.
Landing page section checklist
Run this over a draft before design starts.
- The hero headline states an outcome a stranger could repeat after five seconds.
- There is exactly one primary button, with the same label in the hero and the close.
- The problem section uses the visitor's words, not your category name.
- The mechanism is a sequence or a working demo, not a grid.
- At least one piece of named, specific proof sits above the offer.
- The offer says what is included, what it costs or starts from, and what happens next.
- The objections answer price, time, risk, fit and trust.
- The form asks only for what the next step needs.
- The page loads and reads clearly on a phone over an ordinary connection.
Putting it together
Write the seven sections as plain text before anyone opens a design tool. If the argument does not read clearly as a document, no layout will rescue it.
For real pages that make these decisions well, the landing page design examples teardown reads eight of them for structure. If you are not sure a landing page is even the right tool, landing page vs homepage covers when each one fits. And if you would rather have the page written, designed and built around one action, that is what landing page design covers here.
FAQ
How many sections should a landing page have?
As many as the visitor's questions need, and no more. Seven is the full argument. A free waitlist can compress the offer and objections into a few lines; an expensive service usually needs all seven at length.
What order should landing page sections go in?
Hero, problem, mechanism, proof, offer, objections, close. That follows the order a visitor's questions arrive. The most common mistake is moving proof below the offer, where it reads as an afterthought.
Should a landing page have navigation?
Rarely. Every navigation link is a way off the page. Keep the logo and, if needed, one link for people who want to learn more first.
Useful sources
- Scrolling and Attention, Nielsen Norman Group
- Checkout Optimization: Minimize Form Fields, Baymard Institute