Why Pin data goes stale

Pinterest caches Pin preview data for about 30 days. Updated meta tags or structured data won’t appear on existing Pins – or sometimes even on new Pins from the same URL – until the cache expires or you force a refresh.

How to force a refresh

Clear your own cache first

Make sure your site is actually serving updated content before asking Pinterest to re-scrape:

• CDN cache (Cloudflare, Fastly, CloudFront, etc.)
• Server-side page cache (Varnish, Redis, application-level)
• Reverse proxy cache

Verify with Pinterestbot’s user agent:

curl -A "Pinterest/0.2 (+https://www.pinterest.com/bot.html)" https://example.com/your-page | grep "og:"

Use the URL Debugger

Open the Pinterest URL Debugger, enter your URL, and request a fresh scrape. Propagation may take minutes to hours.

Wait for propagation

Rich Pin data (prices, ingredients, publish dates) updates faster than basic Pin metadata because Pinterest re-scrapes Rich Pin sources more frequently. Basic metadata may take longer.

Existing Pins vs. new Pins

A cache refresh updates the URL’s cached metadata, which affects new Pins. Existing Pins saved to boards retain their own metadata snapshot from when they were created. Some may update when Pinterest re-processes them, but this isn’t guaranteed – especially for Pins saved by other users.

Rich Pin data not syncing

If Rich Pin metadata isn’t updating after a re-scrape:

• Validate your Schema.org JSON-LD with Google’s Rich Results Test
• Confirm your server returns updated structured data to Pinterestbot, not just to browsers
• Pinterest doesn’t always render all Rich Pin fields on every surface – data may be extracted correctly but not displayed

Prevention

• Finalize meta tags before content is first shared on Pinterest
• Use the URL Debugger proactively after significant metadata changes
• For product pages with volatile prices, keep Schema.org markup server-rendered with current data