Compact WP Audio Player is a lightweight shortcode-based audio player that does not maintain its own custom tables. Configuration lives in wp_options, and individual audio embeds live as shortcodes inside wp_posts.post_content referencing MP3 or M4A source URLs that may point at the WordPress media library or at external CDNs. The default plugin admin gives a settings page and a documentation tab; there is no catalog of where audio embeds exist across the site.

SleekView scans post_content for the player's shortcode patterns, parses each match into a row with source URL, embedding post, autoplay flag, loop flag, and width, and joins the source URL against the WordPress media library where the file lives locally. The resulting table answers questions the plugin admin cannot: which posts embed audio, which embeds point at external URLs vs media library files, which embed configurations differ from the site default, which posts have multiple audio embeds.

Inline edits update shortcode attributes through the embedding post's save_post path so the post revision system and any cache layer behave normally. Bulk actions cover replace source URL (useful when migrating audio files to a new CDN) and normalise autoplay or loop attributes across many embeds. Where the plugin or a companion analytics plugin tracks plays, those counts surface as additional columns automatically.

Plugins that work entirely through shortcodes solve the embedding problem and create a tracking problem. Compact WP Audio Player does its job well: a clean compact player wherever a shortcode appears. What it does not give you is a list of where those shortcodes live, what source URLs they reference, whether those URLs still resolve, and whether any of them have autoplay turned on against current accessibility guidance.

The default admin has a settings page and a documentation tab; it has no catalog because the data is scattered across post_content. SleekView builds the catalog by scanning for shortcodes, parsing attributes, and joining against the media library. Editorial teams use it to audit embed configurations before a content refresh.

Site admins use it to find every embed before migrating audio files to a new CDN. Accessibility leads use it to surface autoplay-enabled embeds for remediation. The plugin keeps rendering exactly as it does today, the shortcodes keep living in posts, and the source URLs keep pointing at the media library or external CDNs; SleekView just turns a scattered shortcode pattern into a queryable surface that an audit can actually use.