Subscription includes
Support
This is the next generation of WPGlobus. After years of supporting multilingual stores and learning what merchants actually need, we rebuilt the plugin from the ground up and combined the capabilities of WPGlobus, WPGlobus Plus, and WPGlobus for WooCommerce into a single WooCommerce extension. One plugin now does the work that previously took three.
Most multilingual plugins, including WPML and Polylang, create a separate post, page, or product for every language. A catalog of 500 products in four languages becomes 2,000 entries to create, link, and keep in sync. When you change a price or update stock, you do it in several places.
TIV Globus takes a different approach. All translations live inside a single post, page, or product:
To translate, you switch the editing language in the admin bar, type the translation, and save. The plugin merges your text and leaves the other languages untouched.
See documentation for more details on how to setup and use TIV-Globus.
Visitors land on the right language automatically, based on a clean URL prefix:
example.com/shop/example.com/fr/boutique/example.com/de/laden/The default language has no prefix at all, so your primary market keeps its original URLs. A language switcher lets visitors change languages anywhere on the site.
A multilingual store is more than translated product titles. TIV Globus covers the parts that other tools often leave in the default language.
/shop/ in English, /fr/boutique/ in French, /de/laden/ in Germanurl_to_postid() resolves translated slugs, and all permalink structures are supportedPage builder support is a first-class feature, not an afterthought.
WooCommerce runs your store in one language. TIV Globus adds the multilingual layer on top:
If you already run WPGlobus, WPGlobus Plus, or WPGlobus for WooCommerce, TIV Globus is the consolidated successor. It keeps the one-post-per-all-languages model you know and brings the post, Plus, and WooCommerce features together in a single, modern extension built for current WordPress and WooCommerce.
No. All translations live inside a single product, page, or post. You enter the price, stock, SKU, and settings once, and they are shared across every language. To translate, you switch the editing language in the admin bar, type the translation, and save. This is the main difference from plugins like WPML and Polylang, which create one duplicate entry per language that you then have to link and keep in sync.
Open the product or page in the editor, switch the editing language in the admin bar, enter the text for that language, and save. The plugin merges your translation into the same record and leaves the other languages untouched. There is nothing to duplicate and nothing to connect.
Visitors see each language at its own clean URL prefix such as /fr/ or /de/. The default language has no prefix, so your primary market keeps its original URLs. A language switcher, available as a menu item, a sidebar widget, or a block, lets visitors change language anywhere on the site.
It translates the whole store. That includes product names, descriptions and short descriptions, categories, tags, brands and attributes, the Shop, Cart, Checkout and My Account pages (including block-based checkout), shipping method names, tax labels, and payment gateway titles and instructions. The cart and order item names are translated as well.
Order emails are sent in the language the customer used at checkout. The plugin saves the customer's language with the order and reuses it for every later email about that order, so a French customer keeps receiving French emails. Admin notification emails stay in your store's admin language.
Yes. Each language gets clean, translated URLs, a canonical URL, hreflang tags so search engines understand the language alternatives, and its own XML sitemap discovered through robots.txt. If you use Yoast SEO, the meta title, description, OpenGraph data, and schema are translated per language.
Yes, and this is a first-class feature rather than an afterthought. Elementor is supported with per-language builder data, so each language can have its own design. Avada and Fusion Builder work natively.
Not in this version. You enter translations yourself, which gives you full control over wording and tone. Automatic machine translation is planned for a future release.
Yes. A live demo is available so you can see the multilingual storefront, the language switcher, and the editing workflow in action before you decide: https://tivnet.com/
Extension information
Quality Checks
Countries
