LinguaRank AI Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Developed by Irbis (irbiscss on WordPress.org).
LinguaRank AI creates translated Polylang versions of one original post, page, or selected public custom post type. The original can be Ukrainian, Russian, English, Polish, Turkish, or any configured Polylang language; it does not have to be Ukrainian.
The plugin is admin-only. It does not add public language buttons, front-end switchers, widgets, or visual flags. Polylang remains responsible for language relationships and admin language columns.
Core features:
- One-button translation from the post editor or the plugin dashboard.
- Bulk queue that translates selected pages one by one.
- Progressive translation jobs for large Gutenberg landing pages.
- Gutenberg structure preservation with fragment batching and validation.
- WordPress AI Client support with OpenAI, Gemini, DeepSeek, and OpenRouter direct fallback.
- Manual first-provider selection plus optional fallback.
- Provider benchmark for saved API keys.
- Model dropdowns to avoid typo-broken model IDs.
- Functional glossary and term rules included in every AI prompt.
- Translation memory for repeated fragments.
- Yoast SEO, Rank Math, AIOSEO, SEOPress-style fields, and UAS SEO metadata support.
- Optional review workflow with approve/needs-work statuses.
- Translation snapshots before overwriting existing generated pages.
- Multilingual SEO audit for translated titles, descriptions, slugs, hreflang, and internal links.
- Polylang string translation helper for registered admin strings.
- Media text helper for alt/title/caption checks without duplicating image files.
- Safe WooCommerce product data copy for translated product posts.
- Localized admin UI through the
linguarank-aitext domain and WordPress.org language packs. - Quality report after generation for structure, title, SEO, and slug checks.
- Safe deletion of generated translated pages from the Clear Translations action.
- Export/import of settings without API keys.
Requirements
- WordPress 7.0 or newer.
- PHP 7.4 or newer.
- Polylang installed and configured.
- A configured WordPress AI Client connector or at least one direct fallback AI provider API key saved in the plugin settings or defined in
wp-config.php. - WordPress AI Client mode also needs a compatible provider plugin, such as AI Provider for OpenAI, Google, or Anthropic, activated and configured in Settings > Connectors.
Optional supported SEO plugins/fields:
- Yoast SEO.
- Rank Math.
- AIOSEO-compatible title, description, and keyword fields.
- SEOPress-compatible title and description fields.
- UAS SEO fields: title, description, keywords, and slug.
AI Providers
Automatic mode tries providers in this order:
- WordPress AI Client.
- OpenAI direct fallback.
- Gemini direct fallback.
- DeepSeek direct fallback.
- OpenRouter direct fallback.
WordPress AI Client is the recommended WordPress 7.0+ path. It lets site owners configure AI credentials once in Settings > Connectors and lets LinguaRank AI use the configured provider without storing those credentials.
Manual mode lets an administrator choose the first provider. If provider fallback is enabled, LinguaRank AI tries the remaining available providers after the selected one. If fallback is disabled, only the selected provider is used.
Direct provider endpoints must be public HTTPS URLs. With strict provider hosts enabled, direct fallback requests are limited to official OpenAI, Gemini, DeepSeek, and OpenRouter API hosts.
External Services
LinguaRank AI can send translation requests through the WordPress AI Client when the site owner has configured a provider in Settings > Connectors. In that mode, provider credentials are managed by WordPress and compatible provider plugins, not by LinguaRank AI.
LinguaRank AI can also connect directly to AI providers selected by an administrator as fallback providers: OpenAI, Google Gemini, DeepSeek, and OpenRouter. Direct requests are made with the WordPress HTTP API only after an administrator saves a provider key and starts translation or enables auto-translation.
Content sent can include source post content, selected SEO metadata, taxonomy/custom field text, glossary instructions, and target language data. No remote JavaScript, CSS, tracking pixels, iframes, license checks, or plugin updates are loaded from those services.
Provider terms and privacy links:
- OpenAI Terms: https://openai.com/policies/terms-of-use/ and Privacy Policy: https://openai.com/policies/privacy-policy/
- Google Gemini API Terms: https://ai.google.dev/terms and Privacy Policy: https://policies.google.com/privacy
- DeepSeek Terms: https://cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html and Privacy Policy: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html
- OpenRouter Terms: https://openrouter.ai/terms and Privacy Policy: https://openrouter.ai/privacy
API Keys
WordPress AI Client keys are managed by WordPress in Settings > Connectors. Direct fallback API keys are entered in the LinguaRank AI admin screen. Saved direct fallback keys are stored only in the current WordPress database and are not written into plugin files or the installation ZIP.
When OpenSSL is available, saved keys are encrypted before storage. Leaving a key field empty while saving keeps the already saved key unchanged.
Supported constants:
LINGUARANK_AI_OPENAI_API_KEYLINGUARANK_AI_GEMINI_API_KEYLINGUARANK_AI_DEEPSEEK_API_KEYLINGUARANK_AI_OPENROUTER_API_KEY
Gutenberg Translation
The plugin translates readable text fragments while preserving Gutenberg comments, block names, nesting, attributes, classes, IDs, links, shortcodes, JSON keys, and layout data.
Large pages are processed progressively. LinguaRank AI estimates content size, splits work into safe batches, translates fragments step by step, validates the result, and then saves the translated Polylang page. The user clicks the translation button once; the job continues through AJAX and WP-Cron until complete.
Images are not duplicated or edited. Image references stay the same. Alt text and captions inside block markup can be translated when they are stored as text.
Workflow And Review
The Start screen is designed for a non-technical administrator: add keys, choose languages, select content, and run translation. Advanced model, endpoint, custom field, and automation settings are kept in a separate advanced area.
The Queue screen lets an administrator select multiple visible posts or pages and process them sequentially. Each item still runs as a normal progressive translation job, so large pages are split into safe batches.
When review is enabled, completed translations are marked as needing review. A reviewer can approve a translated page, mark it as needing work, or restore the latest snapshot saved before an overwrite.
SEO Translation
For each target language, Irbis adapts:
- post title and excerpt;
- post slug;
- SEO title;
- meta description;
- focus keyphrase;
- additional keyphrases and synonyms where supported;
- meta keywords;
- Open Graph and Twitter title/description where supported;
- UAS SEO title, description, keywords, and slug.
Slugs are not copied mechanically. If the source slug is Russian, Ukrainian, or Polish words written with Latin letters, the plugin asks AI to infer the meaning and generate a short target-language slug, then sanitizes it into lowercase Latin hyphenated text.
The SEO Audit screen checks visible translated content for missing SEO titles, missing descriptions, identical slugs, very short descriptions, and source-language internal links when a translated target exists.
Polylang registered strings can be translated from the Strings screen when Polylang exposes its string table in the current admin environment. This is optional and disabled by default.
Media And WooCommerce
LinguaRank AI does not generate translated image files. This keeps media libraries light and avoids heavy AI image output. The plugin reuses the same image files and helps localize text metadata where it is stored as post text or media text.
For WooCommerce products, LinguaRank AI can safely copy technical product meta such as prices, SKU, stock, tax class, dimensions, and product flags. It does not translate IDs, layout data, colors, or binary media values.
Glossary And Rules
The glossary is functional. Every non-empty glossary line is included in AI prompts for Gutenberg text, plain text, titles, excerpts, SEO fields, and selected custom meta.
The default glossary is based on the supplied prompt rules: translate only visible text, preserve structure and technical identifiers, use native legal/accounting/tax terminology, keep brands and official names stable, handle FOB/FOP/ФОП and ESW/E-SW carefully, and adapt SEO for real search intent.
Custom glossary lines are appended after the default rules and can override terminology for a project.
Languages
Built-in language definitions:
- Ukrainian:
uk - Russian:
ru - English:
en - Polish:
pl
Additional languages can be added from the language catalog in settings. Open the Additional Languages panel, search for a language, check it, and save. LinguaRank AI creates missing selected languages in Polylang automatically when Polylang exposes its language model.
Only languages that are enabled in LinguaRank AI are shown as translation targets. The original language is skipped automatically.
Clear Translations
The Clear Translations button deletes translated pages generated by Irbis for the selected original page and clears LinguaRank AI statuses, progress, quality report, and Polylang links for that source. The original page is never deleted.
The deletion routine only targets pages that can be linked back to the selected source through LinguaRank AI metadata or verified Polylang relationships.
Admin Localization
The admin UI uses the linguarank-ai text domain and is ready for translate.wordpress.org. The package includes a POT catalog for reviewers and translators, while locale files are generated and delivered by WordPress.org language packs after publication.
Privacy
When translation is requested, source content, selected SEO metadata, taxonomy/custom field text when enabled, and glossary instructions are sent to the configured WordPress AI Client provider or selected direct fallback AI provider. This happens only after an administrator configures a WordPress AI Client connector or direct provider key and starts translation or enables auto-translation. Provider billing dashboards, terms, and privacy policies remain the source of truth for retention and usage. Direct fallback API keys are never shown back in forms and are excluded from settings export.
Uninstall
Uninstall removes LinguaRank AI options, diagnostics, translation memory, capabilities, and _linguarank_ai_* service metadata. It does not delete translated posts/pages; use Clear Translations before uninstalling when you want generated translations removed.
Screenshots
No screenshots provided
