Below is a practical, copy‑pasteable guide with ready-to-use prompt templates and best practices to get predictable, high‑quality outputs from an LLM for PrestaShop products, categories and CMS pages.
Why a “perfect” prompt?
- Gives the model clear context (role + goal).
- Supplies precise inputs (product specs, keywords, audience).
- States strict constraints (length, format, SEO limits).
- Specifies a machine‑readable output (JSON/CSV/HTML) so you can import or paste directly into PrestaShop.
- Prevents hallucinations by instructing the model to only use provided info.
Core elements every prompt should include
- Role: e.g., “You are an e‑commerce copywriter and SEO specialist.”
- Input data: all available fields (name, brand, SKU, features, specs, price, images, audience, USPs).
- Output spec: exact fields and formats you need (short/long descriptions, bullets, meta tags, slug, alt text, JSON‑LD).
- Language + tone + market (e.g., “French (France), formal, B2B”).
- Constraints: length limits, HTML allowed/forbidden, character counts for SEO.
- Safety: “Only use the info provided. If a field is unknown, return MISSING: field_name.”
- Variants: “Provide 3 variations” if you want A/B options.
- Temperature suggestion (for the model): “Use low creativity (temperature 0–0.3) for consistent outputs.”
Useful character limits (SEO basics)
- SEO title: ~50–60 chars (max 60)
- Meta description: ~150–160 chars (max 160)
- Short description / excerpt: ≤160 chars
- Image alt: ≤125 chars
- URL slug: lowercase, hyphens, no stopwords if you prefer
Product prompts
Template (single product -> JSON output)
System: You are an expert e‑commerce copywriter and SEO specialist for PrestaShop stores.
User: I will provide product data. Only use the provided data. If a required field is missing, return "MISSING: field_name". Output must be valid JSON (no extra commentary) with these fields:
- name
- brand
- sku
- short_description (<=160 chars, plain text)
- long_description_html (HTML allowed, up to 400 words, include 2–4 short paragraphs and a 5‑item bullet list of features)
- bullets (array of 4–6 short bullets, each <=120 chars)
- seo_title (<=60 chars)
- seo_description (<=160 chars)
- url_slug (lowercase, hyphen-separated)
- meta_keywords (comma-separated)
- image_alt_text (<=125 chars)
- json_ld (Product schema JSON‑LD with: name, sku, brand, offers.price, offers.priceCurrency, offers.availability, image (first image URL), description (short_description), url)
Language: {language}
Tone: {tone}
Target audience: {audience}
Primary SEO keyword(s): {keywords}
Secondary keywords: {secondary_keywords}
Data: {paste product fields here: name, brand, sku, specs, features list, materials, dimensions, weight, color, images urls, price, availability, warranty, unique_selling_points}
Example prompt filled (short):
Language: English
Tone: friendly professional
Target audience: active runners aged 20–45
Primary SEO keyword: breathable running shoes
Data: name: AeroRun 3, brand: TrailForge, sku: TF-AR3-BLK, features: breathable knit upper; responsive foam midsole; 8 mm drop; 200g (size 42); water resistant; color: black/red; image: https://example.com/images/tfar3-black.jpg; price: 119.99; availability: InStock; warranty: 2 years
Notes:
- Set temperature low (0–0.3) for repeatability.
- Ask for 3 variations if you need A/B tests: “Provide 3 variations, label Variation A/B/C.”
Example short product prompt (copy/paste)
You can copy the template above and replace placeholders with your product data.
Category prompts
What to provide:
- Category name
- Parent category (if any)
- Target keywords
- Number of subcategories or types
- Typical products (list 3–6 representative products)
- Tone and length (short intro 70–120 chars, long description 150–400 words)
- SEO title and meta description lengths
Template
System: You are an SEO content writer specialized in e‑commerce category pages.
User: Create category content for PrestaShop. Output must be JSON with:
- category_name
- short_intro (1–2 sentences, <=120 chars)
- long_description_html (150–400 words, include benefits and who it’s for, internal links in HTML format to 3 sample subcategory URLs)
- seo_title (<=60 chars)
- seo_description (<=160 chars)
- url_slug (lowercase hyphen)
- recommended_filters (array of filter names and example values)
Language: {language}
Tone: {tone}
Target keywords: {keywords}
Representative products: {list}
Example use: “Category: Trail Running Shoes. Representative products: [AeroRun 3, MountainGrip X, StreamLite].”
CMS pages (About, Shipping, Returns, FAQ, Policy)
General CMS templates
- Identify page type: About, Shipping, Returns, Privacy, Terms, FAQ
- Provide business info: founding year, mission, guarantee, contact info, shipping regions, carriers, return window, return cost policy
- Tone, legal/regulatory constraints, language
About Us prompt (short)
System: You are a brand storyteller and UX copywriter.
User: Write an About Us page for PrestaShop. Output HTML with headings and paragraphs. Include these sections: Mission, Our Story (2–3 paragraphs), Why Buy from Us (3 bullets/trust signals), CSR or sustainability statement (if provided), CTA (one button line). Keep tone {tone}. Use {language}. Data: {company_name, year_founded, founders, mission_statement, unique_points, contact_email, store_url}.
Shipping & Returns (concise, friendly)
System: You write clear store policies.
User: Create a Shipping & Returns page. Output must include: Shipping times by region, cost examples, carriers, processing time, order tracking instructions, return window, conditions for returns, refund timeline, exceptions. Keep language plain and concise and use bullet lists.
FAQ generation
- Provide list of common customer questions or let model create 10 likely questions.
- Output as an ordered list or HTML collapsible Q/A.
Bulk generation (CSV/JSON for import)
If you need to generate content in bulk (many SKUs), give the model a CSV/TSV template and ask it to output CSV rows only.
CSV template (columns)
sku,name,brand,short_description,long_description_html,bullets,seo_title,seo_description,url_slug,image_alt_text,price,availability,json_ld
Prompt notes for bulk:
- Provide a CSV of base data (sku,name,brand,features,images,price,availability).
- Ask the model to output CSV rows with generated fields filled.
- Use a delimiter unlikely to appear in text (e.g., pipe | ) or request JSON array to avoid CSV escaping problems.
- Example: “I will paste 50 products. For each row produce these columns separated by |. Return only the rows, no header, no extra commentary.”
JSON bulk example is often safer (one JSON object per product).
Structured data (JSON‑LD)
- Always include a Product schema for product pages:
- @context, @type: Product, name, image (array), description, sku, brand: { @type: Brand, name }, offers: { @type: Offer, priceCurrency, price, availability, url }, aggregateRating (if available), review (if available).
- Prompt the model to fill missing numeric values as MISSING to avoid hallucinations.
Prevent hallucinations
- Insist: “Only use provided facts. Do not invent specs, materials, or certifications. If unknown, write MISSING: field_name.”
- For claims like “best”, “#1”, “award-winning”: require proof or mark as marketing claim and put it in quotes or as optional.
Examples: Ready-to-use prompts
1) Product single JSON (short)
System: You are an expert e‑commerce copywriter and SEO specialist.
User: Create product copy using only the data I provide. Output valid JSON with fields: name, brand, sku, short_description, long_description_html, bullets (array), seo_title, seo_description, url_slug, image_alt_text, json_ld. If any required field is missing, set it to "MISSING: field_name". Language: English. Tone: friendly professional. Primary keyword: breathable running shoes. Data: name=AeroRun 3; brand=TrailForge; sku=TF-AR3-BLK; features=breathable knit upper; responsive foam midsole; 8 mm drop; 200g (size 42); water resistant; color=black/red; image=https://example.com/images/tfar3-black.jpg; price=119.99; currency=USD; availability=InStock; warranty=2 years.
2) Category (short)
System: You are a content strategist for e‑commerce sites.
User: Write a category intro and SEO fields. Output JSON: category_name, short_intro (<=120 chars), long_description_html (200–300 words including internal links to /shoes/running-trail, /shoes/running-road, /shoes/stability), seo_title, seo_description, url_slug. Category_name=Trail Running Shoes. Language: English. Tone: energetic.
3) CMS About page (HTML)
System: You are a brand copywriter.
User: Write an About Us page in HTML with H1 and H2 headings, 3 short paragraphs, 4 trust bullets, and a final CTA (button text). Company: TrailForge; year_founded=2015; mission=make durable, eco-conscious gear for trail runners; founders=Anna Lee & Marco Diaz; contact=hello@trailforge.com. Tone: authentic, slightly informal.
4) Bulk CSV (instruction)
System: You are an automation assistant.
User: I will paste a CSV with columns sku|name|brand|features|images|price|currency|availability. Produce one output row per input, with columns sku|name|short_description|long_description_html|bullets_json|seo_title|seo_description|url_slug|image_alt_text|json_ld. Use | as delimiter. Return only the output rows with the same order, no header, no commentary.
Advanced tips
- Use system message or first line to lock role/constraints.
- Provide examples: include 1–2 example inputs + expected outputs to teach s.
- Request multiple variants and ask the model to mark A/B/C.
- For multilingual stores: generate translations for all fields; include locale codes (en_US, fr_FR) and ask for native idiomatic phrasing; ask the model to never translate brand names.
- For HTML fields: specify allowed tags (p, ul, li, strong, em, a).
- For import safety: always run outputs through a validation script that checks JSON/CSV format, character limits, and removes disallowed HTML.
- Tune model temperature: low for consistent copy, higher for creative taglines.
Quick checklist before running prompts
- Have all required product data in a standardized structure.
- Decide which fields you want auto‑generated (don’t let it invent price/size).
- Set a strict output format (JSON/CSV).
- Test with 5 products, verify, then scale.
- Add a step to QA: check factual fields and SEO lengths.
If you want, I can:
- Convert your PrestaShop product spreadsheet into a prompt-ready CSV template.
- Generate 3 sample product descriptions from a few product rows you paste.
- Produce JSON‑LD templates tailored to your store's currency and availability values.
Which would you like me to do now? Paste one product (or a few) and I’ll produce the exact JSON/HTML you can paste into PrestaShop.
