Landing Page Conversion Audit

Run this when a landing, sales, opt-in, or checkout page is underperforming on paid traffic and you want a ranked fix list rather than a pile of generic CRO advice. It works through message match from ad to page, above-the-fold clarity on mobile, offer and price visibility, form friction, trust placement near the button, what happens after the purchase, and whether conversion events and click IDs actually survive to the order. Output is ordered by expected revenue impact, capped at seven fixes, and it flags when traffic is too thin to separate a real problem from noise. The honest caveat: it can only diagnose the page. If the offer or audience is wrong, the skill says so and stops, which is the right behavior but means you may still need a different fix.

skills.sh installs: 122.1K
GitHub stars: 8
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add autonnel/autonnel-skills --skill landing-page-conversion-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

Landing Page Conversion Audit

Audit a live page (or a mockup) for the things that actually move conversion rate on paid traffic, and return a ranked fix list. Do not return a generic "add more social proof" list - every finding must name the element, the failure mode, and what to change it to.

When to use

"Review my landing page" / "why is my conversion rate so low"
Paid traffic is running and CPA is above target
Before scaling ad spend on a page that has never been audited
A checkout page with a high add-to-cart-to-purchase drop-off

When not to use

The page has no traffic yet - there is nothing to diagnose. Use sales-funnel-blueprint to design it instead.
The problem is upstream (wrong audience, wrong offer). A page audit cannot fix a broken offer; say so and stop.