Feeds for YouTube registers sby_feeds as a custom post type and stores the channel id, channel name, feed type, and post limit on each entry. Cached video metadata, including titles and thumbnails, lands in wp_sby_feed_caches, keyed by feed id, with refresh timestamps written on every successful YouTube API fetch.

Embedding the feed in a post is done with [youtube-feed feed=9] or the Smash Balloon block. Default OG generators see only the shortcode token in post_content, so a creator's landing page that embeds their full uploads feed shares with the same generic theme card as a static About page on the site.

SleekPixel parses the YouTube Feed shortcode, loads the matching sby_feeds entry, reads the channel handle, the feed type, and the cache age, then renders a per-channel OG image. The card names the channel, badges the type of feed configured, and reflects the brand identity of the channel rather than the surrounding site template.

Pages that embed a Feeds for YouTube feed are almost always pages whose value is the channel content. A creator with an uploads-feed landing page, a tutorial site with playlist embeds, a campaign with a search-feed reel: the surrounding WordPress copy is a frame, and the videos are the point. A default OG image that says only the site name strips that point out of the share.

A SleekPixel card that names the channel, badges the feed type, and stamps the cache freshness restores it and recruits the share towards the channel as well as the page. None of this requires new fields to maintain. Feeds for YouTube already stores the channel handle, the feed type, and the cache age on every refresh.

SleekPixel reads what the plugin already writes and turns every cache refresh into a regenerated card. Over a year of hourly refreshes on a single active channel, that is thousands of social-ready snapshots that always match what the embed currently shows.