Compact WP Audio Player ships an intentionally small player driven by a single shortcode. Tracks reference an MP3 or remote URL, options live in compact_wp_audio_player_options, and the actual track footprint sits inside the post_content of wp_posts. The plugin's admin exposes color and style toggles but offers no inventory view of where the player has been embedded.

SleekView parses post_content for the compact-wp-audio-player shortcode, joins to the referenced attachment rows when the source is a media library file, and indexes the option row. Source (attachment vs remote URL), host post, host post type and post date sit as sortable, filterable columns. Pull every compact player on a custom post type or every remote-URL player whose source may have moved without opening any post by hand.

Inline edits run through standard WordPress CRUD, so post-save hooks still fire and Compact WP Audio Player continues to render the button player as before. The playback pipeline stays inside the plugin.

Compact WP Audio Player is small by design, which is part of its appeal: one shortcode, one button player, a few style toggles. That smallness leaves the team without any way to see where the player has spread across the site, whether editors are using media library files or remote URLs, and how the audio footprint changes over time. SleekView reads the option row, the parsed shortcodes and the attachment rows as the structured data they already are.

Publishers confirm new episodes ship with the right source. Agency support fields client questions from a read-only slice. Editors track remote-URL tracks whose source may have moved.

The plugin keeps doing the lightweight playback work it does well, and SleekView gives the team a reading layer they can share.