Below is a compact, practical guide plus ready-to-use prompt templates you can paste into ChatGPT (or other LLM) to generate PrestaShop-ready content for products, categories, and CMS pages. It covers structure, required fields, formatting constraints, SEO best practices, bulk generation, and example prompts.
Quick principles
- Be explicit: tell the model the output format, character limits, required fields and the tone/brand voice.
- Provide context: product attributes, target audience, keywords, language, locale, and any s rules.
- Ask for machine-friendly output: JSON/CSV/Markdown table, with HTML allowed only where PrestaShop needs it (full description).
- Constrain length: meta title ~50–70 chars, meta description ~120–160 chars, short description ~1–3 sentences, long description HTML allowed.
- Include examples (few-shot) when you need consistent patterns or complex mapping (combinations, attributes).
- Use low temperature (0–0.3) for consistent output; higher for creative copy.
Essential fields to ask for (PrestaShop-focused)
- name (product title)
- short_description (brief HTML/text for product list)
- description (long HTML description for product page)
- meta_title (~50–70 chars)
- meta_description (~120–160 chars)
- link_rewrite (SEO-friendly slug, lowercase, hyphen-separated, no special chars)
- price (if you want generated)
- ean13 / upc / reference / sku
- features / attributes / combinations (size/color)
- tags
- image_alt (descriptive alt text)
- category_path (where it should be assigned)
- canonical or redirect suggestions (if applicable)
General prompt structure (recommended)
1. System role: e.g., “You are an expert e-commerce copywriter and SEO specialist for PrestaShop.”
2. Context: product data, audience, brand voice, locale, language.
3. Requirements: list fields, formats, char limits, HTML allowance.
4. Output format: JSON/CSV, sample output structure, and if necessary, one example.
5. Constraints: do not add extra fields; use plain ASCII for slugs; avoid promotional overclaims; etc.
6. Temperature: set low for reliability.
Single-product prompt template (JSON output)
System:
You are an e-commerce copywriter and SEO specialist experienced with PrestaShop. Produce consistent, concise, SEO-optimized product data ready for import.
User:
Product context:
- Name: {product_name}
- Type: {product_type/category}
- Brand: {brand}
- Key features/bullets: {feature1; feature2; ...}
- Technical specs: {spec1:value; spec2:value; ...}
- Target audience: {audience}
- Primary keyword: {primary_keyword}
- Secondary keywords: {keyword2, keyword3}
- Locale and language: {en-US, fr-FR, etc.}
Style and constraints:
- Tone: {e.g., friendly, premium, technical}
- short_description: max 200 characters, plain text or minimal HTML (
...
)
- description: up to 2–4 paragraphs in HTML, can include
- for features
- meta_title: 50–65 characters max, include primary keyword
- meta_description: 120–160 characters, include primary keyword and CTA
- link_rewrite: SEO slug, lowercase, hyphen-separated, no punctuation, ASCII only, max 80 chars
- image_alt: 100 characters max, describe image content and include keyword if natural
- Provide features as an array of {"name": "...", "value": "..."} and attributes/combinations if given.
Output format: Return a single JSON object exactly with these keys:
{
"name": "...",
"short_description": "...",
"description": "...",
"meta_title": "...",
"meta_description": "...",
"link_rewrite": "...",
"image_alt": "...",
"features": [{"name":"", "value":""}, ...],
"attributes": [{"name":"", "options":["",""]}, ...],
"tags": ["", "..."]
}
Do not include extra commentary. Use the provided data and fill gaps sensibly.
Example user fill (for you to replace placeholders):
- Name: "AeroFit Running Shoes"
- Type: "Men's running shoes"
- Brand: "Aero"
- Key features: "breathable mesh; responsive foam midsole; rubber outsole"
- Technical specs: "weight: 240g; drop: 8mm; sizes: 40-47"
- Primary keyword: "running shoes men"
- Tone: "energetic, performance-focused"
- Locale: en-US
Bulk CSV/JSON generation prompt (multiple SKUs)
System:
You are an e-commerce product data writer. Generate consistent product entries in CSV/JSON for PrestaShop import.
User:
I will provide a list of rows with minimal attributes. For each row, expand into full product data. Requirements:
- Return JSON array of objects with keys: name, short_description, description, meta_title, meta_description, link_rewrite, image_alt, category_path, price, reference, features, attributes, tags
- Respect the character limits and slug rules above
- If size/color combinations are present, output combinations as an array with sku/ref and price delta if any
- Keep language: {language}, currency: {currency}
Input rows (example):
1) sku: AF-001; name: AeroFit Running Shoes; color: Black; sizes: 40,41,42; price: 99.99; primary_keyword: "running shoes men"
Output: [ { ... }, ... ]
Category page prompt
System:
You are a content strategist and SEO copywriter. Create category content optimized for PrestaShop category pages.
User:
Category: {category_name}
Parent category path: {Home > Sports > Running}
Target keywords: {primary_keyword, secondary_keyword}
Language/locale: {en-US}
Tone: {tone}
Requirements:
- meta_title: 50–65 chars
- meta_description: 120–160 chars
- short_description: 1–2 sentences visible above products (max 250 chars)
- description: 2–4 short paragraphs or an HTML block (include
and for benefits or buying guide)
- link_rewrite: slug
- suggest 5 related tags and 5 subcategory names (if appropriate)
- include an internal linking suggestion sentence for CMS pages (e.g., “See our Buying Guide: [link]”)
Output format: JSON object with keys: name, meta_title, meta_description, short_description, description_html, link_rewrite, tags, suggested_subcategories
CMS page prompt (about, delivery, returns, FAQ)
System:
You are an e-commerce content writer who writes clear legal-friendly CMS pages optimized for conversion and SEO.
User:
Page type: {About / Delivery / Returns / FAQ / Size Guide}
Brand tone: {friendly / formal / concise}
Locale: {en-US}
Requirements:
- Provide page title, meta_title, meta_description
- Provide full HTML content, structured with headings , , and where needed
- Include an FAQ section if appropriate (Q/A pairs)
- Keep meta_description 120–160 chars
- Provide suggested internal links to other pages
Output: JSON with keys: title, meta_title, meta_description, content_html, internal_links, faq (if any)
Examples (single product filled)
Using the single-product template above; sample output (conceptual — you’d get JSON back):
{
"name": "AeroFit Running Shoes",
"short_description": "Lightweight men's running shoes with breathable mesh and responsive cushioning for daily training.
",
"description": "Performance & Comfort
The AeroFit Running Shoes combine breathable engineered mesh with a responsive foam midsole...
- Breathable mesh upper
- Responsive foam midsole
- Durable rubber outsole
",
"meta_title": "AeroFit Running Shoes — Lightweight Running Shoes for Men",
"meta_description": "AeroFit men's running shoes with breathable mesh and responsive cushioning. Ideal for daily training. Free shipping over $50.",
"link_rewrite": "aerofit-running-shoes",
"image_alt": "AeroFit men's black running shoes, breathable mesh upper",
"features": [{"name":"Weight","value":"240 g (size 42)"}, {"name":"Drop","value":"8 mm"}],
"attributes": [{"name":"Color","options":["Black","Blue"]}, {"name":"Size","options":["40","41","42"]}],
"tags": ["running shoes","men","training"]
}
Practical tips and refinements
- Validate slugs: strip accents, keep ASCII; replace spaces with hyphens; remove punctuation.
- Test character limits by asking the model to count characters or by post-processing.
- Use few-shot examples to force consistent HTML structure or attribute ordering.
- For translations, ask for both language and locale and request that all text be returned in target language only (or include both source+target fields).
- For bulk work, generate machine-readable IDs (SKU) and keep output deterministic (temperature 0–0.2).
- For images: request descriptive alt text and caption suggestions; keep alt concise and factual.
- If you want microcopy (button text, short CTAs), include separate keys (e.g., buy_button_text).
- If PrestaShop field lengths differ in your version, replace the suggested limits in the prompt.
Short “copy-paste” prompts
1) Single product (quick)
You are an expert PrestaShop SEO copywriter. Create product copy for:
Name: {name}
Brand: {brand}
Features: {features}
Specs: {specs}
Primary keyword: {keyword}
Language: {lang}
Return JSON: name, short_description (max 200 chars), description (HTML), meta_title(<=65 chars), meta_description(<=160 chars), link_rewrite, image_alt, features[], attributes[], tags[]. No extra text.
2) Category quick
Create SEO content for category "{category_name}" with primary keyword "{keyword}". Return JSON: name, meta_title, meta_description, short_description (<=250 chars), description_html (2–4 paragraphs, include ), link_rewrite, tags[].
3) CMS quick
Write a {page_type} page for {brand}, tone {tone}, locale {lang}. Return JSON: title, meta_title, meta_description (<=160), content_html (with H1/H2), internal_links[].
Final notes
- Always test sample outputs by importing a small batch into PrestaShop to check field mapping and formatting.
- Keep a standard mapping sheet (CSV header order) and adapt the model’s JSON keys to your import tool.
- Use programmatic validation (slug regex, char counts, missing fields) before full import.
If you want, tell me:
- one product (name, features, keywords, locale) and I’ll generate a ready-to-import JSON entry, or
- a sample CSV/Excel header you use, and I’ll provide a tailored prompt that returns rows matching that exact schema.
