Smash Balloon's Custom Twitter Feeds plugin registers ctf_feeds as a custom post type for every feed an editor configures. Each entry stores the handle or hashtag, the feed type (user timeline, hashtag, mentions, lists), and a configured post limit. Cached posts land in wp_ctf_feed_caches, keyed by feed id, with timestamps written on every successful X API fetch.

Embedding a Twitter feed is done with [custom-twitter-feeds feed=11] or the Smash Balloon block. Default OG generators see a shortcode token in post_content and fall back to the featured image. So a landing page that embeds a brand's X timeline shares with the same generic theme card as a basic About page does.

SleekPixel parses the Custom Twitter Feeds shortcode, loads the matching ctf_feeds CPT, reads the handle, the feed type, and the cache age, then renders a per-handle OG image. The card names the X account being embedded and badges the type of feed configured, so the share signals the timeline rather than the surrounding template.

Pages that embed an X feed are usually pages where the X presence is the point. A newsroom, a campaign hashtag, a community list: the surrounding copy frames the timeline and the timeline carries the value. A default OG image that says only the site name strips that point out of the share at exactly the moment the link gets passed around.

A SleekPixel card that names the handle, badges the feed type, and stamps the cache freshness restores the missing context. The fields already exist in the Custom Twitter Feeds database. The plugin writes the handle, the feed type, and the cache timestamp on every refresh.

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