No. TSF still owns the head tags, canonicals, OpenGraph markup, and sitemap. SleekView Charts reads the _genesis_ postmeta keys TSF already writes and renders them as chart cards, giving SEO leads a site-wide dashboard that TSF intentionally does not ship.

No, but they work well together. The audit grid is the drill-down for fixing specific posts. The Charts dashboard is the overview that tells you which post type and which SEO field need attention first. Many teams pin a Charts dashboard and a saved audit grid as their two daily SEO surfaces.

All of the standard _genesis_ postmeta keys: _genesis_title, _genesis_description, _genesis_canonical_uri, _genesis_noindex, _genesis_nofollow, plus the OpenGraph and Twitter keys. TSF Extension Manager add-ons that store data in postmeta surface as additional aggregatable columns when active.

Yes. Every chart card supports filtering by post type, post status, or any other postmeta key. Build a dashboard scoped only to products, or only to your custom Recipe post type, without affecting the site-wide view.

Live. SleekView Charts queries postmeta directly on each render, so an inline edit in the SleekView audit grid or a save through TSF's metabox shows up the next time the dashboard loads. There is no separate cache layer to invalidate.

Yes. Charts aggregate against indexed postmeta keys and paginate when needed. Sites with tens of thousands of posts stay responsive because the queries are scoped and the chart payload is summary data, not row dumps.

Yes. Each chart card exports its underlying aggregation to CSV, so the values that drive the Bar or Donut can land in a spreadsheet. Useful for monthly retainer reports or for handing fix lists to writers when paired with the audit grid.

Yes. Dashboards can be scoped to specific roles, so editors only see the cards and post types you allow. SEO leads keep the full dashboard while writers get a scoped view of their own post type's coverage numbers.