Free landing page teardown prompt
For founders getting visits but weak CTA conversion: generate a focused prompt that reviews first-screen clarity, trust gaps, visual specificity, and the next test to run.
Generate a landing page teardown prompt
Fill in the page context, pick the review angles, then copy a prompt you can paste into ChatGPT, Claude, or your code agent before rewriting the page.
Designed for community feedback threads
The output asks for replacement copy, section changes, trust gaps, and one fast experiment instead of vague roast comments.
Act as a strict but practical landing page conversion reviewer. Page to review: https://example.com Product: job management software for small service businesses that sell quoted work Audience: operators, founders, and service teams deciding whether to try the guided demo Current conversion problem: the page gets visits, but very few visitors click the primary CTA Primary traffic source: Reddit, X, Product Hunt, and founder-community traffic Review angles: 1. First-screen clarity: Say what a new visitor understands in the first 5 seconds, and rewrite the hero if the product category, user, or outcome is unclear. 2. CTA path: Inspect whether the primary CTA matches visitor intent, whether secondary CTAs compete, and what should happen before account creation. 3. Trust and proof: Find missing trust signals, proof modules, security/privacy objections, customer evidence, and domain-specific details. 4. Visual specificity: Call out generic AI UI patterns, vague screenshots, unreadable product previews, and visual choices that could fit any SaaS page. Output format: 1. First 5-second impression: what the product appears to be, who it is for, and what action seems expected. 2. Conversion blockers: the 5 biggest reasons a qualified visitor might not click. 3. Hero rewrite: one clearer H1, one supporting paragraph, and one primary CTA label. 4. Section changes: exact sections to add, remove, reorder, or simplify. 5. Trust gaps: security, proof, pricing, privacy, customer evidence, and product-detail gaps. 6. Visual/UI notes: anything that feels generic, AI-made, decorative, unreadable, or inconsistent. 7. Mobile priority: what must remain visible first on mobile. 8. Fast experiment: one A/B test to run this week and the metric that would prove it worked. Be specific. Do not give generic advice like "make it clearer" unless you also provide the replacement copy or layout change.
Need launch-page prompts with reviewed visual examples after the teardown?
Use it before asking for feedback
Community replies are more useful when the review asks for exact copy, section order, proof gaps, and one measurable experiment.
Why AI-generated UI looks generic
Use this checklist when visual polish is hurting trust.
Landing page prompts
Browse launch-page, lead-capture, and proof-section prompts.
Free starter kit
Copy the free prompt formulas before upgrading to Pro.
Premium prompt previews
Inspect reviewed visual outputs and live prototypes.
Turn the teardown into better UI prompts
After the review identifies the weak sections, use the library to replace generic prompts with launch-page briefs that include layout, state, trust, and mobile requirements.