OctiAI

Categories

One‑shot PDP Research Prompt — Conversion Template

A concise, research-driven prompt that produces copy-ready, conversion-optimized Product Detail Pages (hero, benefits, proofs, specs, FAQs, SEO) in one run.

What You'll Get

How to Use

Quick verification tip

Always supply the latest product spec sheet and a representative set of verified reviews. If the prompt marks any detail as [ASSUMED], confirm against your source files before publishing. Use the 3 CTA variants and urgency micro-lines to run short A/B tests.

Works Best With

Works best when you provide concise product specs, target audience, and 1-2 verified review excerpts

Prompt Template


## Goal
- Rank the product page for the target keyword while fully satisfying the specified {{search_intent}} and converting visitors into qualified actions (add-to-cart, sign-up, or purchase) with clear CTAs and trust signals.

## Inputs
- Primary keyword: {{primary_keyword}}
- Search intent: {{search_intent}}
- Target audience / ICP: {{audience}}
- Region and language: {{region_language}}
- Content type: {{content_type}}
- Product spec sheet and packaging details: {{product_spec_sheet}}
- Existing PDP copy and verified reviews: {{existing_pdp_and_reviews}}
- Additional inputs to include where available (not required as placeholders): tone of voice, primary CTA, price or pricing model, shipping/returns notes, internal link priorities, required legal/compliance language.

If keyword volume or SERP features are not provided, infer likely intent and propose 2 alternate target keyword phrases with rationale before producing the page.

## Prompt
You are an expert ecommerce copywriter and SEO specialist. Using the inputs above, produce a one-shot, conversion-optimized product detail page (PDP) ready for copy-and-paste into a CMS. Follow these steps and output sections exactly as requested.

1) Short content brief/spec (3-5 bullets)
   - Confirm the exact target keyword and intent (use {{primary_keyword}} and {{search_intent}}).
   - Primary conversion goal and CTA.
   - Top 3 buyer use-cases from {{audience}} and {{product_spec_sheet}}.
   - Key differentiation and proof assets to use (from {{existing_pdp_and_reviews}}).

2) Page content
   - Hero area:
     - H1 (primary headline using exact-match or close-match {{primary_keyword}}).
     - 1-2 line scannable hero product description (benefit-first).
     - 3 micro-benefit bullets (very short).
     - Primary CTA and secondary CTA variants (3 total CTA text variants).
     - One short risk-reversal line (shipping, warranty, or return policy).
   - 6 benefit-driven bullets (each 8-16 words) highlighting features → customer benefits → outcome. Include at least one bullet addressing the biggest objection from {{existing_pdp_and_reviews}}.
   - Short “How it works / Use scenarios” section with 3 H3 subheadings describing buyer use-cases tailored to {{audience}}.
   - 3 social proof blocks ready for placement (each block: 1-2 sentence testimonial, reviewer name/role, star rating if available, and suggested placement on page — e.g., hero, mid-page, near CTA). Source these from {{existing_pdp_and_reviews}} and mark any inferred details as [ASSUMED].
   - Technical specifications table (compact, 6-12 rows) drawn from {{product_spec_sheet}}.
   - 8 FAQ Q&A entries that proactively address top objections and purchase hurdles (shipping, returns, compatibility, warranty, sizing, material safety, setup, longevity). Flag any legal/medical claims that need compliance review.
   - Recommended image and video captions (one caption per asset): hero image, 3 lifestyle images, 2 detail shots, 1 short demo video (15-30s).
   - Cross-sell / up-sell suggestions: 2-4 short lines of copy suggesting complementary products or bundles plus anchor text recommendations for internal linking.

3) SEO product snippet + metadata
   - SEO title (≤70 characters) optimized for {{primary_keyword}} and CTR.
   - Meta description (110-160 characters) that matches intent and includes a clear CTA.
   - Suggested URL slug (short, keyword-focused).
   - Suggested Hreflang or regional variant note if applicable to {{region_language}}.

4) Internal links + anchor text
   - List 4-6 internal link targets (anchor text → suggested URL path) that improve relevance and navigation (e.g., size guide, warranty page, related category, blog buying guide). Use logical slugs if exact URLs unknown.

5) Schema and technical SEO suggestions
   - Provide which structured data to implement (Product, Offer, AggregateRating, Review, FAQPage) and short examples for each field (price, currency, availability, ratingValue, reviewCount). Mark any estimated values as [ASSUMED].
   - Provide canonical tag suggestion and recommended open graph title/description for social sharing.

6) Brief editorial/UX guidance (1-2 bullets)
   - Readability target (Flesch or grade level) and mobile-first copy length guidance.
   - Where to place proofs and CTAs for maximum conversion.

Formatting and deliverables rules (must be followed in the output you generate)
- Start output with the 3-5 bullet content brief/spec.
- Then output the full page content using the exact section order in step 2 above.
- Use the provided {{primary_keyword}}, {{search_intent}}, {{audience}}, {{region_language}}, {{content_type}}, {{product_spec_sheet}}, and {{existing_pdp_and_reviews}} inside the copy where appropriate.
- Clearly label any assumed fact with [ASSUMED] and separate assumptions from verified facts.
- Provide copy-ready lines only — no design notes, no HTML, no CSS.
- For any numeric claims (e.g., battery life, % improvements), include the source line or mark as [ASSUMED] and recommend verification.

