Here’s a practical, copy‑and‑pasteable guide to writing “perfect” AI prompts to generate product pages, category pages, and CMS pages for PrestaShop. Includes reusable prompt templates, examples, JSON/CSV output schemas for bulk imports, multilingual tips, and a quick QA checklist.
Quick principles (apply to every prompt)
- Provide clear context: what field(s) you need and where they will be used (short_description vs description vs meta_title).
- Provide constraints: character limits, use/avoid HTML, SEO keywords, tone, brand voice.
- Provide input variables: product name, brand, features, target audience, keywords, SKU, price, attributes, combinations.
- Ask for structured output (JSON, CSV row, or labeled blocks) to simplify importing.
- Add examples or few-shot pairs if you want a particular s.
- Specify uniqueness and avoidance: avoid copying manufacturer text verbatim; avoid unverified claims.
Common PrestaShop fields to output
- name
- short_description (used on list pages; usually <160–300 chars)
- description (full HTML allowed; long)
- meta_title
- meta_description (SEO snippet, <160 chars recommended)
- friendly_url / link_rewrite (slug)
- tags (comma-separated)
- features (key:value pairs)
- price_blurb / selling_points (bullet list)
- combinations / attributes (if applicable)
- image_alt_texts
- product_condition (new/refurbished)
- category_name (for category prompts)
- cms_title, cms_body_html, meta_title, meta_description (for CMS pages)
Product prompt templates
1) Single product — full structured JSON output (best for API/bulk)
Prompt:
You are an e-commerce copywriter for a PrestaShop store. Generate content for one product using the input data below. Output only valid JSON with these keys: name, short_description, description (HTML allowed), meta_title, meta_description, friendly_url, tags (comma separated), features (array of {"name","value"}), bullets (array), image_alt (array), seo_keywords (comma separated). Use the brand voice: modern, friendly, and concise. Make meta_description ≤155 characters. Make short_description ≤220 characters. Make friendly_url lowercase, hyphenated, no special chars. Avoid manufacturer copy. Ensure descriptions are unique and emphasize benefits and target audience. Input data:
{name}: {name}
{brand}: {brand}
{category}: {category}
{material}: {material}
{key_features}: {features_list}
{target_audience}: {audience}
{primary_keyword}: {primary_keyword}
{secondary_keywords}: {secondary_keywords}
Example of usage (replace placeholders):
{name}: "AquaFlow Stainless Water Bottle 750ml"
{brand}: "AquaFlow"
...
2) Single product — simple text blocks (for manual copy/paste)
Prompt:
Write product copy for {name} by {brand}. Produce the following labeled sections:
- Title:
- Short description (≤220 chars):
- Full description (HTML allowed, use
,
, - ):
- Meta title (≤70 chars):
- Meta description (≤155 chars):
- Friendly URL (slug):
- Tags (comma separated):
Tone: {tone}. Primary keyword: {primary_keyword}. Target audience: {audience}. Highlight {top_benefit} and include these features: {features_list}.
3) Product variants/combinations
Prompt:
Generate a CSV-friendly line for product {name} with variants. Provide header row and one or more product rows with columns: name, sku, attribute_color, attribute_size, price, stock, short_description, description, friendly_url. Include three variant rows (colors: red, blue, black; sizes: S, M, L). Keep descriptions concise and consistent. Primary keyword: {primary_keyword}.
Category prompt templates
1) Category page — SEO + HTML description
Prompt:
Write an SEO-optimized category description for the PrestaShop category "{category_name}". Output labeled sections:
- Category title:
- Intro (<=120 chars for page header):
- Full description (HTML, 2–4 paragraphs; include 2–4 bullet points of popular product types; include internal linking suggestions in plain text like "See: /category/subcategory"):
- Meta title (<=70 chars):
- Meta description (<=155 chars):
Target keyword: {category_keyword}. Tone: {tone}. Audience: {audience}. Avoid promotional slogans; be informative and include product examples.
CMS page templates (About us, Shipping, Returns, Size Guide)
1) About us page
Prompt:
Write a PrestaShop CMS "About Us" page for {shop_name}. Include:
- H1 title
- 3–4 paragraphs (brand story, values, what sets you apart)
- 4 trust-building bullet points (shipping, warranty, support hours, secure payments)
- Suggested meta_title and meta_description
Tone: warm, trustworthy, concise. Do not use generic phrases like "best in the world."
2) Shipping & Returns (legal s + customer-friendly)
Prompt:
Create a CMS page for Shipping & Returns. Include:
- H1
- Shipping options (standard, express) with expected delivery times and costs
- Returns policy step-by-step with timeframes and conditions
- Contact info blurb
- Short FAQ (3 questions)
- Meta title and meta_description
Keep language clear and customer-friendly. Specify country as {country}.
Multilingual & translation
- Provide source language and target language.
- Ask for SEO optimization in the target language using translated keywords.
Prompt:
Translate and SEO-optimize the following product copy into {target_lang}. Keep meta description ≤155 chars. Adapt friendly_url to be a natural slug in {target_lang}. Preserve brand voice: {tone}. Input text: {original_text}.
Examples of few-shot instructions (for s)
Add 1–2 examples: show an original product name and the EXACT output you want (short desc, long desc, meta), so the model mimics the s.
Output formats for bulk import
- JSON schema example:
{ "name":"", "short_description":"", "description":"", "meta_title":"", "meta_description":"", "friendly_url":"", "tags":"", "features":[{"name":"","value":""}], "bullets":[""], "image_alt":[""], "seo_keywords":"" }
- CSV header example (1-line): name,short_description,description,meta_title,meta_description,friendly_url,tags,features,image_alt,seo_keywords
Ask the model to output exactly one JSON object per product or CSV rows with safe escaping.
SEO & technical notes to include in prompts
- Provide primary and secondary keywords and ask the model to use them naturally (don’t keyword-stuff).
- Give character limits for meta fields.
- Specify whether HTML is allowed and which tags (e.g., allow
,
, - , ).
- Ask for friendly_url and image_alt_texts optimized for SEO.
- For schemas: require text-only for CSV or properly escaped JSON.
Tone, voice, and compliance
- Specify tone: professional, playful, technical, minimalist.
- Request avoidance of superlatives or unverifiable claims (e.g., "world's best") if you need compliance.
- For regulated products (medical, supplements), explicitly ask to avoid medical claims unless verified.
Quality-control prompts (post-generation checks)
- "Check this description for factual inconsistencies vs these inputs: {specs}."
- "Give me a second, shorter variant for A/B testing (shorter by ~30%)"
- "Return a readability score (Flesch-Kincaid) and suggest one edit to improve clarity."
Example full prompt (ready to paste)
You can copy this and replace the placeholders:
You are an e-commerce copywriter for PrestaShop. Generate one JSON object for the product with the following keys: name, short_description (≤220 chars), description (HTML allowed:
,
, - ), meta_title (≤70 chars), meta_description (≤155 chars), friendly_url (slug), tags (comma separated), features (array of {"name","value"}), bullets (array), image_alt (array). Voice: friendly, confident, focused on benefits. Primary keyword: {primary_keyword}. Secondary keywords: {secondary_keywords}. Input data:
name: {name}
brand: {brand}
category: {category}
material: {material}
features: {features_list}
target_audience: {audience}
price: {price}
Return only valid JSON. Do not include any extra explanation.
Common pitfalls to avoid
- Not providing character limits -> meta descriptions too long.
- Mixing fields (putting short description into meta title).
- Not specifying allowed tags -> model inserts non-supported HTML.
- Leaving out target keywords -> non-SEO copy.
- Asking for too many variations in one request (split into batches).
Quick QA checklist before importing into PrestaShop
- Character limits: meta_description ≤155, meta_title ≤70.
- Friendly URL: no spaces, lowercase, hyphens, no special chars.
- No unsupported HTML tags.
- No manufacturer copyright text or trademark violations.
- Check uniqueness (especially if bulk-generating).
- Validate CSV/JSON format and escaping.
If you want, I can:
- Convert one of your product spreadsheets (CSV) into AI prompts or prepare a single JSON line for import.
- Generate sample outputs for a demo product, category, and CMS page so you can see the exact format.
Which would you like next: a ready-to-import JSON example for a sample product, a CSV template for bulk generation, or help converting one of your real product rows?
