--- name: landing-page-6ad9965bc6b8 description: Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls. --- # Landing Page (High‑Conversion) — Web Design Skill A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: **one offer → one audience → one primary action**. ## Before you design/write Gather (ask if missing): ### 1) Page purpose - What is the ONE primary action? (trial, demo, buy, waitlist, download) - What’s the offer? (exactly what do they get?) - What counts as conversion? (click, signup, purchase) ### 2) Audience + context - Who is the ICP? - What problem are they trying to solve? - Top 3 objections (why they don’t convert today) - Traffic source: ads / search / social / email - What do visitors already know when they land? ### 3) Proof + assets - Any proof points: logos, testimonials, numbers, case studies - Screenshots, demo video, product GIFs - Guarantees / refund / cancellation terms ### 4) Constraints - Brand voice: casual vs professional - Design direction: minimal editorial vs playful 3D vs glass UI - Mobile priority? --- ## Core structure (what it should include) ### Above the fold (must) 1) **Headline** (outcome + audience) 2) **Subheadline** (clarifies “how” + adds specificity) 3) **Primary CTA** (clear verb + what they get) 4) **One proof signal** (logo strip / stat / short testimonial) 5) **Hero visual** (product screenshot/video) *or* a strong illustration ### Mid page (argument) 6) **Problem → solution** (1 section) 7) **Benefits** (3–5, outcome-driven) 8) **How it works** (3 steps) 9) **Social proof** (testimonials/case study) ### Bottom (objection handling) 10) **FAQ** (6–12 Q/A) 11) **Risk reversal** (trial, cancel anytime, guarantee) 12) **Final CTA** (same as top) --- ## Layout types (pick one) ### A) Classic hero + sections (most common) Best when: - product is understandable with a hero screenshot ### B) Long-form story (sales page) Best when: - you need to educate + overcome skepticism ### C) Minimal conversion page Best when: - high-intent traffic (email → known users) - short offer (download, waitlist) ### D) Comparison landing page Best when: - search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages --- ## High‑conversion strategies (practical) ### 1) Match message to source If traffic is from ads: - mirror the ad headline in the hero - use the same promise and visual tone ### 2) Make the next step obvious - one primary CTA - avoid multiple competing CTAs above the fold ### 3) Write benefit-first - Features: what it does - Benefits: what that means for them ### 4) Use specificity - ❌ “Save time and streamline” - ✅ “Cut your weekly reporting from 4 hours to 15 minutes” ### 5) Reduce risk Pick at least one: - free trial - free plan - no credit card - cancel anytime - money-back guarantee ### 6) Objection handling is a section, not a footer - add FAQ earlier if it’s a high-friction offer - put proof right next to the claim it supports --- ## Copywriting templates ### Headline formulas - “{Outcome} without {pain}” - “The {category} for {audience}” - “Ship {result} in {time}” ### Subheadline rules - 1–2 sentences - clarify what it is + who it’s for ### CTA rules - Verb + what they get - Avoid weak CTAs: “Learn more”, “Submit” Examples: - “Start free trial” - “Book a demo” - “Get the checklist” ### Benefit bullets Format: - **Benefit** — proof/detail Example: - **Faster iteration** — generate 3 layout variants in one click. --- ## Section-by-section workflow (designer-friendly) Work in this order: 1) Hero 2) Benefits 3) How it works 4) Proof 5) FAQ 6) Final CTA Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control. --- ## SEO + AEO checklist (when relevant) ### When landing pages should NOT be indexed - ad-only campaigns - highly time-bound offers Use: - `noindex` (or keep it behind a non-indexed path) ### When they SHOULD be indexed - evergreen offers - search intent matches the promise Add: - clear title + meta - internal links from homepage/feature pages - FAQ in plain Q/A for AEO Optional: - FAQ schema (if appropriate) --- ## Common pitfalls - Too many CTAs above the fold - Vague value prop (“streamline”, “optimize”) - Big feature list with no outcomes - Proof hidden at the bottom - Mobile layout breaks readability - No clear next step --- ## Output format (when generating a landing page) Return: 1) **Page outline** (sections + order) 2) **Hero copy** (headline, subheadline, CTA, proof line) 3) **Benefits section** (3–5 bullets) 4) **How it works** (3 steps) 5) **FAQ** (6–12 Q/A) 6) **SEO/AEO** (indexing recommendation + title/meta if indexed) 7) **Layout recommendation** (A/B/C/D + why) --- ## Quick questions (if user says “make a landing page”) - What’s the ONE primary CTA? - Who is the ICP and what’s the main pain? - Any proof (numbers/testimonials/logos)? - What’s the offer and risk reversal? - Where is traffic coming from? --- Source attribution: MengTo Original project: https://github.com/MengTo/Skills License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Gabriel Moreira Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: MengTo Original project: https://github.com/MengTo/Skills Attribution basis: Upstream repository explicitly recorded in package mirror path Fields of work: Design, Marketing Roles: Content Marketer, Growth Marketer, Product Marketer, SEO Specialist, UX Designer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 02de143d7ccf7e905d96f115246de8038c7a662ce60420e18161e7fba401d01f