On the post being reviewed, in postmeta. Common keys include wp_review_total for the editor's overall score, wp_review_type for the rating style (star, point, percent), wp_review_user_total for the user-rating average, and per-criterion meta keys for each criterion you've configured. SleekView reads them all without depending on the plugin's admin.

The plugin was closed on WordPress.org in May 2025 due to a security issue. Existing installs continue to work — WordPress doesn't auto-deactivate closed plugins — and the review data is still in your database. SleekView reads it independent of the plugin's UI, which matters specifically because the plugin itself is no longer receiving updates and the admin may break with future WordPress releases.

Yes. WP Review stores both — the editor score in wp_review_total and the user-rating average in wp_review_user_total. Add both as columns, sort by the delta between them, and you immediately spot reviews where the editor's verdict and the visitor consensus have drifted apart. That's the most useful single view for trust audits.

Yes. Inline edits go through update_post_meta(), which is the standard WordPress meta API. Any caching the plugin does keyed on those meta keys is invalidated normally. The front-end review boxes re-render with the new values on the next page load. No extra cache flushing is required for the meta changes themselves.

Yes. Review type is stored in wp_review_type as a meta key on each reviewed post. SleekView treats it as a filterable column. Useful when you've migrated rating styles between criteria sets and want to audit which posts are still on the legacy type — sort by type, filter by old value, refresh in a batch.

SleekView is a great migration aid for exactly this case. See all your reviews in one table, export as CSV, and use that to seed whichever review plugin you move to. Postmeta-based reviews are easy to map because the data structure is flat. Once migrated, you can keep SleekView pointing at the new plugin's storage to maintain the corpus view.

WP Review writes JSON-LD review schema based on the postmeta values. SleekView only changes the meta values when you edit them; it doesn't touch the schema generation. Updated scores produce updated schema on the next render. If you're retesting and rescoring, the rich-result preview reflects the new value automatically.

Yes. Add category as a column and group or filter by it. Sort by editor score within a category to produce "best monitors" or "best keyboards" leaderboards inside the admin. That same data export feeds programmatic landing pages — pair this view with SleekRank if you want public-facing leaderboards generated from the corpus.