No. SleekView reads the existing response cache that Site Kit writes during its sync. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the post data without touching Site Kit settings, the GA4 property, or the Search Console verification at all.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or to specific roles like Editor, SEO, or Author, you can flip that in the view settings without touching any code.

You map a review_status meta key when you build the view. SleekView shows a colored pill for each value, and any URL without a status simply renders without a pill rather than blocking the card from showing. Editors can update the status by editing the post or via a custom admin column.

Yes. SleekView reads whichever modules you have connected. If only GA4 is connected, the board uses GA4 sessions as the vote weight. If Search Console is also connected, you get a clicks or impressions option as well. Modules can be added later without rebuilding the view.

Yes. Every saved view has its own role and capability scope, so you can publish a public Top Pages wall on the homepage and a separate Editorial Triage queue that only Editors and Authors can see. Both views share the same Site Kit cache underneath the surface.

When the underlying post is deleted, SleekView removes the card on the next refresh. If the post is trashed rather than fully deleted, the card disappears from the public view but the upvote meta is preserved on the trashed post in case you restore it from the trash later.

Yes. Every SleekView is available as a shortcode and a Gutenberg block, so you can drop a Top this week view onto the homepage, embed a Needs update view on an internal Wiki page, or stitch several views into a single editorial dashboard with separate columns side by side.

SleekView paginates and sorts at the database level rather than loading every cached response into memory, so a site with thousands of posts and a deep Site Kit cache still renders the top of the feedback board in well under a second on a normal shared host. Aggregation queries hit indexed columns by default.