RiTriever
by rioriost 0 (0 reviews)

RiTriever

Adds RAG-style vector retrieval to WordPress search using native database vector indexes and configurable embeddings.

RiTriever ranks #51,507 among WordPress.org plugins with 0+ active installations, and was last updated Sep 23, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v0.2.5 Current Version v0.2.5
Updated 1 month ago Last Update on 23 Sep, 2026
Refreshed 1 week ago Last Refreshed on
View on WordPress.org
Rank
#51,507
— No change
Active Installs
0+
-100%
KW Avg Position
77
— No change
Downloads
364
+1 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 40%
0+ 10+
23,939
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 6 more installs to reach 10+

Rank Changes

48,932 50,219 51,507 52,795 54,082 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
59,938 63,483 67,028 70,573 74,118 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #51,507
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 10 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version
0.2.5
Last Updated
Sep 23, 2026
Requires WP
6.6+
Tested Up To
7.1.4
PHP Version
8.1 or higher
Author
rioriost

Support & Rating

Rating
☆ ☆ ☆ ☆ ☆ 0
Reviews
0
Support Threads
0
Resolved
0%

Keywords

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Frequently Asked Questions

Common questions about RiTriever

OpenAI and Azure OpenAI are supported as external hosted embedding providers.
Yes. Ollama, LM Studio, Infinity, TEI, and Custom HTTP endpoints are available for local or self-hosted embeddings.
Only when an external embedding provider is configured. See the External services section for details.
Yes. MariaDB 11.7 or later is the primary supported target for native vector columns and indexes.
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.
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.
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.
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.

Sign In / Register

You need to sign in or register to use this feature.