How to write a landing page that converts: above-the-fold formula, headlines, proof, and CTAs
Learn how to write a landing page that turns visitors into signups or sales: proven above-the-fold formula, headline patterns, social proof, CTAs, FAQs, and tests.
Most landing pages fail because they make visitors think too hard. To write a landing page that converts, make the first screen answer who it’s for, what it does, why it’s better, and what to do next—then back it up with clear proof and a single focused call to action.
This guide gives you a repeatable structure: an above-the-fold formula, copy patterns for headlines, how to use social proof and visuals, simple pricing blocks, trustworthy FAQs, and a lightweight A/B testing loop.
Key takeaways
Put clarity before cleverness: your headline, subhead, and CTA should make the benefit obvious within 5 seconds.
Use the above-the-fold formula: Problem → Promise → Social proof nudge → Primary CTA. Everything else supports that.
Replace vague claims with specific proof: logos, testimonial quotes, quantified outcomes users care about, and short demo clips.
Make action easy: one primary CTA, reinforced 3–4 times; secondary paths only when truly needed.
Pricing wins on scannability: 3 options max, single highlighted “most popular,” and short bullets of what’s included.
Ship and learn: run small A/Bs on headlines, CTAs, and hero visuals; measure one conversion per test and let it run to a clear result.
Photo: picjumbo.com / Pexels
The above-the-fold formula
Above the fold is where most decisions happen. Your job here: show visitors they’re in the right place and make acting feel safe and obvious. Use this template and customize the language to your audience and offer.
Headline (benefit + audience): Name the outcome and who it’s for.
Subhead (what it is + how it works): One sentence that defines the product and the key mechanism.
Social proof nudge: A concise trust marker within the first screen (a customer logo row or a single strong quote).
Primary CTA: One action that maps to the intent of the page (e.g., "Start free trial," "Get a demo," "Download checklist").
Supporting visual: A focused product shot, animated GIF, or 10–20s demo loop that shows the result, not your settings menu.
Example structure you can adapt:
Headline: "Close deals 2x faster for mid-market sales teams"
Subhead: "[Product] automates prep, notes, and follow-up so reps spend time selling, not clicking."
Proof: "Trusted by teams at [Logo], [Logo], [Logo]"
CTA: "Start free for 14 days" (secondary: "Book a 15‑min tour")
Visual: A short clip of an email sequence being generated and sent, ending with a calendar booked.
Why this works: it aligns with visitor intent (outcome), creates relevance (audience), reduces risk (proof), and makes the next step unmissable (single CTA). Avoid burying your value in jargon or clever metaphors that slow comprehension.
Fast fixes for common hero mistakes
Too many CTAs: Keep one primary. If you need a secondary, make it visually lighter.
Generic headline: Swap "The future of work" for a concrete benefit and persona.
Busy visuals: Crop to the 1–2 UI elements that represent the win. Add a short caption.
Missing proof: Add 3–6 recognizable logos or one short testimonial with a name and role.
Photo: Ron Lach / Pexels
Headline patterns that pull their weight
Clarity beats wordplay. Use patterns that map directly to the problem your audience wakes up with. Then sharpen verbs and outcomes until a stranger nods.
Here are reliable templates with examples you can adapt:
Outcome + Persona
"Cut onboarding time in half for seed‑stage startups"
"Ship pixel‑perfect mockups for freelance designers"
Replace Pain With Gain
"Stop spreadsheet chaos. Track budget in minutes."
"No more tab overload. Find every doc instantly."
Job To Be Done (JTBD) in Plain English
"Plan, price, and launch your course in a weekend"
"Turn meeting notes into client-ready summaries"
Competitive Edge Without Naming Names
"Faster quotes. Fewer clicks. Happier clients."
"All your ops in one view—without switching tools"
Numbered Specifics (when honest and supportable)
"Create proposals in 3 minutes, not 30"
"Onboard new hires in 5 steps"
Tips to sharpen headlines:
Cut filler words ("actually," "really," "very").
Swap adjectives for verbs ("powerful" → "automates").
Read it aloud; if you run out of breath, split into headline + subhead.
Subheads that do the heavy lifting
The subhead is where you add clarity: say what it is, how it works, and what makes it different in one sentence.
Pattern: "[Product] is a [category] that [key mechanism] so you can [primary benefit]"
Example: "Acme is a billing dashboard that auto‑reconciles Stripe payouts so you close your books before lunch."
Photo: Tranmautritam / Pexels
Social proof that actually convinces
Not all proof persuades equally. Focus on proof that maps to your core claim and your buyer’s context.
Logos: 3–6 recognizable customers is often enough. Don’t overload the strip; aim for relevance over sheer count.
Testimonial quotes: Use one crisp sentence with a named person, role, and company. Pair with a headshot when you can.
Short case blurbs: "How [Customer] shipped 2x faster by templatizing sprints" plus a two-sentence summary.
Trust badges: Compliance and security certifications only if truly applicable. Avoid vanity awards that mean nothing to buyers.
Usage outcomes: Replace vanity with utility—call out the specific task your app makes faster or easier.
Where to place proof:
A lightweight proof nudge in the hero.
A deeper proof section halfway down with 2–3 rotating quotes.
One credibility boost near pricing (e.g., "Backed by [Partner]" or "Switch in under an hour").
Write testimonials like mini stories:
Setup: the problem in a clause.
Turn: what your product changed.
Payoff: the outcome that matters.
Example: "Our onboarding dragged for weeks. With [Product], we ship a tailored training in a day, and new hires contribute by Friday." — Jenna P., People Ops at Northwave
Show, don’t tell: visuals, screenshots, and demos
Your visuals should make the value obvious without reading. Lead with the end state customers want, then reveal the "how."
Hero visual: A clean product shot or short video loop showing the moment of value (e.g., invoice paid, task completed, calendar booked).
Feature frames: 2–4 panels with a headline, a one‑line benefit, and a cropped screenshot focused on one UI action.
Microdemos: 10–30 second clips that show a specific workflow from start to finish; add captions for silent viewing.
Annotated screenshots: Use callouts sparingly to highlight exactly what changes for the user.
Avoid:
Full‑dashboard glam shots with tiny text.
Unrelated stock photos that add no meaning.
Overly technical diagrams on the main page (save for docs or a technical deep‑dive).
Pro tip: Add a tiny label above each screenshot that finishes the sentence "Now you can…" It forces benefits‑first framing.
Photo: Pavel Danilyuk / Pexels
Pricing blocks that reduce friction
Pricing is copy. Your goal is to help buyers pick quickly without scanning a novel.
Limit to 2–3 tiers for a single audience. If you serve very different personas, split pages.
Lead with the recommended plan and explain why ("Most teams pick Growth for unlimited projects and priority support").
Summarize each plan with 3–5 bullets that map to outcomes, not features ("Unlimited exports" beats "10 GB storage" if that’s the real unlock).
Answer "What happens if I scale?" early: Note seats, overages, and upgrade path in one clean line.
If you offer a free plan or trial, state the key limits; honesty builds trust.
Pricing microcopy to copy–paste:
"Switch or cancel anytime."
"No credit card required to start."
"All plans include [core benefit]."
If you need a comparison table, keep it scannable. Label rows with outcomes ("Remove watermarks," "Import from Figma") instead of obscure feature names.
CTAs that earn the click
A call to action should mirror visitor intent and reduce the perceived risk of clicking.
Make the verb specific: "Start a 7‑day trial," "Generate your first report," "Book a 15‑min tour."
Clarify the next step: Add a promise under the button ("No card needed," "Takes 60 seconds").
Repeat the primary CTA 3–4 times across the page: hero, mid‑page, and bottom.
Use a single color for primary CTAs; keep secondary links text‑style or outlined.
CTA ideas by funnel stage:
Top‑of‑funnel (unaware): "Watch a 2‑min demo"
Problem‑aware: "See templates for agencies"
Solution‑aware: "Start free for 14 days"
Purchase‑ready: "Get a custom quote"
Your on‑page FAQ is a conversion lever
The right FAQ absorbs objections so sales doesn’t have to. Think of it as pre‑sales enablement embedded on your page.
Common questions to answer:
How does onboarding work, and how long does it take?
What data do you need access to? Can I revoke it?
What happens when I hit limits?
How does billing work for teams?
Can I import my existing data or switch later?
What support is included?
Keep answers short (2–4 sentences), with links to docs for depth. Use plain language, not legalese.
Place the FAQ near pricing or just above the footer CTA so it catches late‑stage hesitations.
Speed, accessibility, and trust signals
Copy can’t save a slow, inaccessible page. Technical quality is part of persuasion.
Performance: Compress images, lazy‑load below‑the‑fold media, and inline critical CSS for your hero. Your demo video should have a small, optimized version for the hero.
Accessibility: Ensure contrast ratios meet standards, buttons are keyboard‑focusable, and images have descriptive alt text.
Privacy and security: If your product touches sensitive data, link to a readable privacy policy and security overview. Use short summaries with optional depth.
Mobile first: Test the hero, CTA, and pricing on small screens; stack wisely and keep copy tight.
A lightweight A/B testing loop
You don’t need a lab to learn. Keep experiments small, targeted, and tied to one primary conversion (e.g., signups or demo requests).
One change per test: Don’t bundle multiple shifts or you won’t know what moved the needle.
Define success before launch: Pick the one metric (e.g., click‑through to signup) and the minimum difference you care about.
Run long enough to trust the result: End early only if the result is a landslide and consistent day over day.
Ship the winner, then move to the next bottleneck.
Simple test ideas:
Outcome vs. JTBD headline framing.
Short demo loop vs. static hero screenshot.
"Start free" vs. "Try it now" CTA.
Adding a single, specific testimonial quote in the hero vs. logos only.
Photo: Kampus Production / Pexels
A teardown checklist you can run in 20 minutes
Use this list to audit any landing page. Work top to bottom; fix the biggest leaks first.
Relevance and clarity
Can a first‑time visitor name the audience, the outcome, and the next step in 5 seconds?
Is the headline specific and benefit‑led?
Does the subhead define what it is and how it works?
Proof and safety
Is there at least one trust nudge above the fold (logos or a strong quote)?
Do you address the top 2–3 objections in an FAQ or near pricing?
Visual communication
Does the hero visual show the moment of value?
Are screenshots cropped to one action each with clear captions?
Focus and flow
Is there exactly one primary CTA style repeated throughout?
Are there any distracting links or competing navigations you can remove?
Pricing and plans
Are there 2–3 clear options with a highlighted recommendation?
Do bullets describe outcomes instead of raw features?
Performance and accessibility
Are images compressed and below‑the‑fold media deferred?
Do buttons have visible focus states and adequate contrast?
Analytics and testing
Is one primary conversion tracked end‑to‑end?
Do you have a short list of prioritized tests to run next?
Examples of strong landing page patterns
You don’t need to copy a specific brand to learn from proven patterns. Try these modular sections that fit most SaaS, tools, and digital products.
Outcome hero: "[Do X] in [Y time] for [Audience]" + demo loop + logos + primary CTA.
Use‑case lanes: A horizontal strip with 3 cards, each labeled for a persona or job ("For founders," "For ops," "For finance"), each with a 1‑line benefit and "See details" links.
Before/After contrast: A split panel—on the left, a short list of pains; on the right, the new flow with a cropped screenshot.
Template gallery: A scannable grid of starter templates or playbooks; each card has a benefit title and a "Use this" CTA.
Objection‑busting FAQ: 5–7 precise questions with brief answers, each linking to docs for depth.
Social proof wall: 2–3 quotes with photos and names, plus a few recognizable logos beneath.
Closing CTA with safety net: Last block repeats the primary CTA with "No card needed" and an email link to support.
How to choose the right structure for your product
Different offers need different emphasis. Match your page to your motion.
Self‑serve freemium: Lead with demo loops and templates. Push a "Start free" CTA and show quick‑start steps.
Sales‑assisted B2B: Lead with outcome claims and social proof. Drive to "Book a demo" with a 3‑field form. Add an ROI blurb and integration list.
Services or courses: Spotlight transformations and student/client wins. Use a curriculum or process section and a prominent schedule/availability box.
Mobile‑first tools: Keep blocks tall and simple. Emphasize thumb‑reachable CTAs and device‑native visuals.
If you’re unsure, start with the outcome hero + use‑case lanes + proof wall + pricing + FAQ. It covers the bases and is easy to maintain.
Writing process: from rough to ready in 48 hours
You can write strong copy fast if you gather the right inputs.
Day 1
Interview 3 users or read 10 recent support tickets to capture exact phrases. Paste the best lines into your draft verbatim.
Draft the headline and subhead options (at least 5 of each). Don’t edit yet.
Sketch the hero visual and one microdemo concept.
Day 2
Pick the clearest headline and subhead; ship a first version.
Add one strong testimonial and 3–6 logos.
Write pricing bullets that describe outcomes.
Fill the FAQ with the top 5 objections you actually hear.
Set up tracking for one primary conversion and plan your first A/B test.
Editing checklist
Read every sentence out loud. Cut any word that doesn’t clarify or persuade.
Replace insider jargon with buyer language from interviews.
Swap clichés ("powerful," "seamless") for concrete actions ("imports your Stripe data," "sends summaries to Slack").
Tools and resources to speed things up
Research and inspiration: Browse Popular apps and Trending pages to study how high‑traffic products frame outcomes and proof.
Category examples: Explore Marketing, Design, and Analytics categories for patterns in your niche.
Drafting and feedback: Use a shared doc with comment threads, or a lightweight editor with version history.
Launch leverage: When you’re ready, list your app on Zivvi via Submit and make it discoverable alongside thousands of web apps.
Zivvi catalogs over 2,300 web apps and organizes them by real‑world usage and purpose so you can see what actually gets attention online. We reference each app’s worldwide traffic rank from the Tranco list, a research ranking that blends multiple traffic sources to reduce bias. When we mention a 30‑day change, we’re comparing the app’s worldwide traffic rank from about 30 days earlier to the latest reading. Ranks are worldwide traffic ranks (Tranco list) as of November 6, 2026. We don’t take paid placements for inclusion or rank adjustments.
Frequently asked questions
What is the most important element of a landing page?
Clarity in the first screen. If your headline, subhead, proof nudge, and CTA make the benefit and next step obvious within seconds, everything else gets easier. Visitors won’t hunt for meaning, and more will start the journey you want.
How long should a landing page be?
Long enough to answer objections and short enough to keep momentum. If you sell a simple self‑serve tool, a concise page with a strong hero, a few use‑case cards, proof, and pricing often wins. For B2B and higher‑stakes decisions, add depth with case blurbs and an FAQ without bloating the copy.
Where should I place social proof for maximum effect?
Add a small proof nudge in the hero to reduce early risk, then a richer proof wall mid‑page where attention dips. A final quote or trust badge near pricing can ease late‑stage jitters. Keep each proof block relevant and specific to the claim it supports.
How many CTAs should a landing page have?
One primary CTA style repeated 3–4 times is ideal. If you need a secondary option (like "Book a demo" vs. "Start free"), make it visually lighter and use it sparingly. Too many equally prominent buttons create choice paralysis and lower conversions.
What should I test first on my landing page?
Start with the headline, hero visual, and primary CTA copy because they influence the most visitors. Test one element at a time against a clear conversion and let the test run to a confident result. Ship the winner, then move to pricing copy, proof placement, and form length.
How do I write a good on‑page FAQ?
List the top 5 objections your buyers actually raise, then answer in 2–4 sentences using plain language. Link to docs or policies for detail and place the FAQ near pricing or the final CTA. Treat it as pre‑sales enablement, not a dumping ground for edge cases.
Ready to put this to work? Study patterns from high‑performing tools on Popular, browse your niche in Categories, and when your page is ready, make your product discoverable by listing it on Zivvi via Submit.
Enjoyed this?
Share it with someone who's picking their next app.
Best of
Launch
Makers