Guides campaign landing page structure, conversion flow, and optimization. Primary use: Paid ads (PPC/SEM) — landing pages are typically built to receive paid traffic; ad-to-page alignment is critical for conversion. See paid-ads-strategy for when to use paid ads and ad-to-page alignment principles. Also applies to affiliate signup, product launch, lead capture, webinar registration, and other single-goal conversion pages. Scale: When building many landing pages (city-specific, product-specific, integration-specific), use programmatic-seo (template + data) and template-page-generator for template design. Differs from homepage (multi-purpose) and product pages (catalog).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
When LP receives paid traffic: ad promise on page immediately; mobile-first (CTA above fold, fast load); minimal form (fewer fields); trust above fold. See paid-ads-strategy for full ad-to-page alignment and Quality Score.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and value proposition.
Identify:
StepPurposeElements1. Stop the scrollCapture attention in ~2.6 secondsHeadline, subheadline, hero image or video2. Earn trustSocial proof before the askLogos, testimonials, ratings, customer count3. Explain valueBenefits, features, use casesClear copy; who it's for, what it does4. Remove doubtObjection handlingFAQ, guarantees, comparison5. Make the askSingle primary CTAOne clear action; repeat at logical points
Every element should serve one of these five functions. Pages with multiple competing offers get ~266% fewer leads.
[Who it's for] + [Specific outcome] + [Time/qualifier]
When you need many landing pages (e.g., city-specific, product-specific, integration-specific), use programmatic-seo: one template + data = hundreds or thousands of LPs. Apply landing page structure (5-step flow, CTA, trust) to the template; see template-page-generator for template design. Example: "[Product] for [City]" LPs with local data; "[App A] + [App B]" integration signup pages.
TypeUseCTA DestinationClick-throughWarm audience before sending to offer; best for SaaS, subscriptionspricing-page, products-page, signupLead captureCollect email for nurture; forms 5 fields or fewer (longer forms cause ~81% abandonment)newsletter-signup, contact-pageProduct-focusedDeep-dive features and benefits; product launchproducts-page, features-pageComparisonX vs Y; competitor brand keyword ads; commercial intentalternatives-page, features-page, pricing-pageUse cases / SolutionsFor integrated products hard to split into toolsfeatures-page, services-pageFree toolsStandalone utilities; lead gen; same ICP; excerpt from producttools-page-generator; tool page as LP when gatedBridge/bonusExtra incentive to purchase through your linkpricing-page, products-pageWebinar/eventEvent registration; collect signups before liveresources-page (webinar as resource)
Pull content from (step 2–4):
CTA sends to:
Internal linking:
Before shipping a landing page, verify:
CategoryCheckVisualNo emojis as icons (use SVG); icons from consistent set (Heroicons/Lucide); hover states don't cause layout shiftInteractionAll clickable elements have cursor-pointer; hover provides clear feedback; transitions 150–300msAccessibilityImages have alt text; form inputs have labels; color not sole indicator; prefers-reduced-motion respectedLayoutNo horizontal scroll on mobile; content not hidden behind fixed nav; responsive at 375px, 768px, 1024pxPerformanceLoad time under 2.5s; LCP optimized; images use WebP/lazy loading where appropriateImagesSee image-optimization for alt, format, responsive, lazy loading