Below is a compact, practical guide and ready-to-use prompt templates you can use with ChatGPT (or any LLM) to create high-quality product pages, category pages, and CMS pages for PrestaShop. Use them as-is or adapt to your brand, data format, and workflow.
Key principles (what every good prompt should include)
- Context: tell the model it’s writing for PrestaShop and which fields you need.
- Goal: SEO, conversions, clarity, brand voice, multilingual output, or all of these.
- Audience & tone: who is the buyer and what voice to use (friendly, technical, premium).
- Constraints: character limits, HTML allowed tags, SEO keyword density, avoid repetition, keep factual values untouched.
- Input format: provide a sample product row or JSON schema to avoid ambiguity.
- Output format: ask for structured output (CSV, JSON, or table) to make import easy.
- Validate: keep SKUs, EAN/UPC, prices and attributes unchanged—only enrich text.
Useful length guidelines (adjust to your shop)
- Meta title: ≤ 60–70 chars
- Meta description: ≤ 150–160 chars
- Short description: 80–300 chars (summary shown in listings)
- Long description: HTML allowed, can be 300–2000+ chars
- URL slug: short, lowercase, hyphen-separated, no stopwords
Allowed HTML (recommended) — instruct the model to use only simple tags:
, , , , , - ,
, /.
Examples and reusable prompt templates
1) Single product — full page (short + long + SEO + attributes)
Prompt:
You are an e‑commerce copywriter for a PrestaShop product page. Produce finished content for one product using the provided product data. Keep all factual fields (SKU, price, EAN, dimensions, attributes) exactly as given. Use only the allowed HTML tags:
, , , - ,
, , . Use the given primary keyword and related keywords naturally.
Input data:
Name: [product_name]
Brand: [brand]
Category: [category]
SKU: [sku]
Price: [price]
EAN13: [ean]
Short features (comma separated): [feature1, feature2, ...]
Technical specs (key:value pairs): [Weight: 0.5 kg; Dimensions: 10×5×2 cm; Battery: 3000 mAh]
Primary SEO keyword: [keyword]
Language: [en/fr/…]
Tone: [friendly/technical/luxury]
Output (JSON):
{
"name": "...",
"meta_title": "...", // <= 65 chars, includes primary keyword
"meta_description": "...", // <=160 chars
"friendly_url": "...", // slug, lowercase, hyphen-separated
"short_description": "...", // HTML or plain, 1–3 sentences
"description": "...", // HTML full description with headings/bullets
"tags": ["tag1","tag2"],
"features": { "Color":"Black", "Battery":"3000 mAh" },
"bullet_points": ["...","..."] // 3–6 bullets
}
Example (filled, shortened):
Input:
Name: SolarPack 10W Portable Charger
Brand: SunCharge
Category: Portable Chargers
SKU: SP10W
Price: 39.99
Primary SEO keyword: portable solar charger
Language: en
Tone: friendly
Output:
{
"name":"SolarPack 10W Portable Charger",
"meta_title":"SolarPack 10W Portable Solar Charger – SunCharge",
"meta_description":"Portable 10W solar charger with fast USB-C charging, IP67 waterproof, ideal for camping and travel.",
"friendly_url":"solarpack-10w-portable-solar-charger",
"short_description":"
Compact 10W portable solar charger with USB-C fast charging, IP67 waterproof rating — perfect for outdoors and emergency power.
",
"description":"Reliable power on the go
The SolarPack 10W converts sunlight into USB power quickly and efficiently...
- Fast USB-C charging
- IP67 waterproof
- Foldable & lightweight
",
"tags":["solar","portable charger","camping"],
"features":{"Weight":"220 g","Dimensions":"18×10×2 cm","Battery":"No internal battery (panel only)"},
"bullet_points":["10W output for charging phones and lights","Rugged IP67 design for outdoor use","Compact & foldable for backpacking"]
}
2) Bulk generation (CSV/rows)
Prompt:
You will receive CSV rows with product columns: name, brand, sku, price, short_features, technical_specs, primary_keyword, language, tone. For each row, output a CSV row with these columns: name, meta_title, meta_description, friendly_url, short_description_html, description_html, tags (semicolon-separated), features_json, bullets (semicolon-separated). Respect length limits and allowed HTML. Keep factual columns unchanged. If any field is missing in input, generate the best output using given data.
Provide an example input row and the exact CSV output row (no extra text).
3) Category page (SEO + human copy)
Prompt:
You are writing a PrestaShop category page description and SEO metadata. Input: category name, target keyword(s), main product types in this category, brand(s), intended audience, tone. Output JSON:
{
"category_name":"...",
"meta_title":"...", // <= 60–70 chars
"meta_description":"...", // <=160 chars
"friendly_url":"...",
"top_description_html":"...intro with primary keyword...
",
"bottom_description_html":"Why buy from us
"
}
Example:
Input:
Category: Mountain Bikes
Keywords: mountain bikes, trail bikes
Audience: intermediate riders, outdoorsy, 25–45
Tone: enthusiastic, expert
Output (excerpt):
meta_title: "Mountain Bikes - Trail & Cross Country | ShopName"
meta_description: "Durable mountain bikes for trail and cross‑country riding. Choose from hardtail and full‑suspension models."
Best practices:
- Put the primary keyword early in the meta title and first sentence.
- Use one strong CTA in meta description sometimes ("Shop now", "Free shipping").
- Category pages should have a short intro (50–120 words) and a longer, keyword-rich bottom section for SEO (200–800 words) that answers buyer questions.
4) CMS page (About / Shipping / Returns / FAQ)
Prompt:
You are creating a PrestaShop CMS page. Inputs: page type (About/Shipping/Returns/FAQ/Privacy), store name, policies (shipping days, return window, costs), tone. Output: HTML content with clear headings, short paragraphs, an FAQ section (if relevant), and at least one CTA. Provide a plain-text meta_title and meta_description for the page (60/160 char limits). Return only JSON with fields: meta_title, meta_description, friendly_url, content_html.
Example: Returns page should include steps to initiate return, condition of returned items, who pays shipping, refund timeline, contact info.
5) SEO-only prompt (quick meta tags)
Prompt:
Given product name and top 3 features and primary keyword, create:
- meta_title (<=65 chars)
- meta_description (<=160 chars)
- friendly_url slug
- 3–5 tags
6) Translation/localization prompt
Prompt:
Translate the provided product meta and descriptions to [language]. Keep SEO keywords natural in target language. Produce both translated fields and a transliterated friendly_url (slug) using hyphens and local characters removed/converted where needed.
7) JSON/CSV output template for PrestaShop import
Ask the model to output CSV with columns matching your import tool (example columns below). Provide a small sample to copy format.
Columns example:
id;name;active;price;currency;description_short;description;meta_title;meta_description;link_rewrite;categories;tags;manufacturer;ean13;isbn;upc;reference;width;height;depth;weight;unit;available_for_order;show_price
Tips to avoid hallucinations and errors
- Don’t ask the AI to invent unique technical specs—only generate if provided; otherwise indicate "Not provided".
- For SKUs, EANs and prices, tell the model to echo input unchanged.
- Use system messages for global constraints (e.g., “Always output JSON only”).
- Test on 10–20 products first, validate import, adjust constraints.
- Keep brand voice and legal wording consistent — for legal pages, have a lawyer review.
Example "perfect" single-product prompt you can paste
You are an e‑commerce copywriter for a PrestaShop product page. Output ONLY JSON (no extra commentary). Allowed HTML tags: , , , - ,
, ,
. Keep the product's factual fields (sku, price, ean13, dimensions, attributes) unchanged. Use the primary_keyword naturally. Respect these character limits: meta_title <=65, meta_description <=160. Provide fields: name, meta_title, meta_description, friendly_url, short_description, description, tags (array), features (key:value), bullets (array). Input:
Name: [insert name]
Brand: [brand]
SKU: [sku]
Price: [price]
Primary keyword: [keyword]
Short features: [list]
Technical specs: [list]
Tone: [tone]
Language: [en/fr/…]
Output (example):
{ ...JSON as above... }
Quick checklist before running prompts at scale
- Provide consistent input schema (CSV/JSON).
- Fix or set canonical punctuation rules (quotes, dashes).
- Decide whether to allow LLM to create image alt text and captions.
- Decide how you will QA generated content (spot check SEO metrics, clarity, accuracy).
- Keep duplicates low — ask LLM to avoid copying manufacturer text verbatim.
If you want, I can:
- Create a ready-to-run CSV-to-LLM prompt that takes your CSV and returns a CSV ready to import into PrestaShop Manager.
- Generate a few sample product/cms outputs from a product sample you paste.
Which would you like to do next?
