
CUSTOM META WIDGET
Custom Meta Widget translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Custom Meta Widget does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Acts like the standard Meta widget while adding controls over which of the standard Meta links are shown.
- Can hide any, all, or none of the standard Meta widget links.
- Can add a custom link to the Meta widget output.
- Includes compatibility with links added by other themes or plugins via wp_meta().
- Uses a separate widget titled "Custom Meta" rather than modifying the standard WordPress Meta widget.
- Provides an options page in the Appearance > Widgets area for configuring the widget.
Distinctive features
Adds selective control over standard Meta widget links, supports a custom added link, and includes links contributed through wp_meta().
Dynamic content
The evidence shows runtime widget output can vary based on which Meta links are enabled and whether a custom link is added. No broader dynamic content behavior is established.
SEO and metadata
No SEO metadata behavior is established in the supplied evidence.
URLs and navigation
The plugin outputs navigation-style links in a Meta widget format and can include a custom link. The evidence does not establish broader URL handling or site navigation behavior.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Custom Meta Widget does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This widget is limited to Meta-widget-style navigation output. It does not indicate broader site content handling, and the available evidence does not establish behavior for translation, forms, commerce, SEO metadata, or URL management beyond the widget’s link output.
COMMON QUESTIONS
Custom Meta Widget and REEID Translate FAQ.
Does the current evidence establish translation scope for Custom Meta Widget?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.