SleekView for WordLift
SleekView reads WordLift's entity custom post type and the schema meta on annotated posts directly from wp_posts and wp_postmeta, and surfaces them as sortable, filterable, inline-editable columns.
♾️ Lifetime License available
A knowledge graph needs more than an entity list
WordLift is unusual among AI/SEO tools because it stores real data in WordPress. Entities live as their own custom post type (entity), each carries schema.org JSON-LD as postmeta, and entity-to-post annotations sit in standard wp_posts and wp_term relationships. The default WordLift admin lists those entities one screen at a time and surfaces almost none of the structure as columns.
SleekView reads the entity post type joined to wp_postmeta and exposes the WordLift keys as real columns. Sort entities by schema.org type, filter to entities without a sameAs reference, scope to posts annotating a specific entity or inline-edit entity-type meta across many rows.
Honest scope: WordLift's natural language analysis, entity linking and cloud-side reasoning stay in WordLift. SleekView surfaces what the plugin has already materialised in WordPress (the entity post type, the schema meta and the annotations) and makes it operable as a list. That is a real and useful surface, far more substantial than most AI/SEO tools leave behind in WP.
Workflow
How SleekView reads your WordLift data
Pick the source post types
Compose your column set
Save and scope the view
Edit inline and ship
Sample columns
A typical WordLift entities view
wp_posts (entity post type) + wp_postmeta (WordLift meta keys)
| Title | Entity type | sameAs | Status | Annotated posts | Updated |
|---|---|---|---|---|---|
| Berlin | Place | wikidata.org/Q64 | Publish | 42 | Apr 21 |
| Open AI | Organization | wikidata.org/Q98012090 | Publish | 27 | Apr 19 |
| Wordpress | CreativeWork | — | Publish | 11 | Apr 12 |
| Jane Doe | Person | linkedin.com/in/janedoe | Draft | 0 | Apr 24 |
Comparison
Default WordLift admin vs SleekView for WordLift
Default WordLift admin
- Entity list shows title and type with no sameAs or annotation count column
- No way to sort entities by schema.org type or annotation density
- Filtering limited to type and status, no missing-sameAs filter
- Bulk edit covers categories and author, not WordLift schema meta
- Post-to-entity annotations stay invisible at the list level
SleekView
- Surface entity_type, schema_jsonld and sameAs as real columns
- Sort the entity catalogue by schema.org type or annotation count
- Filter to entities missing a sameAs reference or stale schema
- Inline-edit entity-type and sameAs meta across many rows at once
- Save named per-role views with their own column sets
Features
What SleekView gives you for WordLift
Custom columns per view
SEO leads, editors and graph editors each get their own column set. One view shows entity type and sameAs, another foregrounds annotated post counts.
Inline-edit without opening entities
Update entity_type, fix missing sameAs, change status directly in the row. Bulk-update dozens of entities in seconds with save_post and transition_post_status firing as expected.
Compose precise filters
Combine schema.org type, sameAs presence, annotation count, status and date range. Save the filter as a named view ("Orphan entities") your team reuses each audit.
Audience
Who uses SleekView for WordLift
SEO leads
Sort entities by annotated post count, scan high-traffic entities for missing sameAs references and bulk-fix the graph in one pass.
Graph editors
Filter to orphan entities (zero annotations) to decide whether to enrich or delete. Plan entity work as a real list rather than clicking through the WordLift admin.
Schema programme owners
Scope a view to one schema.org type, export the filtered set to CSV and brief an external structured-data consultant with a concrete list of entities.
The bigger picture
Why a knowledge graph deserves a real list
Most AI/SEO tools leave almost nothing behind in WordPress, which makes a WordPress-side workspace about them inherently narrow. WordLift is different. It materialises a real knowledge graph: an entity post type, schema.org JSON-LD on every annotated post and a network of relations in standard WP tables.
That graph is exactly the kind of structured asset that deserves governance, and the default entity list is exactly the wrong surface for it. SleekView reads the same posts and meta and turns the graph into a list editors can sort, filter and operate on. Orphan entities, missing sameAs references, stale schema, all become row-level operations rather than per-entity clicks.
Questions
Common questions about SleekView for WordLift
The WordLift entity custom post type plus the schema-related postmeta WordLift writes (entity_type, schema_jsonld, sameAs and friends), plus standard wp_posts columns. SleekView never calls WordLift's cloud API directly.
Yes. SleekView writes through wp_update_post and update_post_meta, so save_post, transition_post_status and notification hooks fire normally. Bulk operations iterate through the same path so side effects stay identical.
Yes. Add an annotation count column derived from the post-to-entity relationship table and filter for rows where the count is zero. Save it as a named view so the orphan-entity cleanup queue is one click away.
Yes. The agent UI scans wp_postmeta for WordLift keys actually present and lists them. You pick from a real menu instead of guessing names. Useful when site-specific wiring adds extra schema fields.
No. WordLift's entity recognition, linking and cloud-side reasoning are the source of the graph. SleekView surfaces the WordPress-side surface those processes produce. Different stages of the same workflow.
Queries hit indexed wp_posts columns plus indexed meta-key joins. Filters and sorts ride those indexes; heavy aggregations are opt-in per view. The default list stays fast on installs with thousands of entities.
Yes, on the WordPress side. SleekView reads the entity post type and schema meta the WordLift plugin writes regardless of plan tier. Cloud-side limits affect what gets written into WP, not what SleekView reports on top of it.
Inline edits go through standard WordPress hooks and persist in WP. WordLift's cloud reasoning remains the source for the underlying graph, so treat WP as the system of record for what is published and WordLift as the source for entity intelligence.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout