AUTOPOLY
AutoPoly – AI Translation For Polylang translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what AutoPoly – AI Translation For Polylang does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides automatic translation for Polylang-managed multilingual content by duplicating and translating page/post titles, content, images, galleries, and meta fields.
- Supports translation workflows for Elementor, including translating Elementor pages, sections, widgets, and templates while preserving original layout/styling (as stated).
- Supports translation workflows for Gutenberg, including translating core blocks and selected third-party Gutenberg block libraries (Spectra, Kadence Blocks, Stackable, Otter Blocks, Essential Blocks as stated).
- Supports translation for Divi content (Divi Builder pages/layouts as stated), with “Divi 5 Page Translation” described as Pro-only.
- Supports translation of selected ACF field types (Text, Textarea, WYSIWYG) in Gutenberg pages as stated.
- Uses translation providers described as Chrome built-in AI and Yandex Translate API; the README states no Yandex account/API key is required and lists the Yandex endpoint used for API calls.
- Includes an “inline translation” capability described in the README (with “Inline Translation” marked available on Free and also described for Pro).
- Does not claim automatic page/post synchronization across languages; the FAQ states updates to the original content do not automatically appear in translated versions.
Distinctive features
Provides automatic translation for Polylang-managed multilingual content by duplicating and translating page/post titles, content, images, galleries, and meta fields. Supports translation workflows for Elementor, including translating Elementor pages, sections, widgets, and templates while preserving original layout/styling (as stated). Supports translation workflows for Gutenberg, including translating core blocks and selected third-party Gutenberg block libraries (Spectra, Kadence Blocks, Stackable, Otter Blocks, Essential Blocks as stated). Supports translation for Divi content (Divi Builder pages/layouts as stated), with “Divi 5 Page Translation” described as Pro-only. Supports translation of selected ACF field types (Text, Textarea, WYSIWYG) in Gutenberg pages as stated. Uses translation providers described as Chrome built-in AI and Yandex Translate API; the README states no Yandex account/API key is required and lists the Yandex endpoint used for API calls. Includes an “inline translation” capability described in the README (with “Inline Translation” marked available on Free and also described for Pro). Does not claim automatic page/post synchronization across languages; the FAQ states updates to the original content do not automatically appear in translated versions.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what AutoPoly – AI Translation For Polylang does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AutoPoly – AI Translation For Polylang and REEID Translate FAQ.
Does the current evidence establish translation scope for AutoPoly – AI Translation For Polylang?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.