內容簡介
LinguaRank AI 是一款專為使用 Polylang 的 WordPress 網站設計的外掛，幫助管理員輕鬆創建文章、頁面及其他公共文章類型的翻譯版本。它能夠自動生成多語言內容，並與原始內容建立連結，提升網站的多語言管理效率。
【主要功能】
• 支援多種語言的內容翻譯
• 自動處理大型頁面的翻譯批次
• 整合多個 AI 翻譯服務提供者
• 提供翻譯記憶與術語庫功能
• 檢查翻譯質量與結構
外掛標籤
開發者團隊
原文外掛簡介
LinguaRank AI helps WordPress administrators create translated versions of posts, pages, and supported public post types.
The plugin is made for sites that already use Polylang. Choose a source item, select the target languages, and start the translation. LinguaRank AI creates a separate WordPress item for each language and connects it to the original through Polylang.
The source can be written in any language configured in Polylang. It does not have to be Ukrainian, Russian, English, or Polish.
LinguaRank AI works only in the WordPress admin area. It does not add a public language switcher or change the language buttons on your site. Polylang remains responsible for front-end language switching and language relationships.
What can be translated
Post titles, excerpts, and readable text inside Gutenberg blocks.
URL slugs and supported SEO titles, descriptions, keywords, and social fields.
Selected categories, tags, reusable blocks, internal links, and text-based custom fields.
ACF blocks and ACF field groups, including text, textarea, WYSIWYG, repeater, group, flexible content, and link labels.
Registered Polylang strings when they are available in the current WordPress setup.
The plugin recognizes Yoast SEO fields and common metadata used by Rank Math, AIOSEO, SEOPress, and UAS SEO. Unsupported technical values, IDs, layout settings, and binary data are left unchanged.
One click for large pages
Large Gutenberg pages are split into smaller translation batches. The plugin processes those batches in sequence, checks the block structure, and saves the completed language version as one translation job. You do not need to click the translation button for every part of the page.
Progress and the current stage are shown in the editor and in the LinguaRank AI dashboard.
AI providers
WordPress AI Client is the recommended option on WordPress 7.0 and newer. It uses the provider configured under WordPress Settings > Connectors, so LinguaRank AI does not need to store that provider’s key.
You can also connect OpenAI, Google Gemini, DeepSeek, or OpenRouter directly. The first provider and the fallback order can be selected in the plugin settings. Direct provider keys can be entered in the admin area or defined as constants in wp-config.php.
Translation tools
A glossary for names, abbreviations, legal terms, and project-specific wording.
Translation memory for repeated text fragments.
A queue for translating several items one after another.
Quality checks for Gutenberg structure, SEO fields, slugs, and source-language text.
Review statuses and snapshots before an existing generated translation is replaced.
A Clear Translations action that removes generated translations without deleting the source item.
Images are reused instead of duplicated. Text stored in image alt text or captions can be translated, but LinguaRank AI does not edit text that is part of the image itself.
For ACF content, LinguaRank AI translates reader-facing text and preserves field references, row order, layouts, URLs, media IDs, relationship values, and other technical data. ACF is optional and is not bundled with this plugin.
AI translation can contain mistakes. Review important legal, financial, medical, or business content before publishing or relying on it.
Requirements
WordPress 7.0 or newer.
PHP 7.4 or newer.
Polylang installed and configured with the required languages.
A configured WordPress AI Client connector or at least one direct provider API key.
Yoast SEO and other recognized SEO fields are optional. The translation workflow still works when an SEO plugin is not installed.
External Services
LinguaRank AI does not run its own translation service. When an administrator starts a translation or enables automatic translation, the plugin sends the required text to the configured AI provider.
Depending on the selected settings, the request may include post content, titles, excerpts, selected SEO metadata, taxonomy or custom-field text, glossary instructions, and the target language. Images and other binary files are not sent for translation.
Requests can be sent through WordPress AI Client or directly to one of these services:
OpenAI: https://openai.com/policies/terms-of-use/ and https://openai.com/policies/privacy-policy/
Google Gemini: https://ai.google.dev/terms and https://policies.google.com/privacy
DeepSeek: https://cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html and https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html
OpenRouter: https://openrouter.ai/terms and https://openrouter.ai/privacy
No translation request is sent until an administrator configures a provider and starts a translation or enables automatic translation. LinguaRank AI does not load remote JavaScript, CSS, tracking pixels, advertisements, license checks, or plugin updates from these providers.
Direct API keys are stored in the current WordPress database and are excluded from settings exports. When OpenSSL is available, saved keys are encrypted before storage. Keys managed by WordPress AI Client remain under WordPress Settings > Connectors.
Privacy
Translation requires sending selected site text to the AI provider chosen by the administrator. The provider’s terms, privacy policy, account settings, and billing rules apply to that request.
LinguaRank AI does not collect analytics, create an external LinguaRank account, or send data to a separate service operated by the plugin author.
