# Website Message Clarity Prompt Pack

Use these prompts before changing a homepage, service page, or landing page. Replace the bracketed text with your own context and ask the model to show assumptions separately from evidence.

## 1. Clarify the offer

```text
You are helping a lean team clarify its website offer.

Offer: [describe the current service or product]
Audience: [who it is for]
Current homepage copy: [paste the copy]

Rewrite the offer as:
1. The specific audience
2. The urgent problem
3. The useful outcome
4. What is included
5. The next action

Do not invent results, customers, statistics, or capabilities. List any missing evidence separately.
```

## 2. Find the message gap

```text
Review this page for a first-time visitor who has never heard of the company:

[paste page copy]

Answer:
- What does the company appear to do?
- Who does it appear to help?
- What outcome is promised?
- What proof is present?
- What question would block a next step?
- What sentence should be clearer first?

Use short, concrete observations. Quote the exact sentence that supports each observation.
```

## 3. Turn proof into useful evidence

```text
Organize these project notes into a proof inventory:

[paste notes]

Create a table with:
- claim;
- evidence source;
- audience problem it supports;
- where it belongs on the site;
- what must remain confidential or qualified.

Never upgrade an estimate into a result or imply work that is not in the notes.
```

## 4. Improve the primary CTA

```text
Generate five primary CTA options for this page:

Audience: [audience]
Page goal: [goal]
Offer: [offer]
Visitor concern: [concern]

Each CTA must be specific about the next step, avoid hype, and be no longer than six words. Explain the tradeoff between clarity and commitment for each option.
```

## 5. Handle objections

```text
Create an objection map for this offer:

[offer and audience]

List the five most likely questions a cautious buyer will ask. For each one, write:
- the honest answer;
- the evidence needed;
- one short FAQ answer;
- one page section where it should appear.

Do not answer with invented guarantees.
```

## 6. Check page hierarchy

```text
Use this page copy to propose a decision-first hierarchy:

[paste copy]

Return only:
1. Hero promise
2. Supporting explanation
3. Proof block
4. Process or scope block
5. Objection-handling block
6. Primary CTA
7. Secondary CTA

Keep the original meaning. Identify any section that has no clear job.
```

## 7. Make the copy more concrete

```text
Rewrite the following copy for clarity without making it louder:

[paste copy]

Prefer specific nouns and verbs. Remove vague claims, filler adjectives, and unexplained jargon. Preserve any documented numbers exactly. Return the revised copy followed by a short change log.
```

## 8. Build a page brief

```text
Create a one-page implementation brief from this strategy:

[paste strategy]

Include audience, job-to-be-done, page promise, required proof, content sections, primary action, secondary action, analytics events, accessibility considerations, and open questions.

Separate decisions from assumptions.
```

## 9. Audit mobile friction

```text
Create a mobile UX review checklist for this page:

Page type: [homepage, service page, landing page, etc.]
Primary action: [action]
Audience: [audience]

Cover navigation, readability, tap targets, form effort, proof visibility, page speed, motion, and error recovery. Rank each check as critical, useful, or optional.
```

## 10. Keep measurement honest

```text
Create a measurement plan for this page goal:

Goal: [goal]
Primary action: [action]
Available tools: [analytics tools]

Define one leading signal, one conversion signal, and one quality check. For each, state what it can tell us, what it cannot tell us, the event name, and the next decision it should inform.
```

## Quick use

Start with prompts 1, 2, and 3. Use the output to make one small copy or hierarchy change, then validate the page with prompts 4 and 10. Treat the model as a drafting partner, not as a source of proof.