Yes. Whether your audio lives on Castos, Libsyn, S3, or self-hosted on the WP install, the metadata in WordPress is the same — duration, file URL, file size, episode number, etc. SleekView reads from postmeta regardless of where the actual audio file is stored. Castos-specific fields (where the integration writes them locally) become additional columns automatically.

Castos download stats are stored on Castos's servers, not in WordPress, since downloads happen against their CDN. Locally tracked stats (where the SSP plugin writes counts to postmeta on the WP side) become sortable columns. The split is honest: cloud-only metrics stay on Castos, WP-side metrics surface in SleekView. For a unified view, you'd need Castos's own dashboard alongside the SleekView episode list.

Transcripts saved in postmeta or a custom field surface as a column. You can filter for episodes missing transcripts to build a backfill list — useful before a directory submission or an SEO push, since transcripts feed both accessibility and search indexability. Inline edits work for short transcript fields; longer transcripts edit best in the full post screen.

Yes. Each show is a series term in the SSP taxonomy. Build a view per series for separate editorial workflows, with the right columns and filters baked in. A single SleekView install supports as many shows as your SSP setup defines, and switching between them is just loading a different saved view rather than a different admin screen.

Yes. Video episodes use the same podcast post type with a video file URL field in postmeta. SleekView surfaces both audio and video metadata in the same view, with file type as a filterable column. Useful for shows that publish both formats — you can build per-format views or a unified catalog view depending on the editorial workflow.

Yes. SleekView writes through the standard save_post path, so any cache layer, feed regenerator, or third-party hook fires normally. The RSS feed updates the same way it would from the post-edit screen, and any aggregator pulling the feed will see the change on its next poll. No special integration needed.

If your install writes per-episode stats (downloads, plays) to postmeta, those become sortable columns. Build views like 'top 10 most-downloaded episodes' or 'episodes with declining downloads month-over-month'. For Castos-cloud-only stats, you'd cross-reference with their dashboard. The combination gives a full picture without forcing all data into one place.

Chapter markers stored in postmeta surface as a column with a count or a presence flag (yes/no). Show notes are typically the post content itself, which SleekView shows as a length-of-content column or via standard post-list excerpts. Useful for spotting episodes with sparse show notes that might benefit from richer descriptions for SEO and listener context.