Landing Page Architecture (8-Section Conversion System)
Use this skill when the user asks to:
- Create a landing page
- Improve conversion on an existing page
- Rewrite landing page copy/sections
- Structure a page before writing final copy
This skill defines structure + conversion logic first. Final copy is produced afterward, section by section.
Core principle
Each section must have one job. If a section has multiple jobs, split it.
Inputs to gather first (ask only if missing)
- Offer: what is being sold (product/service)
- Audience: who it is for
- Primary pain/problem
- Desired outcome/transformation
- Proof available (testimonials, numbers, logos, case studies)
- Risk reducer (refund, guarantee, trial, demo)
- Primary CTA action (buy, book call, start trial, join waitlist)
- Traffic intent (cold ads, warm social, brand search, email)
If inputs are missing, proceed with best assumptions and mark them as assumptions.
Output modes
Choose one based on user request:
Mode A — New landing page blueprint
Return:
- Page strategy summary (audience, promise, CTA)
- 8-section wireframe with purpose + content blocks + copy prompts
- Messaging hierarchy (headline ladder)
- Copy skeleton (what to write in each slot)
- QA checklist before implementation
Mode B — Existing page teardown + rebuild
Return:
- Section-by-section diagnosis of current page
- What to keep / cut / rewrite / reorder
- Revised 8-section architecture map
- Replacement copy guidance by section
- Priority fix list (high impact first)
Mode C — Copy reasoning audit
Return:
- Current section copy
- Why it underperforms (clarity, relevance, trust, friction, specificity)
- Better copy direction (with rationale)
- Example rewrite options (2-3 tones if requested)
The 8 sections (required sequence by default)
1) Hero — “Get email or get scroll”
Job: Stop the right visitor and drive first action. Must include:
- Clear promise/outcome headline
- Subhead with who + what + speed/mechanism
- Primary CTA
- Optional micro-proof or risk-reducer near CTA
Good checks:
- Can a stranger understand the offer in 5 seconds?
- Is CTA specific (not vague like “Submit”)?
2) Success — “Kill buyer’s remorse”
Job: Show this works and reduce post-click anxiety. Must include one or more:
- Result snapshots (metrics, timelines)
- Quick wins or outcomes achieved
- “What happens after signup/purchase” clarity
3) Problem-Agitate — “Make status quo painful”
Job: Increase motivation to change now. Must include:
- Current-state pain points in audience language
- Cost of inaction (time/money/stress/opportunity)
- Emotional and practical consequences
Avoid melodrama; be precise and credible.
4) Value Stack — “Make saying no feel stupid”
Job: Increase perceived value versus price/effort. Must include:
- What they get (components/modules/deliverables)
- Why each piece matters
- Optional bonus, guarantee, or support layer
- Price anchoring if appropriate
5) Social Proof — “Let others convince them”
Job: Transfer trust from existing users to new visitor. Must include:
- Testimonials with specifics (before/after, context)
- Logos, counts, ratings, or case-study snippets
- Objection-matching proof (proof tied to key fears)
6) Transformation — “Make outcome tangible”
Job: Help visitor visualize their future state. Must include:
- Before vs after state
- Day-in-the-life or scenario-based outcome
- Identity shift (“from X to Y”)
7) Secondary CTA — “Catch the scrollers”
Job: Convert users who need one more nudge. Must include:
- Condensed restatement of value
- Objection handling line
- Repeated CTA with low-friction framing
8) Footer — “Professional legitimacy”
Job: Close trust gaps and satisfy compliance expectations. Must include:
- Contact/company details
- Policy links (privacy, terms)
- Basic trust signals (secure checkout badges, etc. where relevant)
Copy rules (all sections)
- Specific beats clever.
- One core idea per block.
- Use concrete nouns, numbers, and timelines.
- Replace hype adjectives with proof.
- Match reading intent: cold traffic needs more clarity + proof.
- Keep paragraphs short and scannable.
Objection mapping framework
For each page, map top objections and where they are handled:
- “Will this work for me?” → social proof + transformation
- “Is this worth the price?” → value stack + success
- “What if I fail?” → guarantee/risk reversal + process clarity
- “Why now?” → problem-agitate + CTA urgency framing
Editing existing pages (mandatory process)
When improving an existing page:
- Inventory current sections and map them to the 8-section model
- Identify missing jobs and duplicated jobs
- Score each section 1-5 on: clarity, relevance, proof, persuasion, friction
- Rewrite highest-impact weak sections first: Hero, Value Stack, Social Proof, CTA
- Preserve what already converts (do not rewrite for style only)
- Provide rationale for each rewrite in plain language
Reasoning format for copy changes
For each changed section, use:
- Issue: what is weak
- Hypothesis: why it hurts conversion
- Change: what to rewrite/restructure
- Expected effect: what should improve
Deliverable template
Use this structure in responses:
- Strategy snapshot (audience, offer, CTA)
- Section architecture table/list (1→8 with job + key elements)
- Copy scaffolds per section (headline/subhead/body/CTA prompts)
- Objection handling map
- Priority implementation order
- Optional A/B test ideas (headline, CTA, proof order)
Guardrails
- Do not invent fake testimonials, fake numbers, or fake logos.
- Flag missing proof assets explicitly.
- Keep claims compliant and defensible.
- If brand voice is provided, adapt tone without losing clarity.
Quick trigger phrases
Use this skill when user says things like:
- “Build my landing page structure”
- “Fix this landing page conversion”
- “Rewrite this hero/value stack/social proof section”
- “Audit this page and tell me what copy goes where”