Three ways to run a multilingual WordPress site. Start with the free plugin; add WPGlobus Plus for the professional tools, or choose TIV Globus if you run a WooCommerce shop. TIV Globus is planned to become a full replacement for the whole WPGlobus family; the table shows what it covers today and what is planned.
| WPGlobus (free) | WPGlobus Plus (add-on to WPGlobus) | TIV Globus (all-in-one) | |
|---|---|---|---|
| Content | |||
| Translate posts, pages, custom post types, categories, tags | yes | yes | yes |
| Translate menus, widgets, site title and tagline | yes | yes | yes |
| Block editor and classic editor | yes | yes | yes |
| Page builders: Elementor, Avada | no | no | yes |
| WooCommerce | no | no | yes |
| Addresses (URLs) | |||
A URL prefix per language (/es/, /fr/) | yes | yes | yes |
| Translated slugs for posts, pages and custom post types | no | yes | yes |
| Translated slugs for WooCommerce products | no | no | yes |
| Translated category, tag and term slugs (also nested) | no | yes | yes |
Translated category, tag and post type bases (/category/ becomes /categoria/ in Spanish) | no | yes | *planned |
| Publishing | |||
| Publish per language (keep a translation as draft) | no | yes | *planned |
| Menus and language switcher | |||
| Language switcher in a menu and as a widget | yes | yes | yes |
| Switcher in the menu as drop-down or flat | no | yes | yes |
| Language switcher block | no | no | yes |
| A different menu for each language | no | yes | *planned |
| SEO (Yoast SEO) | |||
| SEO title and meta description per language | yes | yes | yes |
| Social previews (Open Graph, X), canonical, breadcrumbs and schema per language | yes | yes | yes |
| Draft languages left out of the Yoast sitemap | no | yes | *planned |
| Focus keyphrase, SEO and readability analysis per language | no | yes | *planned |
| Advanced Custom Fields (ACF and ACF PRO) | |||
| Multilingual text and textarea fields | yes | yes | *planned |
| Multilingual WYSIWYG fields | no | yes | *planned |
| Multilingual ACF PRO Options pages | no | yes | *planned |
| Admin | |||
| Make any admin text field or classic editor multilingual | no | yes | *planned |
| WooCommerce | |||
| Translate products (titles, descriptions, variations) | no | no | yes |
| Translate product categories | no | no | yes |
| Translate product tags | no | no | yes |
| Translate product attributes | no | no | yes |
| Cart, checkout, orders and emails in the customer’s language | no | no | yes |
| Shipping, tax, payment method texts | no | no | yes |
| Getting it | |||
| Where | WordPress.org (free) | wpglobus.com | WooCommerce.com |
* Planned for future releases of TIV Globus.
Which one do I need?
- A blog or company site, a few languages, simple needs – free WPGlobus.
- Publishing per language, multilingual ACF, Yoast analysis per language – WPGlobus Plus, on top of WPGlobus.
- A WooCommerce shop, or a site built with Elementor or Avada – TIV Globus.
Questions
Can I use WPGlobus Plus and TIV Globus together?
No. WPGlobus Plus is an add-on to WPGlobus, and TIV Globus runs instead of WPGlobus. Choose one.
Is TIV Globus the new version of WPGlobus Plus?
No. They are different plugins. TIV Globus is the successor of WPGlobus for WooCommerce. It is planned to cover the Plus features too – see the rows marked * above. Until then, sites that need them stay on WPGlobus + WPGlobus Plus.
Will my translations carry over if I switch?
Yes, your translated content and language settings are kept: all three use the same format. Settings of features that TIV Globus does not have yet (marked * above) are not used until they arrive.
Can I try TIV Globus first?
Owned WPGlobus for WooCommerce? Ask for a free test ZIP.