Below is a practical, copy-pasteable guide you can use to get reliable, SEO-ready, PrestaShop-ready product descriptions, category pages, and CMS pages from an LLM (ChatGPT or similar). It contains: a short explanation of what makes a “perfect” prompt, a universal prompt template, many ready-to-use examples (single product, bulk CSV, category, CMS), JSON/CSV output formats and quick tips to avoid hallucinations.
Why prompts matter (brief)
- Give clear context: what system/store, product attributes and constraints.
- Give exact output format (JSON or CSV headers) so you can import directly.
- Provide SEO constraints (title length, meta description length, keywords).
- Provide tone, audience, and language for consistent brand voice.
- Give examples/few-shot if you need a specific s.
Universal prompt template (fill placeholders)
Use this as your master prompt pattern:
System message (optional, for ChatGPT):
You are an e-commerce copywriter specialized in PrestaShop. Produce factual, concise, SEO-optimized product/category/CMS content in the exact format requested. Avoid adding facts not provided. If data is missing, leave the field blank or mark it
.
User prompt:
Create content for PrestaShop using the data below. Output must be JSON (or CSV) exactly matching the schema: [list headers]. Follow these rules:
- Language: {{language}}.
- Tone: {{tone}} (e.g., friendly, premium, technical).
- Product Name length: <= {{n}} characters for title.
- Meta title <= 60 chars; meta description 120–160 chars.
- Short description: 1–3 bullet sentences, max {{n}} characters.
- Long description: detailed HTML-ready content with headings, bullets, and 3 benefits + 2 usage examples. Include a 3–5 item “Key features” bullet list.
- Include 3 SEO keywords: {{keyword1}}, {{keyword2}}, {{keyword3}}. Use them naturally, do not stuff.
- Output fields not listed as when data absent.
- Do not invent numbers (weights, dimensions, price). If required, ask for them.
- Provide recommended product tags and an SEO-friendly slug (lowercase, hyphens).
Product data:
{ product_name: "{{NAME}}", brand: "{{BRAND}}", category: "{{CATEGORY}}", price: "{{PRICE}}", features: ["{{feat1}}", "..."], materials: "{{MATERIALS}}", colors: ["red","blue"], images: ["{{image1_url}}","..."], sku: "{{SKU}}", ean: "{{EAN}}", short_desc: "{{short}}", long_desc: "{{long}}", target_audience: "{{audience}}" }
Then ask for the exact format (give JSON schema or CSV headers) and optionally 3 short variants for A/B testing.
Practical examples
1) Single product — JSON output (import-ready)
Prompt:
You are an e-commerce copywriter. Using data below produce JSON with these fields exactly: name, slug, meta_title, meta_description, tags (array), short_description (HTML), description (HTML), features (array), seo_keywords (array), image_urls (array), manufacturer, reference, ean13, price, quantity. Language: English. Tone: friendly & persuasive. Meta title max 60 chars; meta description 120–160 chars. Use SEO keywords naturally and include a 3-sentence product summary at the top of the description. Do not invent numeric specs. If a field is missing, set it to null.
Data:
{ name: "EcoBrew Stainless Travel Mug 500ml", manufacturer: "EcoGoods", reference: "EB-500TM", ean13: "1234567890123", price: "19.99", quantity: "150", features: ["double-wall insulation", "spill-proof lid", "BPA-free"], image_urls: ["https://example.com/images/eb500-1.jpg"] , target_audience: "commuters" }
Expected output (example):
{ "name": "EcoBrew Stainless Travel Mug 500ml", "slug": "ecobrew-stainless-travel-mug-500ml", "meta_title": "EcoBrew 500ml Travel Mug — Double-wall Insulated", "meta_description": "Keep drinks hot or cold for hours. EcoBrew 500ml stainless travel mug with spill-proof lid. Ideal for commuters.", "tags": ["travel mug","insulated mug","EcoGoods"], "short_description": "500ml stainless travel mug with double-wall insulation and a spill-proof lid — perfect for commuters.
", "description": "Keep drinks at the right temperature
Short 3-sentence summary...
- Double-wall insulation — keeps beverages hot for 6 hours
...
", "features": ["Double-wall insulation","Spill-proof lid","BPA-free"], "seo_keywords": ["insulated travel mug","stainless travel tumbler","EcoGoods mug"], "image_urls":[...], "manufacturer":"EcoGoods","reference":"EB-500TM","ean13":"1234567890123","price":"19.99","quantity":"150" }
2) Product descriptions — three variants (short, medium, long)
Prompt elements:
- Ask for a 10–15 word short sell line for the product (for product listings).
- A 2–3 sentence short description for product card (max 160 chars).
- A long description (HTML) with H2/H3, 3 benefits, 2 usage examples, and 4 bullet “Key features.”
3) Bulk CSV generation from rows (for CSV import)
When you generate lots of products, request CSV with exact PrestaShop headers. Example headers (common PrestaShop import):
"Active (0/1)","Name","Categories (x,y,z...)","Price tax excluded","Tax rules ID","Wholesale price","Description","Short description","Tags","Meta title","Meta description","Meta keywords","Image URLs","Quantity","Reference #","EAN13","UPC","Weight","Additional shipping cost","On sale (0/1)","Condition"
Prompt:
Given the following CSV rows of product data, return a CSV with the PrestaShop import headers above, filling fields from the input and generating SEO-friendly meta title/meta description/slug and tags. Keep meta title <=60 chars, meta description 120–160 chars. Use target language English. If a field is missing, leave blank.
Then paste your product rows (or provide them as JSON for the assistant to convert). Ask for output as plain CSV.
4) Category page prompt
Requirements: meta_title (<=60), meta_description, slug, H1, 150–300 word category description (SEO-targeted), 3 benefits for buying in this category, 5 filter attribute suggestions (e.g., brand, price range, size), image alt text, suggested internal cross-links to up to 3 related categories.
Prompt example:
Create a PrestaShop category entry for the category: "Women’s Waterproof Jackets". Output JSON with fields: name, slug, meta_title, meta_description, h1, description_html, filters (array of attributes), image_alt, related_categories (array). Tone: trustworthy, outdoor-oriented. Include 3 purchase benefits and 3 FAQ bullets (short Q/A) for the category.
5) CMS page prompt templates (About, Shipping, Returns, Privacy)
Common fields: title, slug, meta_title, meta_description, content_html, effective_date (if needed), legal_disclaimer. Provide tone and length and required legal points (e.g., refund period 30 days, shipping carriers, processing time). Ask for plain HTML (no external CSS), with H2 sections and bullet lists for steps.
Prompt example:
Write a PrestaShop CMS page for "Shipping & Delivery". Language: English. Tone: clear & helpful. Include sections: Shipping methods and carriers, Processing times, Shipping costs & free shipping threshold, International shipping notes, Tracking and support. Output fields: title, slug, meta_title, meta_description, content_html. Keep meta_description <=155 chars.
6) SEO additions: slug, FAQ schema, JSON-LD
Add instructions to output a small JSON-LD snippet for product schema (name, description, image, offers.price, offers.priceCurrency, sku, brand) so you can paste it into the CMS or product template.
7) Multilingual support
Prompt:
Translate and localize the following product content into French, German and Spanish. Do not translate brand names or SKU. Keep tone consistent. Output as separate JSON objects per language with the same fields.
8) Tone, factual safety, and hallucination avoidance
- Tell the model explicitly: “Do not invent specs, weights, warranty periods, or technical claims. If such data is missing, mark it .”
- For pricing/taxes/shipping, mark assumptions as and provide the assumption.
- For any claim requiring certification (e.g., ‘organic’, ‘CE certified’), require the user to provide proof. Otherwise do not state it.
9) System message and settings suggestions
- System message: “You are an e-commerce content generator for PrestaShop. Output must be valid JSON/CSV and adhere to formatting rules.”
- Temperature: 0.0–0.3 for factual outputs; 0.4–0.7 for creative variants.
- Max tokens: increase when generating long descriptions or many items.
- Ask for 3 variants per description for A/B testing.
10) Example templates you can copy/paste
Single product JSON template prompt:
You are an e‑commerce copywriter. Using this product data, produce a single JSON object exactly with fields:
name, slug, meta_title, meta_description, tags, short_description, description, features, seo_keywords, image_urls, manufacturer, reference, ean13, price, quantity.
Follow rules: meta_title<=60 chars, meta_description 120–160 chars, short_description max 160 chars, description in HTML with H2 and bullets, include 3 benefits and 2 usage examples. Don’t invent specs. Language English. Tone: premium.
Data:
{ name: "{{NAME}}", features: ["{{feat1}}","{{feat2}}"], images: ["{{url1}}"], manufacturer: "{{BRAND}}", reference: "{{SKU}}", ean13:"{{EAN}}", price:"{{PRICE}}", quantity:"{{QTY}}" }
Bulk CSV template prompt:
Given these product data rows in JSON, produce a CSV with headers:
"Active (0/1)","Name","Categories (x,y,z...)","Price tax excluded","Description","Short description","Tags","Meta title","Meta description","Image URLs","Quantity","Reference #","EAN13"
Generate SEO-friendly values for meta fields and tags. Use English. Keep meta lengths as specified.
Validation checklist (what to check after AI output):
- Are SKUs, EANs, and numeric specs unchanged and exact?
- Is meta_title <= 60 chars? meta_description <= 160 chars?
- Does the slug contain only lowercase letters, numbers, and hyphens?
- Is HTML safe? (no script tags)
- Any invented claims? (warranty, certifications)
- Image URLs exist and are reachable.
- Run the CSV/JSON through a test import in a sandbox before production.
Bonus: quick examples (copyable)
Short product description prompt:
Write a 20–40 word product teaser for product {{NAME}} aimed at {{audience}}. Include the main benefit and a CTA phrase no longer than 8 words.
Category description prompt:
Write a 200-word SEO-optimized category description for "{{CATEGORY NAME}}" targeting keyword "{{PRIMARY_KEYWORD}}". Include 3 bullets (benefits), 2 suggested filters, and one internal link anchor text suggestion.
CMS Privacy page prompt:
Write a privacy policy page section for an EU store (GDPR). Include data collected (name, email, address), purpose of processing, legal basis, data retention period, user rights and contact email. Output as HTML.
Closing tips
- Start with a “seed” example entry (few-shot) so the model learns your format.
- Prefer structured outputs (JSON/CSV) to reduce manual editing.
- Keep temperature low for factual exports; raise temp for creative marketing copy.
- Always verify legal/technical claims and do one import test.
If you want, tell me:
- One sample product (name + features + images + SKU + price)
and I’ll generate a ready-to-import JSON/CSV row, meta tags, slug and 3 description variants for that product.
