The Landing Page Conversion Auditor: Turn Underperforming Copy Into a Prioritized Fix List
Why this prompt matters
For a page getting 10,000 monthly visits at a $3 cost-per-click ($30,000 in ad spend), moving conversion from 1.2% to 2.4% doubles the number of paying customers acquired without spending another dollar on traffic. Most underperforming landing pages fail from vague copy and missing trust signals, not from bad design — problems a redesign budget won't fix but a focused copy audit will.
What we use it for
A marketing manager is about to increase paid search spend by $10,000/month for a SaaS landing page currently converting at 1.2% against a 3% category benchmark, and needs to know exactly what to fix before sending more traffic to a leaky page.
Prompt
Role: Act as a senior conversion rate optimization (CRO) consultant who has run hundreds of landing page A/B tests and can spot friction points other marketers miss. Context: - Page copy: [PASTE YOUR FULL LANDING PAGE COPY, SECTION BY SECTION — HEADLINE, SUBHEAD, BODY, CTA BUTTONS, TESTIMONIALS] - Primary traffic source: [E.G., PAID SEARCH, PAID SOCIAL, ORGANIC, EMAIL] - Current conversion rate: [E.G., 1.2% VISITOR-TO-SIGNUP] - Target audience: [WHO IS LANDING ON THIS PAGE AND WHAT PROBLEM ARE THEY TRYING TO SOLVE] - Primary call-to-action: [WHAT YOU WANT THE VISITOR TO DO] Task: Audit this landing page copy for conversion friction and produce a prioritized list of fixes I can implement without a developer or designer — copy, structure, and CTA changes only. Constraints: - Do not recommend a visual redesign, new images, or layout changes — copy and content structure only - Every friction point you flag must quote the specific line or section it applies to — no generic observations like "make it more compelling" - Explicitly check whether the core value proposition is clear within the first 5 seconds of reading the headline and subhead — state pass or fail - Distinguish between friction that actively stops someone from converting (blocking) and friction that just creates minor doubt (annoying) — these require different urgency - Rank every recommended fix by estimated impact versus effort to implement, not by severity alone - Explicitly call out anything on the page that is already working well — don't recommend changing things that aren't broken Output Format: 1. Value Proposition Clarity Check: Pass/Fail, with the specific reason 2. Friction Point List: each entry quotes the exact copy, explains why it's friction, and tags it as Blocking or Annoying 3. Trust Signal Gaps: what's missing that similar high-converting pages usually include 4. Prioritized Fix List: top 3-5 changes, ranked by impact-to-effort ratio, each with a specific rewrite suggestion 5. What's Already Working: 2-3 elements to leave alone
Result
1. Value Proposition Clarity Check: FAIL
The headline "Project Management, Reimagined" and subhead "The tool your team will actually use" describe a feeling, not a specific outcome. A visitor has no idea within 5 seconds what the product does, who it's for, or what problem it solves. Compare to a passing example: "Ship projects 30% faster with the only PM tool your engineers won't ignore" — names the outcome, the mechanism, and implicitly the audience.
2. Friction Point List:
— Quote: "Reimagined" (headline). Why it's friction: vague marketing language with no concrete meaning; forces the visitor to keep reading to figure out what you actually do, and most won't. Tag: Blocking.
— Quote: "Sign Up Free" (primary CTA button). Why it's friction: doesn't say what happens next or how long it takes — visitors hesitate when a CTA feels like the start of a longer commitment than it is. Tag: Annoying.
— Quote: "Trusted by teams everywhere" (social proof section). Why it's friction: unverifiable vague claim with no logos, numbers, or named companies; reads as filler rather than proof. Tag: Blocking.
— Quote: "Our pricing scales with your needs" (pricing teaser). Why it's friction: visitors evaluating a tool want to know the actual starting price before clicking through; ambiguity here causes drop-off rather than curiosity. Tag: Blocking.
3. Trust Signal Gaps: No customer logos, no specific usage numbers (e.g., "12,000 teams"), no third-party review badges (G2, Capterra), and no named case study. High-converting B2B SaaS pages in this category typically show at least one specific, attributed customer result within the first two scrolls.
4. Prioritized Fix List:
1. Rewrite the headline to name a specific outcome and audience (High impact, Low effort — just copy change). Suggested: "Ship projects 30% faster with the PM tool built for engineering teams."
2. Replace "Trusted by teams everywhere" with 3-5 real company logos or a specific number (High impact, Low effort if logos are available).
3. Add "Free for 14 days, no credit card required" beneath the CTA button to reduce signup hesitation (Medium impact, Low effort).
4. Replace the vague pricing teaser with an actual starting price, even if it's "Starting at $12/user/month" (Medium impact, Low effort).
5. Add one named customer quote with a specific, quantified result near the top third of the page (Medium impact, Medium effort — requires securing a quote).
5. What's Already Working: The page loads fast with minimal above-the-fold clutter, the CTA button color has strong contrast against the background, and the FAQ section near the bottom directly addresses the three most common objections (integration support, data migration, team size limits) — leave all three of these unchanged.
Most landing page feedback is either too vague to act on (“make it pop more”) or too focused on visual redesign when the actual problem is the words. This prompt forces a copy-only audit precisely because most marketers can ship a headline rewrite this afternoon, but a redesign requires a design sprint they don't have time for before their next traffic push.
The constraint requiring every friction point to quote the exact copy line is what separates this from generic feedback. “The messaging feels off” gives a marketer nothing to act on. “The phrase ‘Reimagined’ in your headline is vague marketing language that doesn't tell a visitor what the product does” gives them an exact sentence to rewrite.
The Blocking versus Annoying distinction matters because not all friction deserves the same urgency. A vague headline that hides the value proposition is blocking — it stops conversion outright. A CTA button that doesn't specify what happens next is merely annoying — it creates hesitation but doesn't stop a motivated visitor. Treating both with equal priority wastes a marketer's limited time on low-impact fixes while blocking issues stay unaddressed.
Ranking fixes by impact-to-effort ratio, rather than severity alone, is deliberate. A blocking issue that requires a customer testimonial you don't have yet is lower priority in the short term than a blocking issue you can fix by rewriting one sentence right now. The prompt optimizes for what a marketer can actually ship today, not a theoretically complete fix list.
The requirement to name what's already working exists because audits that only list problems train marketers to distrust every page element, including the ones driving whatever conversions are already happening. Confirming the fast load time and the FAQ section are fine prevents a well-intentioned marketer from breaking something that wasn't broken.