Tone, length, and CTA constraints
- Tone: persuasive, authoritative, and concise; adapt to the tone specified in the extra inputs if provided.
- Desktop hero copy: ≤35 words; mobile hero summary ≤20 words.
- Benefit bullets: exactly 6 bullets.
- FAQ answers: 1-3 short sentences each.
- Provide 3 CTA text variants and 2 urgency/scarcity micro-lines (if applicable).

Delivery: produce a single Markdown document with all sections requested, ready to paste into the CMS.

## Output Format
Enforce this structure in the returned content:
- H1: main headline (use {{primary_keyword}})
- H2: subheads (e.g., Features, Specs, Reviews, FAQs)
- H3: sub-sections (use for use-cases and each FAQ)
- Use short paragraphs (1-2 lines), bullet lists for benefit bullets and CTAs, and a compact table for technical specs.
- Markup hints: show table as plain Markdown table; show JSON-LD snippets only as brief labeled examples (not full code).
- At the top include the 3-5 bullet content brief/spec before the page content.

## Guardrails
- Do not invent statistics or study results. If a figure is needed and not in inputs, mark as [ASSUMED] and recommend verification.
- Separate verified facts (explicitly from {{product_spec_sheet}} or {{existing_pdp_and_reviews}}) from assumptions.
- Apply E-E-A-T: include a short “expert note” line when any safety, legal, or medical claim is present; use cautious language and recommend compliance review.
- Match the stated {{search_intent}}; do not add unrelated buying guides or broad category-level content when intent is transactional.
- Keep claims compliant: flag any claim that could trigger regulatory review (health, medical, warranty beyond standard).
- Use the specified {{region_language}} language and spelling conventions for all copy and metadata.

## Examples
Keyword → 3-bullet content brief excerpt

- Keyword: insulated travel mug
- Intent: purchase (transactional) — users ready to buy or compare
- Conversion goal: Add-to-cart with free-shipping threshold; primary CTA: Add to Cart
- Top use-cases: commuter coffee, outdoor hiking, office desk — focus on leakproof design and temperature retention

Use this template to paste into ChatGPT, Claude, or Gemini. Generate the full PDP content, metadata, FAQs, schema suggestions, image captions, and internal linking recommendations in one response.

Variables

Usage Notes

Not for

Do not include

One‑shot PDP Research Prompt — Conversion Template

Generate a full, CMS-ready Product Detail Page (H1, scannable hero, 6 benefit bullets, 3 social proofs, specs table, 8 FAQs, image/video captions, SEO snippet, internal links, and schema suggestions) from product specs, buyer use-cases, existing PDP copy and reviews.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Search Intent

Provide the key details needed for this variable.

Primary Keyword

Provide the key details needed for this variable.

Audience

Provide the key details needed for this variable.

Region Language

Provide the key details needed for this variable.

Content Type

Provide the key details needed for this variable.

Product Spec Sheet

Provide the key details needed for this variable.

Existing Pdp And Reviews

Provide the key details needed for this variable.

Rules

Canonical Examples

Input: Product: 16 oz double-wall stainless steel insulated travel mug. Keyword: "insulated travel mug". Intent: purchase (transactional). Audience: US commuters, coffee drinkers, gift buyers. Region/language: en-US. Product spec sheet: 16 oz, double-wall vacuum insulated, stainless steel 18/8, leak-resistant lid, dishwasher-safe (lid handwash recommended). Existing PDP & reviews: average 4.5★; praise for temperature retention and build; occasional reports of lid leaking under pressure.

Loading result...

Failed to load output.


H1: insulated travel mug

- Target keyword & intent
- Primary CTA: Add to cart
- Top use-cases: commuter coffee, office desk, travel
- Key proof: 4.5★ avg review praising heat retention

H2: Features, Specs, Reviews, FAQs

H3: How it works / Use scenarios

Hero: Insulated Travel Mug — Keeps coffee hot for hours. Primary CTA: Add to cart. 3 micro benefits. 6 benefit bullets. 8 FAQs. Schema examples and editorial guidance.

Why it works: This example demonstrates a conversion-focused PDP that matches transactional intent: an exact-match H1, short benefit-led hero, concise CTAs, and six tightly worded benefit bullets that map features to outcomes. Objections from reviews (lid leaks) are explicitly addressed in benefit bullets, FAQs, and risk-reversal copy. SEO snippet and schema are included with assumptions flagged.

Input: Product: wireless noise-cancelling earbuds. Keyword: "noise cancelling earbuds". Intent: purchase (transactional). Audience: growth marketers, remote workers, commuters in US/EU. Region/language: en-US. Product spec sheet highlights: Active Noise Cancellation (ANC), Bluetooth 5.3, IPX4 water resistance, 30-hour total battery life with case [SPECIFIED in input]. Existing PDP & reviews: reviewers praise ANC and call clarity; a few mention fit discomfort on long sessions.

Loading result...

Failed to load output.


H1: noise cancelling earbuds

- 3-5 bullet brief
- Hero area with H1, short description, micro-benefits, CTAs, risk reversal
- Six benefit bullets mapping features to outcomes
- 3 use-case H3s
- 3 social proof blocks from reviews
- Specs table, 8 FAQs, captions, cross-sells
- SEO title/meta, internal links, schema suggestions, editorial notes

Why it works: This example targets high-intent buyers searching for noise cancelling earbuds: headline uses exact-match keyword, hero copy is concise and mobile-optimized, benefit bullets tie features to outcomes, and the FAQ proactively addresses comfort, compatibility, warranty, and charging. Battery life and other numeric specs are taken from the provided spec sheet and flagged when assumed.

Works Best With

Works best when you provide concise product specs, target audience, and 1-2 verified review excerpts