You click the Pinterest Save button on your product page, or paste a URL into a pin description, and Pinterest grabs the wrong image — last year's logo, a random screenshot, or nothing at all. Pinterest is a visual search engine, not a chat app: that image doesn't just decorate a card, it becomes the pin people repin and search for. When the thumbnail is wrong, you lose the repins a good visual would have earned.
Pinterest runs its own crawler (PinterestBot) with its own rules, and it's the only platform in this series that gates the fancy preview behind an approval process. Rich pins — the cards that show your headline, description, and site name under the image — require validation and sign-off. Miss that step and your tags can be perfect while your pins still look bare.
Here's what I'll cover: why Pinterest picks the wrong image, the exact specs its crawler needs (the 600px rule most people miss), and a step-by-step fix that runs through Pinterest's own Rich Pin validator. Everything below checks out against ogimgen's free OG checker.
Why Pinterest Shows the Wrong Image or No Image
Pinterest builds its previews from the same Open Graph tags every platform reads — og:title, og:description, og:image, og:url — but it pulls them at two different moments. When you paste a URL into a pin description or comment, PinterestBot fetches the metadata and shows a thumbnail. When you click "Save from site" (the browser extension or bookmarklet), it grabs the og:image as the default image to pin. Both paths fail for the same core reasons:
- No og:image tag. Pasted links render as plain text with no thumbnail; the Save button falls back to scraping whatever images it finds on the page — usually the first one, which is often a logo or banner.
- An image under 600 pixels wide. This is the Pinterest-specific gotcha. Pinterest's rich pin documentation calls for an og:image at least 600 px wide, and smaller images come out soft when the grid scales them up.
- An image URL the crawler can't reach. HTTP links, redirect chains, signed URLs that expire, and hotlink protection all make the fetch fail silently.
- PinterestBot blocked at the edge. robots.txt rules, CDN bot management, or security plugins that challenge PinterestBot stop the fetch before it starts.
- Stale cache. Pinterest caches metadata per URL and re-crawls on its own schedule, so a card built from an old bad fetch stays wrong until the refresh lands.
- Rich pins not approved. Even with perfect tags, without approval your pin shows only the image and your caption — no headline, no site name, no description.
The first three causes are the same ones that break Facebook link previews. The last two — the 600px floor and the approval gate — are what make Pinterest feel like a different beast. Most people fix their tags, see no change, and give up. The change doesn't show up until the cache refreshes and the rich pin approval lands.
The OG Image Specs Pinterest Actually Needs
Pinterest's developer docs are the source of truth here, and they're refreshingly short. The required tags are og:title, og:description, og:type, og:url, and og:image — with the image at least 600 pixels wide. Product pages add four more tags so Pinterest can show price and availability. The full set looks like this:
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A short, punchy description">
<meta property="og:type" content="article">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:image" content="https://yoursite.com/og-image.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<!-- products only: -->
<meta property="og:price:amount" content="29.00">
<meta property="og:price:currency" content="USD">
<meta property="product:availability" content="in stock">| Setting | Pinterest Requirement | Why It Matters |
|---|---|---|
| Minimum size | 600 px wide | Per Pinterest's rich pin docs; smaller images scale up blurry |
| Recommended size | 1200×630 or 1000×1500 | Landscape works; a 2:3 vertical earns more grid space |
| Format | PNG or JPG | Both work; PNG for text-heavy designs |
| File size | Under 1 MB | Heavy files slow the fetch and the pin itself |
| HTTPS | Required | HTTP images are dropped |
| Crawler access | PinterestBot allowed | Edge rules must not block the fetch |
| og:type | article or product | Determines which rich pin layout applies |
| Rich pin approval | Required | The gate that unlocks the full card |
One thing worth testing yourself: drop a 1200×630 landscape image into a grid full of vertical pins. Pinterest's feed favors a 2:3 ratio — 1000×1500 is the size Pinterest itself recommends for pins — and a short wide image gets less space between the tall ones. Your og:image doesn't have to be vertical; plenty of sites run landscape rich pins fine. But if you want saved pins to dominate the grid, a 1000×1500 version of the same design is worth generating. Text inside the image should sit in the middle either way — Pinterest crops edges when it scales.
How to Fix a Pinterest Link Preview (Step by Step)
Pinterest gives you a public debugger, which puts it ahead of TikTok and Telegram in this series — but the debugger is tied to the approval flow, so you use it differently. This is the sequence I run:
- Check what a crawler sees. Paste your URL into the OG checker. It reports your og:title, og:description, og:image, and dimensions exactly as a crawler would read them. If the checker flags a missing or broken image, Pinterest will too.
- Fix the tags. Add or correct the Open Graph tags on your page. The image needs to be at least 600 px wide, served over HTTPS from a public URL with no redirect chain. Confirm the checker now shows a valid card with proper dimensions.
- Run Pinterest's Rich Pin validator. Open developers.pinterest.com/rich-pins/validator, paste your URL, and hit Validate. It fetches your metadata live and shows you exactly what Pinterest stored — title, description, image, and any errors. This is the fastest way to see Pinterest's version of your tags, not your version.
- Apply for rich pins. If validation passes, the validator offers an Apply Now button. Pinterest reviews the site and approves it, typically within a few days. Until that approval lands, your pins show the image and your caption only.
- Unblock PinterestBot. Grep your robots.txt for PinterestBot and check your CDN's bot rules. Cloudflare and similar services have a dedicated Pinterest category in their bot-management settings.
- Force a fresh fetch. Pinterest re-crawls URLs on a rolling schedule, usually within 24–48 hours. To speed it up, re-run the validator (each validation scrapes fresh) or share a cache-busted URL variant with a query string appended.
- Re-save and confirm. Click Save from site again or paste the link into a new pin description. Both pull from the same cache, so if the card is still stale, give it a day — most update within 48 hours once the tags are valid.
Real talk: step 4 is where most people quit. The validator passes, they assume they're done, and a week later the pin still shows no headline. Approval is the missing piece — without it, the only thing your perfect og:image buys you is a pretty pin with your caption underneath. If you want the full card with site name and description, submit the application and wait it out.
Pinterest vs. Facebook vs. X: Preview Behavior Compared
Pinterest, Facebook, and X all read the same standard OG tags, but the card they build from them could not look more different — and the differences come down to one design decision: Pinterest treats your image as the content, not as metadata for a card:
| Aspect | X (Twitter) | ||
|---|---|---|---|
| Preview surface | Pin image + rich pin text | Feed card | Large card below the tweet |
| Public debugger | Rich Pin validator | Sharing Debugger | Card Validator |
| Image minimum | 600 px wide | 200×200 | 200×200 |
| Preferred aspect | 2:3 vertical | 1.91:1 landscape | 1.91:1 landscape |
| Approval required | Yes, for rich pins | No | No |
| Cache refresh | Validator / 24–48h re-crawl | Debugger scrape | Re-scrape |
The 600px floor and the approval gate are the two columns that matter. Facebook and X accept a 200×200 image and render cards instantly; Pinterest demands three times that resolution and a human-reviewed approval before you get the full card. That's not a bug — Pinterest is curating the visual layer of the web. The tradeoff: a Pinterest preview that survives the review keeps earning repins for months, while a Facebook card is gone in 48 hours.
If you're building one image for everywhere, ship the 1200×630 you already use and accept the landscape pin. If Pinterest is a real channel for you, generate the 2:3 variant, keep the text centered, and run the validator once a month — Pinterest's crawler picks up tag changes on re-crawl, so a quick validation pass catches drift before you notice it in the grid.
Summary
Pinterest link previews fail for the same baseline reasons every platform's do — missing og:image, an unreachable image URL, a blocked crawler, stale cache — plus two Pinterest-only rules that catch people off guard: the og:image must be at least 600 pixels wide, and the full rich-pin card requires a one-time approval through the Rich Pin validator. The fix sequence is short once you know the platform: verify your tags with an OG checker, fix them, validate through Pinterest's tool, apply for rich pins, and let the 24–48 hour re-crawl do the rest.
Generate a properly sized image with ogimgen in about 30 seconds, check it with the OG checker, then keep the file light with the OG image file size guide — heavy images fail fetches on every platform, Pinterest included.