SleekView reads wp_postmeta rows written by LinkBoss with the plugin's meta-key prefix. Anchor text, target URL, and confidence are the primary fields. The agent UI auto-detects the exact key names from the installed LinkBoss version, including any new fields added later.

No. The chart view reads from the local wp_postmeta after LinkBoss has already inserted the links. Even if the LinkBoss cloud is unreachable, the dashboard still shows everything inserted up to the most recent successful run.

Yes. The confidence value LinkBoss stores per insert is a column on the data source. Cards can filter to high-confidence inserts only for clean reporting, or to low-confidence ones to surface candidates for editorial review.

The postmeta row is updated on the next run. SleekView reads current state at query time, so removed inserts drop out of the KPI on the next refresh. For longer history, a periodic snapshot table can be maintained that SleekView also reads.

Yes. The source post type donut groups by wp_posts.post_type, including any custom post type LinkBoss processes. A site that registers a sponsored or guide post type sees those slices automatically without additional configuration.

If the editor removes or rewrites a LinkBoss-inserted anchor in the post content, the postmeta record stays unless LinkBoss reconciles it. The KPI continues to report the inserted state. A second card on the actual rendered link, drawn from the post HTML, is required to track post-edit drift.

Yes. Cards accept filters on post_type, post category, or author. A site with multiple brands or topics can pin a chart view per section so each editorial lead reads their own slice of the LinkBoss output independently.

The LinkBoss dashboard reports per-run metrics. SleekView Charts reports the cumulative state inside the WordPress database. The two are complementary: LinkBoss tracks how each run went, SleekView tracks what the catalog currently looks like as a result.