Product Page Conversion Review - E-commerce
Use this skill when
The user wants to improve or audit a product detail page.
Common requests:
- "Audit this product page."
- "Why is this PDP not converting?"
- "Review this page before we scale ads."
- "Find what buyers need before purchasing."
Required input
Minimum useful input:
- Product page URL or screenshots.
- Product category and price point.
- Target customer.
- Product facts, specs, variants, sizing, or compatibility details.
- Current conversion issue or business goal.
Optional:
- Top reviews.
- Support questions.
- Return reasons.
- Competitor pages.
- Traffic source and device mix.
Before analysis
- Confirm the target buyer and purchase intent.
- Confirm whether the page is for cold traffic, warm traffic, search traffic, or returning customers.
- Separate missing product information from weak copy.
- Avoid rewriting claims without product evidence.
Analysis workflow
- Review above-the-fold clarity:
- what the product is
- who it is for
- why it is different
- price and offer clarity
- primary CTA visibility
- Check decision support:
- images and video
- specs
- sizing or compatibility
- delivery and returns
- FAQs
- reviews and proof
- Mine objections from reviews, tickets, and returns.
- Compare the page against buyer questions, not generic page-length advice.
- Prioritize edits by likely buyer uncertainty reduced.
Decision and evidence standard
Every finding should include:
- Evidence tag:
export, screenshot, url, review_cluster, support_ticket, return_reason, policy, feed_diagnostics, margin_csv, inventory_export, hypothesis, or needs_data.
- Severity: low, medium, high, or critical.
- Confidence: low, medium, or high.
- Business impact: revenue, margin, cashflow, retention, conversion, support_load, or risk.
- Effort: XS, S, M, or L.
- Owner decision: do_now, test, investigate, monitor, ignore, or approval_needed.
If the evidence is weak, mark the finding as hypothesis or needs_data and lower confidence.
Output format
PDP verdict
Short verdict with the top 3 blockers.
Review table
| Area |
Issue |
Evidence |
Recommended fix |
Priority |
Buyer questions not answered
List unanswered questions that likely affect purchase confidence.
Page edit brief
A concise brief for the person editing the page.
Example input and output
Input:
- product page URL
- product facts and specs
- top 20 reviews
- target customer
- traffic source
Good output excerpt:
| Finding |
Evidence |
Severity |
Confidence |
Business impact |
Effort |
Owner decision |
| Above-the-fold copy does not explain who the product is for |
url, screenshot |
high |
medium |
conversion |
S |
test |
| Compatibility questions appear in reviews but not on the page |
review_cluster, url |
high |
high |
conversion/support_load |
M |
do_now |
What not to do yet: invent product claims, testimonials, or urgency that is not supported by source material.
Guardrails
- Do not fabricate product claims.
- Do not invent reviews or testimonials.
- Do not recommend aggressive urgency unless the offer truly supports it.
- Do not make legal, medical, nutritional, financial, or safety claims without source material.
- Do not edit live pages without approval.
1---2name: product-page-conversion-review-ecommerce3description: Reviews e-commerce product pages from URLs, screenshots, reviews, product facts, and competitor references to find clarity, trust, proof, objection, and buying-friction issues. Use when product page conversion is weak or before sending more traffic to a product.4---56# Product Page Conversion Review - E-commerce78## Use this skill when910The user wants to improve or audit a product detail page.1112Common requests:1314- "Audit this product page."15- "Why is this PDP not converting?"16- "Review this page before we scale ads."17- "Find what buyers need before purchasing."1819## Required input2021Minimum useful input:2223- Product page URL or screenshots.24- Product category and price point.25- Target customer.26- Product facts, specs, variants, sizing, or compatibility details.27- Current conversion issue or business goal.2829Optional:3031- Top reviews.32- Support questions.33- Return reasons.34- Competitor pages.35- Traffic source and device mix.3637## Before analysis38391. Confirm the target buyer and purchase intent.402. Confirm whether the page is for cold traffic, warm traffic, search traffic, or returning customers.413. Separate missing product information from weak copy.424. Avoid rewriting claims without product evidence.4344## Analysis workflow45461. Review above-the-fold clarity:47 - what the product is48 - who it is for49 - why it is different50 - price and offer clarity51 - primary CTA visibility522. Check decision support:53 - images and video54 - specs55 - sizing or compatibility56 - delivery and returns57 - FAQs58 - reviews and proof593. Mine objections from reviews, tickets, and returns.604. Compare the page against buyer questions, not generic page-length advice.615. Prioritize edits by likely buyer uncertainty reduced.6263## Decision and evidence standard6465Every finding should include:6667- Evidence tag: `export`, `screenshot`, `url`, `review_cluster`, `support_ticket`, `return_reason`, `policy`, `feed_diagnostics`, `margin_csv`, `inventory_export`, `hypothesis`, or `needs_data`.68- Severity: low, medium, high, or critical.69- Confidence: low, medium, or high.70- Business impact: revenue, margin, cashflow, retention, conversion, support_load, or risk.71- Effort: XS, S, M, or L.72- Owner decision: do_now, test, investigate, monitor, ignore, or approval_needed.7374If the evidence is weak, mark the finding as `hypothesis` or `needs_data` and lower confidence.7576## Output format7778### PDP verdict7980Short verdict with the top 3 blockers.8182### Review table8384| Area | Issue | Evidence | Recommended fix | Priority |85|---|---|---|---|---|8687### Buyer questions not answered8889List unanswered questions that likely affect purchase confidence.9091### Page edit brief9293A concise brief for the person editing the page.9495## Example input and output9697Input:9899- product page URL100- product facts and specs101- top 20 reviews102- target customer103- traffic source104105Good output excerpt:106107| Finding | Evidence | Severity | Confidence | Business impact | Effort | Owner decision |108|---|---|---|---|---|---|---|109| Above-the-fold copy does not explain who the product is for | `url`, `screenshot` | high | medium | conversion | S | test |110| Compatibility questions appear in reviews but not on the page | `review_cluster`, `url` | high | high | conversion/support_load | M | do_now |111112What not to do yet: invent product claims, testimonials, or urgency that is not supported by source material.113114## Guardrails115116- Do not fabricate product claims.117- Do not invent reviews or testimonials.118- Do not recommend aggressive urgency unless the offer truly supports it.119- Do not make legal, medical, nutritional, financial, or safety claims without source material.120- Do not edit live pages without approval.
mardab96