Yes. Moving a card calls wp_update_post, the same function the editor uses, so transition_post_status hooks fire normally and the Surfer plugin meta link stays intact through every move. Surfer keeps syncing the content score to the WordPress editor side without any extra plugin glue or workarounds.

SleekView reads the WordPress posts table directly, filters to posts with a Surfer document meta key, and joins the Surfer content score and target keyword meta in the same query. You pick the posts table as the source, choose the stage field to group by, and SleekView renders one card per post.

Yes. SleekView ships with role-based permissions, so SEO leads can have a single page that holds the Surfer pipeline board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so writers cannot publish their own drafts without an editor's approval.

Custom Surfer recommendation fields appear automatically because SleekView reads distinct values from the chosen field. You can group by any custom field, show it on the card front, and decide whether editors can drag cards between any two columns or only along the official Surfer pipeline path.

Yes. The Surfer content score is read from the post meta saved by the Surfer plugin and shown on each card front. Editors can sort columns by score so drafts under a target score stay near the top, and any custom score field added by the team also lands on the card front without any extra plugin glue.

Dragging never deletes data and never touches the Surfer plugin meta link. It changes the post_status field SleekView is grouping by, which matches what the editor does through the Publish dropdown. The Surfer document ID stays in post meta so the plugin keeps syncing the content score.

Yes. Each card can show the time since the post was created or last modified, so a brief that has been sitting for weeks looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column so stale briefs never silently drift out of view for the team.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the posts table for the status and Surfer meta filters. Sites with tens of thousands of Surfer-linked posts stay responsive because heavy fields are only fetched for cards currently on screen.