SleekView Feedback for Relevanssi
Relevanssi indexes posts into the wp_relevanssi table and logs queries into wp_relevanssi_log. SleekView renders one feedback card per indexed post, lets editors and SEOs upvote, and tags entries with status badges so search relevance stays inside WordPress.
♾️ Lifetime License available
Search relevance reviews built on the Relevanssi tables
Relevanssi keeps its own custom tables, including wp_relevanssi for the index itself and wp_relevanssi_log for the search query log, which captures every query along with hit count, timestamp, and the matched post identifiers. The default admin gives you a User Searches screen and an indexing console, but no public-facing way to see which results the team most wants to improve or which the SEO team has already triaged this quarter.
SleekView reads those tables directly and renders one feedback card per indexed post. Pick the post hit count from the log as the vote weight, attach a rl_review_status meta for the status badge, and pull the post category as the chip. Editors and SEOs can upvote a result card to flag content that is ranking for the wrong query or to highlight a high-engagement result, and the increment writes back to the meta key you choose so reporting stays consistent.
Because SleekView is read-only against the Relevanssi records, the indexer, the User Searches screen, and the search filters keep working exactly as before. SleekView only adds a parallel review surface that ranks results by votes, shows category chips, and exposes status pills so anyone on the team can spot Wrong query, Needs boost, and Reviewed results at a glance.
Workflow
From wp_relevanssi_log to a feedback wall
Point SleekView at the Relevanssi log
Pick vote, status, and category
Embed the board on a public page
Upvotes write back to meta
Sample board
Sample Relevanssi review board
Comparison
Default Relevanssi versus SleekView Feedback
Default Relevanssi admin
- Admin-only User Searches screen with no public upvote, status pill, or category chip surface
- No way for editors or SEOs to surface broken results without filing a separate support ticket first
- Top results, no-results, and broken results all sit in the same log screen with no review pill
- Filtering by review state requires custom Relevanssi reports and still keeps data inside admin
- Result review counts and relevance signals live in spreadsheets instead of the Relevanssi log table
SleekView Feedback
-
Reads
wp_relevanssiandwp_relevanssi_logwith joined post meta and zero schema changes - Upvote button writes back to your chosen meta key so the score lives with the post
- Status pills map cleanly to Wrong query, Needs boost, Reviewed, and Archived out of the box
- Category chips pull the post taxonomy so each card shows the topic at a glance
- Saved views let SEOs share filtered boards like Top clicked or Needs boost without code
Features
What SleekView Feedback gives you for Relevanssi
Native Relevanssi tables support
SleekView speaks the Relevanssi schema. It maps wp_relevanssi, wp_relevanssi_log, and joined post meta to vote, status, and category fields automatically, so a search relevance feedback board can go live in minutes without writing custom Relevanssi hooks at all.
Real upvotes on real results
Each Upvote click increments a meta value on the underlying post. The score is queryable, exportable, and visible alongside the Relevanssi User Searches columns, which keeps the User Searches screen as the source of truth instead of forking the data into a separate tool.
Saved relevance triage views
SEOs get scoped saved views like Top clicked this week, Needs boost, or Wrong query. Each view is a stored filter on the wp_relevanssi_log records, so the team can hand off triage without rebuilding the filters every morning before the editorial standup begins.
Audience
Three teams that turn Relevanssi into a feedback board
SEO and search teams
SEOs see a ranked board of results sorted by Relevanssi hit count and tagged with review status. Wrong-query results float to the top of a Needs boost board so they get adjusted before customers keep clicking the old plans page from the search bar.
Editorial teams
Editors upvote results they want re-ranked, see the current hit count on each card, and stop filing duplicate Slack requests. The signal lives next to the post for the SEO team to act on at the next planning session without needing an email thread.
Agency search partners
Agencies running Relevanssi across many client sites scope each board per client. Status pills surface results that need re-ranking, and saved view links can be shared with stakeholders without giving them Relevanssi admin access on the client site at all.
The bigger picture
Why a Relevanssi setup needs a feedback loop
Relevanssi gives WordPress a real search engine, and the User Searches screen captures the exact data a relevance engineer would want. But that screen is admin-only, the log lives in a database table, and the moment a user fires a query the signal goes back to sleep. There is no view that ranks the whole site by hit count, no public surface where an editor can flag the top result that is pointing at the old plans page, no way for an SEO to share a Needs boost queue without exporting a spreadsheet.
The signal exists, it just lives in the wrong room. SleekView gives the Relevanssi log a public, vote-driven home. SEOs get a saved Triage board sorted by hit count and review status pill.
Editors get a feedback wall where they can flag a misbehaving search result without filing a ticket. Agency teams get per-client scoping so each engagement has its own ranked queue. Nothing about Relevanssi changes underneath, the engine and the User Searches screen stay the source of truth, and the review loop now lives where the team already works.
Questions
Common questions about SleekView Feedback for Relevanssi
No. SleekView reads the existing wp_relevanssi and wp_relevanssi_log records that Relevanssi already writes during indexing and search. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the post data without touching the Relevanssi tables or settings.
Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or to specific roles like Editor or SEO, you can flip that in the view settings without touching any code at all.
You map an rl_review_status meta key when you build the view. SleekView shows a colored pill for each value, and any result without a status simply renders without a pill rather than blocking the card from showing. SEOs can update the status by editing the post or via a custom admin column.
Yes. SleekView reads whichever records Relevanssi has indexed, including content from custom fields, taxonomies, and PDF attachments if Premium is active. The mapping happens at view setup time without any new configuration on the Relevanssi side at all.
Yes. Every saved view has its own role and capability scope, so you can publish a public editorial feedback wall on the editor hub and a separate SEO Triage queue that only Editors and Authors can see. Both views share the same wp_relevanssi_log records underneath.
When the underlying post is deleted, SleekView removes the card on the next refresh. If the post is trashed rather than fully deleted, the card disappears from the public view but the upvote meta is preserved on the trashed post in case you restore it later from the trash.
Yes. Every SleekView is available as a shortcode and a Gutenberg block, so you can drop a Top clicked this week view onto the editor hub, embed a Needs boost view on an internal Wiki page, or stitch several views into a single SEO dashboard with separate columns side by side.
SleekView paginates and sorts at the database level rather than loading every wp_relevanssi_log row into memory, so a site with millions of search log entries still renders the top of the feedback board in well under a second on a normal shared host. Aggregation queries hit indexed columns.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout