Oxygen Builder gives full control over WordPress page structure - no theme template, just elements you place. Pages built with Oxygen can look exactly the way the design says they should, and the page itself can pull from any custom field, ACF group, or Meta Box. The piece Oxygen does not handle is the social-share metadata - the og:image meta tag that determines what the page looks like when its URL gets posted on Twitter, LinkedIn, or Slack.

SleekPixel covers exactly that. You build one template in the SleekPixel admin using fields like {post_title}, {category}, and any custom field. Every Oxygen-built page generates an OG image on save. Oxygen handles the visible page; SleekPixel handles the metadata that travels with the URL.

SleekPixel does not interfere with Oxygen itself - they operate at different layers. Oxygen owns the page DOM. SleekPixel writes meta tags into the document head. The two coexist on every page Oxygen builds. Edit the SleekPixel template once and every past page regenerates with the new card.

Oxygen Builder is the kind of tool that gets used because the team cares about pixel-level control. The same teams care about how their pages look in a feed - which is determined entirely by the og:image meta tag, not by the page's actual layout. Oxygen does not generate that image automatically per page; the default behaviour is whatever the theme or SEO plugin sets globally, which means every page on the site shares with the same logo.

A per-page card that pulls from the post's title and custom fields keeps the share preview as considered as the page itself. SleekPixel handles that layer without forcing any change to Oxygen's render path - it sits beside Oxygen in the document head. Edit the template once, and every page Oxygen builds gets a card that matches.