OREO writes the title and description, then stops
og:title and og:description are set. og:image is missing entirely.
oreo.com
So the card collapses to a text row
Title and description, no image, on a brand built entirely on how it looks.
www.oreo.com
What's actually wrong
oreo.com sets og:title and og:description but never emits og:image. That combination produces the worst-looking card on most platforms: a small text-only row rather than a rich preview, because the platform knows it has metadata and renders the compact layout instead of falling back to something larger. Two of the three tags being right is what makes the third one costly.
This is cause 5 of the 5 ways link previews break. The full breakdown covers the manual fix and the automatic one.
meta[property='og:title'] → presentmeta[property='og:description'] → presentmeta[property='og:image'] → not presentOREO, with the cookie in the card
Rendered per page, so recipes and products each get their own.
OREO
Recipes are the pages people share
They're also the ones with the most to show and the least to show it with.
Recipes on Twitter
The recipe index, posted as a link.
OREO Recipes
www.oreo.com
Products on Facebook
The product range.
oreo.com
OREO Products
www.oreo.com
For whoever owns the templates
Partial metadata is worse than none
With og:title and og:description present but no og:image, most platforms render the compact text card rather than reaching for a larger fallback.
og:title ✓ og:description ✓ og:image ✗It's usually a layout default
Title and description are easy to template per page. Images need an asset, so they get left as a TODO and ship without one.
The image becomes automatic
Pointing og:image at a rendered screenshot removes the asset step, which is the step that never happens.