Pinterest Rich Pin Image Fallbacks for Product Boards
Set up pinterest image size compliant og:image fallbacks so Rich Pins populate correctly when product photos are missing from your catalog.
Pinterest Rich Pins pull product data including images from your page's Open Graph meta tags. When the og:image URL is missing or returns an error, Pinterest renders the pin with no image — a blank card that gets zero engagement. For product boards, a missing image means the pin effectively does not exist.
A deterministic fallback og:image URL generated from the product name and category keeps Rich Pins populated and visually consistent even when product photography is incomplete. This is especially useful during catalog launches when new SKUs go live before their product photos are processed.
Requirements
Pinterest image size requirements for Rich Pins and standard pins
Pinterest recommends a 2:3 aspect ratio (1000×1500 pixels) for standard product pins. This vertical format performs best in the Pinterest feed because it takes up more vertical space without being hidden by the 'show more' cutoff. Square images (1:1) also work. Horizontal images (wider than tall) are penalized in the algorithm and display less prominently.
For Rich Pins specifically, Pinterest reads the og:image meta tag. The minimum recommended size is 600px on the shortest side. Pinterest does not have a maximum file size requirement, but images above 10 MB may fail to process. The format must be JPEG or PNG.
Pinterest caches pin images aggressively. Once a pin is created, Pinterest stores its own copy of the image. Updating the og:image URL on the source page does not update existing pins, only new pins created after the change.
OG setup
Wiring og:image fallback for Pinterest Rich Pin validation
Pinterest reads og:image, og:image:width, og:image:height, og:title, og:description, and product-specific tags (og:price:amount, og:price:currency) from your page. All of these should be present for Product Rich Pins to qualify.
Generate the fallback og:image URL from the product name and category. Use a vertical 1000×1500 format to match Pinterest's preferred ratio. Set og:image:width and og:image:height explicitly so Pinterest knows the dimensions without fetching the image first.
<!-- Product page meta tags for Pinterest Rich Pin -->
<!-- Pinterest prefers 2:3 vertical ratio -->
<meta property="og:type" content="product" />
<meta property="og:title" content="Merino Wool Running Socks – 3-Pack" />
<meta property="og:image"
content="https://fallback.pics/api/v1/1000x1500/7C3AED/FFFFFF
?text=Merino+Wool+Running+Socks" />
<meta property="og:image:width" content="1000" />
<meta property="og:image:height" content="1500" />
<meta property="og:image:alt" content="Merino Wool Running Socks in purple packaging" />
<meta property="product:price:amount" content="24.99" />
<meta property="product:price:currency" content="USD" />Product catalog
Generating Pinterest fallback images for new SKUs at catalog launch
When a new product category launches with 200 SKUs and only 80% of the product photos have been processed, the remaining 40 products will have broken pins if you go live without fallback images. A server-side check at page render time — does this product have a photo? — lets you serve a fallback.pics URL for the 20% that do not.
The fallback image does not have to be abstract. Use the product name as the text parameter and the product category color as the background. A pin showing 'Merino Wool Running Socks' on a brand-purple background is more informative than a broken image and can still drive clicks.
// Next.js product page — conditional og:image
import { Metadata } from 'next';
export async function generateMetadata({ params }): Promise<Metadata> {
const product = await getProduct(params.slug);
const ogImage = product.imageUrl
? product.imageUrl
: `https://fallback.pics/api/v1/1000x1500/7C3AED/FFFFFF` +
`?text=${encodeURIComponent(product.name)}`;
return {
openGraph: {
images: [{ url: ogImage, width: 1000, height: 1500 }],
},
};
}Validation
Testing Rich Pins with Pinterest's Rich Pin Validator
Pinterest provides a Rich Pin Validator at developers.pinterest.com/tools/url-debugger/. Paste your product page URL and Pinterest will fetch the og:image and display a preview of how the pin will appear. If the fallback image URL is valid and returns the correct Content-Type, the preview will show the generated image.
After making changes to your og:image tag, clear Pinterest's cache by re-running the validator. Pinterest does not expose a manual cache-clear button for page metadata, but re-running the validator forces a fresh fetch. Allow 24-48 hours for the change to propagate to existing scheduled pins.
SEO impact
Pinterest image quality and its effect on pin discoverability
Pinterest's search algorithm considers image quality as a ranking signal. High-resolution, properly formatted images rank higher in Pinterest search than images that appear low-quality or blurry. A generated placeholder image with clear text on a solid background is visually clear and will not be penalized for quality.
The text in a generated placeholder is not indexed by Pinterest's visual search. Pinterest's visual search engine analyzes photographic content for objects and scenes, not text. The generated image's SEO value comes from the Rich Pin metadata (title, description, price) rather than the image content itself.
Key takeaways
What to standardize before shipping
- Pinterest recommends 1000×1500 pixels (2:3 ratio) for product pins — use this aspect ratio for og:image fallbacks.
- Pinterest reads og:image from the page; a missing or broken URL results in a blank pin card with zero engagement.
- Generate fallback images from the product name and category color to keep new SKU pins informative during photography backlog.
- Use Pinterest's Rich Pin Validator to confirm the fallback URL is accessible and renders correctly before going live.
- Pinterest caches pin images at creation time; updating og:image only affects new pins, not existing ones.
Production fallback layer
Use fallback.pics anywhere an image URL is accepted.
Start with one deterministic URL and standardize fallback behavior across your design system.
Continue reading
Related articles
Facebook and Meta OG Image Fallback Setup Checklist
Fix facebook og image size issues and missing Open Graph images on Facebook and WhatsApp with a deterministic fallback URL strategy.
OG Image Placeholders for Blogs, Docs, and Social Sharing
Use generated OG image placeholders for blog posts, documentation pages, changelogs, and social previews while final artwork is unavailable.
JSON-LD Image Properties When featuredImage Is Missing
Supply valid json-ld image schema values when your CMS featured image is absent to keep structured data eligible for Google rich results.