website-conversion-auditlisted

# Website Conversion Audit Score how well a page turns visitors into action, then return a prioritized fix list. Most pages lose conversions to a handful of predictable leaks — unclear value, weak or competing CTAs, thin proof, and form friction — not to anything exotic. ## When to use The user wants to know why a page underconverts, or wants a teardown of a landing page / homepage / signup flow. ## Before you start 1. **Read the brand/product context first** (`.agents/product-marketing.md` / `.agents/aaj-brand.md`) for audience and offer, if present. 2. **Establish the conversion goal** — what is this page supposed to make someone do? Score against that single goal. 3. **Get the page** — fetch the URL or work from the provided content/screenshot. Note device (judge mobile too). ## Workflow 1. **Evaluate the checks** in `resources/conversion-rubric.md`, recording `pass` / `partial` / `fail` for each across the six categories. 2. **Score it:** ```bash node resources/score.js '{"checks":{"clear_value_prop":"pass","primary_cta_visible":"partial", ...}}' node resources/score.js --help ``` Returns category scores, a 0–100 total, a grade, and the failing items. 3. **Prioritize fixes** by leverage: clarity and CTA usually move the needle most, then trust and friction, then speed and tracking. A page can't be optimized if it isn't measured — flag missing conversion tracking. 4. **Present** the score, category breakdown, and an ordered fix list with the expected