Product & Landing Copy Audit

Goal and scope

Audit selected product or landing copy against actual behavior, audience intent, evidence, and conversion path.

Domain invariants

• Claims, capabilities, prices, plans, limits, permissions, timing, and outcomes match authoritative behavior.
• Labels and calls to action describe the action and destination without dark patterns, ambiguity, or premature success.
• Copy remains concise, accessible, translatable, consistent with product vocabulary, and appropriate to user state.
• Analytics and experiments do not become hidden sources of copy truth or misrepresent causal impact.

Audit method

1. Trace each changed claim or CTA to product behavior, plan/config, destination, and success/failure state.
2. Identify conflicting terminology across UI, docs, emails, pricing, metadata, and support surfaces.
3. Check audience, intent, evidence, legal/privacy sensitivity, localization constraints, and accessibility.
4. Separate messaging opportunities from factual contract defects.

Handoff

For each selected claim or CTA, retain its visible wording, product/version/state source, actual destination and expected user outcome. Pass the concrete mismatch into Improve Product & Landing Copy. A preferred tone is an editorial choice; a wrong version, unsupported capability or misleading success label is a factual defect with an observable repair criterion.