Title: RiTriever Author: rioriost Published: Juli 3, 2026 Last modified: Séptémber 23, 2026 --- Search plugins ![](https://ps.w.org/ritriever/assets/banner-772x250.jpg?rev=3595237) ![](https://ps.w.org/ritriever/assets/icon.svg?rev=3595237) # RiTriever By [rioriost](https://profiles.wordpress.org/rioriost/) [Download](https://downloads.wordpress.org/plugin/ritriever.0.2.5.zip) * [Details](https://su.wordpress.org/plugins/ritriever/#description) * [Reviews](https://su.wordpress.org/plugins/ritriever/#reviews) * [Installation](https://su.wordpress.org/plugins/ritriever/#installation) * [Development](https://su.wordpress.org/plugins/ritriever/#developers) [Support](https://wordpress.org/support/plugin/ritriever/) ## Description RiTriever adds RAG-style vector retrieval to WordPress search. Published content is embedded, stored in a local vector table, and blended with standard WordPress search results. The plugin is intended for WordPress sites that can use native database vector support, primarily MariaDB 11.7 or later. It can index posts, pages, and configured public post types, then use those vectors during front-end search. Main features: * RAG-style search blending with standard WordPress search. * Native vector storage in the WordPress database. * OpenAI and Azure OpenAI support for external embedding APIs. * Local or self-hosted embedding support through Ollama, LM Studio, Infinity, TEI, or Custom HTTP endpoints. * RAG target language selection from WordPress-supported locales. * Admin diagnostics for database support, embedding providers, indexing progress, and live vector queries. External API use is optional. WordPress 7.0 AI Client does not provide embedding generation, so RiTriever uses direct embedding APIs when external embeddings are configured. Post content and configured custom field values are sent to the selected provider to create embeddings. ### External services RiTriever connects to external services only when you select an external embedding provider. It sends post titles, post excerpts, post content chunks, selected taxonomy terms, selected custom field values, and short admin test strings when indexing or testing embeddings. The vectors returned by the provider are stored in your WordPress database. WordPress 7.0 includes the WordPress AI Client for supported AI capabilities, but the current AI Client announcement and implementation do not include an embeddings API. Because RiTriever requires text embeddings for vector search, it calls embedding providers directly instead of using WordPress AI Client. Reference: https://make. wordpress.org/core/2026/03/24/introducing-the-ai-client-in-wordpress-7-0/ OpenAI sends embedding requests to OpenAI for `text-embedding-3-small` or `text- embedding-3-large`. This service is provided by OpenAI: Terms of use https://openai. com/policies/terms-of-use/ and Privacy policy https://openai.com/policies/privacy- policy/. Azure OpenAI sends embedding requests to your configured Azure OpenAI endpoint. This service is provided by Microsoft Azure: Terms of use https://www.microsoft. com/licensing/terms/productoffering/MicrosoftAzure/MCA and Privacy statement https:// privacy.microsoft.com/privacystatement. Local or self-hosted endpoints, including Ollama, LM Studio, Infinity, TEI, and Custom HTTP, receive the same embedding inputs when selected. Review the terms, privacy policy, and network location for the endpoint you operate or configure. ## Installation 1. Upload the `ritriever` folder to `/wp-content/plugins/`, or install the release ZIP from the WordPress admin. 2. Activate `RiTriever` from the Plugins screen. 3. Open Settings -> RiTriever. 4. Run the database capability test. 5. Choose the RAG target language. 6. Configure and test the embedding provider. 7. Initialize the index. ## FAQ ### Which external embedding providers are supported? OpenAI and Azure OpenAI are supported as external hosted embedding providers. ### Can I use a local embedding server? Yes. Ollama, LM Studio, Infinity, TEI, and Custom HTTP endpoints are available for local or self-hosted embeddings. ### Does this plugin send content to external APIs? Only when an external embedding provider is configured. See the External services section for details. ### Does it require native vector database support? Yes. MariaDB 11.7 or later is the primary supported target for native vector columns and indexes. ### What happens when I change the target language or embedding model? The index becomes unavailable to hybrid search until initialization completes. Saving settings does not drop the existing vector table or automatically send every post to the provider. Back up the database and explicitly run initialization after changing target language, provider, model, dimensions, chunking, indexing scope, or vector index settings. Initialization rebuilds vectors and may incur embedding API charges. ### How are post updates indexed? After initialization, post, selected metadata, and taxonomy changes enter a background queue. Search reflects those changes when the queue processes them. WP-Cron needs site traffic or an external scheduler; keeping the settings page open is not a substitute for scheduled processing. ### What happens when retrieval fails? The original WordPress search remains available, including its native pagination. Failed retrievals are not cached as successful hybrid results. Healthy hybrid search uses a bounded candidate set and does not promise every native search match. ### Does upgrading to 0.2.5 require initialization? When upgrading from the published 0.2.4 or earlier, yes. Existing content hashes are not proof of storage in the new index generation. Back up the database, verify customized endpoints, and explicitly initialize once; external embedding providers may charge for reindexing. A previously overwritten endpoint must be re-entered. All WordPress source tables used for indexing must use InnoDB. If you already installed a generation-aware development build and its index is ready, the version change and front-end hook fix alone do not require another reindex. Replace the existing plugin rather than uninstalling it, since uninstall removes plugin settings and index data. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “RiTriever” is open source software. The following people have contributed to this plugin. Contributors * [ rioriost ](https://profiles.wordpress.org/rioriost/) [Translate “RiTriever” into your language.](https://translate.wordpress.org/projects/wp-plugins/ritriever) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/ritriever/), check out the [SVN repository](https://plugins.svn.wordpress.org/ritriever/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/ritriever/) by [RSS](https://plugins.trac.wordpress.org/log/ritriever/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.2.5 * Restore front-end semantic search with Visualizer and other earlier pre_get_posts callbacks while preserving effective query constraints. * Add index generations, durable storage receipts, atomic vector and metadata writes, and protection against stale concurrent workers. * Fix Unicode chunk boundaries, reinitialization and republication skips, queue recovery, retry progress, and metadata/taxonomy synchronization. * Preserve customized embedding endpoints and locales; validate HTTP responses, vector ordering, dimensions, and numeric values. * Preserve native search and pagination on retrieval failure; fix cache invalidation, title decoration, multisite isolation, and uninstall cleanup. * Add regression coverage and Apple Container compatibility/release gates. #### 0.2.4 * Confirm compatibility with the stable WordPress 7.1 release and run Plugin Check on WordPress 7.1. #### 0.2.3 * Resolve remaining Plugin Check SQL preparation warnings for dynamic queue, vector, and uninstall queries. #### 0.2.2 * Escape search title filter output consistently and prepare plugin table identifiers in direct SQL calls. #### 0.2.1 * Tighten WordPress.org review gates and clarify external embedding API documentation. #### 0.2.0 * Rename the public plugin name and WordPress.org slug to RiTriever. * Add RAG target language selection based on WordPress-supported locales. * Document why direct embedding APIs are used instead of WordPress AI Client. * Add WordPress.org release gates for PHPCS, Plugin Check, readme, i18n, and package contents. ## Meta * Version **0.2.5** * Last updated **2 dinten ago** * Active installations **Fewer than 10** * WordPress version ** 6.6 or higher ** * Tested up to **7.1.2** * PHP version ** 8.1 or higher ** * Language * [English (US)](https://wordpress.org/plugins/ritriever/) * Tags * [embeddings](https://su.wordpress.org/plugins/tags/embeddings/)[rag](https://su.wordpress.org/plugins/tags/rag/) [search](https://su.wordpress.org/plugins/tags/search/)[semantic search](https://su.wordpress.org/plugins/tags/semantic-search/) [vector search](https://su.wordpress.org/plugins/tags/vector-search/) * [Advanced View](https://su.wordpress.org/plugins/ritriever/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/ritriever/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/ritriever/reviews/) ## Contributors * [ rioriost ](https://profiles.wordpress.org/rioriost/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/ritriever/)