Smash Balloon's Custom Facebook Feed plugin registers the cff_feeds custom post type. Each row stores the connected Facebook page id, the page name, the feed type, the post limit, and a list of post types to include. Cached posts land in wp_cff_feed_caches, keyed by feed id, with their own refresh timestamps.

Embedding a Facebook feed is done with [custom-facebook-feed feed=5] or with the Smash Balloon block. Default OG generators see only the shortcode token in post_content, so a landing page that embeds the company Facebook feed shares with the same generic theme card as a privacy policy page.

SleekPixel parses the Custom Facebook Feed shortcode, loads the matching cff_feeds entry, reads the page name, the feed type, and the cache freshness, then renders a per-page OG image. The card names the actual Facebook page being embedded and badges it with the type of feed configured, so the share signals what the landing page is really about.

Most pages that embed a Custom Facebook Feed exist because the Facebook page is the active social presence and the WordPress page is the structured landing. Visitors who share the WordPress URL are usually doing it because the embedded Facebook content is the point: the events, the latest update, the group activity. A default OG image that shows only the site logo strips that point out of the share.

A SleekPixel card that names the Facebook page, badges the feed type, and stamps the refresh time restores it. The fields already exist in the Custom Facebook Feed database. The plugin writes the page name, the type, and the cache timestamp on every refresh.

SleekPixel just reads what the plugin already writes and turns every refresh into a new card. Over a year of hourly refreshes on a single live business page, that is thousands of social-ready snapshots that always match what the embed currently shows.