Website Copywriting
Overview
Use this skill to write or critique persuasive website copy that converts without becoming vague, manipulative, or trust-damaging.
Core thesis:
Good website copy meets the reader at their current awareness level, channels an existing desire/anxiety, makes one credible promise, proves it, resolves objections, and asks for the smallest honest next action.
This skill is grounded in old-school persuasion/copywriting principles from Cialdini, Hopkins, Ogilvy, and Schwartz, translated for modern websites.
Use When
- Writing website copy from scratch.
- Rewriting homepage hero, landing page, product page, pricing page, comparison page, FAQ, form, onboarding, upgrade, or CTA copy.
- Reviewing existing copy for conversion quality.
- Turning product positioning into page-level copy.
- Making copy more specific, credible, emotionally sharp, persuasive, or action-oriented.
- Diagnosing why copy feels generic, weak, over-clever, janky, or untrustworthy.
Do Not Do
- Do not invent customers, metrics, testimonials, awards, credentials, guarantees, deadlines, or scarcity.
- Do not use fake urgency, fake social proof, guilt CTAs, or hidden pressure.
- Do not hide risk, pricing, commitment, cancellation, or material caveats.
- Do not output generic sludge: “unlock your potential,” “supercharge your workflow,” “all-in-one platform,” etc.
- Do not treat cleverness as a substitute for clarity.
- When critiquing, do not rewrite before naming the strategic issue.
Minimum Inputs
Minimum viable copy needs:
- Product/service: what is being sold or explained?
- Audience: who is the copy for?
- Surface: homepage hero, landing page, pricing, CTA, etc.
- Conversion job: what should the visitor do next?
- Proof: what evidence is available, or what proof is missing?
If inputs are missing, ask one concise question when it materially changes the copy. If the user wants speed, proceed with labeled assumptions and flag proof gaps.
Core Workflow
- Identify the surface. Homepage hero, landing page, pricing page, product page, comparison page, CTA, form, testimonial, FAQ, onboarding/upgrade prompt, empty/error state.
- Name the conversion job. Continue, sign up, book, buy, compare, trust, self-qualify, upgrade, recover, or learn.
- Diagnose awareness level. Most aware, product aware, solution aware, problem aware, or unaware.
- Extract desire and anxiety. What does the reader want? What blocks action?
- Choose one simple promise. The main believable outcome the page owns.
- Find the mechanism. Why can this product deliver differently or credibly?
- Stack proof. Social proof, authority, numbers, screenshots, demos, samples, case studies, guarantees, operational proof.
- Handle objections. Cost, time, trust, switching, complexity, fit, risk, privacy/security.
- Write the CTA. Action + value + expectation + risk reduction.
- Run trust checks. Truthful, non-manipulative, relationship-safe, no fake pressure.
Awareness Lead Map
| Awareness level |
What the visitor knows |
Lead with |
Avoid |
| Most aware |
Knows product and wants it |
Offer, price, bonus, deadline, CTA |
Long education before action |
| Product aware |
Knows product, not convinced |
Differentiation, proof, why now |
Category basics |
| Solution aware |
Knows category, not product |
Unique mechanism, criteria, proof |
Brand-first copy |
| Problem aware |
Feels pain, lacks solution |
Precise problem, stakes, diagnostic |
Product pitch too early |
| Unaware |
No problem frame yet |
Story, belief, surprising fact, identity/POV |
Direct sale as the main ask |
Rule: page length follows the awareness gap. Hot traffic needs less education; cold/problem-aware traffic needs more bridge, proof, and objection handling.
Page Playbooks
Homepage Hero
Job: make the right visitor understand, care, and continue.
Include:
- audience/problem signal;
- one simple promise;
- mechanism or proof cue;
- primary CTA;
- optional secondary CTA for colder visitors.
Avoid:
- hero copy that could fit 100 competitors;
- puns before clarity;
- multiple equal promises;
- unsupported “best/easiest/powerful” claims.
Landing Page
Job: carry one promise through proof, objections, and action.
Recommended structure:
- Lead matched to awareness.
- Promise and mechanism.
- Specific outcomes/benefits.
- Proof stack.
- Objection handling.
- Offer/CTA.
- FAQ/trust close.
Product Page
Job: connect capabilities to desired outcomes.
For each feature, write:
- what it does;
- why the user cares;
- proof/example/screenshot;
- what objection it reduces.
Pricing Page
Job: reduce anxiety and make plan choice safe.
Include:
- plan fit labels;
- value metric;
- what is included/excluded;
- cancellation/trial/guarantee clarity;
- FAQ for billing, implementation, support, security.
Comparison Page
Job: help the user choose confidently.
Use:
- honest criteria;
- tradeoffs;
- switching risk handling;
- peer proof;
- respectful competitor framing.
Do not write cheap-shot competitor copy unless the user explicitly wants an aggressive teardown and the claims are verifiable.
CTA / Form Copy
A CTA should answer:
- What happens when I click?
- What value do I get?
- How much commitment is involved?
- Why is this the right next step now?
Examples by awareness:
- Problem aware: “Run the free diagnosis.”
- Solution aware: “Compare the workflow.”
- Product aware: “Watch the 3-minute demo.”
- Most aware: “Start free,” “Book onboarding,” “Buy now.”
Proof Standards
Every major claim should have at least one of:
- specific number/result;
- named mechanism;
- customer/example;
- screenshot/demo/sample;
- expert/authority credential;
- operational proof: security, uptime, support, migration, refund/cancellation;
- transparent limitation or tradeoff.
If proof is missing, write with honest caveats or mark [proof needed]. Never invent proof.
Cialdini Persuasion Checks
Use only principles that naturally exist in the situation.
| Principle |
Ethical website use |
Bad use |
| Reciprocity |
Useful free diagnostic, sample, checklist, demo |
Bait/guilt funnel |
| Liking |
Audience-fit language, warmth, cooperation |
Fake chumminess |
| Social proof |
Relevant testimonials, peer usage, case studies |
Fake counters, vague logo soup |
| Authority |
Credentials, methodology, expert review |
Borrowed-authority theatre |
| Scarcity |
Real capacity/deadline/opportunity cost |
Fake countdowns |
| Consistency |
User-owned self-selection, quizzes, plan choice |
Commitment traps |
| Unity |
True shared values/identity |
Identity cosplay |
Trust floor: be truthful, forgo manipulation, preserve the relationship, and inform people into agreement.
Copy Review Scorecard
When reviewing copy, score or comment on:
- Clarity: can the right visitor understand it quickly?
- Awareness fit: does it meet the reader’s stage?
- Promise strength: is there one main believable outcome?
- Specificity: are claims concrete?
- Mechanism: is there a credible “why/how”?
- Proof: are claims supported near where they appear?
- Objections: are reasonable blockers handled?
- CTA: is the next step clear and appropriately low-risk?
- Trust: any fake pressure, hidden caveat, or manipulation?
- Voice: does the tone fit the buyer and product?
Always name the main leak before rewriting: wrong awareness, weak promise, missing proof, vague mechanism, CTA mismatch, trust problem, or janky voice.
Anti-Patterns to Kill
- Vague benefit soup.
- Unsupported superlatives.
- Feature dumping.
- Fake urgency.
- Empty social proof.
- AI pixie dust.
- Over-clever headlines.
- Pain-only/shame copy.
- Pretty design hiding weak argument.
- One-size-fits-all copy despite known traffic/audience.
Output Formats
Fast rewrite
**Strategic read:** [main issue]
**Rewrite:**
Headline: ...
Subhead: ...
CTA: ...
Proof cue: ...
**Why this works:** ...
**Proof needed:** ...
Copy critique
## Copy diagnosis
| Area | Verdict | Notes |
|---|---|---|
| Awareness fit | ... | ... |
| Promise | ... | ... |
| Proof | ... | ... |
| CTA | ... | ... |
| Trust | ... | ... |
**Main leak:** ...
**Highest-leverage fix:** ...
Page brief
Audience:
Awareness level:
Conversion job:
Primary desire:
Primary anxiety:
One promise:
Mechanism:
Proof available:
Objections:
CTA:
Trust constraints:
Verification Checklist
Before finalizing website copy:
1---2name: website-copywriting3description: Use when writing, rewriting, or critiquing website copy for homepages, landing pages, pricing pages, CTAs, product pages, and conversion flows. Produces persuasive, specific, proof-backed copy without fake urgency or trust-damaging pressure.4license: MIT5---67# Website Copywriting89## Overview1011Use this skill to write or critique persuasive website copy that converts without becoming vague, manipulative, or trust-damaging.1213Core thesis:1415> Good website copy meets the reader at their current awareness level, channels an existing desire/anxiety, makes one credible promise, proves it, resolves objections, and asks for the smallest honest next action.1617This skill is grounded in old-school persuasion/copywriting principles from Cialdini, Hopkins, Ogilvy, and Schwartz, translated for modern websites.1819## Use When2021- Writing website copy from scratch.22- Rewriting homepage hero, landing page, product page, pricing page, comparison page, FAQ, form, onboarding, upgrade, or CTA copy.23- Reviewing existing copy for conversion quality.24- Turning product positioning into page-level copy.25- Making copy more specific, credible, emotionally sharp, persuasive, or action-oriented.26- Diagnosing why copy feels generic, weak, over-clever, janky, or untrustworthy.2728## Do Not Do2930- Do not invent customers, metrics, testimonials, awards, credentials, guarantees, deadlines, or scarcity.31- Do not use fake urgency, fake social proof, guilt CTAs, or hidden pressure.32- Do not hide risk, pricing, commitment, cancellation, or material caveats.33- Do not output generic sludge: “unlock your potential,” “supercharge your workflow,” “all-in-one platform,” etc.34- Do not treat cleverness as a substitute for clarity.35- When critiquing, do not rewrite before naming the strategic issue.3637## Minimum Inputs3839Minimum viable copy needs:40411. **Product/service:** what is being sold or explained?422. **Audience:** who is the copy for?433. **Surface:** homepage hero, landing page, pricing, CTA, etc.444. **Conversion job:** what should the visitor do next?455. **Proof:** what evidence is available, or what proof is missing?4647If inputs are missing, ask one concise question when it materially changes the copy. If the user wants speed, proceed with labeled assumptions and flag proof gaps.4849## Core Workflow50511. **Identify the surface.** Homepage hero, landing page, pricing page, product page, comparison page, CTA, form, testimonial, FAQ, onboarding/upgrade prompt, empty/error state.522. **Name the conversion job.** Continue, sign up, book, buy, compare, trust, self-qualify, upgrade, recover, or learn.533. **Diagnose awareness level.** Most aware, product aware, solution aware, problem aware, or unaware.544. **Extract desire and anxiety.** What does the reader want? What blocks action?555. **Choose one simple promise.** The main believable outcome the page owns.566. **Find the mechanism.** Why can this product deliver differently or credibly?577. **Stack proof.** Social proof, authority, numbers, screenshots, demos, samples, case studies, guarantees, operational proof.588. **Handle objections.** Cost, time, trust, switching, complexity, fit, risk, privacy/security.599. **Write the CTA.** Action + value + expectation + risk reduction.6010. **Run trust checks.** Truthful, non-manipulative, relationship-safe, no fake pressure.6162## Awareness Lead Map6364| Awareness level | What the visitor knows | Lead with | Avoid |65|---|---|---|---|66| Most aware | Knows product and wants it | Offer, price, bonus, deadline, CTA | Long education before action |67| Product aware | Knows product, not convinced | Differentiation, proof, why now | Category basics |68| Solution aware | Knows category, not product | Unique mechanism, criteria, proof | Brand-first copy |69| Problem aware | Feels pain, lacks solution | Precise problem, stakes, diagnostic | Product pitch too early |70| Unaware | No problem frame yet | Story, belief, surprising fact, identity/POV | Direct sale as the main ask |7172Rule: page length follows the awareness gap. Hot traffic needs less education; cold/problem-aware traffic needs more bridge, proof, and objection handling.7374## Page Playbooks7576### Homepage Hero7778Job: make the right visitor understand, care, and continue.7980Include:8182- audience/problem signal;83- one simple promise;84- mechanism or proof cue;85- primary CTA;86- optional secondary CTA for colder visitors.8788Avoid:8990- hero copy that could fit 100 competitors;91- puns before clarity;92- multiple equal promises;93- unsupported “best/easiest/powerful” claims.9495### Landing Page9697Job: carry one promise through proof, objections, and action.9899Recommended structure:1001011. Lead matched to awareness.1022. Promise and mechanism.1033. Specific outcomes/benefits.1044. Proof stack.1055. Objection handling.1066. Offer/CTA.1077. FAQ/trust close.108109### Product Page110111Job: connect capabilities to desired outcomes.112113For each feature, write:114115- what it does;116- why the user cares;117- proof/example/screenshot;118- what objection it reduces.119120### Pricing Page121122Job: reduce anxiety and make plan choice safe.123124Include:125126- plan fit labels;127- value metric;128- what is included/excluded;129- cancellation/trial/guarantee clarity;130- FAQ for billing, implementation, support, security.131132### Comparison Page133134Job: help the user choose confidently.135136Use:137138- honest criteria;139- tradeoffs;140- switching risk handling;141- peer proof;142- respectful competitor framing.143144Do not write cheap-shot competitor copy unless the user explicitly wants an aggressive teardown and the claims are verifiable.145146### CTA / Form Copy147148A CTA should answer:149150- What happens when I click?151- What value do I get?152- How much commitment is involved?153- Why is this the right next step now?154155Examples by awareness:156157- Problem aware: “Run the free diagnosis.”158- Solution aware: “Compare the workflow.”159- Product aware: “Watch the 3-minute demo.”160- Most aware: “Start free,” “Book onboarding,” “Buy now.”161162## Proof Standards163164Every major claim should have at least one of:165166- specific number/result;167- named mechanism;168- customer/example;169- screenshot/demo/sample;170- expert/authority credential;171- operational proof: security, uptime, support, migration, refund/cancellation;172- transparent limitation or tradeoff.173174If proof is missing, write with honest caveats or mark `[proof needed]`. Never invent proof.175176## Cialdini Persuasion Checks177178Use only principles that naturally exist in the situation.179180| Principle | Ethical website use | Bad use |181|---|---|---|182| Reciprocity | Useful free diagnostic, sample, checklist, demo | Bait/guilt funnel |183| Liking | Audience-fit language, warmth, cooperation | Fake chumminess |184| Social proof | Relevant testimonials, peer usage, case studies | Fake counters, vague logo soup |185| Authority | Credentials, methodology, expert review | Borrowed-authority theatre |186| Scarcity | Real capacity/deadline/opportunity cost | Fake countdowns |187| Consistency | User-owned self-selection, quizzes, plan choice | Commitment traps |188| Unity | True shared values/identity | Identity cosplay |189190Trust floor: be truthful, forgo manipulation, preserve the relationship, and inform people into agreement.191192## Copy Review Scorecard193194When reviewing copy, score or comment on:1951961. **Clarity:** can the right visitor understand it quickly?1972. **Awareness fit:** does it meet the reader’s stage?1983. **Promise strength:** is there one main believable outcome?1994. **Specificity:** are claims concrete?2005. **Mechanism:** is there a credible “why/how”?2016. **Proof:** are claims supported near where they appear?2027. **Objections:** are reasonable blockers handled?2038. **CTA:** is the next step clear and appropriately low-risk?2049. **Trust:** any fake pressure, hidden caveat, or manipulation?20510. **Voice:** does the tone fit the buyer and product?206207Always name the main leak before rewriting: wrong awareness, weak promise, missing proof, vague mechanism, CTA mismatch, trust problem, or janky voice.208209## Anti-Patterns to Kill210211- Vague benefit soup.212- Unsupported superlatives.213- Feature dumping.214- Fake urgency.215- Empty social proof.216- AI pixie dust.217- Over-clever headlines.218- Pain-only/shame copy.219- Pretty design hiding weak argument.220- One-size-fits-all copy despite known traffic/audience.221222## Output Formats223224### Fast rewrite225226```markdown227**Strategic read:** [main issue]228229**Rewrite:**230Headline: ...231Subhead: ...232CTA: ...233Proof cue: ...234235**Why this works:** ...236**Proof needed:** ...237```238239### Copy critique240241```markdown242## Copy diagnosis243244| Area | Verdict | Notes |245|---|---|---|246| Awareness fit | ... | ... |247| Promise | ... | ... |248| Proof | ... | ... |249| CTA | ... | ... |250| Trust | ... | ... |251252**Main leak:** ...253**Highest-leverage fix:** ...254```255256### Page brief257258```markdown259Audience:260Awareness level:261Conversion job:262Primary desire:263Primary anxiety:264One promise:265Mechanism:266Proof available:267Objections:268CTA:269Trust constraints:270```271272## Verification Checklist273274Before finalizing website copy:275276- [ ] Surface and conversion job are clear.277- [ ] Awareness level is matched.278- [ ] One simple promise leads.279- [ ] Claims are specific or modest.280- [ ] Proof supports the promise.281- [ ] Objections are handled.282- [ ] CTA says what happens next.283- [ ] No fake proof, fake scarcity, or manipulative pressure.284- [ ] Voice fits the buyer/product.285- [ ] The copy would survive being read by a smart skeptical customer.