POLYGLOT FOR POLYLANG
Polyglot for Polylang compatibility with REEID Translate
Polyglot for Polylang compatibility with REEID Translate is being evaluated from available plugin evidence. Runs controlled translation jobs from the WordPress admin under Tools > Polyglot for Polylang. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Polyglot 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
Polyglot 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 Polyglot 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
- Runs controlled translation jobs from the WordPress admin under Tools > Polyglot for Polylang.
- Translates Polylang String Translation entries and can translate existing Polylang-linked Pages/Posts/public Custom Post Types (CPTs).
- Supports translation of default content fields (title, content, excerpt) and optionally custom fields (with an explicit risk acknowledgment checkbox before starting).
- Implements eligibility rules to translate only when the target value is empty (or equals the source value) and to skip when the target contains different non-empty content (treated as edited).
- When custom-field translation is enabled, auto-detects non-protected meta keys and applies safety safeguards (skips protected/internal keys and technical key patterns; skips values that look serialized/JSON/URL/numeric/token-like) and provides an exclusion hook `polyglot_excluded_meta_keys`.
- Processes translation jobs in background batches using WP-Cron and provides a progress view with counts (remaining/scanned/translatable/translated/skipped/failed) and last error details; if no eligible fields are found it shows a success notice and does not start a queue.
- Uses Google Cloud Translation API (Basic v2) authenticated via an API key; sends source text plus source/target language codes to `https://translation.googleapis.com/language/translate/v2` during jobs and calls the languages list endpoint for API key validation when testing the saved key.
CONTENT BOUNDARY
Polyglot 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
Polyglot for Polylang and REEID Translate FAQ.
What does Polyglot for Polylang do according to the available plugin evidence?
Polyglot 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 Polyglot 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 Polyglot 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 Polyglot for Polylang in a multilingual WordPress workflow.
REEID documents Polyglot 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.