Automated ingestion of prompt: Landing Page Copy Architect – Conversion Framework Prompt
This commit is contained in:
parent
b3a2277c2e
commit
11bb58355a
|
|
@ -0,0 +1,168 @@
|
|||
---
|
||||
title: "Landing Page Copy Architect – Conversion Framework Prompt"
|
||||
contributor: "@debashis.sarker@gmail.com"
|
||||
tags: #general, #debashissarkergmailcom
|
||||
---
|
||||
|
||||
Landing Page Copy Architect – Conversion Framework Prompt
|
||||
|
||||
**Role & Goal**
|
||||
You are a senior conversion copywriter and CRO strategist. Design **one high-converting landing page copy framework** (not final copy) for a specific offer. The output must be a reusable blueprint that another AI (Claude, bolt.new, Lovable, ChatGPT, etc.) can use to generate full landing page copy.
|
||||
|
||||
---
|
||||
|
||||
### 1. Fill in the Offer Details (before running)
|
||||
|
||||
* **Offer Type:** [LEAD MAGNET / PRODUCT / WEBINAR / FREE TRIAL / OTHER]
|
||||
* **Offer Name:** [OFFER_NAME]
|
||||
* **Target Audience:** [WHO THEY ARE, SEGMENT, TOP PAINS & DESIRES]
|
||||
* **Target Conversion:** [CURRENT % → GOAL %]
|
||||
* **Page Length:** [SHORT / MEDIUM / LONG]
|
||||
* **Traffic Temperature:** [COLD / WARM / HOT]
|
||||
* **Unique Mechanism / Key Differentiator:** [1–3 SHORT LINES EXPLAINING “WHAT MAKES THIS DIFFERENT”]
|
||||
* **Main Objections (3–5):** [PRICE / TRUST / TIME / COMPLEXITY / ETC.]
|
||||
* **Social Proof Available:** [TESTIMONIALS / REVIEWS / CASE STUDIES / STATS / NONE]
|
||||
* **Brand Voice:** [E.G., BOLD / PLAYFUL / FORMAL / EMPATHETIC]
|
||||
|
||||
Use these details in every part of your answer.
|
||||
|
||||
---
|
||||
|
||||
### 2. Page Strategy Snapshot (≤ 200 words)
|
||||
|
||||
Briefly explain:
|
||||
|
||||
* Who this page is for
|
||||
* What the primary conversion goal is
|
||||
* The **big idea** behind the offer
|
||||
* How the **unique mechanism** changes the usual approach
|
||||
* Recommended page length and section emphasis for this **traffic temperature**
|
||||
|
||||
---
|
||||
|
||||
### 3. Page Structure & Sections
|
||||
|
||||
Create a **scroll-order outline** of the page as a table or numbered list. For each section, include:
|
||||
|
||||
* **Section Name** (e.g., Hero, Problem, Solution, Social Proof, Offer, FAQ, Final CTA)
|
||||
* **Primary Goal** of the section
|
||||
* **Recommended Length:** [VERY SHORT / SHORT / MEDIUM / LONG]
|
||||
* **Emotional State** we want the reader in by the end of the section
|
||||
* **Best Content Type:** [HEADLINE / BULLETS / STORY / TESTIMONIAL / COMPARISON TABLE / FAQ / ETC.]
|
||||
|
||||
---
|
||||
|
||||
### 4. Headline Formula Bank (10 Variations)
|
||||
|
||||
Create **10 headline formulas** tailored to this:
|
||||
|
||||
* Offer Type
|
||||
* Traffic Temperature
|
||||
* Unique Mechanism / Key Differentiator
|
||||
|
||||
For each formula:
|
||||
|
||||
1. Show a **pattern with placeholders in ALL CAPS**, e.g.
|
||||
|
||||
* `Get [RESULT] In [TIMEFRAME] Without [HATED_ACTION]`
|
||||
2. Provide **1 worked example** customized to this offer, audience, and mechanism.
|
||||
|
||||
---
|
||||
|
||||
### 5. Section-by-Section AI Prompts
|
||||
|
||||
For **each section** in the page structure, create a Claude/bolt.new/Lovable-compatible prompt that another AI can paste in to generate copy.
|
||||
|
||||
For every section prompt:
|
||||
|
||||
* Start with the label:
|
||||
`SECTION PROMPT: [SECTION NAME]`
|
||||
* Include:
|
||||
|
||||
* Section purpose
|
||||
* Desired tone & length
|
||||
* Quick reminder of offer, audience, traffic temperature, and unique mechanism
|
||||
* Instructions to generate **2–3 variations** of that section
|
||||
* Keep each prompt in **one copy-pasteable block**.
|
||||
|
||||
---
|
||||
|
||||
### 6. Benefit vs Feature Converter
|
||||
|
||||
Create a simple **conversion tool**:
|
||||
|
||||
1. A **2-column list**:
|
||||
|
||||
* Column 1: **Feature** (e.g., “8-week live cohort,” “lifetime access”)
|
||||
* Column 2: **Benefit phrased in outcome language** with “so you can…” or similar.
|
||||
2. A **mini rulebook** with **5–7 rules** explaining how to turn features into strong benefits.
|
||||
3. **3 examples** of copy rewritten from feature-heavy → benefit-driven.
|
||||
|
||||
---
|
||||
|
||||
### 7. Objection Handling Plan
|
||||
|
||||
Using the “Main Objections” provided, build an **objection handling map**:
|
||||
|
||||
* List the **top 5 objections** (if fewer provided, infer likely ones from offer type & traffic temperature).
|
||||
* For each objection, specify:
|
||||
|
||||
* **Where** on the page to address it (e.g., hero subhead, pricing area, FAQ, near CTA, testimonial block).
|
||||
* **In what format:** microcopy, FAQ item, guarantee block, testimonial, comparison table, etc.
|
||||
* Provide **3 short plug-and-play templates** for objection handling, with placeholders in ALL CAPS, e.g.:
|
||||
|
||||
* `Worried about [OBJECTION]? Here’s how [UNIQUE_MECHANISM] removes [RISK].`
|
||||
|
||||
---
|
||||
|
||||
### 8. CTA Optimization Strategy
|
||||
|
||||
Design a **CTA strategy** that fits this offer and traffic temperature:
|
||||
|
||||
* Identify **3–5 key CTA locations** on the page (hero, mid-page, after social proof, near FAQ, final section).
|
||||
* For each location, provide:
|
||||
|
||||
* A **CTA button copy formula** with placeholders (e.g., `Get [RESULT] In [TIMEFRAME]`)
|
||||
* Suggested **supporting microcopy** (e.g., risk reversal, urgency, reassurance, key benefit reminder).
|
||||
* Give **5 best-practice rules** for CTAs on this type of offer & traffic temperature (e.g., clarity > cleverness, friction-reducing language, etc.).
|
||||
|
||||
---
|
||||
|
||||
### 9. Trust Element Integration
|
||||
|
||||
Create a **trust building plan**:
|
||||
|
||||
* Recommend **which trust elements** to use based on the available social proof:
|
||||
|
||||
* Testimonials, star ratings, logos, mini case studies, guarantees, badges, media mentions, etc.
|
||||
* For each major section, specify:
|
||||
|
||||
* Which trust element fits best
|
||||
* **Why** it belongs there (what doubt or belief it supports).
|
||||
* If social proof is weak or missing, suggest **alternatives** such as:
|
||||
|
||||
* Process transparency
|
||||
* “Why we built this” story
|
||||
* Data, logic, or small commitments to reduce risk.
|
||||
|
||||
---
|
||||
|
||||
### 10. Output & Formatting Requirements
|
||||
|
||||
* Use **clear headings** and **bullet points**.
|
||||
* Start with a **numbered overview** of all parts, then expand each.
|
||||
* Do **not** write the actual final landing page copy. Only provide:
|
||||
|
||||
* Frameworks
|
||||
* Formulas
|
||||
* Tables/lists
|
||||
* Ready-to-use prompts
|
||||
* Use placeholders in **ALL CAPS** (e.g., [AUDIENCE], [RESULT], [TIMEFRAME], [OBJECTION]).
|
||||
* Aim to keep the full response under **~1,800–2,200 words**.
|
||||
|
||||
End with this line, customized:
|
||||
|
||||
> **If visitors remember only one thing from this landing page, it should be: “[ONE CORE PROMISE].”**
|
||||
|
||||
---
|
||||
|
||||
Loading…
Reference in New Issue