.cursor/skills/constructing-a-landing-page/SKILL.md
Design, audit, or optimize landing pages for any business model. Routes to the right configuration (B2B SaaS, B2C ecommerce, high-consideration application, lead gen / local service, content / lead magnet, pricing page), then produces a section-by-section build spec with copy direction, CTA strategy, post-CTA experience, proof tactics, pricing display, micro-copy, performance targets, accessibility, compliance, and experiments.
npx skillsauth add alexwox/genesis-template constructing-a-landing-pageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build or audit a landing page from hero section to post-CTA experience. The output is always a section-by-section action plan with element checklists, copy direction, benchmark targets, risk-labeled tactics, and prioritized experiments — not a list of generic tips.
Slash command: /landing-page
Apply this skill when the user asks things like:
Before building anything, gather the following. Ask only for what is missing; use sensible defaults for the rest.
| Input | Why It Matters | Default If Not Provided |
|---|---|---|
| Goal of the page | Determines structure and CTA type | Lead capture |
| What you sell | Routes to configuration | — (must ask) |
| ACV or average order value | Sets page length and proof depth | Infer from product |
| Audience awareness level | Sets copy angle and section order | Problem-aware |
| Primary traffic source | Determines message match requirements | Paid ads |
| Brand maturity | Determines trust signal weight | Early-stage |
| Existing brand guide | Determines visual/verbal consistency | None |
| Output mode | build_spec, teardown, or optimization_sprint | build_spec |
Route to exactly one primary configuration. Each has its own section emphasis, page length, CTA pattern, and proof requirements.
IF B2B SaaS product with demo or trial CTA:
→ B2B SaaS Landing Page
ELIF physical or digital product with add-to-cart:
→ B2C Ecommerce Product Page
ELIF application/intake form → qualification → consult/purchase:
→ High-Consideration Application Page
ELIF local service or agency with form/call/booking CTA:
→ Lead Gen / Local Service Page
ELIF free resource download (ebook, tool, template, webinar):
→ Content / Lead Magnet Page
ELIF plan comparison or tier selection:
→ Pricing Page
Typical ACV: $1K–$100K+. Long-form. ROI-focused proof required. Multi-stakeholder audience (6–13 buyers per deal — Gartner).
Page length: Long (1,500–5,000+ words). Cold traffic needs education and objection handling before CTA.
Primary CTA: "Book a Demo" / "Start Free Trial" / "Get Started Free"
Must-have sections: hero with outcome headline, logo bar, problem/agitation, how-it-works, features-as-benefits with ROI data, case study with named company and metrics, pricing or "talk to sales" fork, FAQ, final CTA.
Proof emphasis: named case studies with dollar outcomes, G2/Capterra aggregate scores, security/compliance badges (SOC 2, GDPR), integration logos.
95-5 awareness constraint: only ~5% of category is in-market at any time (LinkedIn B2B Institute / Ehrenberg-Bass). For the 95% out-of-market, the page also builds brand memory — so headline, visual identity, and association strategy matter beyond immediate conversion.
Typical AOV: $20–$500. Short to medium form. Visual-heavy. Emotion-driven.
Page length: Short to medium (300–1,500 words). High-intent traffic from search or ads; fast decisions.
Primary CTA: "Add to Cart" / "Buy Now" / "Shop Now"
Must-have sections: hero with product image gallery, price + strikethrough if discounted, star rating + review count, key benefits (3–5 bullets), size/variant selector, shipping and return info above fold, UGC / customer photos, FAQ, sticky mobile ATC bar.
Proof emphasis: star ratings, review count, UGC photos/videos, "X sold" or "Y people viewing" social proof, trust badges (secure checkout, free returns).
Key metric: add-to-cart rate 8–15% of viewers (median); checkout completion 45–55% of carts.
Medvi-style funnel entry. Intake form as CTA. Qualification theater. Multi-step micro-commitment.
Page length: Medium (500–1,500 words above the form). The form itself replaces a long sales page by progressively engaging the visitor.
Primary CTA: "See If You Qualify" / "Get Your Free Assessment" / "Start Your Application"
Must-have sections: hero with outcome headline + "without X" pain removal, trust badge visible before form starts, 3-step progress indicator, intake form with easy questions first, qualification gate, offer/pricing reveal post-qualification.
Proof emphasis: review badge (Trustpilot / Google), doctor/provider/expert credentials, "X patients/clients served" count, media mentions, professional photography (not stock).
Key tactics: commitment boundary — zero form fields visible on the landing page; the CTA button ("See If You Qualify") is the only commitment ask; form appears only after the click. Trust-reinforced transition — loading screen between CTA click and form reveal shows trust badges (TrustPilot score, provider credentials) to amplify the commitment and prevent regret. Micro-commitment ladder (innocuous data first, sensitive data later), progress bar (3–5 visible steps), medical/professional authority framing, all-inclusive pricing to reduce cognitive load.
Typical transaction: $100–$10K. Short form. Form or call CTA with booking emphasis.
Page length: Short (300–800 words). Speed matters — visitor is searching for a solution now.
Primary CTA: "Get a Free Quote" / "Book a Consultation" / "Call Now" / click-to-call button
Must-have sections: hero with specific local outcome headline, phone number visible above fold, short form (3–4 fields max — for warm search traffic, inline is acceptable; for cold or social traffic, place behind a CTA button with form in modal or next step; see Commitment Boundary in Step 4), Google review stars, service area, before/after or portfolio images, FAQ.
Proof emphasis: Google review score + count, local awards, "serving [city] since [year]", license/insurance badges, before/after photos.
Key metric: landing page conversion 5–15% (Google Ads industry averages range 2.9–14.7% — WordStream 2024). Speed-to-lead: respond within 60 seconds for 391% more conversions.
Goal: capture email in exchange for valuable free resource.
Page length: Short (300–600 words). Value proposition must be clear instantly.
Primary CTA: "Download Now" / "Get the Free [Resource]" / "Send Me the Guide"
Must-have sections: hero with specific outcome headline ("The exact [X] that [achieves Y]"), preview image of the resource, 3–5 bullet points of what's inside, single email/name form (inline is acceptable for 1–2 field forms with warm traffic — the commitment boundary benefit is real but too small to measure at this form complexity; see Commitment Boundary in Step 4), privacy reassurance micro-copy, social proof if available.
Proof emphasis: author credentials, number of downloads, testimonials from people who used the resource, preview of content quality.
Key metric: landing page conversion 15–40% for warm traffic, 5–15% for cold traffic (Unbounce benchmark report: median 6.6% across all industries, top quartile 11.4%+).
Goal: help visitor select a plan or tier and commit.
Page length: Medium (focused on comparison clarity, not persuasive length).
Primary CTA: "Start Free Trial" / "Choose Plan" / "Get Started" per tier
Must-have sections: tier comparison table (3 tiers convert 20–35% better than single tier), highlighted recommended tier, feature comparison matrix, FAQ addressing pricing objections, guarantee, enterprise/custom tier CTA.
Proof emphasis: customer logos per tier, "most popular" badge, aggregate review score.
Key tactics:
For the selected configuration, build each section using this template:
Section: [name]
Purpose: [what job this section does for the visitor]
Placement: [position in page sequence and why]
Required elements: [list]
Primary tactic: [with risk classification]
Benchmark: [metric and target range]
Diagnostic: [what to check if section underperforms]
Build sections in this order. Skip sections that don't apply to the configuration, but never skip Hero, Social Proof, or Final CTA.
Purpose: stop the scroll, communicate the core promise, and present the primary action in under 5 seconds.
Required elements (all 5 — pages with all 5 convert 30% higher):
Headline frameworks:
Copy rules:
Visual hierarchy:
Directional cues: use arrows or visual lines to direct attention toward the CTA or key content. Arrows beat human gaze for directing form attention (CXL eye-tracking lab study). Hierarchy: arrow > line > triangle > human gaze looking at the CTA. A human looking away from the CTA was the worst treatment. If using a hero image with a person, ensure their eye line or body orientation points toward the CTA, not away from it.
Navigation: remove site navigation on dedicated landing pages. Removing nav increases conversions 15–28%.
Message match: the headline must echo the exact language from the ad or link that brought the visitor. Word-for-word match delivers 20–35% conversion lift. This is the single biggest factor in landing page success.
Mobile: primary CTA must be thumb-reachable on first load without scrolling. 60%+ traffic is mobile.
Purpose: establish credibility before the visitor invests reading effort.
Placement: immediately below hero or integrated into hero section.
Elements (pick 2–3):
Rule: place best social proof early and repeat near friction points (form, pricing, CTA). Do not relegate all proof to the footer.
Trust badge selection matters: McAfee (+15.7–21.5%) and Norton (+12.2%) are the only consistently positive performers. Authorize.net, TrustGuard, and Trustwave can lower conversion because they're associated with amateur sites. Display 1–3 badges maximum near the CTA — 6+ badges = -5–8% conversion.
Low-volume guardrail: social proof with small numbers is worse than no social proof. "1 person watching" or "6 sales — 2 weeks ago" actively signals low demand. Set minimum display thresholds (e.g., show only when count > 50) or hide the widget entirely until volume is sufficient.
Purpose: make the visitor feel the cost of inaction before presenting the solution.
Copy framework: PAS (Problem → Agitate → Solve). 95% of purchase decisions are emotional, then rationalized logically.
Match to awareness level:
Rule: never skip agitation. Naming the problem without making it feel urgent produces weak motivation.
Purpose: explain how the product/service solves the problem in concrete terms.
Structure: "How it works" in 3–4 numbered steps. Each step = action + outcome.
Ties to Value Equation (from Hormozi local assets): reduce perceived time delay and effort/sacrifice while increasing perceived likelihood of achievement and dream outcome desirability.
Visual: process diagram, numbered steps with icons, or short walkthrough video.
Rule: clarity of mechanism builds perceived likelihood of achievement — the most under-leveraged variable in the Value Equation.
Purpose: translate capabilities into outcomes the buyer cares about.
Structure: 3–6 skimmable blocks. Each block = feature name + benefit statement + proof point (metric, testimonial snippet, or screenshot).
Rule: never list features without a "so that" or "which means" benefit translation. Feature-listing without benefit-proving is the most common landing page failure.
Purpose: show the product working, not just describe it.
Options (by configuration):
Placement: after features, before testimonials. Hero section videos get 300–450% higher view rates but must not slow page load.
Technical: video files < 500KB, WebM + MP4 formats, burned-in captions, lazy-load if below fold.
Purpose: transfer trust from existing customers to the prospect.
Hierarchy of proof strength:
Format rule: hybrid testimonial pages (3–5 videos + 15–30 text testimonials) outperform either format alone. Video-only pages increase bounce rate. Text-only converts lower than hybrid.
Rules:
Compliance: real customers only, with documented consent. No AI-generated testimonials or transformation photos (FDA warning letters, FTC enforcement, platform bans).
Purpose: help the visitor self-identify ("this is for me") or self-disqualify (saves everyone time).
Structure: 2–4 persona cards or use-case scenarios. Each names a role, situation, and outcome.
Rule: self-identification reduces bounce from mismatched visitors and increases conversion quality. This section is especially important when the page receives broad traffic.
Purpose: preemptively address the reasons visitors hesitate before asking for the commitment.
Source objections from: sales call recordings, support tickets, chat logs, review complaints, competitor comparison searches.
Structure: 5–8 items. Each answer is 2–3 sentences maximum, specific, plain language. Covers the mental checklist: What is this? Who is it for? How does it work? What does it cost? Why trust it? What if it doesn't work?
Placement: before the final CTA, not buried in the footer. Objection handling placed near the decision point recovers high-intent visitors who would otherwise leave.
FAQ schema markup: implement JSON-LD for SEO benefit and AI citation eligibility.
Purpose: present the investment clearly and make the decision feel obvious.
Structure varies by configuration:
SaaS / subscription:
Ecommerce:
Service / high-consideration:
All configurations:
Purpose: remove the last barrier to action by transferring risk from buyer to seller.
Types:
Rules:
Purpose: give the visitor a clear, low-friction path to act after consuming the full page.
Structure:
Sticky CTA bar (mobile): always-visible bar at bottom of screen with CTA button and one-line value statement. Sticky CTAs increase mobile conversion 15–40%.
Placement: one final CTA block at the end of the page. Do not end a page without a CTA.
Purpose: catch visitors who scroll past the CTA and provide trust/legal infrastructure.
Elements:
The sections above form the core sequence for every landing page. The sections below are additive — include them when they apply to the configuration and audience. Each specifies which configurations benefit, where to place it, and what to measure.
Applies to: B2B SaaS (Config A), High-Consideration Application (Config C).
Purpose: intercept the "keep researching" exit by answering comparison questions on your page instead of sending the visitor to a competitor's.
Placement: after Features as Benefits (Section 5) or after FAQ (Section 9). Test both — placement closer to hero works when traffic comes from "[competitor] alternative" queries; placement near FAQ works for broader awareness traffic.
Structure:
Comparison table:
Migration / switching reassurance (when replacing an incumbent):
Compliance: do not make false or unverifiable claims about competitor capabilities. Use screenshots or dated citations if referencing specific competitor limitations. FTC Lanham Act risk is real for misleading competitive claims.
Benchmark: pages with a comparison section see 15–25% longer session duration and 10–20% reduction in "competitor alternative" bounce exits (HubSpot, Gartner competitive page data).
Applies to: B2B SaaS (Config A).
Purpose: prove the product fits into the buyer's existing stack, reducing "will this work with what we already use?" friction.
Placement: after Features as Benefits (Section 5) or after Solution/Mechanism (Section 4). Proximity to the "how it works" explanation is most natural.
Structure:
Rule: only show integrations the target avatar uses. A logo bar of tools the buyer doesn't recognize adds visual noise without trust.
Benchmark: B2B SaaS pages with a visible integration section see 8–15% higher demo request rates when the buyer's existing stack is represented (Databox case study patterns).
Applies to: B2B SaaS (Config A) with ACV > $10K, and any configuration selling to regulated industries (healthcare, finance, government).
Purpose: satisfy the security, legal, and procurement reviewers who visit the page on the 2nd or 3rd visit — after the champion has already decided they want the product. These visitors have a different job-to-be-done than the first-time visitor; they need compliance confidence, not persuasion.
Placement: below pricing (Section 10) or as a dedicated "Security & Compliance" section before FAQ (Section 9). Some B2B pages place it as a linked sub-page rather than inline — either works, but the landing page must surface the entry point.
Required elements:
Security posture:
Data governance:
Enterprise features (checklist format):
Compliance certifications:
Rule: do not display security badges you cannot back up with documentation. Enterprise buyers will request the actual reports. Hollow badging destroys trust faster than having no badge at all.
Benchmark: B2B pages with a visible security/compliance section reduce procurement cycle length by 15–30% for deals > $25K (Vanta, Drata customer case studies). Security concerns are the #2 reason enterprise deals stall after technical evaluation (Gartner).
Applies to: B2B SaaS (Config A), Pricing Page (Config F), and any page exceeding ~2,000 words.
Purpose: let visitors jump directly to the section that answers their current question, reducing "TLDR" abandonment on long-form pages. This is distinct from the "remove site navigation" rule — global site nav should still be removed on dedicated landing pages; in-page section navigation helps rather than hurts.
Placement: sticky left sidebar (desktop) or collapsible sticky top bar (mobile). Appears after the visitor scrolls past the hero section.
Structure:
Implementation rules:
id attribute for accessibility and deep-linking.Accessibility benefit: in-page navigation gives keyboard and screen-reader users a way to skip to relevant content, aligning with WCAG 2.4.1 (Bypass Blocks) and 2.4.5 (Multiple Ways).
Benchmark: long-form pages with anchor navigation see 10–18% higher scroll depth and 8–12% lower bounce rates (Hotjar, Crazy Egg heatmap studies). The effect is strongest on pages longer than 3,000 words.
Applies to: B2C Ecommerce Product Page (Config B).
Purpose: address the specific UX and conversion patterns that separate high-performing product detail pages from basic product listings. Config B already covers hero image, price, reviews, benefits, UGC, and sticky ATC bar; these components fill the remaining gaps.
Breadcrumbs:
Size / fit / spec guidance:
Ingredient / material / spec tabs:
Shipping and delivery:
Buy Now, Pay Later (BNPL):
On-page cross-sell / bundles:
Shipping cutoff timer (ethical):
Benchmark targets:
Applies to: B2B SaaS (Config A), Lead Gen / Local Service (Config D), High-Consideration Application (Config C).
Purpose: replace passive reading with active engagement. Interactive tools increase time on page, generate lead data, and produce personalized outputs that make the CTA feel earned rather than asked-for.
ROI / TCO / Savings Calculator:
Placement: after Features as Benefits (Section 5) or as a standalone section between proof and pricing. Can also serve as the primary CTA itself ("Calculate Your Savings →").
Structure:
Compliance: ROI claims must be defensible. Use conservative defaults. If projections are based on average customer data, state that clearly. Avoid guaranteeing specific financial outcomes — frame as estimates ("customers typically see…" not "you will save…").
Benchmark: pages with interactive calculators see 2–3x higher lead capture rates than static pages with the same offer (Demand Gen Report, Ion Interactive benchmarks).
Assessment / Quiz:
Placement: as the primary CTA variant (replacing or complementing the standard form). Works especially well for High-Consideration Application (Config C) and Lead Gen (Config D).
Structure:
Rule: the quiz must deliver genuine value. A quiz that asks 10 questions and then says "book a call to learn more" with no actual results will feel like a bait-and-switch and kill trust.
Benchmark: quiz-style lead capture converts 30–50% of starters vs. 5–15% for standard forms (Typeform, Outgrow benchmarks). Lead quality is typically higher because the quiz pre-qualifies and self-segments.
Product Configurator:
Applies to: B2C Ecommerce (Config B) for customizable products, and B2B SaaS (Config A) for seat/usage-based packaging.
Structure:
Rule: configurators must not hide pricing until the end. Progressive price revelation as the visitor makes choices maintains trust and reduces sticker shock.
Applies to: B2B SaaS (Config A), B2C Ecommerce (Config B) for demonstrable products, Content / Lead Magnet (Config E) when the resource is visual.
Purpose: create a single memorable, brand-specific visual experience that passes the 50ms trust gate, triggers the Von Restorff effect (200–300% better recall for distinctive elements), and does persuasion work — not just decoration.
Placement: integrated into Hero (Section 1) as the hero visual, or embedded in Visual Demo / Proof (Section 6). Never both — one signature moment per page.
Decision framework:
IF product is visual/demonstrable AND page is long-form:
→ Scroll-driven product demo (SuperShrimp laptop, Stripe code animation)
ELIF brand has a strong character/personality AND audience values approachability:
→ Brand character integration (Duolingo owl, Mailchimp Freddie)
ELIF product is abstract AND mechanism needs explaining:
→ Interactive visual explanation (scroll-triggered diagrams, animated process)
ELIF page is short-form OR AOV < $20 OR traffic is high-intent:
→ Skip — the interaction adds friction between intent and purchase
ELIF mobile traffic > 70% AND interaction requires precise scroll/hover:
→ Skip or degrade gracefully — test mobile experience separately
Types with examples:
The gimmick-vs-signature test:
Before building, answer three questions. If any answer is "no," the interaction is a gimmick, not a signature moment:
Risk labels:
Performance rules:
prefers-reduced-motion)Benchmarks:
Near-miss counter-example: A SaaS landing page adds a beautiful parallax scroll interaction where abstract geometric shapes float and rotate as the user scrolls. The animation is smooth, the easing is custom, and the visual craft is high. But the shapes have no connection to the product (project management), and the parallax effect pushes the CTA below the fold on mobile by adding 400px of scroll distance. The interaction earned internal praise and Twitter engagement but conversion dropped 12% because it delayed the purchase decision without building trust or demonstrating the product. Fix: replace the abstract parallax with a scroll-driven walkthrough of the actual product UI — same scroll mechanic, but now it demonstrates the product and earns the CTA.
Rule: if the brand guide defines a signature visual element, use it here. If no brand guide exists, apply the gimmick-vs-signature test above before investing build effort. Reference the brand-guide-creation skill's brand character/signature visual procedure for the element's definition and usage rules.
One primary CTA per page. A single focused CTA increased clicks 371% and sales 1,617% compared to multi-CTA layouts. Multiple CTAs create decision paralysis.
Exception: one secondary CTA is acceptable for visitors not ready for the primary action (e.g., "Not ready? Download the free guide").
The CTA button is the commitment boundary — the point where the visitor decides "yes, I want this." Everything before the button is persuasion (headline, proof, agitation, mechanism). Everything after the button is collection (form fields, qualification, payment). If form fields are visible before the commitment boundary, the visitor evaluates the effort cost before deciding, and most abandon. If the commitment comes first, consistency bias carries them through the collection phase.
This connects to the constructing-a-funnel skill's Principle 2 (commitment escalation): the ladder is click → answer → personal data → time → money. A visible form field is a "personal data" ask. A CTA button is a "click" ask. The ladder says click must come before personal data.
Default rule: when in doubt, hide the form behind a CTA button.
DEFAULT: Hide the form behind a CTA button. When in doubt, use this default.
The commitment boundary is a universal principle. The safe default is
always: button first, form after. The only question is whether the
specific context qualifies for the inline exception.
WHEN IN DOUBT:
→ CTA button only on the landing page (no visible form fields)
→ After click: transition screen with reinforcing proof
(trust badge, review score, "great choice" confirmation)
that validates the decision before the form appears
→ Then: form, escalating from easy to hard
This is the Medvi pattern. It is the safest default because it
never hurts (commitment/consistency always helps) and it
dramatically helps for complex forms and cold traffic.
THE ONE EXCEPTION where inline is acceptable:
IF form has 1-3 fields
AND traffic is warm/high-intent (search ads, retargeting, referral)
AND the form is trivially obvious (single email field, no sensitive data)
→ Inline form is acceptable — the commitment boundary benefit
exists but is too small to measure at this complexity
(Leadpages: 45% inline vs 44% two-step, 10-test A/B)
→ Even here, the CTA button should be visually dominant and the
form fields should feel secondary — not the other way around
FOR BLOG/CONTENT PAGES (not dedicated landing pages):
→ Button → modal or scroll-triggered popup (3-5x more signups
vs passive inline — Sumo/BDOW, 1.8B displays)
→ Inline sidebar/footer forms are passive and ignored
The Medvi pattern (worked example of commitment boundary done right):
The post-commitment transition screen:
Between the CTA click and the form, insert a brief transition that reinforces the visitor's decision. This is not decorative — it amplifies commitment by creating temporal distance between the decision and the data collection, making the decision feel final. Elements to show during the transition:
The visitor should feel validated, not abandoned, during this moment.
Post-commitment escalation rules:
Once the visitor has crossed the commitment boundary and seen the reinforcing transition, escalate data collection:
Benchmarks:
Near-miss counter-example:
A high-consideration application page puts the CTA button in the hero but also shows the first two form fields (name and email) inline below the button as a "preview" of how easy the form is. The intention is good — reduce perceived effort by showing the form is short. But the visible fields shift the visitor's evaluation from "do I want this outcome?" to "do I want to fill out this form?" — reframing the decision from desire to effort. The commitment boundary is broken because the form is visible before the commitment click. Conversion drops 15% compared to a version where only the button is visible and the form appears after the click. Fix: remove all form fields from the landing page. The CTA button should be the only interactive element. The form appears only after the click, preceded by a trust-reinforcing transition screen.
Place risk-reducing micro-copy directly beneath or beside the CTA button:
This micro-copy addresses the last-second hesitation that kills conversions. It is not optional.
What happens in the 30 seconds after the visitor clicks is as important as what happened before. The moment of conversion is the peak of post-decision rationalization — the visitor's evaluation of your brand is at its most favorable point.
Speed-to-lead: respond to every form submission within 60 seconds. Response at 1 minute = 391% higher conversion; response at 5 minutes vs 30 minutes = 21x higher qualification rate (MIT/InsideSales landmark study). Average B2B response is 42+ hours — this is the single largest gap between what the data says and what companies do. For lead gen and demo requests, implement instant callback, SMS auto-reply, or live chat routing.
This is the highest-converting surface in the entire funnel. The visitor is at peak trust, peak post-decision rationalization, and peak behavioral momentum simultaneously. Confirmation page secondary actions convert at 10–15% vs 2–4% for pre-purchase pop-ups (Observed — Cart-X 2026, EasyAppsEcom 2026). A store generating $100K/month that ignores confirmation page optimization leaves $10K–$15K in monthly revenue on the table.
Every confirmation page needs four layers:
Technical requirements:
<meta name="robots" content="noindex"> on all confirmation pagesLead magnet: Deliver the resource immediately on the page itself (download button), not "check your inbox." The page has 100% view rate vs 20–30% email open rate. Include "Also sent to your email" as backup. Single next-step CTA: if the lead magnet reveals a problem, the CTA offers the solution. Reciprocity is at maximum — the request must be proportional to value received.
SaaS trial: Redirect straight to onboarding/activation — not a dead "thanks" page. Time-to-first-value starts now. Products delivering value within 10 minutes see 3x higher trial-to-paid conversion (Observed — 1Capture 2025). Use a confirmation page only when email verification or async setup is genuinely required; in that case show a progress indicator and auto-redirect when ready.
Ecommerce purchase: Order confirmation with: order summary (number, items, payment, total) + delivery timeline with tracking + one cross-sell recommendation (contextually relevant complement, not generic — pair with urgency timer and free shipping hooks) + referral prompt ("Share with a friend, get $X off" — double-sided incentives drive 3.2x higher referral rates) + return policy reassurance.
Application / intake funnel: "We've received your application" + specific timeline ("You'll hear back within 24 hours by email") + numbered next steps + interim value (educational content, FAQ, community access while they wait). Uncertainty at this stage creates regret and cancellation.
Demo booking: Confirmation with date/time/timezone + calendar add (.ics link) + who they're meeting (name, photo, title) + 2–3 bullet agenda + "While you wait" content (case study, product tour video, ROI calculator) + reschedule link. Companies embedding calendar scheduling directly after form submission convert at 66.7% vs 30% industry average (Observed — Prospeo/RevenueHero 2026).
Referral timing (all configs): Ask for referrals within 72 hours of purchase/signup — 3–5x ROI vs later asks. Referral CTA in shipping/confirmation emails drove +35% participation. The post-purchase glow fades fast.
Celebration animations (confetti, success checkmark, character reaction) can amplify the peak-trust moment — but only when the celebration marks the user's milestone, not the company's.
The Ramsey Test: Before adding any celebration, fill in: (1) "This celebration is marking ___." (2) "The user's actual goal was ___." If these are the same → appropriate. If different → the celebration marks a company milestone. Remove it.
When to include celebration: High-effort completion after multi-step process (e.g., publishing first listing, deploying a project). Significant purchase where buyer needs reassurance. Milestone achievement that closes a visible loop.
When to use clean confirmation instead: Routine actions, serious industries (banking, healthcare, insurance), redirect-to-product flows, intermediate steps in a longer process.
Accessibility: Always respect prefers-reduced-motion. Replace animation with a static success state (checkmark + text) — never suppress the feedback entirely.
| Leak | Impact | Fix | |---|---|---| | Blank "Thank you" page with no secondary CTA | Wastes the highest-converting surface in the funnel | Add the 4-layer structure above | | Multiple competing CTAs | Dilutes action — single CTA converts 2–3x | One primary secondary CTA; de-emphasize others visually | | No expectation-setting | Creates anxiety, buyer's remorse, support tickets | Two-bullet "what to expect" above the fold | | SaaS: confirmation page instead of redirect | Squanders behavioral momentum | Redirect to onboarding immediately | | Celebration on trivial action (account creation, email verification) | Feels cheap, contradicts user's actual goal | Apply the Ramsey Test; celebrate goal completion, not prerequisites |
confirmation_page_view (with conversion_type property: lead, trial, purchase, application, demo)secondary_cta_click (with cta_type: share, referral, upsell, download, onboarding_start)resource_download_completedonboarding_started (SaaS)calendar_booking_confirmed (demo)celebration_shown (with celebration_tier: micro, standard, major)Match page length to decision weight:
| Signal | Short (300–500 words) | Medium (500–1,500 words) | Long (1,500–5,000+ words) | |---|---|---|---| | Offer complexity | Simple | Moderate | High | | Audience awareness | High (product-aware) | Mixed | Low (unaware / problem-aware) | | Decision risk | Low (free, cheap) | Medium | High (expensive, commitment) | | Traffic temperature | Hot (retargeting, referral) | Warm (search, content) | Cold (paid, broad) | | Trust level | High (known brand) | Medium | Low (new brand) |
Scroll depth reality: 65–75% of visitors scroll past the fold. Most conversions happen below the fold, not above it. The "above the fold" rule is outdated — but the first screen must earn the scroll.
Attention follows a "bathtub curve": high at top, dips in middle, spikes again near bottom. Structure mid-page content to be skimmable so attention doesn't die in the middle.
| Configuration | Primary CTA | Secondary CTA | |---|---|---| | B2B SaaS | "Start Free Trial" / "Book a Demo" | "See Pricing" / "Watch Product Tour" | | B2C Ecommerce | "Add to Cart" / "Buy Now" | "Save for Later" / "Compare" | | High-Consideration | "See If You Qualify" / "Get Started" | "Learn How It Works" | | Lead Gen / Local | "Get My Free Quote" / "Book Now" | "Call Us" / "Chat Now" | | Lead Magnet | "Download the Free [X]" / "Send Me the Guide" | "Read the Summary First" | | Pricing Page | "Start Free Trial" / "Choose [Plan Name]" | "Talk to Sales" / "Compare Plans" |
Place directly below or beside the email field:
When processing takes >1 second, show a contextual message:
Perceived personalization increases patience and perceived value.
Swap headline and CTA copy based on UTM parameters:
Message match is the highest-leverage personalization: 20–35% conversion lift.
Insert city or region name into headline or subhead:
Adjust messaging for repeat visits:
Use IP-to-company enrichment tools to:
Page speed directly determines conversion. Each additional second of load time reduces conversions by approximately 7%.
| Metric | Target | What It Measures | |---|---|---| | LCP (Largest Contentful Paint) | < 2.5 seconds | When main content becomes visible | | INP (Interaction to Next Paint) | < 200 milliseconds | Responsiveness to user interactions | | CLS (Cumulative Layout Shift) | < 0.1 | Visual stability during load |
Crossing into "good" CWV thresholds yields step-change improvements:
Accessibility is not just compliance — it is a conversion lever. 71% of users with disabilities abandon inaccessible websites. 94.8% of homepages have detectable WCAG failures.
WCAG 2.2 AA minimum for all landing pages.
| Fix | Conversion Impact | |---|---| | Visible form labels (not placeholder-only) | +10–15% form completion | | Specific, friendly error messages | -22% form abandonment | | Proper color contrast ratios | Removes barrier for ~8% of male visitors with color vision deficiency | | Logical tab order for keyboard navigation | Enables conversion for keyboard-only users | | Alt text on all images | SEO benefit + screen reader access | | Proper heading hierarchy (H1 → H2 → H3) | Improves scanning for all users, not just assistive tech | | Touch targets minimum 44x44px | Reduces mobile mis-taps |
Sites that improved accessibility saw an average 12% lift in organic traffic. Accessible markup favors search engines. The global population using assistive technology: 1.3 billion people.
Run this checklist for every landing page before launch:
Every tactic in the output must carry one of these labels:
We believe [changing X on the landing page]
will [improve metric Y] by [estimated magnitude]
because [evidence/reasoning].
We will test this by [A/B test method] over [timeframe]
with [minimum sample size].
Success criteria: [metric] improves by [threshold] at [confidence level].
| Element | Cadence | Minimum Sample | |---|---|---| | Headline | Weekly | 1,000 visitors per variant | | CTA copy | Biweekly | 1,000 visitors per variant | | Hero image/video | Monthly | 2,000 visitors per variant | | Social proof placement | Monthly | 1,500 visitors per variant | | Page length (short vs long) | Quarterly | 5,000 visitors per variant | | Pricing display | Quarterly | 2,000+ visitors per variant | | Form fields (add/remove) | Monthly | 1,000 form starts per variant |
Test elements in this order (highest leverage first):
# Landing Page Build Spec: [Product / Campaign Name]
## Configuration: [Selected Config]
## Page Length: [Short / Medium / Long]
## Primary CTA: [Exact text]
## Section-by-Section Spec
### 1. Hero / Above the Fold
- Headline: [draft]
- Subhead: [draft]
- CTA button: [exact text]
- Hero visual: [description]
- Trust signal: [which one]
- Message match source: [ad / email / search term]
### 2. Social Proof Strip
- Elements: [logo bar / review score / customer count]
### 3. Problem + Agitation
- Pain statement: [draft]
- Cost of inaction: [draft]
### 4. Solution + Mechanism
- How it works: [3–4 steps]
### 5. Features as Benefits
- Feature 1: [feature] → [benefit] → [proof]
- Feature 2: ...
- Feature 3: ...
### 6. Visual Demo / Proof
- Type: [video / screenshots / interactive demo]
### 7. Testimonials
- Testimonial 1: [who, outcome, format]
- Testimonial 2: ...
### 8. Who It's For
- Persona 1: [role, situation, outcome]
- Persona 2: ...
### 9. FAQ / Objection Handling
- Q1: [objection] → A: [answer]
- Q2: ...
### 10. Pricing / Offer
- Structure: [tiers / single / custom]
- Anchor: [high tier first?]
- Guarantee: [type and placement]
### 11. Final CTA
- CTA text: [same as hero]
- Micro-copy: [risk reducer]
### Optional Sections Included
- [ ] Competitive / Migration Block — included: [yes/no] — placement: [after section X]
- [ ] Integrations / Ecosystem Strip — included: [yes/no] — placement: [after section X]
- [ ] Enterprise Trust / Procurement Block — included: [yes/no] — placement: [after section X]
- [ ] Long-Page Anchor Navigation — included: [yes/no] — format: [sidebar / top bar]
- [ ] Ecommerce PDP Extended (breadcrumbs, size guide, BNPL, cross-sell) — included: [yes/no]
- [ ] Interactive Tool (calculator / quiz / configurator) — included: [yes/no] — type: [which]
- [ ] Signature Visual Moment — included: [yes/no] — type: [scroll demo / character / visual metaphor / none] — performance budget: [Xms LCP impact]
## Tracking Events
1. [event_name] — [trigger] — [purpose]
2. ...
## Post-CTA Experience
- Thank-you page: [what it shows]
- Secondary CTA: [what action]
- Follow-up: [email / redirect / booking]
## Compliance Checklist
- [ ] All claims substantiated
- [ ] Testimonials use real customers with consent
- [ ] Countdown timers reflect real deadlines
- [ ] Accessibility WCAG 2.2 AA met
## First 3 Experiments
1. [Hypothesis]
2. [Hypothesis]
3. [Hypothesis]
# Landing Page Teardown: [URL or Business Name]
## Configuration Detected: [type]
## Page Length: [word count estimate]
## Per-Section Analysis
### Section 1: [Name]
- Purpose: [what this section does]
- Copy angle: [headline, subhead, CTA text]
- Trust elements: [what's present]
- Persuasion tactics: [with risk label for each]
- UX observations: [mobile, speed, accessibility]
- Missing: [what should be here but isn't]
### Section 2: ...
## Conversion Scorecard
| Category | Score (1–10) | Notes |
|---|---|---|
| Message match | | |
| Hero effectiveness | | |
| Social proof | | |
| Copy clarity | | |
| CTA design | | |
| Objection handling | | |
| Pricing presentation | | |
| Risk reversal | | |
| Mobile experience | | |
| Page speed | | |
| Accessibility | | |
| Compliance | | |
| Distinctiveness / Signature moment | | |
## Top 5 Strengths
1. ...
## Top 5 Leaks + Fixes
1. [Leak] → [Estimated impact] → [Fix]
## 5 Improvements for Ethical Replication
1. ...
# Optimization Sprint: [Page Name / URL]
## Current Performance
- Conversion rate: [X%]
- Benchmark for config: [Y%]
- Gap: [Z points]
## Top 5 Leaks (ranked by estimated impact)
1. [Leak] — [Evidence] — [Estimated drop-off]
2. ...
## 5 Experiments to Run
### Experiment 1: [Name]
- Hypothesis: [format from experiment OS]
- Element: [what changes]
- Expected lift: [%]
- Timeline: [days/weeks]
- Sample needed: [visitors or conversions]
### Experiment 2: ...
## Quick Wins (implement without testing)
- [ ] [Fix that is clearly broken, e.g., missing alt text, broken mobile CTA]
## Compliance Flags
- [Any issues found]
Do not finalize any landing page plan unless all gates pass:
Avoid:
Route to specialized skills when the landing page plan reveals a deeper need:
offer-pillar-discoverylead-magnet-creationconstructing-a-funnelconsult-hormozi (routes to $100M Pricing Playbook)brand-guide-creation (includes Branding Tactics for Conversion section)product-craftdeep-web-researchhigh-cagr-market-discoveryThis skill does NOT duplicate branding content. Instead, it references the brand-guide-creation skill for:
If no brand guide exists, flag this as a gap and suggest running brand-guide-creation before or in parallel with the landing page build.
$100M Offers - Alex Hormozi.pdf$100M Offers - Alex Hormozi.pdf$100M Offers - Alex Hormozi.pdf$100M-Leads-by-Alex-Hormozi.pdf$100M Branding Playbook.pdf$100M Pricing Playbook.pdftools
Translate role-based organizations into workflow-based organizations by decomposing roles into scored tasks, extracting dark playbooks (proprietary tacit knowledge), formalizing workflows, calculating automation ROI, and producing a sequenced automation roadmap. Use when a company wants to identify what work can be automated, extract undocumented expert knowledge, or build an automation strategy.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
Builds stakeholder-friendly project status updates from markdown sources. Use when asked for progress reports, implementation status, future plans, UI/UX flow summaries, infrastructure/data-flow summaries, risks, code smells, or scout-principle improvement notes.
development
Repeatable playbook for finding and interviewing key stakeholders to validate an offer pillar hypothesis. Produces a pain proximity map, target list, outreach plan, interview protocol, and structured synthesis of findings. Use when a hypothesis needs human validation before building.