AUTOLINGO
AutoLingo — Automatic Translation for Polylang compatibility with REEID Translate
AutoLingo — Automatic Translation for Polylang compatibility with REEID Translate is being evaluated from available plugin evidence. Auto-translates Polylang posts and pages using selectable external providers (DeepL, OpenAI/ChatGPT, or Google Translate) triggered by publish, manual action, or WP-CLI. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for AutoLingo — Automatic Translation for Polylang.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
AutoLingo — Automatic Translation for Polylang is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How AutoLingo — Automatic Translation for Polylang compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Auto-translates Polylang posts and pages using selectable external providers (DeepL, OpenAI/ChatGPT, or Google Translate) triggered by publish, manual action, or WP-CLI.
- Supports Gutenberg content translation including title, blocks, and excerpt, with translation available on publish or manually.
- Provides translation controls including a manual translate button in the post editor and post list, plus bulk translation via WP-CLI commands (e.g., translate-missing, translate-all).
- Performs Polylang navigation menu translation and syncs translated categories and tags via Polylang.
- Implements translation reliability behaviors such as retrying on HTTP 429 with exponential back-off (2s → 4s → 8s) up to 3 retries and using a dual lock (static + transient) to prevent duplicate translations on Gutenberg REST saves.
- Preserves shortcode-based builder markup during translation by replacing shortcodes with neutral placeholders before sending to the translation API and restoring them verbatim afterward (including protection across DeepL, Google Translate, and OpenAI).
- Includes credit-balance checking before each translation and surfaces an admin alert/dashboard widget when credit runs low (for the DeepL Free/Pro plan behavior described).
CONTENT BOUNDARY
AutoLingo — Automatic Translation for Polylang capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AutoLingo — Automatic Translation for Polylang and REEID Translate FAQ.
What does AutoLingo — Automatic Translation for Polylang do according to the available plugin evidence?
AutoLingo — Automatic Translation for Polylang has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for AutoLingo — Automatic Translation for Polylang?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for AutoLingo — Automatic Translation for Polylang?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate AutoLingo — Automatic Translation for Polylang in a multilingual WordPress workflow.
REEID documents AutoLingo — Automatic Translation for Polylang functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.