poppi ships a file literally named PREVIEW_IMAGE.png
One asset, versioned once, used as the share image for the whole store.
drinkpoppi.com
So every flavour shares one card
Twelve flavours, one image.
drinkpoppi.com
What's actually wrong
The og:image on drinkpoppi.com resolves to PREVIEW_IMAGE.png with a single version query string. The filename is the diagnosis: it's the one generic placeholder a theme asks for at setup, uploaded once and never revisited. Flavour pages, the store locator, and the ingredients explainer all inherit it, so a brand that sells on colour and flavour variety advertises every link with the same frame.
This is cause 3 of the 5 ways link previews break. The full breakdown covers the manual fix and the automatic one.
og:image → PREVIEW_IMAGE.png?v=1779892162twitter:card → summary_large_imageone version string, so one upload, reused sitewidepoppi, one card per flavour
The page supplies the colour, the name, and the copy.
poppi
Flavours are the whole catalogue
They're the pages people link, and the ones a single image serves worst.
A flavour page on Twitter
One product, posted as a link.
poppi · Strawberry Lemon
drinkpoppi.com
The ingredients page on Facebook
The explainer people send to sceptical friends.
drinkpoppi.com
poppi · What's inside
drinkpoppi.com
For whoever owns the templates
The filename gives it away
PREVIEW_IMAGE.png is what a theme calls the placeholder it wants at setup. Seeing it in production means nothing replaced it.
og:image → PREVIEW_IMAGE.png?v=1779892162Variety is the product
For a flavour-led brand, the share image is the flavour. One asset throws away the only differentiator the card has.
No asset pipeline needed
OpenGraph+ renders each flavour page into its own card, so launches don't wait on a designer exporting twelve PNGs.