/ Free Tools / Social Share Debugger
Social Share Debugger
Preview and debug social share cards across Twitter, Facebook, LinkedIn, WhatsApp, Slack and Discord. Check your Open Graph tags and Twitter Card meta for your hotel pages.
Why Isn't My OG Image Updating?
When you update your hotel's social preview image, platforms may still show the old photo. Social platforms cache link previews aggressively to reduce server load. After updating your OG tags, you'll need to manually clear each platform's cache.
Cache invalidation is unreliable. Platform cache clearing is flakey and may not work consistently. You may need to try multiple times or wait for the cache to expire naturally.
Caches for approximately 30 days. Force refresh via the Facebook Sharing Debugger. Click "Scrape Again" to fetch fresh data.
Twitter/X
Caches until you request a re-scrape via the Card Validator. Note: The validator UI was removed but the API still works.
Has a particularly sticky cache. Clear via Post Inspector. May take up to 7 days for cache to fully refresh.
Preview style varies by client version and context: some show square (1:1) crops, others show full 1.91:1 cards. No official cache clearing tool, cache typically refreshes within 24-48 hours. For best compatibility, use 1200x600px with important content centered. Particularly important for hotel booking links shared via WhatsApp.
Pro Tips for OG Images
- Use 1200x600px for optimal display across platforms
- Keep important content (hotel name, hero photo) in the center 800x400px safe zone
- Use absolute URLs for og:image (relative URLs won't work)
- Add cache-busting query params when updating hotel seasonal photos:
?v=2 - Use high-quality hotel exterior, room, or pool photos as OG images for best click-through rates
Frequently Asked Questions
What is a social share debugger?
A social share debugger lets you preview how your hotel booking links, property pages, and restaurant pages will appear when shared on platforms like Twitter, Facebook, LinkedIn, WhatsApp, and Slack. It checks your Open Graph (OG) tags and Twitter Card meta tags to ensure your hotel content displays correctly with the right image, title, and description.
Why isn't my image showing when I share on Twitter?
Twitter caches your page's meta tags. If you updated your hotel's og:image after sharing, Twitter still shows the old photo. Use the Twitter Card Validator link above to clear Twitter's cache. Also ensure your image meets Twitter's requirements: minimum 120x120px, maximum 5MB, and accessible via HTTPS.
How do I clear Facebook's OG cache?
Facebook caches Open Graph data for about 30 days. To force a refresh, use Facebook's Sharing Debugger linked above. Note that Facebook requires og:image to be at least 200x200px (1200x600px recommended) and accessible without authentication. This is especially important when updating hotel promotional images or seasonal campaign photos.
What Open Graph tags do I need?
The essential OG tags are og:title (your hotel name and page title), og:description (a compelling summary), og:image (a high-quality hotel photo), and og:url (your hotel page's canonical URL). For better results, also include og:type (usually "website" or "article"), og:image:width, og:image:height, and og:site_name. Twitter also uses twitter:card, twitter:title, and twitter:image for Twitter Cards.
Why do LinkedIn and Slack show different previews?
Each platform has its own cache and rendering rules. LinkedIn and Slack both cache link previews for about 7 days. This is particularly relevant for hotel sales teams sharing property links on LinkedIn. This debugger shows you exactly what each platform will display. To refresh Slack, use the Slack URL Debugger at api.slack.com/tools/debug/url.
Debugged one URL. HotelSignal monitors share previews across your entire hotel website.
Start Free Trial