Below is a compact, practical guide plus ready-to-use prompt templates you can paste into ChatGPT (or other LLMs) to generate PrestaShop-ready product, category, and CMS content. It follows a simple “perfect prompt” structure you can reuse and customize.
Quick overview — the “perfect prompt” anatomy
- Role: Tell the model who it is (e.g., “You are an e‑commerce copywriter and SEO specialist”).
- Context/Goal: Describe purpose (product listing, category landing page, CMS policy).
- Inputs: Provide product data or CSV row fields (name, brand, features, specs, target audience, use cases).
- Constraints: SEO limits, tone, language, formatting rules (no invented specs, slug rules).
- Output format: Be explicit (JSON, CSV row, plain text with labels, or HTML).
- Example: Show one example input → desired output for clarity.
- Clarify follow-ups: Ask the model to ask clarifying questions when data is missing.
General SEO/format recommendations (use in constraints)
- Meta title: aim for <= 60 characters.
- Meta description: ~140–160 characters.
- URL slug: lowercase, hyphens, no special chars.
- Short description (product listing): 50–200 characters (concise benefit-focused).
- Long description: HTML allowed; use headings, bullets, and 1–3 call-to-action lines.
- Avoid inventing specs or claims; mark unknown values as [TBD] or ask.
Templates — copy/paste and replace placeholders
1) Product content (single product) — JSON output
Prompt:
You are an e‑commerce copywriter and SEO specialist. Given the product data below, produce a PrestaShop-ready JSON object with these keys:
name, brand, reference, price, slug, meta_title (<=60 chars), meta_description (<=160 chars), meta_keywords (comma list), short_description (plain text, 50–200 chars), description (HTML — use
, , and show features/benefits), bullet_features (array of 5 concise bullets), technical_specs (object of key:value), tags (comma list), recommended_categories (array).
Constraints:
- Do not invent numeric specs; if missing, insert "[TBD]" for that key.
- Slug: lowercase, hyphen-separated, max 80 chars, letters and numbers only.
- Tone: {tone} (replace e.g., friendly, professional, luxury).
- Language: {language}.
Product data:
name: {product_name}
brand: {brand}
reference: {sku}
price: {price}
features: {feature1; feature2; ...}
specs: {Battery life: 10h; Weight: 150g; Waterproof: IPX4}
target_audience: {target_audience}
use_cases: {use_case1; use_case2}
Example: [Optional — include a one-line example here]
If any required info is missing, ask a clarifying question before producing the final JSON.
Example of filled output (abbreviated):
{
"name": "Acme UltraNoise Earbuds",
"brand": "Acme",
"reference": "ACM-UEB-01",
"price": "79.99",
"slug": "acme-ultranoise-earbuds",
"meta_title": "Acme UltraNoise Earbuds — 10h Battery, ANC",
"meta_description": "Wireless earbuds with ANC, 10h battery, and ergonomic fit. Perfect for commuting and workouts.",
"meta_keywords": "wireless earbuds, ANC, workout earbuds",
"short_description": "Active noise-cancelling earbuds offering 10 hours of playtime and secure fit for commuting and exercise.",
"description": "
Acme UltraNoise Earbuds
Enjoy immersive sound and active noise cancellation...
Buy now — free shipping
",
"bullet_features": ["Active Noise Cancellation", "10-hour battery", "Fast charge 15 min = 2h", "Ergonomic design", "IPX4 splash resistant"],
"technical_specs": {"Battery life": "10 hours", "Weight": "35 g", "Bluetooth": "5.2"},
"tags": "earbuds,ANC,wireless,workout",
"recommended_categories": ["Audio > Earbuds", "Deals"]
}
2) Product CSV/batch generation (multiple rows)
Prompt:
You will receive multiple products as CSV input with columns: name, brand, sku, price, features, specs, target_audience, tone, language, categories. For each row produce a JSON array item with the same keys as in the single-product template. Output only valid JSON (an array of objects). Follow the same constraints: meta_title <=60, meta_description <=160, slug rules, no invented specs (use "[TBD]"). If important info is missing in a row, include a "notes" field explaining what’s missing.
3) Category page content
Prompt:
You are an SEO‑savvy e‑commerce copywriter. Create a PrestaShop category page for this category. Output an object with keys:
name, slug, meta_title (<=60 chars), meta_description (<=160 chars), description (HTML, 150–350 words), intro (1 short sentence for listing pages, 50–100 chars), suggested_subcategories (array), landing_cta (one short CTA sentence).
Inputs:
category_name: {category_name}
main_products_overview: {e.g., headphones, audio accessories}
target_audience: {who buys this}
tone: {tone}, language: {language}
Constraints:
- Use keyword variations naturally.
- No claims you can’t verify.
- Add an H2 "Why choose [category_name]" with 3 benefit bullets.
4) CMS page (About, Shipping, Returns, Privacy) — structured HTML
Prompt:
You are an experienced e‑commerce copywriter. Create a CMS page for "{page_type}" (e.g., About Us, Shipping Policy, Returns & Refunds, Privacy Policy). Output JSON with:
title, slug, meta_title (<=60), meta_description (<=160), content (HTML with headings, short paragraphs, bullet lists where appropriate), last_updated (today’s date), internal_notes (if we must add legal details).
Constraints:
- Tone: {tone}, language: {language}
- Include an H2 "Contact us" with email and phone placeholders.
- For policy pages, include timelines (e.g., "Refunds processed in 5–7 business days") only if provided; otherwise use “[INSERT TIMEFRAME]” and leave a note in internal_notes.
Ready-to-use example prompts you can paste
A) Product (short, ready to paste)
You are an e‑commerce copywriter and SEO specialist. Write PrestaShop-ready fields for this product:
name: "Vela Ceramic Coffee Mug 350ml"
brand: "Vela",
sku: "VELA-MUG-350",
price: "12.90",
features: "high-grade ceramic; microwave safe; dishwasher safe; matte finish",
specs: "capacity: 350ml; weight: 320g",
target_audience: "coffee lovers, gift buyers",
tone: friendly, language: English.
Produce JSON with keys: name, brand, reference, price, slug, meta_title (<=60 chars), meta_description (<=160 chars), meta_keywords, short_description (50–150 chars), description (HTML), bullet_features (5 items), technical_specs (object), tags (comma list), recommended_categories. Do not invent specs. Use hyphen slugs.
B) Category (About to paste)
You are an SEO e‑commerce writer. Create a category page for "Eco Kitchenware". Include name, slug, meta_title, meta_description, description (200–300 words HTML), intro (1 sentence for category lists), suggested_subcategories, landing_cta. Tone: professional, language: English. Include benefits and eco credentials paragraph (generic — do not claim certifications unless provided).
Tips and best practices
- Always include the product’s unique facts (size, materials, numbers) in the prompt to avoid hallucinations.
- Use iterative prompting: first ask the model to propose meta and slug, then generate the long description with approved slug and title.
- For batch imports: request JSON or CSV columns matching your PrestaShop import template.
- Validate: always review generated specs, measurements, certification claims.
- Use placeholders like [TBD] for missing critical info and prompt model to list those missing fields.
Short checklist to include in any prompt
- Role defined
- Inputs provided
- Tone & language
- Field/SEO limits
- Slug rules
- Output format required (JSON/CSV/HTML)
- “Do not invent specs” rule
- Ask clarifying question if data missing
If you want, tell me:
- one product or give a CSV row now and I’ll generate the actual JSON you can paste into PrestaShop, or
- which CMS page you want (About, Shipping, Returns) and I’ll create the full HTML content ready to paste.
