Homepage Structure

Design a high-converting homepage structure for [Business/offer].
For each section, explain its purpose and what the visitor should do next.
Focus on clarity and conversion.

Design a landing page with one job. You are a conversion-focused web designer; you care about clarity and honesty more than cleverness.

<inputs>
Offer: [Offer]
Visitor: [Visitor]
Where the visitor is coming from, and what the ad, email or link promised: [Traffic source and what it promised]
The single action the page asks for: [The single action]
Proof we can truthfully show: [Proof you can truthfully show]
Doubts and objections we hear: [Doubts and objections]
Tone: [Tone]
</inputs>

Deliver the following, in this order.

A. Message match
State in two sentences what the visitor expects to see when they arrive, based on the traffic source, and how the first screen will confirm they are in the right place.

B. First screen
Specify what is visible before scrolling on a phone: headline, supporting line, the call to action and its button label, and one visual. Give three headline options that take different angles (outcome, problem, specificity) and say which you would run first.

C. Section sequence
List the remaining sections from top to bottom. For each: the question in the visitor's mind that it answers, the content it contains, and whether the call to action repeats there. Map each objection from the inputs to the section that handles it.

D. The conversion step
Define the form or checkout entry: every field, why it is needed, and what happens immediately after submission. Remove any field you cannot justify.

E. Draft copy
Write draft copy for every section, labeled DRAFT. Keep paragraphs to three lines or fewer on a phone.

F. What to test
Give three test ideas, each written as: change, expected effect, and the reason you expect it.

Constraints
- One conversion action only. No site navigation, no secondary offers, no social links competing with the button.
- Use only the proof listed in the inputs. Never invent testimonials, customer names, logos, numbers, awards or guarantees. Where proof would help and none was supplied, insert [PROOF NEEDED: what kind].
- No false urgency: no countdowns or scarcity claims unless the inputs state a real deadline or limit.
- Button labels must say what happens next.
- Body text and buttons must be able to meet WCAG 2.2 AA contrast, and tap targets must be comfortably large on touch screens.

Format: headings A to F, a table for section C, plain lists elsewhere.