Landing Page Copywriting Prompts: Build a Section-by-Section Message Hierarchy

Quick answer

Useful landing page copywriting prompts do more than request a headline or “persuasive copy.” They tell the model what evidence exists, what the visitor saw before arriving, what each section must decide, and what the copy must not invent.

The goal is a message hierarchy: an ordered sequence of claims, evidence, objections, and actions. Build that hierarchy before polishing sentences.

Start With an Evidence Brief

Gather these inputs:

Set one strict rule: if the supplied sources do not support a detail, the model must insert `[EVIDENCE NEEDED]`. For claims that require current authoritative verification, use `[PRIMARY SOURCE NEEDED]`.

Apply this rule to statistics, testimonials, credentials, mechanisms, comparisons, prices, discounts, guarantees, deadlines, urgency, scarcity, and compliance language.

Use this extraction prompt:

> Review the source material below. Extract only explicitly supported information under these headings: audience, recognized problem, desired outcome, product, mechanism, benefits, offer terms, objections, proof, qualifications, prohibited claims, and missing evidence. Cite the supplied source behind each factual claim. Label uncertain interpretations as assumptions. Insert `[EVIDENCE NEEDED]` for unsupported details. Do not draft copy.

• Audience and traffic source
• Problem the audience recognizes
• Desired outcome
• Product and its mechanism—the documented explanation of how it is supposed to work
• Supported benefits
• Offer terms, including price and availability
• Common objections
• Available proof
• Material limitations or qualifications
• Prohibited or unverified claims
• The preceding ad, email, post, search result, or VSL

Preserve the Incoming Message

A landing page should continue or explicitly resolve the message that brought the visitor there. It should not attract visitors with one problem or promise and quietly replace it with another.

> Analyze the preceding `[AD / EMAIL / SEARCH RESULT / SOCIAL POST / VSL]`. Identify its audience, problem, promise, terminology, emotional frame, and expected next step. Create a table showing what the landing page should preserve, clarify, substantiate, qualify, or reject. Flag every carryover claim that lacks support.

If a video precedes the page, use a dedicated VSL copy research workflow to document its claims and framing first.

Find the Page’s Unifying Idea

In practitioner theory, a sales message can revolve around one idea connecting its opening, claims, benefits, product, and offer. **[1]**

Use that idea as a consistency check:

> Based only on the approved brief, write one sentence connecting the audience’s situation, desired change, and the product’s supported role. Map that sentence to the headline, problem, outcome, product explanation, benefits, proof, offer, objections, and CTA. Flag any section that introduces a competing promise.

This is not a complete method for developing a campaign concept. It is a way to keep one page from drifting among unrelated promises.

Choose an Opening as a Hypothesis

Audience knowledge and traffic context can inform how directly the page opens. A visitor who already understands the offer may suit a direct opening. A skeptical or less informed visitor may need more context. Treat either choice as a hypothesis, not a universal rule. **[2]**

> Using the incoming-message evidence, describe what the visitor probably knows before arriving. Draft one direct and one indirect opening from the same verified facts. For each version, state the assumed knowledge, required proof, relevance risk, and bridge to the product. Do not declare either version the winner.

Use Lead Categories as an Idea Menu

Offer, Promise, Problem-Solution, Big Secret, Proclamation, and Story are practitioner categories for openings. They can overlap and are not exhaustive. **[3]**

#### Offer or Promise

An Offer Lead can introduce the product, price, trial, premium, or guarantee early. Any term used must be verified. **[4]**

> Draft an Offer Lead using only `[PRODUCT]` and `[VERIFIED TERMS]`. Add a supported outcome and next step. Do not create a price, discount, bonus, guarantee, deadline, inventory limit, or availability claim.

> Draft a Promise Lead around `[SUPPORTED OUTCOME]`. Place each qualification beside the claim it limits. Insert `[EVIDENCE NEEDED]` where support is missing. Do not imply certainty.

#### Problem-Solution

Practitioner descriptions of a Problem-Solution Lead emphasize an important concern, recognition of that concern, and hope connected to a relevant solution. **[5]**

> Describe one documented moment when `[PROBLEM]` appears. Acknowledge it without diagnosing the reader, increasing fear, or inventing consequences. Introduce `[PRODUCT]` as an option using supported benefit language.

#### Big Secret

A Big Secret Lead creates curiosity around knowledge, a formula, a system, a hidden problem, or an undisclosed solution. **[6]**

> Identify one verified distinction the audience may not know. Explain why it matters and reveal it clearly. Connect it directly to the product. Do not imply suppression, conspiracy, a secret cure, or unsupported superiority.

#### Proclamation or Story

> Draft one concise assertion about `[SUBJECT]`. List every factual and implied claim within it. Label each `supported`, `unsupported`, `ambiguous`, or `[PRIMARY SOURCE NEEDED]`. Rewrite the assertion until no unsupported implication remains.

