How to Enable Rich Pins on WordPress, Shopify, and Etsy

Rich Pins attach structured metadata from the pinned page onto the pin itself: the real title instead of image alt text, the page description, the author or brand, and — for products — live price and availability. Three flavors matter: article pins (headline, author, description), product pins (price, stock status, and a direct buy link), and recipe pins (ingredients, cook time, servings).

The payoff is passive but real: product pins update their price everywhere a pin has been saved, the moment your page changes. Article pins keep the correct headline even when someone pins a screenshot instead of your card. And because the metadata comes from the page, Rich Pins are also how Pinterest understands what your content is about — which feeds distribution as much as the display extras.

The one-time setup matters less than staying valid. Sites redesign, themes strip meta tags, plugins conflict, and Rich Pins quietly degrade — so the checking habit matters more than the enabling ceremony.

Rich Pins are generated from metadata on your pages, so the work starts on your site, not inside Pinterest. Article pins read Open Graph tags (og:title, og:description, og:type) plus schema.org Article or Recipe markup. Product pins read product markup: price, availability, and title in either Open Graph product tags or schema.org Product JSON-LD. If you run WordPress with an SEO plugin (Yoast, Rank Math, or Jetpack), Open Graph output is usually already on — confirm by viewing page source and searching for og:title.

Shopify and Etsy storefronts emit product metadata natively, so sellers on those platforms can skip straight to validation. Custom sites need to emit the tags themselves; Pinterest's developer documentation lists the exact fields per pin type.

Pinterest retired the manual Rich Pin application years ago. Today, metadata is picked up automatically when Pinterest crawls your pin's destination URL — which means the real task is making sure your metadata survives that crawl. Run your URL through a rich pin validator before you publish a single pin: it parses your Open Graph and schema markup the way Pinterest's crawler would and tells you which fields are missing or conflicting.

The common failure is not "no metadata" — it's conflicting metadata: an og:title that disagrees with schema.org name, a product price present in JSON-LD but missing from Open Graph, or a recipe missing the cook time Pinterest displays. Fix the conflict, not just the absence.

Once validation is clean, publish (or schedule) any pin pointing at the validated URL. When Pinterest fetches the destination, Rich Pin data — title, description, author, price, availability — attaches automatically. If you edit the underlying page later, the Rich Pin data refreshes on Pinterest's next crawl of that URL; forcing a refresh is as simple as re-pinning the URL.

WordPress. SEO plugins handle Open Graph, but page builders and custom post types are where metadata goes missing — a landing-page template without og:type or a portfolio custom post type with no description tag will produce bare pins. Validate one representative URL per template type, not just the homepage. If you automate pin production with the WordPress automation route, validation is worth running once per new template because every future post inherits its markup.

Shopify. Product pages emit solid product metadata by default; the gaps are usually collection and blog pages, where og:type is often generic. Validate a collection URL too — those are the pages that quietly miss Rich Pin treatment.

Etsy. Listings carry product metadata that flows through when the listing URL is pinned, but you do not control the markup — so the leverage shifts to which listings you pin and how the pin presents them. The Etsy seller workflow covers turning public listings into consistent pin assets at scale.

• Conflicting markup. Two sources of truth (Open Graph says one title, schema says another) make Pinterest pick unpredictably. Make them agree — most SEO plugins let you sync them.
• Blocked crawling. A staging robots.txt left in production, or a firewall that challenges Pinterest’s crawler, means the destination URL never gets read. White-list Pinterest’s crawler or drop the block.
• Wrong og:type. Everything marked “website” instead of “article” or “product” renders as a plain pin. This single tag is the most common miss on custom themes.

After any fix, re-run the rich pin validator on the affected URL, then pin it once more to trigger a fresh crawl. Rich Pin data refreshes on Pinterest’s schedule, so give it a day before assuming the fix failed.