Prompt: Landing Page Critique and Rewrite
A rewrite prompt for diagnosing weak landing page copy and rebuilding it with a clearer offer, stronger proof logic, and sharper calls to action.
Use cases
Marketing & Growth, Content & Writing
Platforms
Claude, GPT, Model-Agnostic
Jump to a section
Workspace-ready resource
Copy the raw material, then check the setup, output contract, and failure modes.
You are reviewing a landing page like a sharp conversion copywriter, not a polite assistant. First, critique the page against:- clarity of offer- audience specificity- headline strength- proof and credibility- friction or confusion- CTA quality- message-to-market fit Then rewrite the page. Output:1. Top 5 issues2. What the page should say more clearly3. Revised positioning in one sentence4. Revised hero section5. Revised body sections6. Revised CTA set Constraints:- Keep the rewrite specific.- Remove filler and generic benefits.- Do not invent proof or customer claims.- If proof is missing, write the copy to expose that gap instead of hiding it.Workspace translation
Turn this resource into an inspectable run.
Best next step
Run it once manually. If the same job appears twice, package it.
From resource to system
Use it once
Copy and adapt the prompt for a one-off run.
Make it reusable
Save the durable pattern, turn repeated use into a playbook, or attach the reasoning as project knowledge.
Decide after the run
Run it once manually. If the same job appears twice, package it.
Quality bar
Before using this, check the contract.
What input does this require?
What output should it produce?
Where can it fail?
What should a human review?
Recommended path
When to Use This
Use this when a landing page feels vague, bloated, or polished on the surface but weak where it matters: the offer, the proof, and the CTA logic.
It is useful for founders, marketers, agencies, and product teams who need a fast diagnosis plus a rewrite direction before handing the page to design, paid traffic, or CRO work.
Why It Works
The critique-first step matters because rewriting without diagnosis usually produces a cleaner version of the same broken page.
The instruction not to invent proof is equally important. Conversion copy becomes actively harmful when the model fills evidence gaps with fake certainty.
How to Customise
Add context about traffic source, ICP, awareness stage, and offer maturity if you want more precise rewrites. A paid acquisition page and a homepage hero should not sound the same.
If the page already has a strong structure, ask for “surgical edits only” so the model critiques without rebuilding everything.
Limitations
This prompt improves messaging, not product strategy. If the offer itself is weak, badly targeted, or under-evidenced, the rewrite will still hit a ceiling.
It also should not be used blind. Strong landing page copy still needs a human with real product, market, and customer context.
Model Notes
Claude tends to produce stronger diagnosis before the rewrite. GPT often benefits from explicit section labels in the output.
Model-agnostic overall, but the prompt works best when you supply the actual page copy instead of asking the model to guess.
Related Resources
Browse PromptsSystem Prompt: Content Writer
A production-ready system prompt for configuring any LLM as a content writer with tone control, format awareness, and a built-in self-check.
Pattern / playbook seed
Content & Writing · Marketing & Growth
Skill: Product Marketing Messaging Architect
A reusable messaging skill for turning product context, ICP detail, and proof into clearer positioning, sharper claims, and a stronger message hierarchy.
Operator seed
Marketing & Growth · Strategy & Planning
Skill: QA Reviewer for AI Drafts
A review skill for catching weak claims, structural drift, tone problems, and hidden assumptions in AI-generated drafts before they go live.
Operator seed
Content & Writing · Operations & Workflow
Related Guides
Need this operationalized?
Turn the pattern into a workspace system.
Use MPV for the private workspace loop, or work with Encanta to turn operators, playbooks, context, and review flows into a team-ready implementation.