# Landing Page Conversion Checklist

Use this to audit a landing page before paid traffic, launch, or recruiter-facing portfolio promotion.

## 1. Message

- [ ] The first viewport explains what the offer is.
- [ ] The headline names the product, person, category, or literal offer.
- [ ] Supporting copy explains the value proposition.
- [ ] The page avoids vague claims that could apply to any competitor.
- [ ] The primary audience is obvious.
- [ ] The call to action matches the user's stage of intent.

## 2. Structure

- [ ] The primary CTA appears early.
- [ ] The page answers: what is it, who is it for, why trust it, what happens next.
- [ ] Sections follow a logical buying or evaluation path.
- [ ] Important proof appears before the user loses interest.
- [ ] Repeated CTAs are placed after new reasons to act.
- [ ] The page has one dominant conversion goal.

## 3. Proof

- [ ] Claims are backed by examples, metrics, screenshots, clients, testimonials, or demos.
- [ ] Social proof is specific.
- [ ] Visuals show the real product, work, or outcome.
- [ ] Case studies or examples answer likely objections.
- [ ] Any logos, stats, or quotes are current and accurate.

## 4. UX And Visual Design

- [ ] The page is scannable in 30 seconds.
- [ ] Mobile layout is clear.
- [ ] Buttons and forms are easy to tap.
- [ ] Text does not overlap or overflow.
- [ ] Visual hierarchy guides the eye to the next action.
- [ ] Decorative elements do not hide the product or message.

## 5. Form And CTA

- [ ] The CTA label describes the action.
- [ ] Form fields are limited to what is necessary.
- [ ] Error states are clear.
- [ ] Success states explain what happens next.
- [ ] Calendars, downloads, or submissions are tested end to end.
- [ ] Tracking distinguishes CTA clicks from successful conversions.

## 6. SEO

- [ ] Page title is specific.
- [ ] Meta description is written.
- [ ] One clear H1 exists.
- [ ] Headings describe the actual content.
- [ ] Internal links support discovery.
- [ ] Images have useful alt text when meaningful.
- [ ] The page can render useful content without client-only data fetching.

## 7. Performance And Technical

- [ ] Images are compressed and sized correctly.
- [ ] Third-party scripts are justified.
- [ ] Core interactions work without layout shift.
- [ ] The page has a canonical URL if needed.
- [ ] Open Graph metadata is set.
- [ ] Analytics events are verified in the target environment.