OPENSOLR SEARCH
Opensolr Search translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Opensolr Search 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
- 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.
Distinctive features
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.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Opensolr Search 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 integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Opensolr Search and REEID Translate FAQ.
Does the current evidence establish translation scope for Opensolr Search?
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.