Custom tables. Reviews, templates, criteria, and votes each have dedicated tables in the WordPress database, separate from wp_postmeta. SleekView's agent UI handles the schema discovery directly so you don't need to know the table names ahead of time. Once discovered, columns are filterable, sortable, and joinable like any other table.

Yes. Reviewer's reviews reference a template ID; templates carry the criteria definitions and rating type. SleekView joins them so the template name, type, and criteria appear alongside the review row. That single join is what unlocks the corpus view — without it, you're stuck switching between two unrelated screens.

SleekView writes to the same tables and triggers any database-level hooks the plugin has registered. If Reviewer caches review HTML in transients (it does in some versions), you may need to flush after bulk edits. The agent UI offers an opt-in flush button that runs the plugin's documented cache-invalidation routine after a SleekView edit batch.

Yes. Reviewer keeps a reference to the post containing the shortcode in its review record. SleekView joins that to wp_posts so the post title appears as a column. Sorting by embed location surfaces reviews used in many comparisons — the highest-leverage refresh candidates from an SEO perspective.

Yes. Comparison templates contain multiple reviews. SleekView groups them by template ID so you can see all reviews in a comparison together, with each criterion's score side by side. That's the view that surfaces inconsistent scoring within a single comparison — a 7.4 next to a 9.0 on the same criterion is worth a second look before publishing.

There are several plugins with "Reviewer" in the name. SleekView's agent UI auto-discovers any custom tables in the WordPress database, so as long as your plugin uses MySQL tables (the common case), it will work — the schema is read live. The same approach handles forks, white-labeled versions, and plugins that simply share the name without sharing the codebase.

Yes. SleekView's table export covers the joined data, not just the raw review table. The export includes the template name, criteria scores, and embed-location columns you've configured in the view. Useful for migrating to a different review plugin or for feeding the data into a programmatic-page generator like SleekRank for public leaderboards.

Reviewer's vote table is separate from the reviews table. SleekView joins it as a counted column so each review row shows the total user votes inline. Sort by votes descending to find your highest-engagement reviews; filter by vote count = 0 to find reviews that may be underperforming on visibility or page placement.