ChiefOSby ConversintStart free
Menu
← Back to the library
Marketing and creative direction

Landing page review

Audit, design, or improve a paid-campaign landing page for message match, offer clarity, conversion path, privacy-safe measurement, mobile usability, and next-test decisions. Use when a user asks about ad landing pages, lead-magnet pages, conversion, landing-page copy, or whether a page is ready for paid traffic.

Works with the context you provideVersion 3.0.0Historical revision

Landing Page Review

Use this method to decide whether a landing page can turn paid traffic into a useful signal or qualified response. It can provide a review, copy, or an implementation proposal. It does not publish ads, change budgets, send leads, or alter analytics, source code, or a customer system without the host's explicit approval and capability.

Context

Collect the page URL or draft, the ad promise, intended buyer, offer, CTA, available funnel evidence, and current measurement design. Ask only for missing facts that affect the decision. Treat platform metrics, web analytics, lead delivery, and stakeholder feedback as evidence inputs, not proof that a change occurred.

Read `references/host-operations.md` only if the user asks to inspect, implement, deploy, or verify a live page.

Workflow

1. **Identify the campaign cell.** Name buyer, concrete problem, offer, message, CTA, and desired next action. Repair an unclear cell before debating visual polish. 2. **Score the page.** Assess message match, offer clarity, conversion path, trust and friction, measurement readiness, and implementation quality. Explain evidence for every score. 3. **Audit the copy.** Check whether the headline names a recognizable problem, the offer is specific, the first action delivers value before an optional contact request, and claims match evidence. 4. **Audit the journey.** Trace ad URL, CTA, first action, result, optional contact, confirmation, lead delivery, and measurement. Keep private form data out of analytics and advertising parameters. 5. **Check mobile and accessibility.** Review the first action on a small viewport, layout, contrast, keyboard access, page weight, and competing calls to action. 6. **Choose one change next.** Locate the first material drop-off, propose the smallest change, state the metric and review window, and distinguish a tracking gap from a copy or audience hypothesis.

Scorecard

| Area | Weight | |---|---:| | Message match | 20 | | Offer clarity | 20 | | Conversion path | 20 | | Trust and friction | 15 | | Measurement readiness | 15 | | Implementation quality | 10 |

Output format

```markdown ## Landing Page Review - Page: - Score: - Decision:

## Main finding ## Scorecard | Area | Score | Evidence | Fix |

## One change next - Change: - Metric: - Review window:

## Implementation proposal ## Handoffs and approvals needed ```

Quality rules

- Do not approve traffic or scale solely on clicks or a visual impression. - Prefer a clear give-first action over a meeting-first gate when the offer calls for it. - Do not claim tracking is working without inspecting the established host evidence. - If implementation is requested, prepare a scoped change and obtain the required host approval before acting.