Yes. SleekView reads from wp_wpcr3_reviews and wp_wpcr3_options, the same tables the free WPCR3 plugin uses. There is no premium tier requirement; everything WPCR3's free version stores is available in the SleekView table view, including ratings, page references, and the approval status field.

Yes. SleekView writes back into the same rows WPCR3 reads from on render, so changes to text, author, rating, or status appear on review pages on the next page load. The WPCR3 review widget and schema.org microformat keep working unchanged because nothing about how WPCR3 renders the data changes; only the moderation surface does.

Yes. WPCR3 stores a page reference per review (Services, Contact, a specific product page). SleekView surfaces it as a filterable column, so you can scope the table to one page during moderation, or pull all approved reviews for a single landing page when prepping marketing copy.

Yes. If you have added custom fields via WPCR3 settings (extra ratings, departments, response notes), they store as additional columns in wp_wpcr3_reviews and SleekView includes them as columns alongside the built-in fields. Filter and sort on custom fields the same way as on rating or status.

Yes. Filter to approved reviews (or any combination of rating, page, and date), then export the visible rows to CSV. The export includes rating, author, title, body, page, and submitted timestamp, which matches the schema fields most external review aggregators or rich-snippet tools expect.

No. SleekView only changes how you manage reviews in admin. WPCR3 keeps rendering its schema.org Review and AggregateRating microformat on the front-end exactly as before. Inline edits update the underlying rows, so the schema reflects current data, but the rendering pipeline itself is untouched.

Yes. The page reference column is editable, including via bulk action. Useful when a service page URL changes or you consolidate two pages and need to move historical reviews. The schema markup on the destination page picks up the moved reviews on the next render without manual republishing.

No. SleekView only renders inside WP Admin and never touches the front-end submission path. WPCR3's review form, captcha, and email notification flow stay identical, so visitors submitting reviews don't experience any change in performance whether SleekView is active or not.