AI Skill Report Card

Designing Core Four Landing Pages

A-83·Oct 28, 2026·Source: Extension-page
13 / 15

Before designing anything, identify which of the Core Four page types the campaign needs:

  1. Lead Gen Page — collects contact info via a form (ebook, checklist, free trial signup)
  2. Click-Through Page — warms up cold traffic before sending to a transactional step (e.g., checkout, demo booking)
  3. Sales Page — long-form page that sells a product/offer directly on the page
  4. Webinar/Event Page — drives registration for a live or on-demand event

Pick the type based on the single conversion goal of the campaign. Never mix goals on one page.

Recommendation▾
Add 1-2 more examples covering Sales and Webinar page types, including a 'bad output' example to show contrast
15 / 15

Progress:

  • Step 1: Define the single conversion goal and page type
  • Step 2: Write the message hierarchy (headline → subhead → proof → offer → CTA)
  • Step 3: Build wireframe sections in Figma using the matching template
  • Step 4: Apply visual design (hierarchy, contrast, whitespace, imagery)
  • Step 5: Add trust/proof elements
  • Step 6: Review against conversion checklist
  • Step 7: Prep responsive/mobile variants

Step 1: Define the goal and page type

Ask: "What is the ONE action I want the visitor to take?" If there's more than one answer, split into separate pages.

Step 2: Message hierarchy

Draft copy blocks in this order before touching visuals:

  • Headline: states the outcome, not the feature
  • Subheadline: clarifies who it's for or how it works
  • Supporting bullets: 3 benefit-driven points
  • Social proof: logos, testimonials, numbers
  • Offer recap: restate value right before the CTA
  • CTA: action-oriented, matches the page type (e.g., "Get the Guide" not "Submit")

Step 3: Build wireframe by page type

Lead Gen Page structure:

  • Hero: headline + short form (3-5 fields max) above the fold
  • Benefit section (3 bullets with icons)
  • Social proof (logos or testimonial)
  • Secondary form or repeated CTA at bottom
  • No navigation menu, no footer links that exit the page

Click-Through Page structure:

  • Hero: headline + single CTA button (no form)
  • Problem/solution section
  • Feature highlights (3-4 with visuals)
  • Testimonial or case study snippet
  • Final CTA repeating the hero button copy

Sales Page structure:

  • Hero: headline + CTA + hero image/video
  • Pain point agitation section
  • Solution/product walkthrough
  • Feature-to-benefit table
  • Pricing/offer stack
  • Testimonials (multiple, with specifics)
  • FAQ section addressing objections
  • Final CTA with urgency/guarantee

Webinar/Event Page structure:

  • Hero: date/time + topic headline + registration form
  • "What you'll learn" bullet list
  • Speaker bio with photo
  • Agenda or timeline
  • Social proof (past attendee count, testimonials)
  • Final CTA with countdown or urgency element

Step 4: Visual design pass

  • One primary CTA color, used consistently and nowhere else on the page
  • F-pattern or Z-pattern layout for scanning
  • Mobile-first spacing — design the mobile frame alongside desktop in Figma, not after
  • Max 2 fonts, clear type scale (headline/subhead/body/caption)

Step 5: Trust elements

Place at least one proof element (testimonial, logo bar, stat, guarantee badge) within the first scroll and again near the final CTA.

Step 6: Conversion checklist

  • Single, unambiguous CTA goal
  • Headline passes the "5-second test" (clear value, no jargon)
  • No nav bar (except Sales pages may keep minimal anchor links)
  • CTA button text is specific, not generic ("Submit"/"Learn More" banned)
  • Form length matches offer value (low-commitment offer = short form)
  • Mobile frame checked for tap-target size and form usability

Step 7: Responsive prep

Duplicate the desktop frame, set to mobile breakpoint, and manually re-stack sections — don't rely on auto-resize alone for landing pages, since hierarchy often needs to change order on mobile (e.g., move form above benefits).

Recommendation▾
Include a concrete copy snippet or mini wireframe (ASCII/text layout) for at least one page type to make the output format more tangible
14 / 20

Example 1: Input: "Need a page for a free ebook download targeting cold Facebook traffic." Output: Lead Gen Page. Hero with headline stating the ebook's outcome ("Cut Your CAC in Half: The Growth Playbook"), 3-field form (name/email/company) above the fold, no nav, 3 benefit bullets, one testimonial, repeated form at bottom.

Example 2: Input: "Need a page to warm up retargeting traffic before they book a demo call." Output: Click-Through Page. Hero headline + single "Book Your Demo" CTA button (no form on this page), problem/solution section, 3 feature highlights with screenshots, one case study quote, final CTA button repeating hero copy.

Recommendation▾
Add edge cases like what to do when a client insists on combining two goals, or how to handle low-traffic pages with limited testimonial data
  • Design copy first, visuals second — never let visual design dictate the message hierarchy
  • Every section should answer "so what?" for the visitor
  • Keep forms as short as the offer value allows; cut fields that aren't essential to follow-up
  • Use real customer language in headlines and testimonials, not generic marketing speak
  • Design the final CTA section with the same care as the hero — it's the last chance to convert
  • Adding site navigation to a landing page (gives visitors an exit ramp)
  • Using multiple CTA colors or competing buttons on one page
  • Writing feature-focused headlines instead of outcome-focused ones
  • Treating mobile as an afterthought resize instead of a re-prioritized layout
  • Mixing two conversion goals (e.g., "Download" and "Book a Call") on the same page
  • Skipping the FAQ/objection-handling section on Sales pages
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
15/15
Examples
14/20
Completeness
16/20
Format
15/15
Conciseness
13/15