0
Diagnosing why a high-traffic page has low conversion
⁂auto-checked, 2 hours oldAauraNovice
The prompt
Our page_type gets solid traffic but converts poorly. Help me diagnose likely causes before I rewrite the copy blindly.
Page copy (current): current_page_copy
What we know about the traffic source and behavior: traffic_and_behavior_data
Do this:
1. Read the copy as if you were the actual traffic source's typical visitor (if traffic is mostly from a specific channel, e.g. paid search for a specific keyword, or organic from a specific comparison article, read it through THAT lens, expectations differ hugely by source).
2. Identify any expectation mismatch: does this page actually deliver what someone arriving from that specific source expects to find? A mismatch here (not the copy quality) is often the real conversion killer.
3. Separately, evaluate the copy itself for the usual issues (unclear CTA, buried value prop, too much friction before the ask, no urgency or reason to act now).
4. Rank your suspected causes by likely impact, don't give me 10 equal-weight suggestions, tell me what to fix first.
5. Propose ONE specific change to test first (not a full rewrite) so we can isolate what's actually driving the improvement, if any.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 2 hours ago |
Example output
Expectation-mismatch check: given that most traffic comes from a comparison-focused search query per your data, but the page opens with a generic product overview rather than directly addressing the comparison, this is a likely primary mismatch, visitors arriving to compare aren't immediately shown how this stacks up against the alternative they searched against. Copy-quality issues found but ranked secondary: CTA button copy is generic ('Get Started') rather than outcome-specific, and there's a 3-paragraph delay before any concrete claim appears. Ranked causes: (1) expectation mismatch with comparison-intent traffic, highest suspected impact given the traffic source data, (2) delayed value prop placement, (3) generic CTA copy, lower impact alone. Recommended first test: add a comparison-framed section near the top of the page addressing the specific alternative your search traffic is likely coming from, isolate this one change before touching CTA copy, so you can attribute any lift correctly.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.