AI Content Optimiser

VIDEO WALKTHROUGH

AI Content Optimiser: setup guide

2:39

Recorded on version 1.0.2 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters

1. 0:00Set up AI Content Optimiser
2. 0:13Open settings and choose scope
3. 0:33Choose your text provider
4. 0:53Review product prompts
5. 1:13Review category prompts
6. 1:32Review page prompts and the draft workflow
7. 1:54Save and verify your setup
8. 2:16Your setup checklist

Read the full video transcript

AI Content Optimiser 1.0.2 — Magento Admin setup

00:00:00 — Set up AI Content Optimiser
Welcome to the Agentic Ecom A I Content Optimiser Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed.

00:00:13 — Open settings and choose scope
Start in Magento Admin and open Stores, Configuration. Choose AI Content Optimiser. Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store.

00:00:33 — Choose your text provider
Enable AI Content Optimiser and choose a primary text model. Enter your own OpenAI or Google Gemini API key for the selected provider. Review the fallback model too; if it uses another provider, that provider needs its own key. API usage can be billed separately by the provider.

00:00:53 — Review product prompts
Open Product Field Prompts. Keep instructions factual and tailored to the fields you generate. A prompt should not invent specifications, prices or compatibility. Review the current product facts before using an Optimise or AI Write button, and check every draft before saving the product.

00:01:13 — Review category prompts
Category Field Prompts control the draft copy for supported category fields. Choose the intended store scope before editing translated content. Keep the category purpose and search metadata aligned, and verify that generated text accurately describes the products in that category.

00:01:32 — Review page prompts and the draft workflow
Review C M S Page Field Prompts separately. The extension drafts one supported Admin field at a time; it does not publish content in bulk or generate images. Save the configuration, open a product, category or C M S page, generate a draft, and review the text before saving that entity.

00:01:54 — Save and verify your setup
When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers.

00:02:16 — Your setup checklist
That's the Admin setup walkthrough for A I Content Optimiser. Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.

Download videoEnglish captionsDownload transcript

AI Content Optimiser 1.0.2 adds ✨ Optimise and ✨ AI Write buttons to Magento Admin product, category and CMS edit forms. Each click drafts one field for the merchant to review before saving. It uses OpenAI or Google Gemini text models with the merchant’s own API key. This release does not generate images, publish content in bulk or add a storefront widget.

Install

Back up Magento and install one copy using licensed Composer or the Adobe package supplied with your purchase. Do not install Composer and app/code copies together.

composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x
composer require 'agenticecom/module-aicontent:^1.0.3'
php bin/magento module:enable AgenticEcom_AiContent
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:clean

The exact 1.0.2 package installed and compiled on Magento Open Source 2.4.9 / PHP 8.5.10. Its Composer constraints allow PHP 8.3–8.5 with compatible Magento framework, backend, catalog and CMS packages. Test other combinations in staging. The Admin buttons work with a Luma storefront.

Configure AI

1. Open Stores → Configuration → AgenticEcom → AI Content Optimiser and set Enable AI Content Optimiser to Yes.

2. Choose a Primary Text Model. New installations default to OpenAI GPT-6.1 Sol and GPT-6 Luna as the fallback for HTTP 429 or 503 errors. To use these models, enter your own OpenAI API Key. To use a Gemini model, select it and enter your own Google Gemini API Key. Keys are stored with Magento’s encrypted configuration backend.

3. Review the product, category and CMS field prompts. Each prompt is editable by store scope. Existing 1.0.1 Gemini key-only setups and merchant-edited prompts are preserved on upgrade; untouched older defaults are refreshed. If your fallback uses a different provider, configure that provider’s key too.

4. Open a product, category or CMS page in Magento Admin and use a ✨ button on a supported field. Review the draft before saving the entity.

External API costs

OpenAI and Google Gemini can charge for API use under your own account. These charges are separate from the extension purchase price. Model availability and provider rates can change.

Supported fields

Product

Product name, short description, long description, meta title and meta description.

Category

Category description, meta title and meta description.

CMS page

CMS content, meta title and meta description.

Long description, category description and CMS content may return HTML. Name and meta fields return plain text with length limits: 80 characters for a product name, 60 for a meta title and 155 for a meta description. The chosen store view controls the response language.

Give the model reliable facts

The selected entity name, merchant-supplied context and relevant existing field values are sent to the selected provider. Put verified specifications, product uses or page facts into the editor context where available. The default prompts ask the model to use only those facts, ignore instructions embedded in source text and write less when context is sparse. They avoid mandatory filler lengths and unsupported specifications tables.

Review every draft

AI output can still be wrong. Check specifications, compatibility, pricing, stock, links, policies, rights, tone and translation before saving. A prompt is guidance, not a guarantee of accuracy or search ranking.

Rich HTML output is sanitised server-side to remove unsafe markup before it reaches the editor. Access to generation and configuration is controlled by separate Magento Admin permissions.

What changed in 1.0.2

• Added current OpenAI text choices alongside Google Gemini, with OpenAI defaults for new installations.
• Preserved existing Gemini key-only setups and merchant-edited prompts during upgrade.
• Replaced untouched default prompts that encouraged filler with more factual instructions.
• Corrected category and CMS meta-prompt routing, capped plain-field length and rejected incomplete provider responses.

Purchase and support

A one-time purchase includes the right to keep using your eligible version plus 12 months of updates and priority support. Renewal is optional and is never billed automatically. See the AgenticEcom licence and your order terms. Contact support@agenticecom.net for help.