Any meta key GetGenie writes to wp_postmeta. Common ones are the focus keyword and SEO score, plus generation status. The agent UI lists the meta keys present so you pick from a real list.

No. SleekView never calls GetGenie's backend or a model vendor. It reads what GetGenie has already written to your WordPress database. A generation that never reached WP cannot appear in the table.

Yes. SleekView treats the SEO score meta key as a sortable column. Sort ascending and the weakest content surfaces first, which is the fastest path to a useful rewrite sprint.

Yes. Add a filter for the focus keyword meta key and the table narrows to posts targeting that keyword. Useful for cannibalisation checks and for category-level audits.

Yes. Select rows, pick a new status and SleekView writes through wp_update_post so post-status hooks and listening plugins still fire as expected.

Yes. GetGenie writes meta at creation, so drafts, pending and published posts all appear. A filter on post_status narrows the view to whichever stage you care about.

Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for briefing an SEO consultant or for archiving a snapshot before a cleanup sprint.

It reads whichever meta the installed GetGenie version writes. If an SEO scoring feature is locked behind premium, the table will simply show the data that actually exists on your site rather than faking missing values.