Home › Web Design › Landing Pages
LANDING PAGES
An effective landing page aligns a visitor’s intent with a clear message, a focused structure, the information they need to decide and an understandable next step.
This guide covers the whole subject: goals and intent, value propositions and headlines, page structure, CTAs, forms, trust, responsive behaviour, accessibility, SEO, performance, analytics, testing and optimisation.
THE BASICS
A landing page is a focused web page built around a specific user intent, campaign, offer or action. Where a homepage serves many audiences at once, a landing page usually serves one — the person who just clicked a particular link expecting a particular thing.
The traffic source matters as much as the page. Someone arriving from a search ad about booking consultations expects to see that offer immediately; if the page talks about something broader, they leave confused. Matching the message to the expectation created before the click removes that friction, though it doesn’t by itself determine what anyone chooses to do.
Not every landing page collects a form submission. Some exist to explain, compare or direct people onward. What defines one is focus on a single purpose, not the presence of a form.
COMPARISON
The distinction is about purpose rather than technology — the same CMS builds both. A page becomes a landing page when it’s designed around one intent and one outcome. Some landing pages keep full navigation because trust and context matter more than containing the visitor; others strip it back for a tightly scoped campaign. Neither is a rule.
PURPOSE
Deciding the goal first is what makes every later decision easier. The structure, copy, CTA and measurement all follow from it — and a page trying to serve three goals usually serves none well.
Collect relevant contact information from interested visitors.
Introduce a specific product or offer in depth.
Encourage visitors to request information or a quote.
Support signups for an event, webinar or service.
Offer a guide, checklist or other resource.
Guide visitors toward a transaction.
Encourage people to explore or install an application.
arriveexpectmatchevaluateactINTENT
Visitors arrive from organic search, paid search, social media, email, referral links, display campaigns and direct visits — and each arrival carries a different expectation and level of readiness.
Someone clicking a search ad for a specific service has already stated their need. Someone clicking a social post may have been curious rather than committed. The same offer often needs different framing, different depth and sometimes a different page.
The practical test: does the first screen confirm the visitor is in the right place? If a person has to work that out, the page is already losing them.
VALUE PROPOSITION
A value proposition communicates what is being offered, who it is for and why it might be relevant to that person. It isn’t a slogan — it’s the answer to “why should I care about this?”
Specificity is what makes one useful. “Better websites for growing businesses” says almost nothing; naming the actual service, audience and outcome says something a visitor can evaluate. Avoid superlatives you can’t support: unsupported claims invite scepticism rather than confidence.
1234HEADLINES & COPY
A headline should let someone understand what is offered, who it’s for and what need it addresses without reading further. Clarity beats cleverness — a witty line that requires decoding costs attention you may not get back.
The subheadline then does the clarifying work: features, benefits, audience, process, what to expect, what makes this different. It should answer the question the headline provokes rather than restate it in other words.
The example is illustrative. No headline formula guarantees an outcome — what a specific audience responds to is something to observe rather than assume.
COPY
A feature is what the product or service includes. A benefit is why that feature might matter to this visitor. Both have their place: benefits help people decide whether to care, features help people who have already decided to compare specifics.
Online booking system
Customers can request an appointment without waiting for office hours.
Three months of support included
Someone is available to fix issues while you learn the new site.
Leading with benefits and supporting them with features usually reads better than a bare specification list — though technical audiences often want the specifics first.
STRUCTURE
A common order moves from context to relevance to evidence to action. That sequence mirrors how people actually decide: understand what this is, judge whether it applies to them, look for reasons to believe it, then act.
Not every page needs all nine sections. A simple download might need three; a considered service purchase might need more than nine. The right depth depends on the offer, the audience, how much they already know and how much information the decision genuinely requires. Padding a page to look substantial helps nobody.
HERO SECTION
The hero establishes context fast. It typically carries the headline, a subheadline, the primary CTA, a supporting visual that shows rather than decorates, and sometimes a light trust signal.
Resist filling it. A hero with two competing buttons, a video, a form and a badge strip gives the eye nowhere to land. One message, one clear action, and a reason to keep scrolling is usually enough — the rest of the page exists to do the explaining.
primarysupportactionsupportoptionalCALLS TO ACTION
CTA wording should describe what actually happens next. Request a consultation sets an accurate expectation; Submit sets none. Action-oriented, specific language reduces the hesitation that comes from not knowing what a click commits you to.
Visually, the primary CTA needs contrast, a clear place in the hierarchy, enough surrounding space and consistent styling wherever it repeats. Claims that a particular colour or phrase always performs better don’t survive contact with different audiences and contexts — treat them as things to test, not rules.
On placement: repeat the CTA where someone is plausibly ready to act — after the offer is clear, after the benefits, after proof — rather than every few hundred pixels.
FORMS
Every field is a request for effort, so ask for what you’ll actually use. Mark required and optional fields clearly, use visible labels rather than placeholders, choose input types that trigger the right mobile keyboard, and validate helpfully — beside the field, explaining the fix, preserving what was typed.
Say what happens after submission and include privacy information where you’re collecting personal data. Confirm success explicitly rather than leaving people wondering.
Shorter forms are often easier to complete, but not always better: fewer fields can mean less useful enquiries. Balance the information you need against the effort you’re asking for, and see UI/UX design for the wider form patterns.
TRUST
Trust elements answer an unspoken question: is this real, and can these people do what they say? Useful ones include genuine testimonials and reviews, client logos you’re permitted to show, relevant certifications, clear business and contact information, honest guarantees, case studies and accessible policies. Security information matters wherever payment or personal data is involved.
Never fabricate any of it. Beyond the ethical and legal problems, invented proof tends to read as invented — vague praise from nobody in particular lowers credibility rather than raising it. If you don’t yet have testimonials, clear business information and a straightforward explanation of your process do more than fiction.
OBJECTIONS
Most people arrive with unspoken hesitations: what does this cost, what’s the process, how long does it take, what do I need to provide, is my data safe, what support comes after, can I cancel, am I even eligible? Unanswered, these become reasons to postpone.
A well-placed FAQ handles many of them — but only if the questions are the ones people actually ask. FAQ sections written to hold keywords rather than answers add length without helping anyone. Keep answers short, specific and honest, including about limitations. Pressure tactics and artificial urgency tend to erode the trust the rest of the page is building.
HIERARCHY & UX
Hierarchy on a landing page carries more weight than usual because the page has one job. Headings, typography, colour, spacing, images, CTA styling, section order and contrast together decide what gets noticed and in what order — ideally primary message, supporting information, benefits, evidence, then action.
The UX principles are familiar: clarity, consistency, predictability, readability, a coherent user flow, accessibility, useful feedback and less friction. What’s different is the discipline required — on a landing page, anything that doesn’t support the task is competing with it.
12345RESPONSIVE
Landing pages often receive a large share of mobile traffic, particularly from social and email. The hero usually stacks, benefit columns become one, and everything that sat side by side gains a reading order.
On small screens keep typography readable without zooming, shorten the visual path to the CTA, make buttons and controls touch-friendly, keep forms simple with appropriate keyboards, serve responsive images, tighten spacing without crowding and prevent horizontal overflow. Intrusive pop-ups are particularly unwelcome on a small screen where they’re hard to dismiss. More in responsive design.
CONTENT
A common content sequence runs problem or need → solution → benefits → evidence → objections → action. It works because it follows how people evaluate, but the order should follow your audience: someone already sold on the category doesn’t need the problem explained back to them.
The first screen should establish what the page is about, who it’s for and what the main action is. That’s enough — it doesn’t need to contain everything important.
The idea that nobody scrolls hasn’t held for a long time. People scroll readily when the top of the page gives them a reason to. Cramming every element above the fold usually produces a crowded screen that gives no reason at all.
Avoid hype throughout. Superlatives and urgency without substance make a page harder to believe, not more persuasive.
NAVIGATION
There are several reasonable approaches: full website navigation, minimal navigation (logo plus perhaps contact), campaign-specific links, or no traditional navigation at all.
The argument for removing it is focus: fewer routes away from the decision. The argument against is trust and context — for a considered purchase, people often want to check who you are, what else you do and how to reach you, and a page with no way out can feel like a trap.
The claim that removing navigation always improves results is not supportable as a universal rule. It depends on the campaign goal, traffic source, where the visitor is in their journey, brand requirements, trust needs and page complexity. Related patterns in website navigation.
MEDIA
Product shots, service imagery, interface screenshots, illustrations, diagrams, before-and-after examples and contextual photography all earn their place when they help someone understand the offer. Generic decorative stock rarely does.
Watch consistent aspect ratios, sensible compression, responsive sizing, meaningful alt text and the performance cost — a hero image is often the heaviest element on the page.
Video can help with product demonstrations, service explanations, tutorials, genuine testimonials and walkthroughs — anything easier to show than describe.
Consider loading cost, avoid autoplay with sound, provide captions and controls, respect mobile bandwidth and keep the key message available in text too. Video doesn’t automatically improve a page; an unwatched video is just weight.
ACCESSIBILITY
Accessibility applies to landing pages exactly as it does elsewhere, and the stakes are concrete: an inaccessible form is a visitor who cannot complete the one action the page exists for.
Cover semantic headings in a logical order, sufficient contrast including on CTA buttons, full keyboard navigation, visible focus states, real form labels, accessible buttons, meaningful alt text, captions for video, clear error messages, readable text and practical touch targets.
Build it in from the start rather than auditing at the end. This is an introduction to the principles, not a compliance assessment — see website accessibility.
SEO
Where organic traffic matters, the usual work applies: match the page to a real search intent, write a useful title and H1, structure content with meaningful headings, cover the topic properly, add relevant internal links, optimise images and alt text, keep performance and mobile usability healthy, and handle canonicalisation where similar pages exist.
But not every landing page needs organic search. A short-lived campaign page built for paid traffic may reasonably be excluded from indexing. Confusing the two produces thin pages that serve neither purpose. See our website SEO guides.
A page can serve both, but the requirements pull in different directions — depth and internal linking for search, focus and message match for ads. Neither approach is better; they answer different questions.
PERFORMANCE
Landing pages accumulate weight quickly: a large hero image or video, several fonts, form scripts, animations, and the tracking tools campaigns tend to attract — analytics, ad pixels, heatmap recorders, chat widgets. Each is a defensible addition on its own.
Conceptually this affects LCP (how soon the main content renders, often that hero), INP (how quickly the page responds, which matters for forms) and CLS (whether things shift while loading, which causes mis-taps on CTAs). Audit what each script earns, and see website speed for measurement.
MEASUREMENT
What to measure follows from the page’s goal. Useful categories include traffic by source, engagement, CTA interactions, form starts versus completions (the gap between them is often revealing), downloads, purchases and overall conversion rate.
Conversion rate is simply conversions divided by relevant visits, expressed as a percentage. The numbers in the example are fictional, chosen because they divide neatly — they are not benchmarks, and published “average” rates vary so widely by industry, offer and traffic source that comparing against them tells you little.
No single metric decides whether a page works. A high conversion rate on unqualified enquiries can be worse than a lower one on good-fit leads.
Conversion rate = conversions / relevant visits x 100 Example (fictional numbers): relevant visits = 100 completed actions = 10 conversion rate = 10%
TESTING
An A/B test compares two versions under controlled conditions, splitting traffic and measuring the same outcome. Common variables include the headline, CTA wording, form layout, images, page structure, supporting copy, how pricing is presented and which trust elements appear.
Testing only pays off with enough relevant traffic and sound methodology. Small samples produce differences that look meaningful and aren’t; stopping a test as soon as one side pulls ahead is a common way to learn something false. Decide the outcome measure and duration in advance.
No variable is universally the most important, and testing guarantees nothing — it tells you what happened with your audience, on your offer, during that period.
OPTIMISATION
Optimisation is continuous rather than a one-off fix. Each pass narrows the gap between what visitors expect and what the page delivers.
Decide the one action the page supports.
Who they are, what they need, what they know.
What the click promised before arrival.
Where people hesitate, stall or leave.
Sharpen clarity and relevance.
Simplify the path and the form.
Compare changes properly where traffic allows.
Track the outcomes that match the goal.
Keep what works, revisit what doesn't.
BEHAVIOUR
Heatmaps, scroll and click data, session recordings, analytics, form analytics and direct feedback all show what people do rather than what they say. Form analytics in particular can reveal the exact field where people abandon.
Interpret it in context. A cluster of clicks on a non-clickable element might mean interest — or confusion. Behavioural data raises good questions more reliably than it answers them.
Some steps are necessary. A qualifying question that prevents mismatched enquiries, or a confirmation step before a significant commitment, adds effort deliberately and usefully.
The goal is removing unnecessary friction — effort that serves no purpose for either side — rather than stripping every step until the form asks nothing worth knowing.
USER JOURNEY
One way to think about the page as a sequence: a visitor arrives, understands the offer, sees benefits relevant to them, finds supporting evidence, has their questions addressed, reaches the CTA or form, and receives confirmation with a clear sense of what happens next.
Each stage answers a question the previous one raised. When a page underperforms, it’s often because one stage is missing — benefits with no evidence, or a form with no confirmation. This is one useful model, not a universal formula; plenty of effective pages compress or reorder it.
1234567PRINCIPLES
Make the offer understandable at a glance.
Match the page to the intent behind the traffic.
Guide attention through the content deliberately.
Keep visual patterns predictable throughout.
Use genuine, relevant supporting evidence.
Make the page usable by a broad range of people.
Work properly at every viewport size.
Avoid unnecessary page weight.
Keep everything aligned with the page's purpose.
Be clear about what happens after the CTA.
PITFALLS
Visitors can't tell what the page offers or who it's for.
Generic claims give no reason to keep reading.
Several equal actions turn a decision into a choice of decisions.
Sections in an order that doesn't match how people decide.
Asking for information the task doesn't require.
No business details, contact route or evidence.
Cramped layouts and forms that are hard to complete.
Heavy heroes and stacked tracking tools delay everything.
Vague errors that lose what was already typed.
Pop-ups and animations competing with the message.
Superlatives and invented figures that invite scepticism.
Unclear scope or hidden costs stall decisions.
Forms and CTAs some visitors simply cannot use.
A page written for the business rather than the visitor.
Assumptions shipped and never checked.
TYPES
These categories overlap constantly — a campaign page for a service that offers a downloadable guide is all three at once. The labels are useful for deciding structure, not for filing pages.
Collects relevant information from interested visitors through a form.
Provides information first, then directs visitors to the next step elsewhere.
Focuses on one product or offer in detail.
Explains a service and provides a relevant next action.
Supports signups for an event, webinar or workshop.
Offers a guide, checklist or other resource.
Introduces an application and encourages an appropriate next step.
Built around a specific campaign or traffic source.
EXAMPLE
A worked example: a minimal header, a hero carrying the headline and primary CTA, three benefit blocks, a fuller features or details section, trust elements, an FAQ, the form or final CTA, and a footer with contact information and policies.
Wireframing first keeps the conversation on structure and order before anyone argues about colours. It’s also the cheapest point at which to discover the page is trying to do two jobs.
This is an illustrative layout, not a real project or a template to copy exactly. Actual structures vary with the offer and audience.
COMPONENTS
A component library for landing pages. No page needs all of them — adding components because they exist is how focused pages become cluttered ones.
Establishes context, message and the primary action.
The action itself, styled consistently wherever it appears.
One capability or detail, scannable in isolation.
Why a feature matters to this visitor.
Genuine feedback, attributed and relevant.
Clients or partners, used only with permission.
Collects what the next step requires.
Answers the questions that stall decisions.
Presents cost and scope clearly.
Sets options side by side on shared criteria.
Certifications or security information, where genuine.
A final route for people who read to the end.
WORKFLOW
Decide what action the page supports.
Identify needs, context and intent.
Review where visitors come from and expect.
Clarify what the visitor receives or can do.
Plan headline, benefits, proof, objections, CTA.
Organise the page before visual styling.
Apply typography, colour, spacing and components.
Implement desktop, tablet and mobile behaviour.
Check usability, accessibility, performance and forms.
Use data and feedback to iterate.
END TO END
Structure and content hierarchy, with no styling to argue about. Decide what the page says and in what order.
Typography, colour, spacing, components and visuals applied. Hierarchy becomes visible and CTA states get defined.
Built responsively and accessibly, with working forms, tracking in place and real content tested on real devices.
IMAGE PLACEHOLDER
Landing page wireframe to final design comparison
Recommended ratio: 16:9 — replace this container with an Image widget.
SEO STRUCTURE
For pages meant to rank, structure carries much of the weight: a descriptive title, one H1 stating the topic, an introduction that confirms relevance quickly, meaningful H2 sections, supporting content that covers the questions people actually have, relevant internal links, an FAQ where useful, and a clear CTA.
Good SEO here isn’t repeating a phrase. It’s covering the topic properly in the language your audience uses, so both readers and search engines can tell what the page is for.
metah1openbodydepthlinksfaqactionINTENT & SOURCE
The same offer needs different treatment depending on why someone is looking and where they came from. Messaging should match the actual intent behind the traffic rather than the stage the business wishes people were at.
People want to understand something. Pages should explain first and offer an action second.
People are comparing options. Comparisons, detail and honest trade-offs matter most.
People are ready to act. Remove steps and make the action obvious.
People are trying to reach something specific. Confirm they've arrived and route them quickly.
Traffic sources shape expectations in the same way. No source is inherently better — each simply arrives with different context.
Focus on search intent, useful depth and discoverability.
Align closely with the campaign and the query context.
Provide continuity between the post or ad and the page.
Continue the context the email established.
Stay relevant to what the referring source described.
Give clear context and an obvious next step.
OPTIMISATION
Keep the page aligned with what the click promised.
Make the offer understandable without effort.
Prioritise what matters to this visitor.
Use genuine evidence, not decoration.
Remove what competes with the purpose.
Support different users and interaction methods.
Stay usable across devices.
Avoid unnecessary page weight.
Track outcomes that match the goal.
Improve using evidence and feedback.
TOOLING
Categories rather than rankings. Most teams need fewer tools than they accumulate, and every tracking script added to a landing page has a performance cost.
Create interface designs and visual systems.
Plan structure before styling.
Test flows before building.
Build and publish pages visually.
Manage content and templates.
Measure traffic, engagement and conversions.
Check loading and Core Web Vitals.
Check contrast, focus order and structure.
Run controlled comparisons.
Heatmaps, scroll and session data.
Build, validate and route submissions.
ELEMENTOR
Elementor covers most of what a landing page needs without custom code. Work with containers and flexbox for structure, responsive controls for per-device spacing and typography, global colours and fonts for consistency, and the built-in button and form widgets with proper heading hierarchy.
Responsive visibility settings can adapt content per device — use them sparingly, since hidden content is usually still loaded. Save repeated sections as reusable components, and keep custom CSS for genuine gaps. Menu labels shift between versions, so these are concepts rather than click paths.
ELEMENTOR PRACTICE
Build with proper parent and child containers rather than nesting to patch layout problems.
Leave out sections that don't serve the page's purpose.
Global colours and fonts keep typography and CTAs consistent.
Check smaller widths throughout, not at the end.
Use proper labels, validation and clear feedback.
Appropriate dimensions and formats, especially the hero.
A lighter DOM is easier to maintain and faster to load.
Check links, forms, responsiveness and performance.
CHECKLIST
Work through this before publishing. It’s a reference list rather than an automated tool — copy it into your own project tracker.
[ ] Clear page goal [ ] Clear target audience [ ] Relevant traffic intent [ ] Strong value proposition [ ] Clear headline [ ] Useful supporting copy [ ] Logical page structure [ ] Clear primary CTA [ ] Appropriate supporting CTAs [ ] Relevant benefits [ ] Genuine trust elements [ ] User-friendly forms [ ] Responsive layout [ ] Mobile-friendly interactions [ ] Accessible content [ ] Optimized images [ ] Good performance [ ] Clear FAQ where useful [ ] Analytics configured appropriately [ ] Testing plan [ ] Clear confirmation or next step
NEXT TOPICS
Learn the fundamentals of structure, typography, colour, spacing and visual hierarchy.
Learn how interface and experience principles influence landing page usability.
Learn how landing pages adapt across desktop, tablet and mobile.
Learn how navigation and information architecture affect website journeys.
Learn how to make landing page interfaces more accessible and usable.
Explore current design approaches and how to evaluate them for real projects.
FAQ
Short answers to the questions people ask most about landing page design.
Learn how to structure landing pages around user intent, clear messaging, useful content, responsive design, accessibility and measurable goals.