Ambientador Mikado higo - 1000ml

055. Ambientador Mikado higo - 1000ml

Ambientador Mikado higo (055) er en duftpinde refill med Aromastik Mikado – Duftdiffuser Figen; en sød og behagelig duft, der præcist beskriver produktets olfaktive profil.

Produktet leveres i dunk på 1 liter i større format til professionel brug og er beregnet til genopfyldning af duftpinde. Ideel til professionelle kunder, forhandlere, detailhandlere, distributører og engroskunder, der søger refill til duftpinde eller en duft til hjemmet i professionelt format.

Du kan finde flere oplysninger her: læs mere om duftpinde og hvordan de fungerer.

35,63 € 

Beskrivelse

Below is a practical, ready-to-use guide to writing “perfect” AI prompts for generating or improving PrestaShop product pages, category pages, and CMS pages. It includes prompt structure, concrete templates you can paste and customize, examples, output-format suggestions (so results can be imported into PrestaShop), and QA/check steps. Key principles (short) - Be explicit about the role: tell the model it is an e-commerce copywriter with PrestaShop experience. - Provide store context: brand voice, target audience, country/language, SEO keywords (primary + secondary). - Specify exact output fields and format (JSON or CSV) so you can import or map to PrestaShop fields. - Give strict constraints: word counts, HTML allowed/forbidden, tone, and not to invent technical specs. - Ask the model to validate: list missing input fields or say “insufficient data” rather than guessing. - Use low temperature for deterministic results when bulk generating. Essential PrestaShop fields to include in prompts - name (product/category/CMS page title) - meta_title - meta_description - friendly_url (slug) - short_description (product list snippet) - description (full HTML product description) - price / tax info (only used for context; don’t let AI invent pricing) - features / attributes (key technical specs, bullet list) - tags - image_alt_text - canonical_url (optional) - visibility / status (online / offline) - category breadcrumbs (for context) - language and currency Prompt structure (recommended order) 1. System role 2. Store context: store name, brand voice, audience, country, languages, primary keywords 3. Input data: provide a structured JSON or CSV row for the item (fields you know) 4. Task and constraints: what to generate, exact fields, word counts, HTML rules, SEO rules 5. Output format: JSON schema or CSV with exact keys and types 6. Error handling: what to do if data is missing 7. Tone/SEO instructions and examples (optional few-shot examples) Product prompt template (paste and replace placeholders) You can use this directly with ChatGPT or other LLMs. System role: You are an expert e-commerce copywriter and SEO specialist experienced with PrestaShop. Generate clear, conversion-focused, SEO-optimized content that fits PrestaShop fields. Do not invent technical specs. If required data is missing, list missing fields and wait for input. Context: Store name: {STORE_NAME} Brand voice: {BRAND_VOICE} (e.g., friendly, premium, technical, playful) Target audience: {AUDIENCE} (e.g., hobbyists, professionals, parents) Country/language: {COUNTRY}/{LANGUAGE} Primary keyword(s): {PRIMARY_KEYWORDS} Secondary keywords: {SECONDARY_KEYWORDS} Input product data (replace values): { "sku": "{SKU}", "name": "{RAW_NAME}", "manufacturer": "{MANUFACTURER}", "features": ["Feature 1","Feature 2", "..."], "short_specs": "{short specs or bullet list}", "images": ["image1.jpg","image2.jpg"], "intended_use": "{use case}", "notes": "{any restrictions or compliance info}" } Task and constraints: - Produce the following exact JSON object with keys: name, meta_title, meta_description, friendly_url, short_description, description_html, features_list, tags, image_alt_texts. - name: polished product name, max 70 chars, include primary keyword. - meta_title: 50–60 chars, include primary keyword and brand where possible. - meta_description: 140–160 chars, include primary and one secondary keyword, call to action, no HTML. - friendly_url: lowercase slug using hyphens, remove stopwords where possible, max 80 chars. - short_description: 20–40 words, no HTML, for product listing. - description_html: full product description in HTML (

,

    ,
  • ,

    allowed), 200–400 words, includes benefits, key specs, dimensions/materials, one CTA, use natural language, no promotional superlatives like “best” unless supported by facts. - features_list: JSON array of 5–10 concise feature objects: { "name": "...", "value": "..." }. - tags: up to 10 comma-separated tags. - image_alt_texts: array aligned with images, 6–12 words, include primary keyword when appropriate. - Do not invent horsepower/voltages/materials unless provided. - If data is insufficient, output a JSON with key "missing_fields": [ ... ] and do not generate content. Output format: Return only valid JSON. No additional commentary. Example output schema: { "name": "...", "meta_title": "...", "meta_description": "...", "friendly_url": "...", "short_description": "...", "description_html": "...", "features_list": [{"name":"","value":""}, ...], "tags": "...", "image_alt_texts": ["...","..."] } Category prompt template System role: You are a conversion and SEO content specialist for PrestaShop categories. Context: Store, brand voice, language, audience, primary category keyword(s). Input: { "category_raw_name": "{RAW_CATEGORY_NAME}", "products_count": {N}, "main_attributes": ["attr1","attr2"], "purpose": "{category purpose or users}" } Task: - Generate: category_name, meta_title(50–60 chars), meta_description(140–160 chars), friendly_url (slug), short_intro (1-2 short sentences for listing), description_html (150–300 words with H2/H3, benefits + CTA), suggested subcategory names (3–6), suggested CMS pages to link (e.g., size guide). - Provide JSON only. Do not invent product-level info. CMS page prompt template (About, Shipping, Returns, Size Guide) System role: You are a technical content writer specialized in e-commerce policy & help pages. Context: Store name, tone, country legal context (e.g., EU consumer rights), language. Input: { "page_type": "about|shipping|returns|size_guide|privacy", "key_points": ["point1","point2"] } Task: - Produce: title, meta_title (50–60 chars), meta_description (140–160 chars), friendly_url, body_html (clear headings H2/H3, bullet points, step-by-step instructions if relevant), FAQ section (3–7 Q&As). - For legal topics, include suggestion: “Consult local law—do not rely solely on this text.” - JSON-only output. Example filled product prompt + expected output (short) Prompt (inputs replaced): - Store: “GreenTrail Outdoor” - Brand voice: friendly, informative, slightly informal - Audience: hikers and campers in EU, language: English - Keywords: primary “lightweight camping stove”, secondary “portable backpacking stove, compact stove” Input product: { "sku":"GT-PS100", "name":"GT Ultralight Stove 2026", "manufacturer":"GreenTrail", "features":["Weight: 210 g", "Fuel: canister", "Boil time: 3 min 30 s", "Pack size: 10 x 6 cm", "Material: stainless steel"], "images":["stove1.jpg","stove2.jpg"], "intended_use":"backpack camping, ultralight hikers", "notes":"CE compliant" } Task: (use the product template above) Expected output (JSON keys only — truncated example): { "name":"GreenTrail Ultralight Camping Stove — 210 g", "meta_title":"GreenTrail Ultralight Camping Stove | Lightweight Stove", "meta_description":"Lightweight camping stove for backpacking — 3.5 min boil time, 210 g. Compact, CE-compliant. Shop now.", "friendly_url":"greentrail-ultralight-camping-stove-210g", "short_description":"210 g ultralight camping stove with fast boil time and compact pack size — ideal for backpackers.", "description_html":"

    The GreenTrail Ultralight Camping Stove weighs just 210 g and delivers a 3 min 30 s boil time with standard canister fuel...

    • Weight: 210 g
    • ...

    Buy now to cut pack weight without sacrificing performance.

    ", "features_list":[{"name":"Weight","value":"210 g"},{"name":"Boil time","value":"3 min 30 s"},...], "tags":"camping stove,lightweight,backpacking,portable", "image_alt_texts":["GreenTrail lightweight camping stove top view","Close-up stove burner and pot supports"] } Bulk generation considerations (CSV/JSON import) - Provide a template CSV with columns matching the JSON keys defined above. - Use the same prompt but iterate rows programmatically; set temperature low (0–0.2) for consistent outputs. - Use a unique identifier column like sku or id to map outputs back. - Validate outputs with a script: check meta lengths, friendly_url format, no missing required fields, no HTML in fields that shouldn’t contain it. Few-shot examples and safety - Provide 1–3 examples in the prompt if you want a consistent s. - Tell the model NOT to fabricate specs; if missing, it should return missing_fields. - Ask for alt_texts and slugs that are unique and keyword-aware. Testing and QA checklist - Meta title <= 60 chars, meta_description 140–160 chars. - Friendly URL: no spaces, lowercase, hyphens, no special chars. - Short description: 20–40 words, no HTML. - Description_html uses allowed tags only and is user-friendly. - No hallucinated specs (verify feature values against source). - Unique content across products (use plagiarism/duplication checks). - Check for required legal lines on returns/shipping pages (depending on country). Prompt tuning tips - Use system message: “You are an e-commerce copywriter...” - Keep temperature low for bulk/deterministic output; raise slightly for creative product names. - Use function calling or explicit JSON schema if your LLM supports it to enforce structure. - For translations: include “Translate outputs into X language while preserving SEO keywords and match local idioms” and ask for both original and translated fields in the JSON. Quick ready-to-use one-liners (for quick generation) - Product rewrite: “Rewrite the following product description for SEO and conversion, keep primary keyword {keyword}, produce JSON fields: name, meta_title, meta_description, friendly_url, short_description, description_html, features_list. Do not invent specs.” - Category page: “Write a category page for {category} targeting keyword {keyword}. Produce JSON: category_name, meta_title, meta_description, friendly_url, short_intro, description_html, subcategories.” Final checklist to save time - Always include primary keyword(s), brand voice, language. - Provide as many factual inputs as possible (weights, materials, model numbers). - Specify output format and constraints. - Validate outputs automatically before import. - Iterate: ask the model to score the output on SEO, readability, and conversion and then refine. If you want, I can: - Produce a copy-ready prompt for a specific product or category if you paste the raw product data. - Generate a CSV template for bulk generation. Which would you like me to do next?

Produktoplysninger

MK-higo-1000ml

Related products

Reviews (0)

No reviews

Kunder, der købte denne vare, købte også

8 andre varer i den samme kategori:

Product added to wishlist