Rich Pins Not Working: What Is Missing From Markup

Rich Pins not working is almost always a markup problem on your own page rather than something wrong at Pinterest's end. A Rich Pin pulls structured data from the destination URL, so if the data is absent, invalid or unreachable, the Pin falls back to an ordinary one.

The validator checks the markup a Rich Pin needs on any URL and reports which pieces are missing, which is usually the whole diagnosis.

Rich Pins read structured data from the page — Open Graph properties and, for products and recipes, schema.org markup. A page with none of it cannot produce a Rich Pin.

The minimum for an article Pin:

<meta property="og:type" content="article">
<meta property="og:title" content="The article title">
<meta property="og:description" content="One sentence.">
<meta property="og:url" content="https://example.com/page">

Products and recipes need more, and the requirements are documented by Pinterest.

A typo in a property name, a content attribute left empty, or two conflicting og:type declarations all produce the same result as no markup at all. The common version is a plugin adding one set of tags while a theme adds another.

The preview debugger shows exactly what a crawler reads from the page, which settles the question of whether the tags you think are there actually are.

Rich Pins require applying once per domain. Until that application is approved, correct markup produces nothing. This is the single most common cause among people who "set everything up" and saw no change — the markup was right and the domain was not enrolled.

Pinterest caches what it reads. A Pin created before the markup was fixed keeps the old data, and the fix appears on new Pins first.

Anything that blocks bots blocks Pinterest's: a robots.txt rule, bot protection, a login wall, or markup injected by JavaScript that the crawler does not execute. Structured data belongs in the server-rendered HTML.

This is the same failure that produces a link preview not showing on other platforms, and the underlying tags are the same ones — Open Graph tags.

Worth knowing before you spend an afternoon on this, because the benefit is real and modest.

A Rich Pin pulls live detail from your page onto the Pin: for an article, the headline and author; for a product, price and availability; for a recipe, ingredients and cooking time. That information updates when your page updates, which is the genuinely useful part - a price change propagates without re-pinning anything.

What it does not do is rank the Pin higher. Ranking comes from the title, the description, the board and whether people save the Pin. A Rich Pin makes a Pin more informative and slightly more clickable; it does not rescue one nobody sees.

So the honest priority order is: get the image and the title right first, get the description right second, and set up Rich Pins once - after which they work for every Pin to that domain forever, which is what makes the one-off effort worth it.

Rich Pins improve a Pin; they do not rank it. The fields that decide whether a Pin surfaces at all are the title, description, board and destination:

See Pinterest SEO and writing a Pin description Pinterest can read. And the image still has to work at feed-tile size — Pinterest Pin size.

Check what a Rich Pin needs on your own URL with the Rich Pin validator.