內容簡介
WPGlobus 將您的 WordPress 網站轉換為多語言網站，讓您可以輕鬆地為文章、頁面及其他內容添加翻譯，並支援多種語言的 SEO 設定，提升網站的可達性與使用者體驗。
【主要功能】
• 支援文章、頁面及自訂文章類型的翻譯
• 提供多語言的 SEO 標題與描述
• 允許自訂語言的 URL 結構
• 前端語言切換選單與小工具
• WooCommerce 產品及屬性的翻譯（Pro 版）
• 與流行的頁面編輯器相容（Pro 版）
外掛標籤
開發者團隊
原文外掛簡介
WPGlobus turns your WordPress site into a multilingual one. You choose the languages you want, and WPGlobus adds the fields where you enter your own translations – post and page titles, content, excerpts, categories, tags, and more.
Free and Pro versions
Free: WPGlobus – this plugin. The essential multilingual tools, free from WordPress.org.
Pro: TIV Globus – the successor to WPGlobus Plus and WooCommerce WPGlobus. The complete multilingual tools, sold on the WooCommerce.com marketplace.
WPGlobus allows you to:
Enter translations for posts, pages, custom post types, categories, tags, menus, and widgets;
Enter translations for the Site Title and Tagline;
Enter multilingual SEO titles and meta descriptions – compatible with Yoast SEO (free version);
Add one or several languages using custom combinations of country flags, locales, and language names;
Give each language its own URL (example.com/, example.com/es/, example.com/fr/, and so on);
Switch languages on the front-end with a drop-down menu extension and/or a customizable widget with various display options;
Switch the admin interface language from the top bar.
What is in the Pro version (TIV Globus)?
Everything in the Free version, plus the ability to:
Give each page a full translated address, including “slug” (/my-page/ becomes /fr/ma-page/, /es/mi-pagina/, and so on);
Enter translations for WooCommerce products, categories, and attributes;
Use popular page builders (Elementor, Avada, and more) in every language;
…and much more.
Get TIV Globus – the Pro version of WPGlobus. It replaces WPGlobus without losing your settings or translations, and works with or without WooCommerce.
A free upgrade for our customers
Already own WPGlobus Plus or WooCommerce WPGlobus? You can move to TIV Globus at no extra cost. This is a limited-time offer for existing customers.
Claim your free upgrade
Important Notes: please read first!
These notes apply to both WPGlobus (free) and TIV Globus (Pro).
NO AUTOMATIC TRANSLATION:
The plugin does NOT translate texts automatically! You translate texts manually.
IF YOU UNINSTALL, YOU MUST REMOVE THE EXTRA LANGUAGES:
All translations are stored together in a special format: {:en}English{:}{:fr}French{:}{:es}Spanish{:}. If the plugin is not active, every language shows at once and your site becomes unreadable. Before you deactivate and uninstall, you must run the cleanup tool to remove all languages but one. See the details in the plugin’s settings.
PAGE BUILDERS / COMPOSERS:
Page-builder support is available only in TIV Globus (Pro).
COOKIES:
The plugin uses a browser cookie to remember your language preference. It stores only the language code (such as en or es) – no personal information.
MULTISITE:
The multisite mode (multiple virtual sites sharing a single WordPress installation) is not tested and not officially supported. It may still work, but use it at your own discretion.
Compatibility with themes and plugins
WPGlobus works with any theme or plugin that passes its text through the standard WordPress filters before displaying it – which covers the large majority of them.
Some add-ons that render their own output (sliders, forms, page composers, and the like) are not always multilingual-ready. When you find an element that will not translate, please let its author know – the fix is usually small.
We test against many popular themes and plugins and follow their updates as closely as we can. Since third-party code changes frequently, an occasional tweak on our side may be needed after an update.
Permalinks
WPGlobus needs “pretty” permalinks. Go to Settings -> Permalinks and pick any structure other than “Plain” (with no index.php in it) – URLs like example.com/?p=123 will not work.
WooCommerce: set your store bases explicitly (for example, Shop Base /product/). If you leave them blank, WooCommerce may translate the base itself (e.g. /produkt/ for German), causing 404 errors.
