USAGERAY
UsageRay compatibility with REEID Translate
UsageRay compatibility with REEID Translate is being reviewed using official plugin documentation. Read-only plugin usage and dependency auditing for administrators (site-wide audit and per-plugin scans) No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What UsageRay 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
UsageRay is documented in the Other 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 UsageRay 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
- Read-only plugin usage and dependency auditing for administrators (site-wide audit and per-plugin scans)
- Adds a “Find usage” action on the Installed Plugins screen and integrates “Deactivation Preflight”/bulk “Review deactivation with UsageRay” workflows without automatically deactivating plugins
- Scans and attributes multiple dependency surfaces (content, Gutenberg blocks, shortcodes, legacy widgets, custom post types, reusable blocks, Site Editor templates/parts, navigation records, cron events, and custom database tables) and links to matching edit screens when available
- Performs evidence/risk reporting with explicit uncertainty and a Scan Coverage manifest distinguishing checked vs unsupported/failed/partially inspected surfaces
- Supports audit control and persistence: cancel/resume after reload for running audits; resumes automatically if a page reload occurs; temporary audit data expires after one hour
- Exports completed audit results as CSV or JSON with scan coverage/limitations and evidence counts/locations, while omitting sensitive values (e.g., post content, metadata values, option values, filesystem paths, and cron event arguments)
- Implements safety around deactivation: opening scans/preflights never changes plugin state; deactivation requires separate explicit confirmation handled by WordPress’s normal nonce-protected workflow
TRANSLATION BOUNDARY
UsageRay 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
UsageRay and REEID Translate FAQ.
What does UsageRay do?
UsageRay has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does UsageRay 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 UsageRay?
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 UsageRay in a multilingual WordPress workflow.
REEID documents UsageRay 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.