I can’t open that link, but I can give you a complete, practical guide and ready‑to‑use prompt templates for generating PrestaShop product pages, category descriptions, and CMS pages with AI (ChatGPT or similar). Use these to get SEO‑ready, brand‑consistent content in structured output you can paste into PrestaShop or import as CSV/JSON.
Quick checklist (what to include in every prompt)
- Brand voice (tone, desired reading level)
- Target audience and geography
- Purpose (SEO, conversion, information)
- Exact fields you need (name, short description, long description HTML, meta title, meta description, friendly URL, tags, features, attributes, combinations, schema)
- Required keywords (primary + 2–4 secondaries)
- Length constraints (characters or words) and formatting rules (HTML allowed? bullet points?)
- Don’t-invent rule for specs; if unknown, say “leave blank” or “ask”
- Output format (JSON, CSV row, HTML block)
- Number of variations or language translations required
Core prompt components (use these in every prompt)
1. System/role instruction: “You are an expert ecommerce copywriter and SEO specialist for X brand/category.”
2. Brand and audience: short description with tone examples.
3. Product/category/CMS data: include SKU, features, specs, images, existing copy if any.
4. Requirements: list fields, character limits, SEO keywords, formatting.
5. Constraints: no invented specs, slug rules, markup rules.
6. Output format: strict JSON or CSV with exact keys, or HTML snippet.
7. Optional: provide 1–2 examples (few-shot) of ideal output.
Useful length guidelines (common SEO & PrestaShop practical limits)
- Meta title: ~50–60 characters (keep under 70)
- Meta description: 120–160 characters (keep under 160)
- Short description: 120–300 characters (front‑page / listing)
- Long description: 150–800+ words depending on product complexity
- Friendly URL: lowercase, hyphens, no special chars
- Tags: comma-separated short phrases
Templates — copy & paste and fill
1) Basic product description (single product, quick)
You can paste this to ChatGPT or your LLM prompt box.
Prompt:
You are an expert ecommerce copywriter and SEO specialist for [BRAND NAME]. Write product content for PrestaShop using only the data provided. Do NOT invent any technical specs or materials. If info is missing, leave those fields empty or write "TBD".
Product data:
- SKU: [SKU]
- Name: [Product name]
- Category: [Category name]
- Key features (bullets): [feature1; feature2; ...]
- Materials/specs: [spec1; spec2; ...]
- Target audience: [e.g., young professionals, parents, etc.]
- Primary keyword: [primary keyword]
- Secondary keywords: [keyword2, keyword3]
Requirements:
- Output JSON only with these keys: name, short_description, description_html, meta_title, meta_description, friendly_url, tags, features_bullets, attributes.
- short_description: max 250 characters (no HTML).
- description_html: full HTML description (use
,
, - ,
if needed).
- meta_title: ≤70 chars; include primary keyword.
- meta_description: 130–155 chars; include primary keyword and one secondary if natural.
- friendly_url: lowercase slug version of name; max 100 chars; use hyphens.
- tags: comma-separated.
- features_bullets: array of 3–6 short bullets.
- attributes: JSON object with keys exactly as supplied in “Materials/specs” (if empty, leave {}).
Tone: [e.g., friendly, premium, technical, playful]. Target persona: [one sentence].
Do not use emojis. Do not invent specs. If anything is ambiguous, set as "TBD".
Produce the JSON only.
2) SEO-optimized product + JSON-LD schema (advanced)
Prompt (fill fields):
You are an ecommerce SEO writer and JSON-LD specialist. Create PrestaShop product fields and a Product JSON-LD schema for the product below.
Product: [full product info: sku, name, manufacturer, price, currency, availability, images, features, materials, color, size, weight, dimensions, warranty, gtin if any]
Requirements:
- Provide two outputs in JSON: "product_fields" and "product_schema".
- product_fields must include: name, short_description (≤220 chars), description_html, meta_title (≤70 chars), meta_description (≤155 chars), friendly_url, tags (array), features (array), attributes (object), canonical_url (if provided).
- description_html should include one H2 and bullet list of core benefits. Write for conversions.
- meta fields must include primary keyword [PRIMARY_KEYWORD].
- product_schema must be valid JSON-LD according to schema.org/Product including offers (price, currency, availability), sku, name, image array, description (short), brand, aggregateRating only if rating data is provided (otherwise omit), review only if reviews provided (otherwise skip).
- Friendly URL slug must be lowercase hyphenated version of name.
- If any spec is missing, set the JSON field to null (do not invent).
Output exactly valid JSON with two keys: "product_fields" and "product_schema".
3) Category description (SEO + buyer intent)
Prompt:
You are an SEO writer. Create an SEO-optimized category page for PrestaShop.
Category data:
- Category name: [name]
- Top keywords: [primary and 3 secondaries]
- Target audience: [e.g., budget shoppers, eco-conscious, professionals]
- Tone: [e.g., informative & trustworthy]
Requirements:
- Output JSON with keys: name, description_html, meta_title (≤70), meta_description (≤155), friendly_url, h1 (optional), intro_snippet (100–150 chars), product_highlights (3 bullets).
- description_html should include a short intro, 3 subheadings for shopper concerns (quality, selection, shipping or size), and a closing CTA.
- Include internal linking suggestions as a list of slugs (e.g., "/brand-x", "/sale") — you may suggest generic slugs if specifics not provided.
- Keep SEO keywords used naturally.
4) CMS page (About Us, Shipping Policy, FAQ)
Prompt (fill):
You are a UX writer and ecommerce copywriter. Create a CMS "About Us" page.
Input:
- Company name: [name]
- Year founded, location, mission statement, unique selling points (USPs)
- Tone: [e.g., friendly, formal]
Requirements:
- Output HTML for CMS with sections: short intro H1, "Our Story" H2, "What We Offer" H2 with bullet USPs, "Sustainability / Promise" H2, "Call to Action" H2 with a short button text suggestion.
- Also return meta_title and meta_description optimized for brand search (≤70 and ≤155 chars).
- Keep under 600 words. Output JSON with keys: page_html, meta_title, meta_description, friendly_url.
5) Bulk generation (CSV input to output JSON array)
Prompt:
You can ask the LLM to parse a CSV table pasted inline or say “I will upload CSV.” Example prompt:
You will receive CSV rows with columns: sku,name,category,features,materials,price,currency,images (pipe-separated). For each row, generate a JSON object with fields: sku,name,short_description,description_html,meta_title,meta_description,friendly_url,tags,attributes,price,currency,images. Use brand voice: [X]. Do not invent specs. Return a JSON array of objects only.
Practical example (filled basic product) — prompt + expected type of output
Prompt (short):
Brand: Northern Wool Co. Tone: warm, artisanal, premium but accessible. SKU: NW-123. Name: "Alpine Merino Beanie". Features: "100% merino wool; breathable; machine washable". Primary keyword: "merino beanie". Secondary: "warm winter hat", "breathable beanie". Output JSON with fields as in template 1.
What you should expect:
- short_description: 1–2 sentences with primary keyword
- description_html: 2–4 paragraphs + benefits
- meta_title/meta_description contain keyword and CTA-s wording
- friendly_url: alpine-merino-beanie
- features_bullets as array of concise benefit statements
Prompting tips and best practices
- Provide as much structured data as possible (specs, images, price). The model won’t guess exact specs reliably.
- Use "Do not invent" repeatedly and instruct to set null/TBD for missing data.
- Ask for strict JSON only if you intend to parse output programmatically; include exact key names.
- Use examples (1–2 few-shot) of ideal outputs to teach the model s.
- For SEO: give main & related keywords, desired keyword density is not necessary; ask to include keyword once in meta title and meta description and 2–3 times in long description naturally.
- For multilingual stores: request translations, but advise feeding a language tag and asking for native-level phrasing. Example: “Translate to French (France) and return the same JSON structure but with language code 'fr' and translated fields.”
- To avoid hallucinations: include "If you don’t have the product measurement/specs, set the spec to null and add a footnote 'specs missing'." Also add "Do not list features not provided."
Common output formats to use
- JSON for importing (e.g., module or API)
- CSV row if you need to paste into a spreadsheet importer
- HTML snippet for the PrestaShop WYSIWYG long description
- JSON-LD for rich snippets
Sample copy-paste prompt (ready-to-use, multi-field, strict JSON)
You can paste and fill the bracketed parts:
You are an ecommerce copywriter and SEO expert for [BRAND]. Produce PrestaShop-ready product content. Do NOT invent specs. If a spec is missing, set the field to null.
Product:
- SKU: [SKU]
- Name: [Product Name]
- Manufacturer: [Manufacturer]
- Price: [price] [currency]
- Key features: [feature1;feature2;...]
- Materials/specs: [key:value;key2:value2;...]
- Primary keyword: [primary]
- Secondary keywords: [k2,k3]
- Target audience: [audience]
- Tone: [tone]
Output format:
Return a single JSON object with keys:
name, sku, manufacturer, price, currency, short_description, description_html, meta_title, meta_description, friendly_url, tags (array), features (array), attributes (object keyed by spec name), product_schema (JSON-LD object).
Constraints:
- short_description ≤250 chars, meta_title ≤70 chars, meta_description ≤155 chars
- friendly_url lower-case hyphen slug
- description_html may contain ,
, - ,
- product_schema must be valid schema.org/Product; include offers with price and availability only if provided
- Do not invent specs or reviews. Set unknown fields to null.
Produce only JSON.
Pitfalls to avoid
- Vague prompts: “Write a product description” → not enough context. Give product data and goals.
- Allowing hallucination: LLMs will invent specs unless told not to.
- No output format: you’ll get prose not parsable data.
- Changing brand voice midstream: give consistent tone parameters and examples.
If you want, I can:
- Convert a spreadsheet of products into PrestaShop-ready JSON using one of the templates above,
- Create 3 SEO variations per product for A/B testing,
- Produce translations for specific languages,
- Generate a JSON-LD schema for a product you paste.
Tell me: do you want ready prompts only, or shall I generate content for a sample product/category/CMS page? If you paste one product’s data I’ll return the exact JSON/HTML you can import.
