WEUX CONTENT FINDER
WEUX Content Finder compatibility with REEID Translate
WEUX Content Finder compatibility with REEID Translate is being evaluated from available plugin evidence. Searches for exact text across WordPress posts, pages, and public custom post types, returning matching results with direct edit links. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WEUX Content Finder.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
WEUX Content Finder is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How WEUX Content Finder compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Searches for exact text across WordPress posts, pages, and public custom post types, returning matching results with direct edit links.
- Searches Gutenberg block editor content within post bodies.
- Searches WordPress Site Editor / Full Site Editing entities including block templates (`wp_template`), template parts (`wp_template_part`), synced patterns (`wp_block`), and navigation (`wp_navigation`), with results linking to the matching Site Editor targets where available.
- Searches block theme files from the active theme (e.g., `templates/*.html`, `parts/*.html`, and referenced `patterns/*.php`) and provides editor-focused deep links to the relevant template/template part/pattern usage.
- Searches navigation menus and can include classic menu items when the active theme supports classic menus.
- Detects Elementor content and provides an “Edit in Elementor” link for matching Elementor pages when Elementor data is detected.
- Provides an admin search workflow with optional filtering by content type and a results review step including match count, snippet, status, and modified date; clicking a result opens the best available editor target.
- Free version runs search inside the WordPress site and does not change content; Pro is described as a separate package that adds preview-first Search and Replace, ACF field search/replace, and batch undo (with free package described as not including executable Pro mutation endpoints).
CONTENT BOUNDARY
WEUX Content Finder capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
WEUX Content Finder and REEID Translate FAQ.
What does WEUX Content Finder do according to the available plugin evidence?
WEUX Content Finder has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for WEUX Content Finder?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WEUX Content Finder?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate WEUX Content Finder in a multilingual WordPress workflow.
REEID documents WEUX Content Finder functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.