Site Reviews stores each submission as a site_review custom post type with structured ratings and content in related tables. Each record carries a post_status, typically pending or publish, plus an is_approved meta flag the plugin uses to gate frontend display. The default review list screen shows everything as a paginated list, which works for a small site but breaks down once a busy store collects dozens of submissions a day across many products.

SleekView Kanban reads the same site_review rows you would query with WP_Query or the Site Reviews API. Pick post_status as the group column and every submission becomes a card grouped under its current state. Cards can show the reviewer name, the star rating, the assigned product or page, the snippet of text, and the submission date so moderators see the full context before deciding to approve or reject.

Dragging a card from Pending to Approved triggers the same Site Reviews approval flow the admin edit screen uses, which fires site-reviews/review/approved for analytics and automation, updates the assigned post's aggregate rating, and pushes the review to the live frontend. Spam goes straight to Trash, borderline submissions sit in Unapproved while a senior moderator weighs in, and the underlying database stays in sync with what your team is actually doing.

User-submitted reviews shape conversion more than almost any other element on a product page, which means the moderation queue is part of the marketing funnel whether the team treats it that way or not. The default Site Reviews list screen is built around per-record editing, not throughput, so a moderator working through 40 submissions a day clicks open detail screen after detail screen, judges each in isolation, and loses track of patterns. One product collecting four one-star reviews in a single morning is a problem worth a phone call, but on a flat list those four cards look the same as any other four.

A kanban view aggregates the same data into a shape the brain can read. Pending becomes a tangible queue with a clear count. One-star clusters become visible the moment they form.

Spam submissions get a permanent home in Trash where they cannot pollute the main view. The data and the writeback both stay with Site Reviews. The moderation interface finally matches the rhythm of the work, which makes the difference between a team that clears the queue daily and a team that lets it grow into a problem nobody owns.