AI Blocks › Audit a landing page
Find what's wrong with your page and decide what to test
Give it your page and analytics. Get a research plan, ranked page problems and a check that you can test.
Find what's wrong with your page and pick tests is a free AI workflow for the job "Audit a landing page". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Level: advanced · Thinking: high
What it does
Most people fix a weak page by guessing. They change the headline, move a button and wait, and a test with too little traffic tells them nothing. Or they test before they know why visitors leave, so they test the wrong thing. Worse, if the analytics count twice, every number they trust is off. The steps put the work in order. It plans the research first, so you learn where people drop, what is on the page and why they hesitate. Then it audits the page like a stranger would. It sorts each problem by what to do about it, with tracking faults first, since they break the data. Last, it checks whether your traffic can prove a test and how many weeks that takes. The order comes from Peep Laja's keynote, Optimizing Optimization.
You give it
- The address or saved copy of the page (optional for the first step, needed for the audit)
- Your analytics, with visits, steps and sales or sign-ups by page
- Customer words from reviews, chats or surveys (optional)
- Your brand file or a note on your offer, proof and buyer doubts (optional)
- Time to do the research the plan lists (a few days to a few weeks)
- Your visits and conversions for the page you want to test, pulled after the research
- Brand brain (optional)
- Your website (optional)
You get
- A research order that says what to check first and why, with a tracking check up front
- A ranked audit of the page, quick wins first, with a score out of 100
- Every problem sorted into fix now, investigate, test or tracking, in order of likely gain
- A clear yes or no on whether your traffic can prove a test, and how many weeks it needs
Use it when
- Your page gets visits but few people buy, sign up or book, and you do not know what to fix first.
- You have a list of changes you want to test and need to know which ones deserve the traffic you have.
- Someone says to run an A/B test and you want to know if your numbers can support one.
Steps
- Conversion research planner: Paste your page and analytics. Get a research order that finds where, what and why before you test anything.
- Landing page conversion review: Share your page and screenshots. Get conversion problems ranked by impact, with recommended fixes and a score.
- Page issue sorter: Paste a list of site problems. Get each one sorted into fix now, investigate, test or tracking, with a ranked order.
- A/B test traffic checker: Paste visits, orders and revenue. Get the test size, weeks needed and a readiness score out of 100.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Share your page and analytics. It writes the research plan and stops.
- Do the research the plan lists, such as the analytics check, a walk-through of the page and a few customer questions. Then say "carry on".
- Pull your visits and orders for the page you want to test when it asks, so the last step can size the test.