Below is a practical guide + ready-to-use prompt templates you can copy/paste and adapt for generating PrestaShop product, category, and CMS-page content with ChatGPT (or other LLMs). Each template shows: role/context, what to produce, constraints (length, field names), SEO guidance, and a JSON/CSV output format that you can import or transform into PrestaShop fields.
General tips before you start
- Be explicit about the role and audience: “Act as an e‑commerce copywriter for [market/country/audience].”
- Specify channel and use: product page, category page, CMS page (help article), or meta tags.
- Give exact field names and required formats (e.g., link_rewrite = lowercase, hyphens, ASCII).
- State character limits for fields (meta title ~60–70 chars; meta description ~150–160 chars; meta keywords rarely used but include if needed).
- Request output in machine-friendly format (JSON or CSV) so you can import or script.
- Include keyword(s) and SEO intent; ask for tone and CTAs.
- Ask for variants (A/B titles, 3 short descriptions, FAQ list).
- Provide product attributes/data (sku/reference, features, materials, dimensions, use-cases, audience) as input — the richer the input, the better output.
Useful PrestaShop field names to include in prompt
- name, link_rewrite, description_short, description (long), meta_title, meta_description, meta_keywords, tags, image_alt, price, reference, ean13, upc, quantity, condition, visibility, active, id_category_default, features (key:value), attributes, related_products, minimal_quantity
Recommended character limits (practical)
- meta_title: up to 60–70 chars (aim ≤ 60)
- meta_description: ~150–160 chars
- short description: 150–300 chars (depends on theme)
- long description: 300–2000+ chars (rich, SEO-driven)
- link_rewrite: short, hyphenated, lowercase, no special chars
Template 1 — Single product (complete, JSON output)
Prompt:
You are an experienced e‑commerce copywriter and SEO specialist for [store name], selling to [country] customers in [language]. Create optimized PrestaShop product content for the following product. Use the provided product facts and produce only valid JSON with the exact keys below. Do not include extra commentary.
Product facts:
- product_name: [product name]
- brand: [brand]
- sku/reference: [SKU]
- materials: [materials]
- color/variants: [colors]
- dimensions/weight: [dimensions/weight]
- main_features: [bullet list]
- use_cases: [e.g., home office, outdoor]
- target_audience: [e.g., busy parents, cyclists]
- keywords: [primary_keyword, secondary_keyword]
- price: [xx.xx] (optional)
Output JSON keys and constraints:
{
"name": string, // product name (max 110 chars)
"link_rewrite": string, // lowercase, hyphenated, ASCII only
"meta_title": string, // <= 60 chars, include primary keyword
"meta_description": string, // <= 160 chars, include primary keyword
"meta_keywords": string, // comma separated
"tags": [string], // array of keywords/tags
"image_alt": string, // 8–12 words describing product + keyword
"description_short": string, // 100–250 chars, bullets OK
"description": string, // 400–1200 chars, SEO-rich, headings allowed
"features": [{"name": string, "value": string}], // list product features
"attributes": [{"name": string, "value": string}], // attributes for combinations
"recommended_products": [string], // product names/refs for cross-sell
"faq": [{"q":string, "a":string}] // 3 short QA pairs
}
Constraints:
- Use primary_keyword at least twice: once in meta_title and once in description.
- Tone: [tone, e.g., friendly professional].
- Audience: [audience].
- Output valid JSON only.
Example (fill with your actual product facts)...
How to use: replace the [bracketed] facts with your product data. The model will return a JSON ready to be processed into CSV/import.
Template 2 — Bulk CSV generation (products)
Prompt:
You will act as an e‑commerce content generator. For each row in the CSV below, produce a row with these output fields: name, link_rewrite, meta_title, meta_description, meta_keywords, tags, image_alt, description_short, description. Follow character limits and format link_rewrite lowercase-with-hyphens. Use the CSV input rows (the columns contain product_name, brand, key_features, keywords, target_audience). Return only CSV with header matching the output fields.
CSV input (example rows):
product_name,brand,key_features,keywords,target_audience
"Ergo Office Chair","SuperSeat","lumbar support; adjustable arms; mesh back","ergonomic office chair, adjustable chair","home office workers"
Notes:
- Keep meta_title ≤ 60 chars, meta_description ≤ 160 chars.
- Short description ≤ 250 chars.
- Make descriptions unique and avoid repeating product_name more than 3 times.
- Include primary keyword in meta and description.
Template 3 — Category page
Prompt:
You are an SEO‑focused copywriter. Create a category page description for the category: [category_name]. Store sells to [country], in [language]. Primary keyword: [keyword]. Secondary keywords: [list]. Produce:
- meta_title (≤60 chars)
- meta_description (≤160 chars)
- link_rewrite (lowercase, hyphens)
- top_paragraph: short intro 2–3 sentences (50–80 words) that matches user intent
- mid_section: 2–3 short paragraphs (200–400 words) covering benefits, how to choose, and top subcategories
- bottom_section: 2–3 FAQ items (question + 1–2 sentence answer)
Return JSON: {meta_title, meta_description, link_rewrite, top_paragraph, mid_section, bottom_faqs:[{q,a}]}
Template 4 — CMS page (about, help, how-to)
Prompt:
You are a technical writer for an e‑commerce CMS. Create a CMS page called “[page_title]” aimed at [audience] in [language]. Purpose: [purpose: e.g., “explain returns policy”]. Produce:
- page_title (H1)
- meta_title (≤60 chars)
- meta_description (≤160 chars)
- slug (link_rewrite)
- intro_paragraph (50–80 words)
- sections: list of sections with heading and 2–4 short paragraphs each
- checklist or steps (if relevant)
- 5 FAQs with short answers
Return JSON {page_title, meta_title, meta_description, slug, intro, sections:[{heading, body}], checklist_or_steps:[string], faqs:[{q,a}]}
Template 5 — Image alt, tags, and microcopy quick prompt
Prompt:
Given this product: [short product data]. Produce:
- 5 image alt texts (each 8–12 words, include primary keyword)
- 10 tags (comma separated)
- 3 product page microcopy lines for cart/button/stock (e.g., “Add to cart CTA”, “Stock message”)
Return JSON.
Prompt-level best practices (to get near “perfect” outputs)
- Provide examples: show one ideal output for a sample product.
- State strict output format and to produce only that format (e.g., only JSON or CSV).
- Provide required keywords, and how many times to include them.
- Give length/char limits per field and s/tone guidance.
- Tell the model to avoid repeated phrases or claims (e.g., “do not claim without evidence”).
- Ask for multiple variants (title A/B, 3 short descriptions) for A/B testing.
- If multilingual, request translation into specific languages and locale variations (en-GB vs en-US spelling).
- For bulk: provide the CSV rows with clear headers and ask for one output row per input row.
Examples (concrete product example)
Prompt:
Act as an e‑commerce writer. Product facts: name = “Commuter 20L Waterproof Backpack”, brand = “TrailPro”, materials = “recycled polyester”, features = “waterproof, padded laptop sleeve 15”, breathable straps, reflective trim”, audience = “urban cyclists, commuters”. Keywords: "waterproof commuter backpack, laptop backpack". Output only JSON with keys: name, link_rewrite, meta_title, meta_description, description_short, description, image_alt, tags (array), features (array). Meta limits: title ≤60 chars, description ≤160 chars.
Expected output (example simplified):
{
"name":"TrailPro Commuter 20L Waterproof Backpack",
"link_rewrite":"trailpro-commuter-20l-waterproof-backpack",
"meta_title":"Waterproof Commuter Backpack – TrailPro 20L",
"meta_description":"Waterproof 20L backpack with 15\" laptop sleeve and reflective trim—perfect for urban cyclists. Durable recycled polyester.",
...
}
Testing and QA
- Spot-check: ensure link_rewrite has no accented characters.
- Check meta lengths: trim if too long.
- Verify keywords are used naturally, not stuffed.
- Fact-check claims (waterproof vs water-resistant). Avoid legal/false claims.
- Run generated text through readability and SEO tools.
- For multilingual: have a native speaker review tone and idioms.
Common pitfalls to avoid
- Leaving link_rewrite with spaces or uppercase.
- Generating meta_text longer than search results show.
- Producing descriptions that repeat product name excessively.
- Using inconsistent terminology across variants.
- Making unverified performance claims (e.g., “lasts for years”) without evidence.
Quick checklist before running a prompt
- Provide product facts and keywords.
- Define expected output format (JSON/CSV).
- State field names and char limits.
- Specify tone and target audience.
- Ask for variations and FAQs.
Short prompt templates to copy/paste
Single-product JSON (short):
You are an e‑commerce SEO writer. Create PrestaShop fields for this product. Facts: name="[name]", brand="[brand]", features="[list]", keywords="[kw1,kw2]". Return only JSON with keys: name, link_rewrite, meta_title (≤60 chars), meta_description (≤160 chars), description_short (≤250 chars), description (400–700 chars), image_alt (8–12 words), tags (array). Tone: [tone]. Include primary keyword in meta_title and description.
Category page short:
Write a category page for "[category]" in [language]. Include meta_title ≤60, meta_description ≤160, link_rewrite, top_paragraph (50–80 words), 2 short sections (benefits + how-to-choose), and 3 FAQs. Target keyword: [keyword]. Return JSON.
If you want, tell me:
- One product (paste its facts) and I’ll craft the exact prompt filled in and give the JSON output example.
- Or paste several CSV rows and I’ll return the bulk prompt you can use with ChatGPT to generate ready-to-import CSV.
Would you like me to prepare a filled prompt for a real product or a sample CSV to test?
