LinguaRank AI

LinguaRank AI helps WordPress administrators create translated versions of posts, pages, and supported public post types.

LinguaRank AI is made for sites that 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.
• Elementor pages, standard and third-party widgets, repeaters, nested containers, Atomic widgets, and referenced saved templates.
• 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.
• WooCommerce product text, safe product data, attributes, and variation descriptions when WooCommerce support is enabled.

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 and Elementor pages are split into smaller translation batches. The plugin processes those batches in sequence, checks the document 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.

Large sites and existing translations

The dashboard loads a limited, paginated set of source items and provides server-side search, so existing sites with hundreds or thousands of posts do not need to load every item at once. Bulk translations are processed sequentially. Background jobs use a shared worker lock and short cooldown to avoid launching many provider requests at the same time.

Maintenance work, such as marking completed translations for review after glossary changes, runs in small batches. Existing Polylang translations are left in place unless an administrator explicitly translates or clears the related source item.

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.

OpenAI and Google are configured through WordPress Settings > Connectors. DeepSeek and OpenRouter can be added in LinguaRank AI as optional direct backups. An administrator can also enable an OpenAI-compatible endpoint such as Ollama running on the web server or a trusted LiteLLM gateway. The first provider and fallback behavior can be selected in the plugin settings.

Translation tools

• A language-aware structured glossary for required translations and protected names, abbreviations, legal terms, and project-specific wording, including CSV import/export.
• Translation memory for repeated text fragments.
• A queue for translating several items one after another.
• A preflight estimate for approximate tokens, request count, and optional provider cost.
• Quality checks and a deterministic score for structure, SEO fields, slugs, completeness, and glossary compliance.
• Review statuses, reviewer assignments, and snapshots before an existing generated translation is replaced.
• Automatic locks that protect manually edited translations from an accidental AI overwrite.
• A local Elementor compatibility report and an adapter API for unusual third-party widgets.
• A redacted diagnostics export for support without exposing API keys or glossary text.
• 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, a DeepSeek/OpenRouter backup key, or an enabled OpenAI-compatible endpoint.

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 the provider selected in WordPress AI Client, or directly to the optional DeepSeek and OpenRouter backups. Common WordPress AI Client connectors include OpenAI and Google Gemini:

• 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

An administrator may enter a custom OpenAI-compatible Chat Completions endpoint. Public endpoints must use HTTPS. Plain HTTP is accepted only for loopback addresses on the WordPress server (localhost, 127.0.0.1, or ::1). The custom service receives the same selected text and translation instructions described above. Its operator’s terms and privacy policy apply. A local Ollama address refers to the server that runs WordPress, not automatically to the administrator’s personal computer.

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 DeepSeek, OpenRouter, and optional custom-provider keys are stored in the current WordPress database and are excluded from settings exports and diagnostics. When OpenSSL is available, saved keys are encrypted before storage. OpenAI and Google keys remain under WordPress Settings > Connectors and are not stored by LinguaRank AI.

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.

Third-party assets

The Manrope font is bundled locally for the LinguaRank AI admin interface. Copyright 2018 The Manrope Project Authors. Manrope is licensed under the SIL Open Font License 1.1; the full license is included at assets/fonts/OFL.txt. No font is loaded from a remote service.