SleekView Kanban for SearchWP
SleekView reads the SearchWP index and statistics tables directly, groups every indexed item by its current indexing state, and lets your team drag document cards between Pending, Indexing, Indexed, and Excluded so the underlying SearchWP record updates the moment the column changes.
♾️ Lifetime License available
Why SearchWP index health fits a kanban view
SearchWP stores its index in dedicated custom tables, including wp_swp_index for the per-document index rows, wp_swp_log for query statistics, and wp_swp_status for indexing progress per engine. Each indexed document carries fields like post_id, source, last_indexed, token_count, and an excluded flag for documents the engine should skip. The default SearchWP dashboard shows a progress bar and a list of recent searches and nothing about which documents are stuck in the queue or were silently excluded.
SleekView Kanban reads the same SearchWP index rows the dashboard already queries. Pick a derived index_state field that buckets documents by their indexing progress, the excluded flag, and the last indexed timestamp and every document becomes a card grouped under Pending, Indexing, Indexed, and Excluded. Card fronts can show the document title, the source post type, the token count, the last indexed date, and the engine name so the search admin can act on the board without opening the SearchWP debug panel.
Dragging a card between columns writes back through the SearchWP API. A move from Excluded to Pending clears the exclusion flag and queues the document for the next indexing cycle, and a move from Indexed to Excluded sets the exclusion flag so the SearchWP engine drops the document from query results on the next request.
Workflow
From the SearchWP progress bar to a real index board
Connect the SearchWP index source
Pick the index state column to group by
Choose what each document card shows
Enable drag-and-drop state updates
Sample board
Sample SearchWP index health board
Comparison
Default SearchWP dashboard vs SleekView Kanban
Default SearchWP dashboard
- Single progress bar and recent searches list with no queue of pending documents
- Excluded documents hidden behind the engine settings rather than visible on a board
- No visual sense of how many documents are stuck pending versus actively indexing
- Bulk reindexing requires the SearchWP Index button and reindexes the entire engine
- Search admins need full manage_options access just to inspect what was excluded
SleekView Kanban
-
Reads directly from
wp_swp_indexand the SearchWP statistics tables - Drag a card to Excluded and the SearchWP exclusion flag writes via the engine API
- Cards show document title, source post type, token count, last indexed, engine
- Column counts update live so an indexing backlog surfaces during a debug session
-
Per-role capabilities tie writeback to
manage_optionsfor admin access
Features
What SleekView Kanban gives you for SearchWP
Native SearchWP index model
Every column maps to a real state derived from the index row indexing progress and excluded flag SearchWP already maintains. SearchWP's own reindexing on save continues to run normally, so a manual move on the board never overrides the token count or the relevance weights the engine produced on the last cycle.
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 document back from Indexed to Excluded for a content cleanup, the chain of custody stays visible to the team during the next debug session.
Saved board views per engine
Filter to the main site engine for the content team, the products engine for the WooCommerce team, and a docs engine for the support 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 SearchWP kanban changes search admin work
Index rebuild monitoring
Search admins scope the board to a single engine, watch the Pending column drain during a rebuild, and confirm every expected document landed in Indexed before signing off on the rebuild without polling the dashboard progress bar.
Exclusion audit
The search lead pulls the Excluded column quarterly, reviews each excluded document with the original reason, and clears stale exclusions by moving cards back to Pending so they reenter the index on the next cycle without manual reindex.
Stale index triage
Developers scope to Indexed rows with a last_indexed date older than the post modified date, queue a focused reindex by moving cards to Pending, and clear the backlog without searching one document at a time through SearchWP's debug panel.
The bigger picture
Why this view matters for site search health
SearchWP is brilliant at relevance scoring and unhelpful at showing the whole team where the index actually stands today. The default dashboard shows a progress bar and the most recent searches, but a stale index or a silently excluded document never surfaces until a user reports a missing search result. By the time the search admin has queried the index tables manually, a redirected post is still appearing in results and a new product is missing from the products engine entirely.
A kanban view that reads and writes the same SearchWP index rows the dashboard uses keeps the team and the live index aligned. Pending, Indexing, Indexed, and Excluded all live on one board. Token counts, last indexed dates, engines, and source post types 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 is actually serving.
Questions
Common questions about SleekView Kanban for SearchWP
Live. SleekView queries the same wp_swp_index table the SearchWP dashboard reads from. Filters apply at the SQL level, so a board scoped to one engine reflects rows updated this hour, not a snapshot from yesterday or a stale cache that needs the SearchWP rebuild button pressed before the data refreshes.
No. Drag-and-drop writes the excluded flag and queues a single document for the next cycle. The full engine rebuild button continues to do exactly what it did before, and a move to Excluded never accidentally drops the entire index or reindexes documents that did not change.
Yes. The wp_swp_index table tags every row with its engine name. SleekView exposes engine as a filter so a board can scope to one engine at a time, and group by engine for an overview board that shows the health of every search engine on the site in one place.
Yes. Every move runs through current_user_can('manage_options') and the SearchWP settings capability before any index API call fires. A non-admin account can drag for personal sorting but the change does not persist, with a toast notification explaining the missing capability and pointing to the admin.
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 documents remain queryable in archive views without slowing the live debug board.
Yes. Token count and last_indexed are stored on the index row. SleekView exposes both as card fields, so the search admin can see at a glance which documents have the lowest token count and which have a last_indexed date older than the post modified date in a single board view.
Yes. SearchWP Pro sources, including users, taxonomies, and custom database tables, all land in the same index table tagged by source. SleekView exposes source as a filter and as a grouping field, so the search lead can manage a users source the same way the content team manages the post source.
Yes. Every drag writes a log entry to the SearchWP log table naming the user, the source column, the destination column, and the timestamp. The entry uses the SearchWP log API 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