SleekView Kanban for Relevanssi
SleekView reads the Relevanssi index table and exclusion settings directly, groups every indexed post by its current state, and lets your team drag document cards between Unindexed, Queued, Indexed, and Excluded so the underlying Relevanssi record updates the moment the column changes.
♾️ Lifetime License available
Why Relevanssi indexed posts fit a kanban view
Relevanssi stores its full-text index in the wp_relevanssi table, with one row per token per document and metadata in wp_options entries like relevanssi_index_post_types, relevanssi_excluded, and relevanssi_index_terms. Each indexed post carries a post_id, a type, and per-term frequency rows that drive the relevance scoring. The default Relevanssi admin shows an indexed post count and an indexing queue and nothing about which posts are excluded today or which posts are queued for the next index cycle.
SleekView Kanban reads the same Relevanssi index rows the admin already queries. Pick a derived index_state field that buckets posts by their presence in the index, the relevanssi_excluded option, and the indexing queue and every post becomes a card grouped under Unindexed, Queued, Indexed, and Excluded. Card fronts can show the post title, the post type, the term count, the last indexed date, and the post status so the search admin can act on the board without opening the Relevanssi debug screen.
Dragging a card between columns writes back through Relevanssi's helper functions. A move from Excluded to Queued removes the post ID from relevanssi_excluded and queues a reindex, and a move from Indexed to Excluded adds the post to relevanssi_excluded so the Relevanssi search query immediately drops the post from results.
Workflow
From the Relevanssi index count to a real index board
Connect the Relevanssi index source
Pick the index state column to group by
Choose what each post card shows
Enable drag-and-drop state updates
Sample board
Sample Relevanssi index board
Comparison
Default Relevanssi admin vs SleekView Kanban
Default Relevanssi index screen
- Indexed post count and a build queue with no per-document view of state
- Excluded posts hidden behind a comma separated list in the Relevanssi options
- No visual sense of how many drafts will never enter the index versus queued posts
- Bulk exclude requires editing the relevanssi_excluded option by hand in the admin
- Search admins need full manage_options access just to inspect why a post is missing
SleekView Kanban
-
Reads directly from
wp_relevanssiand therelevanssi_excludedoption - Drag a card to Excluded and Relevanssi's exclusion helper writes the option update
- Cards show post title, post type, term count, last indexed date, and post status
- Column counts update live so a missing indexed post surfaces during a debug session
-
Per-role capabilities tie writeback to
manage_optionsfor admin access
Features
What SleekView Kanban gives you for Relevanssi
Native Relevanssi index model
Every column maps to a real state derived from index presence, the relevanssi_excluded option, and queue membership Relevanssi already maintains. Relevanssi's own reindexing on save continues to run normally, so a manual move on the board never overrides the term frequencies or the title boost the engine produced last.
Drag-and-drop with audit trail
Each move writes a log entry naming the admin who dragged it, the source column, the destination column, and the timestamp. If a search lead pushes a post back from Indexed to Excluded for an editorial cleanup, the chain of custody stays visible to the team during the next debug session.
Saved board views per post type
Filter to posts for the content team, pages for the marketing team, and products for the WooCommerce team. Each saved view becomes a shareable URL that opens straight into the right board ahead of the weekly search health review.
Audience
Where a Relevanssi kanban changes search admin work
Index rebuild monitoring
Search admins scope the board to one post type, watch the Queued column drain during a rebuild, and confirm every expected post landed in Indexed before signing off on the rebuild without polling the Relevanssi index count repeatedly.
Exclusion audit
The search lead pulls the Excluded column quarterly, reviews each excluded post with the original reason on the card, and clears stale exclusions by moving cards back to Queued so they reenter the index on the next cycle without manual edits.
Missing post triage
Developers scope to posts with status publish but not present in the index, queue a focused reindex by moving cards from Unindexed to Queued, and clear the backlog without searching one post at a time through Relevanssi's debug screen output.
The bigger picture
Why this view matters for site search transparency
Relevanssi is excellent at full-text relevance and unhelpful at showing the whole team why a specific post is missing from results today. The default admin shows an indexed post count and a build queue, but a missing post never surfaces until a user reports a broken search result. By the time the search admin has queried the index table manually and cross-referenced the excluded option, an excluded post is still appearing in the wrong reports and a new post is invisible to every site visitor.
A kanban view that reads and writes the same Relevanssi index rows and exclusion option the admin uses keeps the team and the live index aligned. Unindexed, Queued, Indexed, and Excluded all live on one board. Term counts, post types, last indexed dates, and post statuses are visible on every card.
The team can debug faster, the search lead can audit exclusions in minutes instead of hours, and the index never drifts from what the site actually serves to users.
Questions
Common questions about SleekView Kanban for Relevanssi
Live. SleekView queries the same wp_relevanssi table and relevanssi_excluded option the Relevanssi admin reads from. Filters apply at the SQL level, so a board scoped to one post type reflects rows present in the index right now, not a snapshot from a previous Relevanssi rebuild that needs a refresh.
No. Drag-and-drop writes the relevanssi_excluded option and queues a single post for the next cycle. The full rebuild button continues to do exactly what it did before, and a move to Excluded never accidentally drops the entire index or reindexes posts that have not changed since the last cycle.
Yes. The wp_relevanssi rows carry a type field tagged with the post type. SleekView exposes type as a filter and a grouping field so a board can scope to posts only, pages only, or a specific custom post type, and group by type for a separate workflow per content surface on the site.
Yes. Every move runs through current_user_can('manage_options') and the Relevanssi settings capability before any helper function is called. A non-admin account can drag for personal sorting but the change does not persist, with a toast notification explaining the missing capability in plain language.
Filters are applied at the database query level rather than in JavaScript. A typical board scopes to one post type or to in-progress states only, so the rendered card count stays under a few thousand. Older indexed posts remain queryable in archive views without slowing the live debug board down.
Yes. Term count is derived from the wp_relevanssi rows and last indexed is available from Relevanssi's per-post meta. SleekView exposes both as card fields, so the search admin can see at a glance which posts have the lowest term count and the oldest last indexed timestamp in a single view.
Yes. Relevanssi Premium fields, including user index, custom field index, and multisite scope, all land in the same Relevanssi rows or in adjacent meta. SleekView reads those fields the same way the admin does, so the search lead can manage Premium features from the same kanban board as the free index.
Yes. Every drag writes a log entry to the SleekView audit table naming the user, the source column, the destination column, and the timestamp. The entry uses Relevanssi's option update hooks so audits, exports, and downstream automations can read it without a separate event log table to maintain.
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