¶ GoAi Translator – User Guide
¶ 1. Introduction
GoAi Translator is an AI-based translation module for Adobe Commerce (Magento 2) that allows store owners to automatically or manually translate content such as products, categories, CMS pages, and more into different store views.
Key benefits:
Seamless translation of store content using AI.
Automated or manual translation triggers.
Translation queue and log management.
Term exclusion and replacement for better translation quality.
CLI support for developers.
This guide will help you configure and use the module effectively.
¶ 2. Module Configuration
¶ Step 1: Access Module Settings
Go to Stores > Configuration.
Open GoAi > Translator.
¶ Step 2: Configure General Settings
Enable Module – set General > Enabled to "Yes" to activate.
Auto-Trigger – enable automatic translation on create/update.
Default Store View – select source view for translation.
API Endpoint – enter your GoAi translation service endpoint.
Batch Size – number of entities per request (default: 5).
Customer ID – paste your unique GoAi customer ID.
Enabled Entity Types – select which entities (Products, Categories, CMS Pages, etc.) will be translated.
Enable Module
: Set
General > Enabled
to "Yes" to activate the module.
¶ Step 3: Redirect Behavior
Enable permanent 301 redirects for products and categories to avoid broken links after translation changes.
¶ Step 4: Manage Vocabulary
Excluded Terms – add brand names or technical terms (up to 100).
Term Replacement – enable replacement of specific words/phrases.
Define replacement rules for each entity type and store view.
¶ 3. Translation Types
¶ 3.1 Site Onboarding
Adds all enabled entities for a selected store view to the queue.
Only manual trigger available.
Used when launching a new store view.
How to start onboarding:
Go to Stores > All Stores.
Select a non-default store view.
Click Run Translation.
⚠️ Once started, onboarding cannot be stopped.
¶ 3.2 Content Update
Automatically queues entities when created/updated.
Applies only to supported entities with AI translation enabled.
¶ 4. Triggering Translations
¶ 4.1 Automatic Trigger
Runs when supported entities are created/updated in Default Store View.
¶ 4.2 Manual Trigger (Admin Panel)
Open entity → click Translate with AI.
Mass actions available for products.
¶ 4.3 Manual Trigger (CLI)
goai:translator:run --store-id=3
Options:
store-id – required for onboarding.
store-ids – comma-separated list.
entity-ids – comma-separated list.
entity-type – product, category, CMS, etc.
¶ 5. Managing Translations
¶ 5.1 Logs
Go to Stores > Translation Logs.
View queue status, error details, and messages.
Mass actions:
Delete entries.
Refresh status for skipped/error items.
¶ 5.2 Statuses
New – awaiting processing.
In Progress – translation started.
Translated – completed successfully.
Error On Translation – AI service failed.
Error On Saving – could not save results.
Error On Processing – failed before sending.
Pending – reserved for future use.
¶ 6. Advanced Features
¶ 6.1 EAV Attribute Translation
Enable AI Translation for Values = Yes.
Translate Label with AI? = Yes (for attribute labels & option values).
¶ 6.2 Entity Exclusion
Field Is Skip AI Translation = Yes → entity won’t be auto-translated.
¶ 7. Developer Notes
If using Amasty FAQ, apply Composer patch (see README).
¶ 8. Best Practices
Run Site Onboarding before editing content.
Use Excluded Terms for brand names.
Enable Term Replacement for SEO control.
Check logs regularly.
Use CLI for large-scale translations.
Logs:
📩 For additional support, contact us ai@gomage.com, rtsehynka@gomage.com