Shopify Product Page
Own product-page analysis, information architecture, and copy drafts for a named product or template.
Operating contract
- Preserve supplied product truth. Do not invent ingredients, materials, specifications, compatibility, certifications, outcomes, reviews, urgency, inventory, shipping, guarantees, or results.
- Keep sourced customer language distinct from paraphrase and interpretation.
- Use one primary audience, problem, promise, proof path, and call to action unless the brief requires variants.
- Drafting does not authorize editing or publishing the product or theme.
- Treat legal, medical, financial, environmental, comparative, and performance claims as evidence-sensitive.
Required inputs
Collect product source data, target customer, job or problem, awareness stage, approved promise, proof, objections, price, variants, availability, offer, shipping, returns, warranty, reviews with provenance, brand voice, page constraints, traffic context, and authorization.
When source truth is incomplete, create a gap list or clearly marked placeholders for the merchant to complete. Never fill gaps with plausible-sounding claims.
Workflow
- Build a product truth table from authoritative inputs.
- Define the page's one central conversion job and traffic context.
- Map the questions a buyer must answer before commitment.
- Audit content order, media, variant and price clarity, purchase controls, proof, objections, policies, mobile behavior, accessibility, and measurement.
- Draft the smallest complete message system using approved facts.
- Separate content changes from theme or app implementation.
- Add QA for claim truth, variant logic, price, links, mobile rendering, accessibility, analytics, and live verification.
For message and page design, read references/copy-frameworks.md. For reusable briefs and drafts, read references/templates.md.
Output contract
Return the page objective, truth table, evidence gaps, current issues, proposed information order, copy draft or brief, proof mapping, implementation notes, QA, authorization, and verification. Explain which lines are final facts, merchant-supplied claims, proposed phrasing, or unresolved placeholders.
1---2name: shopify-product-page3description: Audits and drafts Shopify product-page structure, copy, proof, offer, and mobile UX. Use for a specific PDP or product template, not a whole-store audit.4license: MIT5---67# Shopify Product Page89Own product-page analysis, information architecture, and copy drafts for a named product or template.1011## Operating contract1213- Preserve supplied product truth. Do not invent ingredients, materials, specifications, compatibility, certifications, outcomes, reviews, urgency, inventory, shipping, guarantees, or results.14- Keep sourced customer language distinct from paraphrase and interpretation.15- Use one primary audience, problem, promise, proof path, and call to action unless the brief requires variants.16- Drafting does not authorize editing or publishing the product or theme.17- Treat legal, medical, financial, environmental, comparative, and performance claims as evidence-sensitive.1819## Required inputs2021Collect product source data, target customer, job or problem, awareness stage, approved promise, proof, objections, price, variants, availability, offer, shipping, returns, warranty, reviews with provenance, brand voice, page constraints, traffic context, and authorization.2223When source truth is incomplete, create a gap list or clearly marked placeholders for the merchant to complete. Never fill gaps with plausible-sounding claims.2425## Workflow26271. Build a product truth table from authoritative inputs.282. Define the page's one central conversion job and traffic context.293. Map the questions a buyer must answer before commitment.304. Audit content order, media, variant and price clarity, purchase controls, proof, objections, policies, mobile behavior, accessibility, and measurement.315. Draft the smallest complete message system using approved facts.326. Separate content changes from theme or app implementation.337. Add QA for claim truth, variant logic, price, links, mobile rendering, accessibility, analytics, and live verification.3435For message and page design, read [references/copy-frameworks.md](references/copy-frameworks.md). For reusable briefs and drafts, read [references/templates.md](references/templates.md).3637## Output contract3839Return the page objective, truth table, evidence gaps, current issues, proposed information order, copy draft or brief, proof mapping, implementation notes, QA, authorization, and verification. Explain which lines are final facts, merchant-supplied claims, proposed phrasing, or unresolved placeholders.
vinceservidad