WordLift Pro pushes a structured knowledge graph into WordPress: entities live as a custom post type (entity), the relations between entities and articles live in a dedicated relations table (typically wl_entity_relations), and analyses are stamped onto posts as _wl_entity_* postmeta. The vocabulary and the inference live in WordLift's cloud. The artifacts live in your WordPress database.

Those artifacts are exactly what an editorial and SEO team needs to govern, and what the default WordPress screens handle poorly. SleekView reads wp_posts filtered by post_type=entity, joins the relations rows back to the source articles and surfaces entity type, related-post count and last-analysed date as real columns. Sort by relation count, filter to entities of a specific type, or pull every article tagged with a specific entity without leaving WP Admin.

Inline edits to entities and articles run through standard WordPress CRUD, so save hooks still fire and any WordLift listener stays in sync. The relations rows themselves are read-mostly: SleekView surfaces them as a queryable list rather than a frozen graph view.

WordLift Pro models content as a graph: entities, relations, types and analyses. That model is genuinely useful, but the default WordPress screens still show it as a flat post list with most of the signal in meta. SleekView reads the same entity rows and the same relations table and renders them as columns a team can sort and filter.

SEO leads spot orphans and hubs in one screen. Editorial finds every article tagged with a topic without a custom query. Governance tracks which entities have not been re-analysed recently.

Same graph, same plugin, very different operating posture.