WAKALANG
WakaLang compatibility with REEID Translate
WakaLang compatibility with REEID Translate is being reviewed using official plugin documentation. Generates and outputs hreflang alternate links (optionally including x-default) for translated content, with x-default derived from the current page’s default-language URL when left empty. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What WakaLang does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
WakaLang is documented in the SEO category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How WakaLang compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Generates and outputs hreflang alternate links (optionally including x-default) for translated content, with x-default derived from the current page’s default-language URL when left empty.
- Scopes language-specific archives, search, RSS/Atom feeds, and the core wp-sitemap.xml to the current language.
- Provides per-translation SEO title and meta description values and hands them to WordPress core; it also supports Yoast and Rank Math by providing their meta inputs without directly modifying their own meta.
- Implements URL-prefix language routing where the URL prefix is the single source of truth for the active language, and keeps internal/menu/navigation links within the current language prefix.
- Ensures each page’s attribute (and dir="rtl" for right-to-left languages) is set directly from the plugin’s configured language registry, independent of installed language packs.
- Translates taxonomy terms (category, tag, and custom taxonomies) with per-language name and slug, and supports linking posts/pages/terms into translation groups with draft translations.
- Provides language switcher output via automatic header/footer placement, an editor block, and a shortcode ([wakalang_switcher]) plus a template function (wakalang_language_switcher()).
TRANSLATION BOUNDARY
WakaLang capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
WakaLang and REEID Translate FAQ.
What does WakaLang do?
WakaLang has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does WakaLang have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from WakaLang?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate WakaLang in a multilingual WordPress workflow.
REEID documents WakaLang functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.