
EDGE LINK ROUTER
Edge Link Router compatibility with REEID Translate
Edge Link Router compatibility with REEID Translate is being reviewed using official plugin documentation. , "Supports creation of custom short link redirects using the /go/ prefix with configurable HTTP status codes (301, 302, 307, 308).", "Automatically appends UTM parameters to target URLs and passes through original query strings.", "Provides a catch-all redirect rule to route all 404 errors to a specified homepage or URL.", "Enables CSV import and export functionality for bulk management and migration of redirect rules.", "Offers optional integration with Cloudflare Workers for edge-level redirect handling with fail-open fallback to WordPress.", "Tracks aggregated daily click statistics without storing personal data such as IP addresses or user agents." ], No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Edge Link Router 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
Edge Link Router is documented in the Navigation category with 1 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 Edge Link Router 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
- , "Supports creation of custom short link redirects using the /go/ prefix with configurable HTTP status codes (301, 302, 307, 308).", "Automatically appends UTM parameters to target URLs and passes through original query strings.", "Provides a catch-all redirect rule to route all 404 errors to a specified homepage or URL.", "Enables CSV import and export functionality for bulk management and migration of redirect rules.", "Offers optional integration with Cloudflare Workers for edge-level redirect handling with fail-open fallback to WordPress.", "Tracks aggregated daily click statistics without storing personal data such as IP addresses or user agents." ],
TRANSLATION BOUNDARY
Edge Link Router 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
Edge Link Router and REEID Translate FAQ.
What does Edge Link Router do?
Edge Link Router has 1 documented features listed in its official documentation. See the Plugin Information section for details.
Does Edge Link Router 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 Edge Link Router?
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 Edge Link Router in a multilingual WordPress workflow.
REEID documents Edge Link Router 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.