Below is a practical, copy‑and‑pasteable guide and set of prompt templates you can use to generate high‑quality product, category and CMS copy for PrestaShop with any LLM (ChatGPT). It includes field mappings, best practices, ready templates, and example prompts + expected output formats (JSON/CSV/HTML) so you can plug results directly into PrestaShop or your import tool.
Quick principles
- Be explicit: tell the model its role (e.g., “You are an expert e‑commerce copywriter and SEO specialist familiar with PrestaShop”).
- Provide structured inputs: include product data (name, key specs, use cases, target audience, keywords, images, categories).
- Request structured outputs: ask for JSON, CSV or HTML with exact field names matching your PrestaShop import.
- Give constraints: character limits, slug rules, tone, CTA, and whether HTML is acceptable.
- Include SEO guidance: primary & secondary keywords, meta length targets (meta title ~60–70 chars; meta description ~150–160 chars), and link_rewrite (slug) format.
- Ask for alt text and image captions.
- Use examples and ask for multiple variants (A/B titles, 1 short + 1 long description).
Common PrestaShop fields and recommended formats
- product_name: string
- reference (SKU): string
- link_rewrite: slug (lowercase, hyphen-separated, no special chars)
- short_description: HTML allowed, ~50–200 chars (shows on listings)
- description: HTML allowed, long product page content, up to several hundred words (detailed features, benefits, usage)
- meta_title: ~50–70 chars
- meta_description: ~140–160 chars
- tags: comma-separated keywords
- categories: list or primary category name
- price, wholesale_price, condition (new/refurbished), weight, availability
- features/specifications: list of key/value or HTML table
- images: filenames or URLs + alt text
- combinations/variants: JSON list of attribute => values
- visibility / active: boolean
Best practices & constraints to include in prompts
- Tone: neutral/technical, friendly, luxury, playful, etc.
- Audience: B2C/B2B, age range, experience level.
- Format rules: “Return only JSON,” or “Return HTML for the description field,” or “No fluff; each output must follow this template exactly.”
- SEO rules: include primary & secondary keywords naturally, avoid keyword stuffing.
- Slug rules: one line, lower-case, hyphen-separated, max ~100 chars.
- Character limits for meta fields: enforce exact max lengths.
- Avoid hallucination: instruct model to only use provided product facts; if missing facts, output placeholders or ask follow-up questions.
Product prompt template (single product, JSON output)
You can paste this and replace placeholders.
Prompt:
You are an expert ecommerce copywriter and SEO specialist familiar with PrestaShop. Using only the product facts provided, produce a single JSON object for importing into PrestaShop. Do not invent technical specs. Use HTML for short_description and description. Follow these constraints: meta_title max 70 chars, meta_description max 160 chars, link_rewrite must be lowercase hyphen-separated, short_description 50–200 chars, description up to 400–800 words with headings and bullet lists. Provide alt text for each image (max 125 chars). Output only valid JSON; do not add commentary.
Product facts:
- product_name: {PRODUCT_NAME}
- reference: {SKU}
- categories: [{CATEGORY1},{CATEGORY2}]
- main_image: {URL or filename}
- other_images: [{URL1},{URL2}]
- price: {PRICE}
- condition: {new|refurbished}
- weight: {WEIGHT}
- features: {key:value, ...}
- target_audience: {audience}
- primary_keyword: {keyword}
- secondary_keywords: [{kw1},{kw2}]
- benefits/use_cases: {short sentence list}
Output JSON fields must be:
{
"product_name": "",
"reference": "",
"link_rewrite": "",
"short_description": "",
"description": "",
"meta_title": "",
"meta_description": "",
"tags": [],
"categories": [],
"price": "",
"condition": "",
"weight": "",
"features": [{"name":"", "value":""}, ...],
"images": [{"url":"", "alt":""}, ...],
"variants": [{"attribute":"", "values": [""]}, ...]
}
Example filled prompt for a headphone:
(Replace placeholders with actual facts)
Example expected output (abridged):
{
"product_name": "Aurora Bluetooth Over‑Ear Headphones",
"reference": "AUR-BT-300",
"link_rewrite": "aurora-bluetooth-over-ear-headphones",
"short_description": "
Comfortable over‑ear Bluetooth headphones with 30h battery and active noise cancellation. Ideal for commuters.
",
"description": "
Long battery life & noise cancellation
...
",
"meta_title": "Aurora Bluetooth Over‑Ear Headphones – 30h Battery | Brand",
"meta_description": "Comfortable over‑ear Bluetooth headphones with 30h battery and active noise cancellation. Perfect for travel & work.",
"tags": ["bluetooth headphones","noise cancelling","over ear"],
"categories": ["Audio > Headphones"],
"price": "99.99",
"condition": "new",
"weight": "0.25",
"features": [{"name":"Battery life","value":"30 hours"},{"name":"ANC","value":"Yes"}],
"images": [{"url":"aurora-front.jpg","alt":"Aurora Bluetooth over‑ear headphones front view"}],
"variants": [{"attribute":"Color","values":["Black","White"]}]
}
Category prompt template
Prompt:
You are a copywriter experienced with PrestaShop categories and SEO. Given the category name and main keyword(s), produce a JSON object with these fields:
{
"name": "",
"parent": "",
"link_rewrite": "",
"description": "", // HTML, 2–4 short paragraphs with bullets of what buyers find here
"meta_title": "", // <=70 chars
"meta_description": "", // <=160 chars
"display_mode": "products/list", // optional
"thumb_image": "",
"active": true
}
Constraints: link_rewrite lower-case hyphen; description should include target audience and three buying benefits. Use provided keywords naturally.
Category example:
Input: name = "Running Shoes", keywords = ["running shoes","trail running shoes"], audience = "runners looking for cushioning and grip".
Output hint: meta_title "Running Shoes for Men & Women | Brand" etc.
CMS page prompt template (About, Shipping, Returns, FAQ)
Prompt:
You are an expert ecommerce content writer. Create a CMS page. Output only JSON:
{
"title": "",
"slug": "",
"content": "", // full HTML content, with H2/H3, paragraphs, bullet lists
"meta_title": "",
"meta_description": "",
"visible_in_footer": true,
"active": true
}
Constraints: slug lower-case hyphen, meta lengths as above. For policy pages include headings: Overview, How it works, Timeframes, Contact. For FAQ include question/answer pairs as JSON array.
Examples of practical prompts to copy
1) Product short & long copy + SEO (quick)
You are an expert ecommerce copywriter. Using the product facts below, write:
- one SEO title (meta_title) <=70 chars
- one SEO meta_description <=160 chars
- one short_description (100–150 chars) in HTML
- one long description in HTML with H2 headings and bullet lists
- 3 tag keywords
Return a JSON object with fields: product_name, meta_title, meta_description, short_description, description, tags. Facts: {paste facts}.
2) Bulk generation (CSV -> JSON list)
You have N rows of product facts in this CSV format. For each row produce one JSON object using this exact schema: [...fields...]. If a fact is missing, set value to null and include a "needs_review":true flag. Output a JSON array only.
3) Category SEO variations (A/B)
Write 3 meta_title variants (<=70 chars) and 3 meta_description variants (<=160 chars) for the category "Eco Kitchenware" targeting "eco-friendly cookware" and "non-stick ceramic". Return JSON: {"meta_titles":[...],"meta_descriptions":[...]}.
Tips for generating HTML descriptions for PrestaShop
- Use H2 for main features, H3 for sub-features.
- Use short paragraphs (1–3 sentences) and bullets for specs.
- Avoid inline CSS — PrestaShop themes handle styling.
- Include care instructions and compatibility sections for technical products.
- Add a short CTA at the end: e.g., “Buy now — free shipping over $50.”
Multilingual prompts
- Provide product facts in language X and ask "Translate and adapt to [target language], preserving tone and SEO keywords. Provide field values for language code [xx] and slug appropriate for that language."
- Output a separate JSON for each language, including translated meta fields and slugs.
Validation + anti‑hallucination
- Tell the model: “Do not invent specs; if data missing, return null or ask follow‑up questions.”
- Add a final key "source_verified": false or true if you provided external spec links the model should cite.
Example end-to-end prompt you can use immediately
You are an expert ecommerce copywriter & SEO specialist experienced with PrestaShop. I will give you product facts. Produce a JSON object exactly matching this schema:
{...include the schema from earlier...}
Rules:
- Use only supplied facts. If a fact is missing, set the field to null and add "needs_review":true.
- meta_title <=70 chars, meta_description <=160 chars.
- short_description: 80–150 chars (HTML
).
- description: HTML with at least two H2 headings and a bullet list of 4 features.
- link_rewrite: lowercase, hyphen-separated.
- Provide alt text for each image (<=125 chars).
Product facts: {paste actual product facts here}
Final checklist for production use
- Verify each meta field lengths (automate trimming if needed).
- Validate slugs for diacritics & length.
- Human‑review AI copy for factual accuracy and compliance (technical specs, claims).
- Add product-specific tags and attributes in your import mapping.
- Use a low temperature (0.0–0.3) when you want consistent, factual outputs.
If you want, I can:
- Convert one of your product spreadsheets into prompt-ready rows and create JSON outputs for direct import, or
- Give 3 ready prompts tailored to a product you paste here (I’ll produce the JSON result). Which would you like to do?
