Skip to content

Open Graph Cards for Every Shipping Moment

Three ways into the same library: by the page you're publishing, by the kind of site you run, by the mood the link should carry.

For Teams & Platforms

Integrations, partnerships and bulk workflows — ship Open Graph at the scale of a CMS, an agency book of work, or an AI coding platform.

Use Cases FAQ

How the three axes actually work together — and where to start when the grid above feels like a lot.

Why three axes instead of one topic list?

Because the same card decision changes depending on what you're optimizing for. A Shopify PDP and a SaaS pricing page are both landing pages but need very different cards. Page-type says what to put on the card; website-type says which patterns scale across a catalog; style says how to stand out in the feed.

Which axis should I follow first?

Start with the page you're shipping today — that's the fastest path to a finished card. Move to the website-type guide once you want a system that covers every page in your stack, and to the style guide once you're A/B testing for CTR.

Do I have to pick just one axis?

No — the three overlap on purpose. Most teams land on page-type first, then cross-link into style once one page proves out. Every leaf page in the grid above links to its neighbours on the other two axes so you can walk the map.

Can I plug Oginify into my CMS or codegen platform?

Yes. There are integration paths for WordPress, Webflow, Sanity, Contentful and Ghost on the CMS side, and partnership programs for vibe-coding platforms like Lovable, v0, Bolt, Cursor and Windsurf. Agencies get a white-label flow; high-volume teams use the API. Email hello@oginify.com to start a conversation.

Stop Browsing, Start Shipping

The cards you've been browsing on this hub were all painted the same way — one URL, four variants, no template picker in the middle.