Web Page Copy
Write conversion-focused copy for landing pages and marketing sites. Output ready-to-paste text matched to the product and audience.
Before writing
Gather or infer:
- Product/service — what it does in one sentence
- Audience — who buys or uses it
- Differentiator — why them vs alternatives
- Primary action — call, WhatsApp, signup, quote
- Language — Spanish (CL/LATAM), English, or both
- Tone — professional, friendly, urgent, premium (match brand if known)
If missing, ask 1–2 quick questions max, then draft.
Page structure (default)
Deliver sections in this order unless the user specifies otherwise:
## Meta
- title: (≤60 chars, primary keyword + brand)
- description: (≤155 chars, benefit + CTA hint)
## Hero
- eyebrow: (optional, 3–6 words)
- headline: (6–12 words, outcome-focused)
- subheadline: (1–2 sentences, clarify who it's for)
- primary CTA: (verb + benefit, e.g. "Cotiza por WhatsApp")
- secondary CTA: (optional, lower commitment)
## Social proof (optional)
- stat or rating line
- 1 short testimonial hook
## Benefits / Servicios
- 3–4 cards: title (3–5 words) + body (2–3 sentences, concrete)
## How it works (optional)
- 3–4 numbered steps, each ≤1 sentence
## FAQ (optional)
- 3–5 Q&A pairs, objections and logistics
## Final CTA
- headline + button label + reassurance line (e.g. "Respuesta en minutos")
Copy rules
- Lead with outcomes, not features ("Tus paquetes llegan a tiempo" not "Tenemos flota propia")
- Specific beats vague — numbers, places, timeframes when true
- One idea per sentence — scannable on mobile
- CTAs use verbs — Cotiza, Escribe, Reserva, Llama (not "Submit" or "Click here")
- No filler — cut "soluciones integrales", "de vanguardia", "apasionados por"
- No false claims — don't invent stats, certifications, or reviews
- Match existing brand — if the project has copy on site, mirror voice and terms
Headline patterns (pick one fit)
- Outcome:
[Resultado] para [audiencia]
- Problem → solution:
¿[Problema]? [Marca] [solución].
- Trust:
[Años/clientes/zona] + [servicio confiable]
Spanish (Chile/LATAM)
- Use tú or usted consistently (default tú for SMB/consumer unless B2B formal)
- Local terms when natural (flete, mudanza, región, despacho)
- Avoid Spain-only slang unless audience is Spain
Output format
Return copy in markdown with clear section headers. If implementing in code, note which file/section each block maps to when the user provides context.
With design skills
When also building UI, pair with @frontend-design for layout and @theme-factory for color/font themes — copy first, then implement.
1---2name: web-page-copy3description: Write landing page and marketing web copy — hero, benefits, CTAs, FAQ, meta tags, and section structure. Use when the user asks for website copy, landing text, headlines, value proposition, or Spanish/English marketing content for a web page.4license: MIT5---67# Web Page Copy89Write conversion-focused copy for landing pages and marketing sites. Output ready-to-paste text matched to the product and audience.1011## Before writing1213Gather or infer:14151. **Product/service** — what it does in one sentence162. **Audience** — who buys or uses it173. **Differentiator** — why them vs alternatives184. **Primary action** — call, WhatsApp, signup, quote195. **Language** — Spanish (CL/LATAM), English, or both206. **Tone** — professional, friendly, urgent, premium (match brand if known)2122If missing, ask 1–2 quick questions max, then draft.2324## Page structure (default)2526Deliver sections in this order unless the user specifies otherwise:2728```markdown29## Meta30- title: (≤60 chars, primary keyword + brand)31- description: (≤155 chars, benefit + CTA hint)3233## Hero34- eyebrow: (optional, 3–6 words)35- headline: (6–12 words, outcome-focused)36- subheadline: (1–2 sentences, clarify who it's for)37- primary CTA: (verb + benefit, e.g. "Cotiza por WhatsApp")38- secondary CTA: (optional, lower commitment)3940## Social proof (optional)41- stat or rating line42- 1 short testimonial hook4344## Benefits / Servicios45- 3–4 cards: title (3–5 words) + body (2–3 sentences, concrete)4647## How it works (optional)48- 3–4 numbered steps, each ≤1 sentence4950## FAQ (optional)51- 3–5 Q&A pairs, objections and logistics5253## Final CTA54- headline + button label + reassurance line (e.g. "Respuesta en minutos")55```5657## Copy rules5859- **Lead with outcomes**, not features ("Tus paquetes llegan a tiempo" not "Tenemos flota propia")60- **Specific beats vague** — numbers, places, timeframes when true61- **One idea per sentence** — scannable on mobile62- **CTAs use verbs** — Cotiza, Escribe, Reserva, Llama (not "Submit" or "Click here")63- **No filler** — cut "soluciones integrales", "de vanguardia", "apasionados por"64- **No false claims** — don't invent stats, certifications, or reviews65- **Match existing brand** — if the project has copy on site, mirror voice and terms6667## Headline patterns (pick one fit)6869- Outcome: `[Resultado] para [audiencia]`70- Problem → solution: `¿[Problema]? [Marca] [solución].`71- Trust: `[Años/clientes/zona] + [servicio confiable]`7273## Spanish (Chile/LATAM)7475- Use **tú** or **usted** consistently (default tú for SMB/consumer unless B2B formal)76- Local terms when natural (flete, mudanza, región, despacho)77- Avoid Spain-only slang unless audience is Spain7879## Output format8081Return copy in markdown with clear section headers. If implementing in code, note which file/section each block maps to when the user provides context.8283## With design skills8485When also building UI, pair with `@frontend-design` for layout and `@theme-factory` for color/font themes — copy first, then implement.