copywriting
When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
Copywriting
You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
Before Writing
Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Page Purpose
- What type of page? (homepage, landing page, pricing, feature, about)
- What is the ONE primary action you want visitors to take?
2. Audience
- Who is the ideal customer?
- What problem are they trying to solve?
- What objections or hesitations do they have?
- What language do they use to describe their problem?
3. Product/Offer
- What are you selling or offering?
- What makes it different from alternatives?
- What's the key transformation or outcome?
- Any proof points (numbers, testimonials, case studies)?
4. Context
- Where is traffic coming from? (ads, organic, email)
- What do visitors already know before arriving?
Copywriting Principles
Clarity Over Cleverness
If you have to choose between clear and creative, choose clear. Clarity also converts. Clearer positioning and copy is associated with +81% conversions, a 38% shorter sales cycle, 28% lower CAC, and 175% more referrals. When a reader has to decode your line, you've lost them.
For message-market fit tools (the "Now you can" test, the Human Action Model (discomfort → vision → path), the Perception Gap, and the clarity metrics): See references/copy-frameworks.md
Benefits Over Features
Features: What it does. Benefits: What that means for the customer.
Specificity Over Vagueness
- Vague: "Save time on your workflow"
- Specific: "Cut your weekly reporting from 4 hours to 15 minutes"
Customer Language Over Company Language
Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.
One Idea Per Section
Each section should advance one argument. Build a logical flow down the page.
Writing Style Rules
Core Principles
- Simple over complex: "Use" not "utilize," "help" not "facilitate"
- Specific over vague: Avoid "streamline," "optimize," "innovative"
- Active over passive: "We generate reports" not "Reports are generated"
- Confident over qualified: Remove "almost," "very," "really"
- Show over tell: Describe the outcome instead of using adverbs
- Honest over sensational: Fabricated statistics or testimonials erode trust and create legal liability
Quick Quality Check
- Any AI tells? (see No AI Tells below)
- Jargon that could confuse outsiders?
- Sentences trying to do too much?
- Passive voice constructions?
- Exclamation points? (remove them)
- Marketing buzzwords without substance?
For thorough line-by-line review, use the copy-editing skill after your draft.
No AI Tells
Clients and buyers reject copy that reads as AI-written, and a reader who spots a tell tends to doubt the claims around it. Write like a senior copywriter: specific, uneven in rhythm, and built from facts rather than formulas.
Never write these
- Contrast reveals. "It's not X, it's Y." "Not because X. Because Y." "Not just X, but Y." State Y directly, with the reason.
- Negation lists. "No setup call, no templates, no waiting on IT. No contract." Say what does happen. State a real absence once, near the CTA ("No card required"), and turn the others into what happens.
- Trailing pile-ons. A full claim followed by a comma and more clauses: "...the data you already have, no exports, no spreadsheets, no second copy." End the sentence at the claim.
- Self-answered questions and colon reveals. "The result? 3x faster." "The best part: it learns." Just say it. FAQ questions and a reader's own question ("Need to share a screenshot?") are fine.
- Stock openers and phrases. "In today's fast-paced world," "Whether you're X or Y," "Here's the thing," "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level."
- Em dashes in short copy. Headlines, subheads, ads, social posts, and subject lines use none.
Keep these rare
- At most one fragment and one list of three per section (a hero, a page section, or one short post). CTA microcopy and a real three-feature list are fine.
- Words like seamless, robust, powerful, unlock, and streamline: replace them with the fact they stand in for.
- Swap test: if a line would work unchanged on a competitor's site, rewrite it. If you lack the differentiator to fix it, flag
[NEED: differentiator].
Check before delivering
Before handing over any draft, run the self-check in references/ai-tells.md: search for the banned patterns, read every sentence over 20 words, and read it aloud. Fix from the facts, since swapping synonyms creates new tells, and flag missing proof as [NEED: ...] rather than inventing it.
For the full blacklist with examples and rewrites: See references/ai-tells.md
Best Practices
Be Direct
Get to the point. Don't bury the value in qualifications.
❌ Slack lets you share files instantly, from documents to images, directly in your conversations
✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.
Use Rhetorical Questions
A question that names the reader's pain can open a section well.
- "Hate returning stuff to Amazon?"
- "Tired of chasing approvals?"
A question in the reader's voice followed by what to do is fine (see Be Direct). A question that labels your own claim ("The result? 3x faster.") is an AI tell.
Use Analogies When Helpful
Analogies make abstract concepts concrete and memorable.
Pepper in Humor (When Appropriate)
Puns and wit make copy memorable when they fit the brand and don't cost clarity.
Page Structure Framework
Above the Fold
Headline
- Your single most important message
- Communicate core value proposition
- Specific > generic
Example formulas:
- "{Achieve outcome} without {pain point}"
- "The {category} for {audience}"
- "Never {unpleasant event} again"
- "{Question highlighting main pain point}"
For comprehensive headline formulas: See references/copy-frameworks.md
Structure the hero as a transformation: current discomfort → better vision → path to action (the Human Action Model), then run every headline through the "Now you can" test. See references/copy-frameworks.md
For natural transition phrases: See references/natural-transitions.md
Subheadline
- Expands on headline
- Adds specificity
- 1-2 sentences max
Primary CTA
- Action-oriented button text
- Communicate what they get: "Start Free Trial" > "Sign Up"
Core Sections
| Section | Purpose |
|---|---|
| Social Proof | Build credibility (logos, stats, testimonials) |
| Problem/Pain | Show you understand their situation |
| Solution/Benefits | Connect to outcomes (3-5 key benefits) |
| How It Works | Reduce perceived complexity (3-4 steps) |
| Objection Handling | FAQ, comparisons, guarantees |
| Final CTA | Recap value, repeat CTA, risk reversal |
For detailed section types and page templates: See references/copy-frameworks.md
CTA Copy Guidelines
Weak CTAs (avoid):
- Submit, Sign Up, Learn More, Click Here, Get Started
Strong CTAs (use):
- Start Free Trial
- Get [Specific Thing]
- See [Product] in Action
- Create Your First [Thing]
- Download the Guide
Formula: [Action Verb] + [What They Get] + [Qualifier if needed]
Examples:
- "Start My Free Trial"
- "Get the Complete Checklist"
- "See Pricing for My Team"
Page-Specific Guidance
Homepage
- Serve multiple audiences without being generic
- Lead with broadest value proposition
- Provide clear paths for different visitor intents
Landing Page
- Single message, single CTA
- Match headline to ad/traffic source
- Complete argument on one page
Pricing Page
- Help visitors choose the right plan
- Address "which is right for me?" anxiety
- Make recommended plan obvious
Feature Page
- Connect feature → benefit → outcome
- Show use cases and examples
- Clear path to try or buy
About Page
- Tell the story of why you exist
- Connect mission to customer benefit
- Still include a CTA
Voice and Tone
Before writing, establish:
Formality level:
- Casual/conversational
- Professional but friendly
- Formal/enterprise
Brand personality:
- Playful or serious?
- Bold or understated?
- Technical or accessible?
Maintain consistency, but adjust intensity:
- Headlines can be bolder
- Body copy should be clearer
- CTAs should be action-oriented
Output Format
When writing copy, provide:
Page Copy
Organized by section:
- Headline, Subheadline, CTA
- Section headers and body copy
- Secondary CTAs
Annotations
For key elements, explain:
- Why you made this choice
- What principle it applies
Alternatives
For headlines and CTAs, provide 2-3 options:
- Option A: [copy]. Rationale: [why]
- Option B: [copy]. Rationale: [why]
Meta Content (if relevant)
- Page title (for SEO)
- Meta description
Related Skills
- copy-editing: For polishing existing copy (use after your draft)
- cro: If page structure/strategy needs work, not just copy
- emails: For email copywriting
- popups: For popup and modal copy
- ab-testing: To test copy variations
References
Ai Tells
ai-tells.md
AI Tells: The Copy Blacklist
Patterns that make marketing copy read as machine-written. Clients and buyers spot these fast, and a reader who decides a page was generated starts doubting its claims too.
Most of these are old human rhetoric. AI copy gives itself away by using them by default, stacked, and with nothing specific behind them. So the rules below are a mix of hard bans (for patterns that are tells even once) and frequency caps (for devices that are fine when chosen on purpose).
Confidence key
- Ban: a tell even once. Don't write it.
- Cap: fine once, a tell when repeated or stacked. Stay under the cap.
What the scopes mean
- Short copy: headlines, subheads, the hero, CTAs, ads, social posts, email subject lines.
- Long copy: body sections of a page, articles, long emails.
- Section: one hero, one page section, or one whole short post.
- CTA microcopy ("No card required") doesn't count toward the fragment cap.
Still fine: FAQ questions, a single "No card required," a list of three when there really are three features, a single "without" headline, and a formal brand voice that makes specific claims.
Contents
- Structural Patterns (the worst offenders)
- Openers, Closers, and Setups
- Marketing Phrases
- Vocabulary
- Hedges, Puffery, and Weasels
- Tone
- Formatting
- Rewrite Rules
- The Self-Check
- Sources
Structural Patterns
These matter more than any word list. A draft can avoid every banned word and still read as AI because of its shape.
1. The contrast reveal: "Not X. Y." (Ban)
Sets up an assumption nobody stated, denies it, then gives the "real" answer.
Variants: "It's not X, it's Y." "Not because X. Because Y." "This isn't X. This is Y." "Not just X, but Y." "Less X, more Y." "The question isn't X, it's Y." "X? Think again."
- ✗ Most marketing teams have a list of campaign ideas that never launch. Not because they're bad. Because each one needs a developer.
- ✓ Most marketing teams have a list of campaign ideas that never launch, because each one needs a developer they can't get.
Why it's a tell: It's one of the most frequently cited AI patterns. Wikipedia's AI-cleanup guide calls it "negative parallelism," and EQ-Bench's Slop Score gives "not X, but Y" patterns their own weighted category.
Rewrite: State Y directly and attach the concrete reason or cost. If the reader holds a wrong belief you need to correct, state the correct fact and the evidence; don't stage the denial.
2. The negation list: "No X, no Y, no Z." (Ban)
Defines the product by what's absent, usually in threes, often with a fragment tacked on.
Variants: "No X. No Y. Just Z." "Without X, without Y." "Zero X, zero Y."
- ✗ No setup call, no templates to fill in, no waiting on IT. No contract.
- ✓ Install it from the app store and it's running on your data in five minutes.
Rewrite: Say what does happen, in the order it happens. If an absence really is a selling point (no card required, no install), state it once, plainly, next to the CTA: "Free to start. No card required." A brief with several absences doesn't need a list: turn the rest into what happens ("no signup form" becomes "Log in with your Shopify account").
A single "without" or "Never X again" headline is fine. Don't follow it with a negation list in the subhead.
3. The trailing pile-on (Ban)
A complete claim, then a comma, then a run of add-ons: a negation list, an "-ing" clause, or a string of extra benefits.
- ✗ Reports pull directly from the data you already have, no exports, no spreadsheets, no second copy to keep updated.
- ✗ It syncs your calendar automatically, ensuring nothing slips through the cracks.
- ✓ Reports pull from the data you already have. There's nothing to export.
Rewrite: End the sentence when the main claim ends. If the benefit matters, give it its own short sentence with one concrete detail. Test: after the main clause is complete, cut anything past the next comma that doesn't add a new fact. A clause that adds one ("Imports run nightly, keeping your existing IDs") can stay; a string of restatements can't.
4. Rhetorical question, then answer (Ban)
"The result? 3x faster onboarding." "The catch? There isn't one." "Why does this matter? Because..."
- ✗ The result? Onboarding that takes minutes, not weeks.
- ✓ New hires finish onboarding on day one.
Rewrite: Delete the question and keep the answer.
Still fine: FAQ questions ("Does it work with Shopify?"), and a question in the reader's voice about their own need, followed by what to do ("Need to share a screenshot? Drop it in the thread."). The tell is a question that labels your own claim ("The result?" "The catch?" "Why does this matter?").
5. The colon reveal (Ban)
"The best part: it learns." "Here's the secret: consistency." "One word: speed."
Rewrite: Write it as a normal sentence ("It learns from every correction"). Save colons for lists, labels, and quotes.
6. Fragment drumbeat (Cap: one per section)
Stacked fragments or one-line paragraphs for manufactured punch. "Simple. Fast. Done." "That's it. That's the whole thing."
Rewrite: Merge them into one full sentence that carries a fact. One fragment that lands a real payoff is a copywriting device. A paragraph of them is a tic.
7. Reflexive threes (Cap: one per section)
Everything comes in threes: adjectives, benefits, clauses, bullets. "Fast, secure, and scalable." "Save time, cut costs, and grow revenue."
Rewrite: Use as many items as the facts support: one, two, or four. Usually the fix is the single strongest concrete claim: "Fast, secure, and scalable" → "Handles 40,000 webhooks a second on the free plan."
8. Em dashes (Ban in short copy; cap at 1–2 per page in long copy)
The dash as the default pause, several per paragraph, often carrying a contrast reveal ("It's not a tool — it's a teammate").
Rewrite: Use a period, a comma, a colon, or parentheses. In heroes, ads, subject lines, and social posts, use none.
9. Uniform rhythm (Cap)
Every sentence 12–18 words. Every paragraph is topic sentence → elaboration → wrap-up. Every section the same length. Three pros, three cons, every time.
Rewrite: Vary on purpose. A long sentence, then a short one. Let a section be two lines if that's all it needs. Put the payoff first sometimes.
10. Dodging "is" and "has" (Cap)
"Serves as a central hub." "Stands as a testament." "Boasts a library of 200 templates." "Represents a new approach."
Rewrite: Use "is" and "has", or better, the actual verb: "Tracks every contract, renewal date, and owner in one place."
11. Abstract subjects (Cap)
"The platform empowers teams to..." "Our solution enables..." Nobody does anything.
Rewrite: Make the customer the subject. "Your team ships experiments without filing a ticket."
12. False ranges (Cap)
"From startups to enterprises." "From onboarding to renewal." The two ends don't describe a real span.
Rewrite: Name the segment you actually serve, or the steps you actually cover.
13. Synonym cycling (Cap)
Calling the same thing a dashboard, an interface, a portal, and a hub in one page to avoid repeating a word.
Rewrite: Pick the word your customer uses and repeat it.
Openers, Closers, and Setups (Ban)
| Pattern | Example | Instead |
|---|---|---|
| Era opener | "In today's fast-paced world..." | Open with the customer's problem |
| False-choice opener | "Whether you're a solo founder or a Fortune 500..." | Name who the page is for |
| "Imagine..." | "Imagine never chasing an invoice again." | Show the actual before and after |
| "When it comes to..." | "When it comes to billing, ..." | Start with the subject |
| Throat-clearing | "Here's the thing:" "The truth is" "Let me be clear" "Here's what nobody tells you" | Cut it. If the claim can't stand alone, it needs evidence, not a drumroll |
| Announcing | "In this guide, we'll explore..." "Let's dive in" | Start with the content |
| Recap ending | "In conclusion" "Ultimately" "At the end of the day" | End on the last concrete point or the CTA |
| Fake-profound kicker | "Because growth shouldn't wait." "And that changes everything." | Cut it. End on a concrete sentence |
| Filler transitions | "It's worth noting" "Moreover" "Additionally" "Importantly" | Delete. The sentence usually works without it |
Marketing Phrases (Ban)
| Phrase | Instead |
|---|---|
| "Say goodbye to X" / "Say hello to Y" | Show the new workflow: "Reconciliation runs nightly. You review the exceptions." |
| "Unlock / unleash the power of X" | Name the outcome and the number |
| "X, reimagined" / "X, redefined" | Say what's actually different: "Billing that retries on payday" |
| "Take X to the next level" | Name the level: the metric and the target |
| "Transform the way you work" | A before and after with numbers |
| "The X you deserve" | The specific gap you close |
| "The future of X is here" | What ships today |
| "Built for teams who move fast" | The real customer and trigger: "For subscription teams past $1M ARR fighting failed payments" |
| "Everything you need to X" / "all-in-one" | The 2–3 things buyers actually check for |
| "Effortless" / "in just a few clicks" | The real step count or time: "3 steps, about 4 minutes" |
| "Join thousands of happy customers" | The real count, logos, or a named quote |
| "Game-changer" / "this changes everything" | What changes, for whom, by how much |
Vocabulary
Swapping a banned word for a synonym just creates a new tell. Replace the word with the fact it was standing in for: "robust" → "99.99% uptime over two years"; "seamless" → "imports your Stripe data in about 90 seconds."
Ban: delve, tapestry, testament to, realm, embark, beacon, multifaceted, paradigm, synergy, myriad, plethora, meticulous, intricate, utilize, leverage (as a verb), supercharge, turbocharge, game-changer, "ever-evolving landscape," "plays a crucial role"
Cap (two in a paragraph means rewrite it): seamless, robust, streamline, empower, elevate, unlock, unleash, harness, foster, enhance, optimize, cutting-edge, innovative, revolutionary, transformative, holistic, comprehensive, pivotal, crucial, vital, powerful, next-level, world-class, best-in-class, landscape, navigate, ecosystem, journey (unless literal)
Cap (empty intensifiers): truly, genuinely, incredibly, deeply, fundamentally, significantly, simply, actually, literally, quietly
Favored words drift as models change ("delve" peaked in 2024; "enhance," "showcase," "foster," and "align with" rose after). Treat the lists as current examples, and lean on the structural patterns and the tests below, which don't go stale.
Hedges, Puffery, and Weasels
- Hedge stacks (Cap): "can help you potentially reduce..." State what you know, or scope the claim honestly.
- Importance puffery (Ban): "marks a pivotal moment," "redefines the category." State the fact; let the reader judge.
- Weasel sources (Ban): "experts agree," "studies show," "trusted by industry leaders." Name the source or the customer, or cut it.
- Invented labels (Cap): "the integration tax," "the growth trap." Only coin a term you'll define and use across the site.
Tone
- Chummy openers (Ban in email and social): "Great question!" "Let's be honest..." "We get it."
- Fake vulnerability (Ban): "I'll be honest, I was skeptical too..." with no real story behind it.
- Over-explaining (Cap): "Let's break this down," "Think of it as..." Give the explanation directly.
- Hype punctuation (Ban): "Ready to level up?!" Exclamation points and interrobangs in body copy.
Formatting
- Emoji as structure (Ban in B2B): 🚀 ✨ ✅ leading bullets or headings.
- Bold label on every bullet (Cap): "Seamless integration: ..." Keep it for reference tables, not every list.
- Parallel bullet openers (Cap): every bullet starting "Ensures... / Provides... / Enables..." Start bullets with the customer outcome and vary the grammar.
- Title Case Everywhere (Cap): use sentence case unless the brand style guide says otherwise.
- Unicode decoration (Ban): arrows, ×, 𝗯𝗼𝗹𝗱 letters in body copy.
- Label headings (Cap): "What / Why / How" sections. Write headings that make a claim.
Rewrite Rules
- Rewrite from the facts. Go back to what's true (the mechanism, the number, the customer, the step) and write that. Synonym swaps and "humanizer" substitutions produce new tells.
- Specificity test. Every claim sentence needs a number, a name, a mechanism, or a concrete action.
- Swap test. If the line would work unchanged on a competitor's site, rewrite it.
- Stacking test. Two or more Cap patterns in one paragraph means rewrite the whole paragraph.
- Don't invent to de-slop. Replacing "industry-leading" with a made-up stat is worse. Mark it
[NEED: proof]and ask. - Choose devices on purpose. A fragment you picked once, for a reason, is copywriting. The same device on every line is slop.
- Keep the brand's register. A formal sentence that makes a specific claim is fine. Don't flatten an enterprise voice into clipped startup copy, which is its own tell.
- Vary the fixes. The ✓ examples show one way out. Don't reuse them as templates. If every reveal becomes ", because..." and every negation list becomes "There's nothing to X," those are the new tics.
- Flag a missing differentiator. If no headline can pass the swap test with what you have, write the best one and mark
[NEED: differentiator vs. named competitors].
The Self-Check
Run this on every draft before delivering it:
- Search for the bans. Look for "not ", "isn't", "no ", "without", "?", ":" and "—" in headlines, subheads, and short copy, and check each hit against patterns 1–5 and 8.
- Read every sentence over 20 words. If it has more than two commas, check for a trailing pile-on (pattern 3).
- Count the caps. Fragments, threes, and Cap vocabulary per section.
- Read it aloud. Mark anywhere you'd sound like a press release or a LinkedIn post.
- Apply the swap test to the headline, subhead, and every section heading.
If a fix needs information you don't have (a number, a customer, a mechanism), flag it rather than writing around it.
Sources
Patterns and evidence drawn from, and rewritten in our own words:
- Wikipedia, Signs of AI writing (WikiProject AI Cleanup)
- Kobak et al., excess vocabulary in 15M+ PubMed abstracts (arXiv 2406.07016)
- Juzek & Ward, Why Does ChatGPT "Delve" So Much? (COLING 2025)
- Paech et al., Antislop (arXiv 2510.15061) and EQ-Bench Slop Score
- tropes.fyi catalog of AI writing tropes
- Charlie Guo, The Field Guide to AI Slop
- Blake Stockton, Don't write like AI: negation
- Counter-view: A case for the defense (devices are fine when chosen, not defaulted)
For a broader word-level list used in content audits, see the seo-audit skill's references/ai-writing-detection.md.
Copy Frameworks
copy-frameworks.md
Copy Frameworks Reference
Headline formulas, page section types, and structural templates.
Contents
- Headline Formulas (outcome-focused, problem-focused, audience-focused, differentiation-focused, proof-focused, additional formulas)
- Landing Page Section Types (core sections, supporting sections)
- Page Structure Templates (feature-heavy page, varied engaging page, compact landing page, enterprise/B2B landing page, product launch page)
- Section Writing Tips (problem section, benefits section, how it works section, testimonial selection)
- Clarity & Message-Market Fit (the "Now you can" test, Human Action Model, the Perception Gap, the SavvyCal case, clarity metrics)
Headline Formulas
These are starting points. Fill every slot with specifics, and check the result against ai-tells.md: a "without" or "Never X again" headline is fine once, but don't follow it with a negation list.
Outcome-Focused
{Achieve desirable outcome} without {pain point} > Understand how users are really experiencing your site without drowning in numbers
{Achieve desirable outcome} by {how product makes it possible} > Generate more leads by seeing which companies visit your site
Turn {input} into {outcome} > Turn your hard-earned sales into repeat customers
[Achieve outcome] in [timeframe] > Get your tax refund in 10 days
Problem-Focused
Never {unpleasant event} again > Never miss a sales opportunity again
{Question highlighting the main pain point} > Hate returning stuff to Amazon?
Stop [pain]. Start [pleasure]. > Stop chasing invoices. Start getting paid on time.
Audience-Focused
{Key feature/product type} for {target audience} > Advanced analytics for Shopify e-commerce
{Key feature/product type} for {target audience} to {what it's used for} > An online whiteboard for teams to ideate and brainstorm together
You don't have to {skills or resources} to {achieve desirable outcome} > With Ahrefs, you don't have to be an SEO pro to rank higher and get more traffic
Differentiation-Focused
The {opposite of usual process} way to {achieve desirable outcome} > The easiest way to turn your passion into income
The [category] that [key differentiator] > The CRM that updates itself
Proof-Focused
[Number] [people] use [product] to [outcome] > 50,000 marketers use Drip to send better emails
{Key benefit of your product} > Sound clear in online meetings
Additional Formulas
The simple way to {outcome} > The simple way to track your time
Finally, {category} that {benefit} > Finally, accounting software that doesn't suck
{Outcome} without {common pain} > Build your website without writing code
Get {benefit} from your {thing} > Get more revenue from your existing traffic
{Action verb} your {thing} like {admirable example} > Market your SaaS like a Fortune 500
What if you could {desirable outcome}? > What if you could close deals 30% faster?
The {adjective} {category} built for {audience} > The lightweight CRM built for startups
Landing Page Section Types
Core Sections
Hero (Above the Fold)
- Headline + subheadline
- Primary CTA
- Supporting visual (product screenshot, hero image)
- Optional: Social proof bar
Social Proof Bar
- Customer logos (recognizable > many)
- Key metric ("10,000+ teams")
- Star rating with review count
- Short testimonial snippet
Problem/Pain Section
- Articulate their problem better than they can
- Create recognition ("that's exactly my situation")
- Hint at cost of not solving it
Solution/Benefits Section
- Bridge from problem to your solution
- 3-5 key benefits (not 10)
- Each: headline + explanation + proof if available
How It Works
- 3-4 numbered steps
- Reduces perceived complexity
- Each step: action + outcome
Final CTA Section
- Recap value proposition
- Repeat primary CTA
- Risk reversal (guarantee, free trial)
Supporting Sections
Testimonials
- Full quotes with names, roles, companies
- Photos when possible
- Specific results over vague praise
- Formats: quote cards, video, tweet embeds
Case Studies
- Problem → Solution → Results
- Specific metrics and outcomes
- Customer name and context
- Can be snippets with "Read more" links
Use Cases
- Different ways product is used
- Helps visitors self-identify
- "For marketers who need X" format
Personas / "Built For" Sections
- Explicitly call out target audience
- "Perfect for [role]" blocks
- Addresses "Is this for me?" question
FAQ Section
- Address common objections
- Good for SEO
- Reduces support burden
- 5-10 most common questions
Comparison Section
- vs. competitors (name them or don't)
- vs. status quo (spreadsheets, manual processes)
- Tables or side-by-side format
Integrations / Partners
- Logos of tools you connect with
- "Works with your stack" messaging
- Builds credibility
Founder Story / Manifesto
- Why you built this
- What you believe
- Emotional connection
- Differentiates from faceless competitors
Demo / Product Tour
- Interactive demos
- Video walkthroughs
- GIF previews
- Shows product in action
Pricing Preview
- Teaser even on non-pricing pages
- Starting price or "from $X/mo"
- Moves decision-makers forward
Guarantee / Risk Reversal
- Money-back guarantee
- Free trial terms
- "Cancel anytime"
- Reduces friction
Stats Section
- Key metrics that build credibility
- "10,000+ customers"
- "4.9/5 rating"
- "$2M saved for customers"