Below is a concise, practical guide and ready-to-use prompt templates you can copy/paste and adapt for generating product, category and CMS content for PrestaShop using ChatGPT or other LLMs. It covers what to feed the model, how to instruct it, output formats for bulk import, SEO constraints, multilingual notes, and examples.
Quick checklist — data to provide with every prompt
- Product/category/CMS identifiers: SKU, ID, slug, category path (for mapping).
- Names/titles.
- Product facts: features, specs, materials, dimensions, colors, weight.
- Use cases, target audience, unique selling points (USPs), brand voice/tone.
- Keywords: main keyword + 2–4 secondary keywords.
- Required lengths and limits (meta title, meta description, short and long description).
- Images: filenames and primary image alt text hints.
- Language and locale (e.g., en_US, fr_FR).
- Any forbidden terms or claims (e.g., no medical claims).
General prompt-writing principles
- Start with role + goal: “You are an e‑commerce copywriter specializing in SEO for PrestaShop.”
- Be explicit about each output field and exact format (prefer JSON or CSV-ready).
- Give constraints (char counts, HTML allowed or not, tone).
- Provide examples of desired s (one or two sample lines).
- Ask for multiple variants when useful (A/B titles or 3 meta descriptions).
- Request a short checklist or tags to help mapping into PrestaShop fields (e.g., short_description, description, meta_title, meta_description, url_slug, image_alt).
Best-practice SEO constraints (recommended)
- Meta title: 50–70 characters (aim ~50–60).
- Meta description: 120–160 characters (aim ~140–155).
- URL slug: lowercase, hyphens, no stopwords if possible.
- H1 ~ same as product name but optimized if needed.
- Short description: 1–3 short sentences or 150–300 characters (for product listing).
- Long description: 100–400+ words depending on complexity and category.
Product prompt template (JSON output)
You can paste this into the ChatGPT prompt box and replace placeholders or provide a data table.
Prompt:
You are an e‑commerce copywriter and SEO specialist for a PrestaShop store. For each product described, produce the following JSON object exactly (no extra commentary). Adhere to character limits and provide clean HTML for the long description only (allowed tags:
,
, - , , ,
, ). Language: {{language}}. Tone: {{tone}}. Primary keyword: {{primary_keyword}}. Secondary keywords: {{secondary_keywords}}.
JSON schema (example — produce exactly these keys):
{
"sku": "{{sku}}",
"product_name": "{{name}}",
"url_slug": "{{slug (lowercase, hyphenated)}}",
"meta_title": "{{meta_title (50-70 chars)}}",
"meta_description": "{{meta_description (120-160 chars)}}",
"h1": "{{H1}}",
"short_description": "{{short_description (150-300 chars, no HTML)}}",
"long_description_html": "{{long_description (HTML allowed)}}",
"bullet_points": ["feature 1", "feature 2", "..."],
"technical_specifications": {"Weight": "1.2 kg", "Material": "Aluminium", "..."},
"image_alt_text": "{{short alt for primary image}}",
"call_to_action": "{{1-line CTA}}",
"seo_keywords": ["keyword1", "keyword2", "..."]
}
Constraints:
- Include the primary keyword in meta_title, meta_description, H1 and the first sentence of the long_description.
- Use plural or singular forms appropriately.
- For multilingual generation, return language code.
- Provide 2 meta_title variants and 3 meta_description variants in addition to the main fields (add keys meta_title_variants and meta_description_variants arrays).
Example filled input (for a single product):
sku: PSH-1234
name: "AeroLight Carbon Road Bike Helmet"
primary_keyword: "carbon road bike helmet"
secondary_keywords: "lightweight bike helmet, aerodynamic helmet"
language: en_US
tone: confident, technical but user-friendly
features: "carbon shell, 12 vents, adjustable fit, MIPS compatible"
specs: "weight 220 g, sizes S/M/L, material carbon composite"
image_filenames: "aerolight-front.jpg"
forbidden_claims: "no medical claims, no unproven safety statements"
Category prompt template
Prompt:
You are an SEO copywriter and eCommerce content specialist. For the category "{{category_name}}" produce a JSON object with these keys:
{
"category_id": "{{id}}",
"category_name": "{{category_name}}",
"url_slug": "{{slug}}",
"meta_title": "{{meta_title (50-70 chars)}}",
"meta_description": "{{meta_description (120-160 chars)}}",
"h1": "{{H1 for category page}}",
"short_description": "{{short description 100-200 chars}}",
"long_description_html": "{{long HTML description (100-400 words)}}",
"image_alt_text": "{{category image alt}}"
}
Constraints: include main keyword once in H1 and first sentence; include top 3 product subcategories if provided; format long_description_html with and for benefits and subcategories.
CMS page template (About, Shipping, Returns, FAQs)
Prompt:
You are a professional web copywriter. For the CMS page titled "{{page_title}}" produce this JSON:
{
"page_slug": "{{slug}}",
"page_title": "{{page_title}}",
"meta_title": "{{meta_title (50-70 chars)}}",
"meta_description": "{{meta_description (120-160 chars)}}",
"h1": "{{H1}}",
"content_html": "{{HTML content with headings, paragraphs and FAQ schema}}",
"structured_faq": [{"question":"Q","answer":"A"}, ...]
}
Constraints: content_html should be structured with H2s, short paragraphs (2–4 sentences), and an FAQ section if applicable. Avoid company internal jargon; use customer-focused language.
Example product prompt (short, ready-to-use)
Below is a short practical prompt you can paste and change variables:
You are an e‑commerce SEO copywriter. Create product copy for this product: name="AeroLight Carbon Road Bike Helmet", sku="PSH-1234", primary_keyword="carbon road bike helmet", secondary_keywords="lightweight bike helmet,aerodynamic helmet", features="carbon shell;12 vents;adjustable fit;MIPS compatible", specs="weight 220 g;sizes S/M/L;material carbon composite", language="en_US", tone="confident and technical but approachable". Output JSON with keys: sku, product_name, url_slug, meta_title (50–65 chars), meta_description (120–155 chars), h1, short_description (max 300 chars), long_description_html (HTML, include a 3-bullet features list), bullet_points (array), technical_specifications (object), image_alt_text, call_to_action. Include two meta_title variants and three meta_description variants.
Prompt engineering tips for batch processing and imports
- Ask for JSON or CSV-ready output with consistent keys for automatic mapping to PrestaShop import module.
- Use SKU as the primary key so you can match generated fields back to your product feed.
- Keep prompts consistent across batches; feed a table of product rows in one prompt if model supports long inputs (or use small batches).
- Set temperature low (0–0.3) for factual SEO copy; increase (0.6–0.9) for creative category names/marketing headings.
- For reproducibility, use system messages to set s and rules (if your interface supports system messages).
Multilingual & localized content
- Provide locale-specific keywords and units (metric vs imperial).
- Ask the model to localize idioms, spelling, punctuation, and currency.
- Example: "Translate and localize into fr_FR; use metric units; keep SEO keywords translated to French."
Quality & compliance checks
- Ask the model to produce a short QA checklist for each item it generates (e.g., "meta_title length X, meta_description length Y, primary keyword present? yes/no").
- Validate claims against product data; don’t invent specs. If a field is missing, ask the model to say "MISSING_FIELD: [which]" rather than guessing.
- Manually review a sample batch before publishing.
Good vs poor prompt examples
- Poor: "Write a product description for a helmet."
- Good: "You are an e-commerce SEO copywriter. For the product 'AeroLight Carbon Road Bike Helmet' (sku PSH-1234) produce JSON with keys sku, product_name, url_slug, meta_title (50–65 chars), meta_description (120–155 chars), h1, short_description (max 300 chars), long_description_html (include 3 benefits and a 4-item bullet list), include image_alt_text. Use primary keyword 'carbon road bike helmet' and include it in meta_title, meta_description, H1 and first sentence."
Final checklist before you run a batch
- Ensure product data fed into prompt is accurate and complete.
- Set output format (JSON) and character limits.
- Run 1–5 samples, review for factual accuracy and voice.
- Tweak prompts and retest.
- Integrate into import pipeline and keep backups of original content.
If you want, I can:
- Generate a ready-to-use prompt file tailored to your catalog size (single product, 50 products, 1000+).
- Create a JSON schema mapped exactly to PrestaShop import fields.
- Produce 3 example product outputs using the template so you can test imports.
Which of those would you like me to do next?
