landing-page

Landing Page

When to Use

• Creating a new landing page from scratch (product launch, feature page, waitlist).
• Auditing an existing page for conversion rate optimization (CRO).
• Rewriting headlines, CTAs, or hero sections.
• Structuring page sections for a specific audience and traffic source.
• Generating A/B test variants for copy or layout changes.

Context Required

• From startup-context: product description, ICP (ideal customer profile), value proposition, competitive positioning, stage, tone of voice.
• From the user: page URL or current copy (if auditing), page type (homepage, landing page, pricing, feature, blog), primary conversion goal (signup, demo, purchase, subscribe, download), traffic source (organic, paid, email, social), any existing conversion data or user research.

Workflow

1. Identify page type and conversion goal -- Every page gets one primary conversion action. Determine whether this is a homepage, landing page, pricing page, feature page, or blog post -- each has a different CRO framework.
2. Assess value proposition clarity -- Can a visitor understand what this is and why they should care within 5 seconds? Check whether copy is benefit-focused (good) or feature-focused (common problem). Ensure it is written in the customer's language, not company jargon.
3. Evaluate headline effectiveness -- Does the headline communicate the core value proposition? Is it specific enough to be meaningful? Does it match the traffic source's messaging? Apply headline patterns:
   • Outcome-focused: "Get [desired outcome] without [pain point]"
   • Specificity: Include numbers, timeframes, or concrete results
   • Social proof: "Join [N] teams who [achieve outcome]"
   • Direct address: "You [do painful thing]. There's a better way."
4. Audit CTA placement, copy, and hierarchy -- Is there one clear primary action visible without scrolling? Does button copy communicate value, not just action? ("Start my free trial" beats "Submit"). Check CTA hierarchy: primary vs. secondary, repeated at key decision points.
5. Check visual hierarchy and scannability -- Can someone scanning the page get the main message? Are the most important elements visually prominent? Is there sufficient whitespace? Do images support or distract from the message?
6. Evaluate trust signals and social proof -- Look for: customer logos (especially recognizable ones), testimonials with specifics and attribution, case study snippets with real numbers, review scores, security badges. Place trust signals near CTAs and after benefit claims.
7. Identify objection handling -- Are common objections addressed? Price/value concerns, "will this work for me?", implementation difficulty, "what if it doesn't work?" Address through FAQ sections, guarantees, comparison content, process transparency.
8. Find friction points -- Too many form fields, unclear next steps, confusing navigation, required fields that should not be required, poor mobile experience, slow load times.