A Story Lead can use a concise narrative to create curiosity while carrying an embedded promise. **[7]**

> Using only verified events, write a short contrast between two relevant situations. Identify the embedded promise and bridge to the product in the next paragraph. Do not fabricate dialogue, customers, or results.

Indirect openings can become slow or disconnected. Require an explicit product bridge. **[8]**

Adapt Sampled Hook Patterns Carefully

The following observation comes from a stratified convenience sample of Daily Intel transcripts. It does not represent the wider market and provides no evidence about conversion performance.

One sampled execution opened by naming an exact daily frustration before introducing a product. **[9]**

> Open with one documented daily frustration in plain language. Connect it to the product’s supported role. Do not invent symptoms, fear, consequences, or a customer quotation.

Another observed pattern challenged a familiar explanation before offering a different frame. Some sampled executions used unsupported conspiratorial claims, so the safe adaptation is narrower. **[10]**

> Identify one audience assumption that the supplied evidence can genuinely qualify. Present the alternative explanation as a possibility, not a hidden truth. Do not attack institutions, claim suppression, or reduce a complex problem to one unverified cause.

These are editorial options derived from sampled observations. Their presence in the sample does not show that they caused any commercial result.

Message-Hierarchy Worksheet

Complete this worksheet before requesting finished prose:

For every row, also write the question that leads naturally to the next section. This exposes repetition, dead ends, and sudden offer shifts.

Worked Example

**Original hypothetical example:** Northstar Templates is a fictional reporting-template product. It is not a real campaign, customer, testimonial, or measured winner.

**Source notes:** The product contains reusable report layouts for account teams that repeatedly rebuild client presentations. Price, license terms, and measured time savings are absent.

**Evidence extraction:**

**Incoming message:** “Stop rebuilding the same client reports every Monday.”

**Continuity decision:** Preserve the recurring-report problem and Monday context. Reject any expansion to “eliminate all administrative work.”

**Unifying idea:** Northstar Templates gives account teams a reusable structure for recurring client reports without replacing their analysis.

**First draft:** “Stop rebuilding the same client report every Monday. Northstar Templates gives your team reusable layouts for presenting work it has already completed.”

**Audit:** “Stop rebuilding” could imply complete elimination. A safer version is: “Start each recurring client report with a reusable structure.”

• Audience: account teams
• Problem: rebuilding recurring presentations
• Product role: reusable layouts
• Supported benefit: a reusable reporting structure
• Missing: `[PRICE NEEDED]`, `[LICENSE TERMS NEEDED]`, `[TIME-SAVING EVIDENCE NEEDED]`

Run Separate Diagnostic Prompts

> **Proof audit:** Classify every factual and implied claim as supported, unsupported, ambiguous, or requiring primary-source verification.

> **Continuity audit:** Find changes in audience, problem, promise, terminology, emotional frame, or next step between the incoming message and page.

> **Contradiction audit:** Find conflicting claims, qualifications, prices, product descriptions, and CTAs.

> **Hook-to-product audit:** Explain the connection between the opening and product. Flag curiosity that never becomes relevant.

> **Transition audit:** State the question leading from each section to the next. Mark repetition, dead ends, and premature offer shifts.

“First-sentence function” and “slippery slide” are editorial diagnostics associated here with *The Adweek Copywriting Handbook*. No supporting passage from that book was supplied. Do not attribute those labels to the cited *Great Leads* material or present them as performance evidence.

Rewrite Without Losing Qualifications

> Rewrite for `[AUDIENCE]` in `[VOICE]` at `[READING LEVEL]`. Preserve every protected fact, limitation, and qualification. Do not invent proof, testimonials, credentials, mechanisms, comparisons, offer terms, urgency, guarantees, or compliance language. Return the revision with a change log for every qualification removed, compressed, or reframed.

For broader strategy beyond these prompts, see the guide to landing and sales page copy.

Sources and Method Notes

Books support theory and history; corpus notes are observational, not performance evidence.

• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 64.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 42.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 65.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 104.
• **Book — *Great Leads: The Six Easiest Ways to Start Any Sales Message***, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 92.
• **Daily Intel transcript corpus.** Convenience sample (n=0); observational, not conversion evidence.
• **Daily Intel transcript corpus.** Convenience sample (n=0); observational, not conversion evidence.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For external context, readers should compare advertising and research decisions against authoritative primary references such as Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel adds the proprietary direct-response layer: blackhat, greyhat, and whitehat campaign pattern comparison across VSL-heavy niches and 14+ language markets.

For deeper evaluation, continue through Copywriting research library, Facebook Ad Copy Examples: Patterns to Study and Adapt, How to Write a VSL: A Record-Ready Script Process, Storytelling Copywriting Examples: 11 Patterns to Study and Adapt, Storytelling in Copywriting: The Evidence-Led Guide, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.