if allowed; otherwise plain text. Provide 3 variants for short_description and meta_description (label them variant_1..variant_3 inside JSON). Ensure readability and include 3 image alt texts. Example input values: product_name = "Urban Waterproof Jacket", brand = "NorthLane", categories = ["Men > Outerwear","Sale"]. Now generate the JSON. Product prompt — short example (text you can paste) Create strict JSON for product import. Required fields: product_name, reference, price (EUR), quantity, short_description (<=320 chars), description (<=2000 chars), meta_title (<=70), meta_description (<=160), friendly_url slug, categories array, tags array, images array with alt text, brand, attributes array. Tone: active, concise, premium. SEO keywords: "waterproof jacket, men’s waterproof jacket, breathable outerwear". Return three variants for short_description and meta_description. No extra text — JSON only. Bulk product generation - Provide a CSV/JSON input with columns you have and ask the model to return matching rows as CSV/JSON. - Example prompt addendum: “Given this CSV input with columns [sku, name, brand, base_price, category, color_list], produce a CSV with columns [reference, product_name, price, quantity, short_description, description, meta_title, meta_description, friendly_url, categories, tags, images]. Use price with two decimals. Return CSV only.” Category — fields checklist - category_name - parent_category (or root) - description (short & long) - friendly_url (slug) - meta_title, meta_description - thumbnail image filename and alt - position / active (true/false) Category prompt template Prompt: You are an expert ecommerce content strategist. For each category below produce strict JSON: { "category_name":"", "parent":"", "description":"", "friendly_url":"", "meta_title":"", "meta_description":"", "thumbnail":{"filename":"", "alt":""}, "active":true }. Use [LANGUAGE], tone: [neutral/brand voice]. Target audience: [audience]. SEO keywords: [keywords]. Constraints: meta_title <=70, meta_description <=160, friendly_url lower-case hyphenated. Provide an internal short blurb (<=160 chars) for category listing and a longer SEO description (200–600 chars). Output JSON only. CMS pages — fields checklist - page_title - url_rewrite / friendly_url - meta_title - meta_description - content (HTML allowed? define) - summary/teaser - template (if using theme templates) - active (true/false) CMS prompt template Prompt: You are a professional copywriter for PrestaShop CMS pages. For each page produce JSON with { "page_title":"", "friendly_url":"", "meta_title":"", "meta_description":"", "summary":"", "content":"", "active":true }. Write content in [language]. Tone: [brand voice]. Content should include a short H1, two H2 subheads, one bullet list of 4 benefits, and a CTA sentence. If HTML is allowed, use simple tags:

,

,

,

,
• ,. Meta constraints: meta_title <= 70 chars, meta_description <=160 chars. Provide JSON only. Examples of high-quality micro-prompts (quick) - Product description (short): “Write a 150–220 char short description for [product_name] in [language] that highlights [key benefit] and includes keyword “[primary_keyword]”. Tone: [X].” - Meta description: “Write 155-char meta description for [product_name] with primary keyword and a clear CTA, no punctuation-heavy emojis.” - Alt text for images: “Give 6 distinct image alt texts of <=125 characters for images showing [scenes], include the keyword once each, avoid file names.” Advanced tasks and prompts - Variants/A-B testing: ask for 3 headline & description pairs optimized for conversions, noting primary CTA and target persona. - Combinations & stock: ask the model to return combinations as JSON with unique combination_ref and quantity per combo. - Translate or localize: ask the model to localize into a locale (e.g., fr-FR) and adapt measurements/currency/time formats. - Tone and readability: request grade-level (e.g., “write at Grade 8 reading level”), avoid passive voice, include product specs as bullet list. - SEO emphasis: ask for long-tail keyword variations, internal linking suggestions, H1/H2 structure for the category page. - CSV import-ready: “Return a CSV with these headers exactly: ... Do not include any extra columns. Escape commas inside fields with quotes.” Do’s and don’ts - Do: specify exact output format and validation rules; give examples. - Do: set character limits for meta fields and slugs format. - Do: include brand voice, target audience, and keywords. - Don’t: ask for “a good description” without specifying length, s, or fields — results will be inconsistent. - Don’t: ask for HTML if your import process will strip it — specify plain text if needed. - Don’t: forget to validate generated slugs/characters for non-ASCII or accented characters (or request ASCII-only). Quick checklist before running bulk generation - Confirm required PrestaShop columns and any import mapping (CSV headers exact). - Decide whether descriptions will include HTML. If yes, restrict allowed tags. - Provide example input row (one or two) in the prompt. - Limit meta tags to recommended lengths. - Ask for atlas/locale-specific units and currency formatting if needed. - Validate output programmatically (slug regex, JSON schema, CSV fields). One-line “perfect” prompt examples you can paste Product (single) — JSON, SEO, 3 variants: You are an ecommerce copywriter. Produce strict JSON for the product fields: product_name, reference, price, quantity, short_description (<=320), description (<=2000), meta_title (<=70), meta_description (<=160), friendly_url (slug), categories[], tags[], brand, images[{filename,alt}], attributes[]. Tone: premium, active. Target: urban professionals age 25–45. Keywords: "waterproof jacket, breathable jacket." Provide 3 variants for short_description and meta_description and 3 image alts. Return JSON only. Category: Produce JSON for category with fields: category_name, parent, description (short<=160, long 200–600), friendly_url, meta_title<=70, meta_description<=160, thumbnail{filename,alt}, active. Tone: neutral, target shoppers looking for rainwear. Return JSON only. CMS page: Create JSON for a CMS page: page_title, friendly_url, meta_title<=70, meta_description<=160, summary<=160, content (HTML with

  ,

  ,

  ,

  ,
  • ,): include 2 H2s, 4-item benefits list, and CTA. Tone friendly/expert. Return JSON only. Final tips - Start small: test prompts on 5–10 products first, validate imports, iterate. - Add post-processing scripts (slug sanitization, max lengths) to catch edge cases. - Keep provenance: store AI outputs before import to review SEO, accuracy, and compliance (claims, trademarks). - If you want, paste a sample product row/CSV here and I’ll produce a ready-to-import JSON/CSV with the fields you need. Would you like a ready-made CSV/JSON template tailored to your PrestaShop import columns? If so, paste your column headers or sample row and I’ll build the exact prompt and example output.