,
- ,
- , ,
) - Length & tone: e.g., short 25–40 words, long 120–300 words, tone: friendly/technical/luxury - SEO constraints: include main keywords, avoid keyword stuffing, meta title 50–60 chars, meta description 145–160 chars - Localization: language, measurements, currency - Validation: ask to ensure grammar, uniqueness, and that slug contains only lowercase letters, numbers and hyphens Single-product prompt (short + long + metadata, HTML-ready) Example: You can paste product attributes where indicated. Prompt: You are an e-commerce product copywriter and SEO specialist. Generate PrestaShop-ready content for one product using the data below. Output a JSON object only (no additional commentary) with these keys: name, reference, price, quantity, description_short (max 35 words, no HTML tags), description (HTML allowed:,
- ,
- , ,
), meta_title (50–60 chars), meta_description (145–160 chars), meta_keywords (comma-separated), link_rewrite (slug: lowercase, hyphens, no accents), image_alt (max 125 chars), features (JSON list of {"name":"", "value":""}), tags (comma-separated). Tone: friendly, informative, benefit-first. Target audience: busy urban professionals. Language: English (US). Product data: name: {{product_name}} brand: {{brand}} short_features: {{short_features}} (one-line bullets) technical_specs: {{specs}} (key:value pairs) primary_keywords: {{primary_keywords}} (comma separated) secondary_keywords: {{secondary_keywords}} (comma separated) Constraints: Keep descriptions unique, factual (do not invent specs), include the primary keywords naturally at least once in description and meta_title, do not exceed lengths above. Output (example JSON structure): { "name":"{{product_name}}", "reference":"{{reference}}", "price":"{{price}}", "quantity":"{{quantity}}", "description_short":"...", "description":"...
- ...
,
- ,
- , ). Each description_short max 30 words. meta_title 50–60 chars. meta_description 145–160 chars. Create unique slugs and alt text. Language: English (US). Tone: professional and benefit-focused. Input sample rows below (you will receive more rows in the same format):
INPUT ROWS:
product_name | brand | reference | price | quantity | short_features | specs | primary_keywords | secondary_keywords
Wireless Noise-Canceling Headphones | AcmeAudio | H12345 | 129.99 | 150 | “ANC, 30h battery, Bluetooth 5.2” | “Battery:30h|ANC:Yes|Weight:250g” | “noise cancelling headphones, wireless headphones” | “Bluetooth headphones, travel headphones”
Output CSV example row must correspond to that input.
Category description prompt
Prompt:
You are an SEO copywriter. Generate a category title, short description (1–2 sentences, 20–35 words), and full description (HTML allowed:
,
- ,
- — 120–220 words) for the PrestaShop category “{{category_name}}”. Audience: {{audience}}. Include these keywords: {{primary_keyword}}, {{secondary_keywords}}. Provide meta_title (up to 60 chars) and meta_description (145–160 chars). Output only JSON with keys: title, description_short, description, meta_title, meta_description, meta_keywords, link_rewrite.
CMS page prompt (About us, Shipping, Returns, FAQs)
Short example for an About Us page:
Prompt:
You are a brand storyteller and legal-aware copywriter. Write a PrestaShop CMS “About Us” page for “{{store_name}}” ({{years_in_business}} years), mission: {{mission}}, audience: {{audience}}. Output HTML content only using
,
,
,
- ,
- , . Include: 1) a 1-line tagline, 2) a 3-paragraph story (founding, what we do, why customers choose us), 3) 4 bullet points of core values, 4) one short CTA and a suggested meta_title and meta_description at the end as an HTML comment like .
Privacy, Shipping, Returns templates:
- Provide legal-safe, plain-language templates.
- For returns: include return window, condition, refund/exchange policy, steps to return.
- For shipping: include carriers, typical delivery times, tracking, international rules, duties/taxes.
SEO-specific constraints and best practices to include in prompts
- meta_title: 50–60 chars (include primary keyword).
- meta_description: 145–160 chars (encourage click).
- URL slug: lowercase, no spaces, only letters/numbers/hyphen.
- image_alt: descriptive, include main keyword where natural, ≤125 chars.
- Ensure H1/H2 usage for CMS pages and long descriptions (H1 usually product name).
- Avoid duplicate content across product pages; request slight variations.
- For multilingual sites, request output per language and provide translations or instruct to translate into given languages.
HTML rules for PrestaShop descriptions
- Allowed tags usually:
,
, , ,- ,
- ,
-
,
(check theme compatibility). - Request only allowed tags in prompt. - Avoid inline CSS and external scripts. Examples of “perfect” final prompts you can copy-paste 1) Single product (JSON output): You are an e-commerce copywriter and SEO specialist. Produce a JSON object for a PrestaShop product using the data below. Keys required: name, reference, price, quantity, description_short, description, meta_title, meta_description, meta_keywords, link_rewrite, image_alt, features (array), tags. description_short: max 35 words, no HTML. description: 120–250 words, HTML allowed (
,
- ,
- ,). meta_title: 50–60 chars and must include primary_keyword. meta_description: 145–160 chars and must include primary_keyword. link_rewrite: slug (lowercase, hyphens). image_alt: 8–12 words, include primary_keyword. Tone: modern, energetic, benefit-focused. Language: English (US). Ensure no invented specs—only use the supplied technical_specs. Do not output anything besides valid JSON.
DATA:
{
"product_name":"{{product_name}}",
"brand":"{{brand}}",
"primary_keyword":"{{primary_keyword}}",
"technical_specs": {"Battery":"30h", "ANC":"Yes", "Weight":"250g"},
"short_features":"{{short_features}}"
}
2) Bulk JSON array (return array for direct import):
You are an e-commerce content generator. For each product in the input array, output a JSON array of product objects ready for PrestaShop import. Each object must have keys: name, reference, price, quantity, description_short, description (HTML allowed), meta_title, meta_description, meta_keywords, link_rewrite, image_alt, features (object). Keep meta_title ≤60 chars and meta_description 145–160 chars. Avoid duplicate meta titles among products. Output only a single JSON array.
3) Category page (HTML + meta in comment):
Write a category landing page for "{{category_name}}" for a PrestaShop store selling {{product_type}}. Provide a headline
, a short intro
(20–35 words), a benefits list
- (4 items), a longer paragraph
- Active Noise Cancellation for travel
- Lightweight 250g design
- Up to 30 hours per charge
- ,), meta_title, meta_description, meta_keywords, link_rewrite, image_alt, features (array), tags. Language: {{language}}. Tone: {{tone}}. Target audience: {{audience}}. Enforce: description_short max {{short_words}} words; description 120–250 words; meta_title 50–60 chars and must include primary_keyword: {{primary_keyword}}; meta_description 145–160 chars and must include primary_keyword. Use supplied data below; do not invent technical specs. Product data: {{insert data as JSON}}. Output valid JSON only.
If you want, I can:
- Convert 10 sample products you paste into a CSV you can import.
- Create per-language versions (e.g., EN/FR/ES) from a single product.
- Generate a canonical PrestaShop CSV header tailored to your PrestaShop version.
Would you like a ready-to-import CSV header and a small demo conversion? If so, paste 5 sample product rows (name,sku,price,qty,short_features,specs,image_urls) and I’ll return a CSV/JSON ready for PrestaShop import.
Produktoplysninger
MK-ropalimpia-500mlRelated products
Reviews (0)
No reviewsKunder, der købte denne vare, købte også
8 andre varer i den samme kategori:
(120–180 words) and a concluding CTA
. At the end add an HTML comment with meta_title and meta_description: . Quality-control follow-up prompts (for iterations) - “Improve readability: shorten passive sentences and reduce Flesch–Kincaid grade level to X.” - “Produce 3 alternative meta_title options (distinct) and 3 meta_description options.” - “Rewrite descriptions to emphasize eco-friendly aspects and remove any technical jargon.” - “Check for duplicates across this list of N product names and create unique meta titles.” Helpful checklists to include in your prompt (ask the assistant to verify) - Slug uses only a-z0-9 and hyphens; length < 100 chars. - meta_title includes primary keyword and ≤60 chars. - meta_description includes primary keyword and 145–160 chars. - No forbidden HTML tags or inline ss. - No invented specs; if a spec is missing, output “N/A”. - Provide alt text for each image and at least one tag. Sample outputs brief examples Single-product JSON (short sample): { "name":"Acme Noise-Canceling Headphones", "reference":"H12345", "price":"129.99", "quantity":"150", "description_short":"Comfortable wireless headphones with active noise cancellation and 30-hour battery life, perfect for travel.", "description":"
Experience deep, immersive sound with Acme’s Noise-Canceling Headphones. With 30 hours of battery life and Bluetooth 5.2, enjoy long listening sessions and true wireless convenience.
,
- ,
- ,). meta_title: 50–60 chars and must include primary_keyword. meta_description: 145–160 chars and must include primary_keyword. link_rewrite: slug (lowercase, hyphens). image_alt: 8–12 words, include primary_keyword. Tone: modern, energetic, benefit-focused. Language: English (US). Ensure no invented specs—only use the supplied technical_specs. Do not output anything besides valid JSON.
DATA:
{
"product_name":"{{product_name}}",
"brand":"{{brand}}",
"primary_keyword":"{{primary_keyword}}",
"technical_specs": {"Battery":"30h", "ANC":"Yes", "Weight":"250g"},
"short_features":"{{short_features}}"
}
2) Bulk JSON array (return array for direct import):
You are an e-commerce content generator. For each product in the input array, output a JSON array of product objects ready for PrestaShop import. Each object must have keys: name, reference, price, quantity, description_short, description (HTML allowed), meta_title, meta_description, meta_keywords, link_rewrite, image_alt, features (object). Keep meta_title ≤60 chars and meta_description 145–160 chars. Avoid duplicate meta titles among products. Output only a single JSON array.
3) Category page (HTML + meta in comment):
Write a category landing page for "{{category_name}}" for a PrestaShop store selling {{product_type}}. Provide a headline
- ,
- ,
- , . Include: 1) a 1-line tagline, 2) a 3-paragraph story (founding, what we do, why customers choose us), 3) 4 bullet points of core values, 4) one short CTA and a suggested meta_title and meta_description at the end as an HTML comment like .
Privacy, Shipping, Returns templates:
- Provide legal-safe, plain-language templates.
- For returns: include return window, condition, refund/exchange policy, steps to return.
- For shipping: include carriers, typical delivery times, tracking, international rules, duties/taxes.
SEO-specific constraints and best practices to include in prompts
- meta_title: 50–60 chars (include primary keyword).
- meta_description: 145–160 chars (encourage click).
- URL slug: lowercase, no spaces, only letters/numbers/hyphen.
- image_alt: descriptive, include main keyword where natural, ≤125 chars.
- Ensure H1/H2 usage for CMS pages and long descriptions (H1 usually product name).
- Avoid duplicate content across product pages; request slight variations.
- For multilingual sites, request output per language and provide translations or instruct to translate into given languages.
HTML rules for PrestaShop descriptions
- Allowed tags usually:
- — 120–220 words) for the PrestaShop category “{{category_name}}”. Audience: {{audience}}. Include these keywords: {{primary_keyword}}, {{secondary_keywords}}. Provide meta_title (up to 60 chars) and meta_description (145–160 chars). Output only JSON with keys: title, description_short, description, meta_title, meta_description, meta_keywords, link_rewrite.
CMS page prompt (About us, Shipping, Returns, FAQs)
Short example for an About Us page:
Prompt:
You are a brand storyteller and legal-aware copywriter. Write a PrestaShop CMS “About Us” page for “{{store_name}}” ({{years_in_business}} years), mission: {{mission}}, audience: {{audience}}. Output HTML content only using
- , ,