WooCommerce Integration
Omnalingo supports WooCommerce stores out of the box. Product content, shop archives, checkout flows, and cart UI are all translatable. This page explains what gets covered, how it works, and what to watch for on a WooCommerce site.
What Gets Translated
Section titled “What Gets Translated”Product Content
Section titled “Product Content”Product titles, descriptions, short descriptions, product category names, and product tags are all standard WordPress content. Omnalingo discovers and scans them the same way it handles regular posts and pages.
To make sure products are included, go to Omnalingo → Settings and confirm that Products is enabled under your content type settings. Product categories and tags follow the same setting.
Shop, Cart, and Checkout Pages
Section titled “Shop, Cart, and Checkout Pages”The WooCommerce shop page, cart, checkout, and order confirmation pages are treated as regular pages. Gather and scan them from the dashboard as you would any other page.
WooCommerce UI Strings
Section titled “WooCommerce UI Strings”Strings like “Add to Cart”, “Proceed to Checkout”, “Your cart is empty”, order status labels, and error messages come from WooCommerce’s own language system, not from your page content. Omnalingo detects these automatically during scanning and adds them to your translation index alongside your page content.
If a WooCommerce UI string is already covered by WooCommerce’s own translation files for your target language, Omnalingo counts it as translated and doesn’t duplicate the work. Strings that aren’t covered — gaps in WooCommerce’s official translations — are queued for AI translation.
Checkout Blocks and Cart Blocks
Section titled “Checkout Blocks and Cart Blocks”Modern WooCommerce uses React-rendered blocks for the cart and checkout experience. Omnalingo hooks into these at the JavaScript level so translations are applied from the very first render — you don’t need to do anything special. The strings from these blocks appear in the visual editor and can be translated there.
Mini-Cart
Section titled “Mini-Cart”The WooCommerce mini-cart (the slide-out or dropdown cart widget) is handled automatically. Both the static labels and the dynamic content that updates as customers add or remove items are translated client-side using Omnalingo’s translation map.
AJAX Updates
Section titled “AJAX Updates”When a visitor adds a product to the cart, updates a quantity, or applies a coupon, WooCommerce updates the page via AJAX. Omnalingo intercepts these updates and applies translations to any new content that appears, so the experience stays in the correct language throughout the shopping flow.
Product Reviews
Section titled “Product Reviews”The review count link (for example, “40 customer reviews”) is handled as a single translation unit, preserving the number as a dynamic value. Review author names are intentionally excluded from translation — they’re user-generated data and should stay as written.
Translating in the Visual Editor
Section titled “Translating in the Visual Editor”Open any WooCommerce page in the visual editor the same way you would any other page — click the editor icon in the dashboard row for that page.
The shop, cart, and checkout pages are fully supported in the editor. If you see a blank preview for one of these pages, check that the page is published and correctly configured under WooCommerce → Settings.
WooCommerce UI strings (the button labels and messages) appear in the editor sidebar alongside your page’s own content. You can translate them directly or let the AI chatbot handle the page in one click.
Known Issues and Things to Watch For
Section titled “Known Issues and Things to Watch For”WooCommerce Strings Appearing in the Wrong Language
Section titled “WooCommerce Strings Appearing in the Wrong Language”On some server setups, WooCommerce loads its own language files before Omnalingo has had a chance to set the correct language for the current request. Omnalingo includes an automatic fix for this — it detects stale language data and reloads the affected strings using the correct locale.
If WooCommerce strings still appear in the wrong language after a page reload:
- Check that Omnalingo is active and that no other translation plugin is also active on the site.
- Check that you’re running WordPress 6.5 or later — the fix works best on current WordPress versions.
- Check whether another plugin has a language filter that might override Omnalingo’s locale setting.
Translator Role and WooCommerce Admin Access
Section titled “Translator Role and WooCommerce Admin Access”By default, WooCommerce redirects non-administrator WordPress users away from the admin area. Omnalingo overrides this for users with the Omnalingo Translator role so they can access the translation dashboard and visual editor.
If a translator is still being redirected to the “My Account” page after being assigned the Translator role, check whether another plugin or your theme’s functions.php is adding its own redirect rule that runs after Omnalingo’s override.
Caching
Section titled “Caching”If your site uses a full-page caching plugin, translated WooCommerce content may not appear to visitors until the cache is cleared. After running bulk translation or making edits in the visual editor, clear your cache so visitors see the updated translations.
Summary
Section titled “Summary”| Content type | How it’s translated |
|---|---|
| Product titles, descriptions, categories | Scanned and translated like any page — enable Products in content settings |
| WooCommerce UI strings (buttons, labels) | Detected during scanning; gaps filled by AI translation |
| Cart and checkout block labels | Translated via JavaScript hooks — automatic |
| Mini-cart content | Translated client-side — automatic |
| AJAX cart updates | Handled by Omnalingo’s output processing — automatic |
| Product review author names | Excluded from translation by default |