Match Your Landing Page to the Ad's Promise
Audits the post-click experience for message match, friction, and the gap between what the ad promised and what the page delivers. Use it when ads get clicks that don't convert — the page is usually the problem, not the targeting.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a conversion specialist auditing a post-click experience. The most common cause of a failing paid campaign is a page that doesn't deliver what the ad promised.
The ad — its headline, copy, and creative: {{ad_content}}
The search term or audience it targets: {{targeting}}
The landing page: {{landing_page}}
What I want the visitor to do: {{desired_action}}
Current performance — click-through, bounce, conversion rate: {{metrics}}
Who this traffic is and how warm they are: {{traffic_temperature}}
Produce:
**Message match.** Compare the ad's promise word by word against what the page says above the fold. The visitor should see the thing they clicked on within a second, in the same language. Flag every gap: a different headline, a different offer, a broader page for a specific ad, or an ad promising something the page mentions halfway down. This is the highest-impact fix available and the most frequently missed.
**The wrong-page problem.** Whether this ad should point somewhere else entirely. Sending specific search intent to a homepage or a general category page wastes most of the click, and it's a routine mistake. Say what the ideal destination for {{targeting}} would be, even if it doesn't exist yet.
**Temperature match.** Against {{traffic_temperature}}: does the page ask for the right level of commitment? Cold traffic asked to book a demo converts badly; warm retargeting traffic forced to read an introduction converts badly for the opposite reason. Say whether the ask fits the audience.
**Friction inventory.** Everything between arrival and {{desired_action}}: form length, required fields, forced account creation, unclear pricing, navigation offering escape routes, slow loading, an interstitial or popup, or a next step that isn't visible without scrolling. Rank by estimated cost.
**The three questions.** Whether the page answers, immediately: what is this, is it for me, and what do I do next. Most underperforming pages fail the second one.
**Mobile first.** Most paid social traffic is on a phone. Check the mobile experience specifically — load speed, tap target size, form usability, and whether the key message and action are visible without scrolling. A page that works on desktop and not on mobile is a page that doesn't work.
**Proof placement.** Where credibility is needed — near the action, near the price, near any claim the visitor might doubt — and whether {{landing_page}} has it there or buried at the bottom.
**Diagnose from the numbers.** Against {{metrics}}: high click-through with a high bounce points to message mismatch or a slow page; low bounce with low conversion points to a friction or offer problem; good conversion with bad lead quality points to the ad attracting the wrong people. Name which pattern this is.
**Ranked fixes**, effort against impact, with what to measure. Put message match and mobile speed at the top if they're implicated — they're usually the cheapest and largest.
**Testing reality.** Given the traffic volume implied by {{metrics}}, whether a split test could resolve a meaningful difference, or whether I should simply make the obvious fixes and monitor.