OPENSOLR SEARCH
Opensolr Search compatibility with REEID Translate
Opensolr Search compatibility with REEID Translate is being evaluated from available plugin evidence. Hosted search backend: replaces WordPress default search with a hosted Apache Solr search engine; search queries are sent directly to Opensolr cloud infrastructure (zero search load on WordPress server). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Opensolr Search.
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
Opensolr Search is documented in the Analytics category with 7 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 Opensolr Search 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
- Hosted search backend: replaces WordPress default search with a hosted Apache Solr search engine; search queries are sent directly to Opensolr cloud infrastructure (zero search load on WordPress server).
- Hybrid keyword + vector search: combines keyword matching (BM25) with semantic vector search using 1024-dim embeddings.
- Search analytics collection (optional): can track queries, clicks, CTR, no-results queries, and visitor patterns; click tracking includes clicked result URL/title/position/query and stores a SHA-256 hash of the visitor IP (raw IP not stored).
- AI features (optional): can generate AI Hints (streamed answers) and an AI Reader summary; AI requests are based on the top matching documents from the site’s already-indexed content.
- Frontend script injection for embeddable mode (optional): loads `https://search.opensolr.com/embed.js` only when Search Mode is set to “Embeddable”; in Native mode the script is not loaded.
- Indexing methods: supports automatic Web Crawler indexing via sitemap and a Data Ingestion API that pushes post content + metadata from WordPress (cron worker and real-time sync on post save/delete).
- Multilingual compatibility behavior: when WPML or Polylang is active, search results are automatically filtered to the current language/locale.
CONTENT BOUNDARY
Opensolr Search 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
Opensolr Search and REEID Translate FAQ.
What does Opensolr Search do according to the available plugin evidence?
Opensolr Search has 7 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 Opensolr Search?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Opensolr Search?
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 Opensolr Search in a multilingual WordPress workflow.
REEID documents Opensolr Search 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.