AYM MULTILINGUAL LITE
AYM Multilingual Lite compatibility with REEID Translate
AYM Multilingual Lite compatibility with REEID Translate is being evaluated from available plugin evidence. Generates clean language-based URL paths (e.g., `/tr/`, `/en/`, `/de/`) for multilingual pages No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for AYM Multilingual Lite.
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
AYM Multilingual Lite is documented in the SEO category with 8 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 AYM Multilingual Lite 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
- Generates clean language-based URL paths (e.g., `/tr/`, `/en/`, `/de/`) for multilingual pages
- Adds multilingual SEO relationship handling via `hreflang` and `canonical` for translated pages
- Clones and manages translations for Pages, Posts, and supported public Custom Post Types (including a “+ Language” action)
- Supports per-language menu mapping (assigning different menus to different languages)
- Supports per-language header and footer template mapping for Elementor Theme Builder and ElementsKit
- Provides a language switcher via a built-in shortcode and via language switcher controls in the WordPress admin
- Optionally performs browser-language detection and redirects first-time visitors to the matching language (off by default)
- Includes a built-in read-only “Health” panel for multilingual configuration checks (e.g., missing/duplicate translations, broken mappings/links, template mismatches)
CONTENT BOUNDARY
AYM Multilingual Lite 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
AYM Multilingual Lite and REEID Translate FAQ.
What does AYM Multilingual Lite do according to the available plugin evidence?
AYM Multilingual Lite has 8 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 AYM Multilingual Lite?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for AYM Multilingual Lite?
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 AYM Multilingual Lite in a multilingual WordPress workflow.
REEID documents AYM Multilingual Lite 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.