landing-page-strategy git:20260720.41d8423A

Immutable. This exact content is served forever at /api/v1/blob/470c26ebb93ac1a7.

---
name: landing-page-strategy
description: Build landing pages with a clear message hierarchy, credible proof, and one decisive call to action, tested where it matters. Use when creating or fixing pages that must convert visitors.
---

# Landing page strategy

A visitor gives you five seconds to answer three questions: what is
this, is it for me, why should I care. The page is a message
hierarchy that answers them in order; design decorates the answers,
never substitutes for them.

## Method

1. **Lead with outcome-first clarity.** The headline states
   the outcome in the visitor's words ("Ship database
   migrations without downtime"), the subhead adds the how
   and the for-whom; cleverness loses to clarity every
   test (see readme-writing's first-screen rule: the same
   job for a different visitor). The five-second test:
   show a stranger the fold, ask what the product does:
   if they cannot say, iterate the words before anything
   else.
2. **Show the product doing the thing.** A real screenshot,
   a 30-second product clip, or an interactive demo beats
   abstract illustration: the visitor is deciding whether
   the product is real and whether it looks like work they
   understand (see product-launch's announcement ethic).
   Fake-looking product shots read as vaporware.
3. **Sequence the page as an argument.** Fold: what/who/
   why + CTA. Then: the problem named (recognition), how
   it works (three steps max), proof (logos, numbers,
   testimonials with names and faces: specificity is
   credibility: "cut deploy time 60%" beats "amazing
   tool"), objection handling (pricing transparency,
   security posture, migration ease: see
   trust-adjacent pages linked), final CTA. Each section
   answers the objection the previous one raised.
4. **Give the page one job.** One primary CTA repeated
   ("Start free", "Book a demo": matched to the funnel
   stage and honest about what happens next), secondary
   actions visually subordinate (docs, changelog);
   navigation minimal on campaign pages. Forms ask the
   minimum (every field costs conversion: see
   mobile-input-ux's field-cutting, form-handling);
   the ask matches intent temperature: cold traffic gets
   the low-commitment step.
5. **Load fast and read honest.** Core Web Vitals green
   (see web-vitals, technical-seo: speed is conversion
   and ranking at once), mobile-first layout (see
   responsive-design), and no dark patterns (fake
   countdown timers, sneaky checkboxes: short-term lifts
   that poison trust and brand: see ab-test-design's
   ethics boundary).
6. **Test big swings, read whole-funnel.** A/B test
   message-level changes (headline framing, proof order,
   CTA commitment: see ab-test-design's power math:
   button-color tests on small traffic are noise
   ceremonies); measure to activation, not click ("more
   signups, fewer activated users" is a worse page
   wearing a better conversion rate: see
   user-activation, product-metrics' guardrails).
   Qualitative sessions (watch five people use the page:
   see customer-interviews' observation ethic) find what
   the numbers cannot name.

## Boundaries

- The page amplifies positioning; it cannot create it.
  If you cannot write the headline, the problem is
  strategy (who is this for, against what alternative:
  see product-discovery), not copy.
- SEO landing pages and campaign landing pages have
  different jobs (durable intent capture vs message
  match); do not average their designs (see
  technical-seo).
- B2B enterprise deals close in rooms, not on pages;
  there the page's job is credibility and the meeting
  booking, and "Request demo" friction is intentional
  qualification (see saas-pricing's enterprise tier).