Deployed in a few steps
Built for multi-store Magento shops.
Install via Composer
Add the module via Composer and enable it with bin/magento module:enable.
Add your API key
Configure your DeepL, Google Cloud, Microsoft, OpenAI or DeepSeek key in the Magento admin.
Map store-views
AutoLingo maps each store-view to its locale so it translates in the right place.
Bulk translate
Run bin/magento autolingo:translate-missing to translate all missing content.
Multilingual at Magento scale
Locale-aware translation, per store-view.
Products & categories
Names, descriptions and attributes translated for each store-view.
CMS pages & blocks
Your CMS pages and blocks are translated like the rest of the catalogue, with their own copy for each store-view — including blocks placed with Page Builder.
Per store-view
Locale-aware translation: every store-view gets its language.
Custom emails
Your custom email templates (order, account, newsletter…) are translated, and each store-view sends its own version. Magento variables stay intact.
Translation CLI
bin/magento autolingo:translate-missing for bulk migrations.
Five providers
DeepL, Google Translate, Microsoft Translator, OpenAI and DeepSeek, configurable in the admin.
DeepL Glossary
Define your key terms once — brand names and industry jargon stay consistent per store-view.
Formality control
Pick a formal or informal tone for DeepL (DE, FR, IT, ES…) per market.
Translation log
Every request logged with 30-day retention.
Context-aware translation
Each call tells the provider what it is translating (product page, article, menu…), so short, ambiguous texts come out right.
Protected passages & alt text
[notranslate]…[/notranslate] or translate="no" keeps a brand name untouched; image alt and title text is translated for SEO.
Low credit alert
A warning appears when fewer characters than your chosen threshold are left on your DeepL account.
What gets translated
A native integration with the Magento catalogue.
Content types
- Products
- Categories
- CMS pages
- CMS blocks
- Custom emails
- Meta fields
Providers
- DeepL Free & Pro
- Google Translate
- Microsoft Translator
- OpenAI
- DeepSeek
- Automatic switch when a quota runs out
Requirements
- Magento 2.4.7+ (2.4.x)
- PHP 8.2 – 8.4
- Magento cron (recommended)
Everything included, no tiers
The first year includes updates and support. After that, an optional renewal at 50% per year extends them — without it, the extension keeps working.
- ✓Products, categories, CMS pages & blocks
- ✓Custom email templates
- ✓Per store-view translation (locale-aware)
- ✓CLI: autolingo:translate-missing
- ✓DeepL, OpenAI, Google Translate, Microsoft Translator, DeepSeek
- ✓Translation log (30-day retention)
- ✓12 months of updates & support
- ✓Products, categories, CMS pages & blocks
- ✓Custom email templates
- ✓Per store-view translation (locale-aware)
- ✓CLI: autolingo:translate-missing
- ✓DeepL, OpenAI, Google Translate, Microsoft Translator, DeepSeek
- ✓Translation log (30-day retention)
- ✓12 months of updates & support
AutoLingo vs Magefan
Magefan keeps AI translation for its Extra tier ($299 on Open Source, $598–748 on Adobe Commerce); AutoLingo includes five providers at a fixed price.
| AutoLingo | Magefan | |
|---|---|---|
| AI providers | DeepL, Google, Microsoft, OpenAI, DeepSeek | The same 4, Extra tier |
| Price of AI translation | $199.99 (Open Source) · $399.99 (Adobe Commerce) | $299 (Open Source) · $598–748 (Adobe Commerce) |
| Per store-view | ✓ | ✓ |
| Manual edits preserved | ✓ | Not documented |
| CLI command | ✓ | Not documented |
| CMS blocks (incl. Page Builder) | ✓ | ✓ |
| Custom emails | ✓ | ✓ |
| Interface labels | ✗ | ✓ |