DEVICE-BASED REDIRECT
Device-Based Redirect compatibility with REEID Translate
Device-Based Redirect compatibility with REEID Translate is being reviewed using official plugin documentation. , "Device-based redirection routing using user agent detection to send visitors to specific iOS, Android, or fallback URLs", "Page-specific redirect configuration allowing different destination URLs for individual WordPress pages based on device type", "Custom URL slug redirection enabling creation of unique entry points that route users to platform-specific destinations", "Deep linking support facilitating navigation to specific app sections via platform-appropriate deep link schemes", "302 temporary redirect implementation ensuring non-permanent routing suitable for dynamic marketing campaigns and app promotions", "Transient caching mechanism for redirect data to optimize performance and reduce database load on high-traffic sites", "Bulk enable/disable controls for managing all active redirects simultaneously through the admin interface"], "unknowns": [ No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Device-Based Redirect 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
Device-Based Redirect is documented in the Navigation category with 3 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 Device-Based Redirect 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
- , "Device-based redirection routing using user agent detection to send visitors to specific iOS, Android, or fallback URLs", "Page-specific redirect configuration allowing different destination URLs for individual WordPress pages based on device type", "Custom URL slug redirection enabling creation of unique entry points that route users to platform-specific destinations", "Deep linking support facilitating navigation to specific app sections via platform-appropriate deep link schemes", "302 temporary redirect implementation ensuring non-permanent routing suitable for dynamic marketing campaigns and app promotions", "Transient caching mechanism for redirect data to optimize performance and reduce database load on high-traffic sites", "Bulk enable/disable controls for managing all active redirects simultaneously through the admin interface"], "unknowns": [
- Specific integration behavior with third-party navigation menus or breadcrumb plugins
- Exact logic for handling query string preservation during device-based redirects
TRANSLATION BOUNDARY
Device-Based Redirect 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
Device-Based Redirect and REEID Translate FAQ.
What does Device-Based Redirect do?
Device-Based Redirect has 3 documented features listed in its official documentation. See the Plugin Information section for details.
Does Device-Based Redirect 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 Device-Based Redirect?
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 Device-Based Redirect in a multilingual WordPress workflow.
REEID documents Device-Based Redirect 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.