OG Use Case Comparison: X vs AWS

Objective

This page compares how X (Twitter) and AWS-hosted sites interpret and render Open Graph (OG) metadata.

Twitter (X)

• Uses twitter:card and falls back to OG tags
• Prefers direct URLs to images — must be public and crawlable
• Often caches aggressively — need to use ?v=1 trick
• Best tag combo: og:image, og:title, og:description, and twitter:card

AWS-hosted Pages

• Static hosting (e.g. S3) may require correct MIME headers for images
• Ensure Content-Type is image/jpeg or image/png
• If using CloudFront, beware of caching/lazy loading conflicts
• Some bots (like X or LinkedIn) may not resolve unsigned URLs

Live Example

Try sharing this page or og-image.jpg directly on X and WhatsApp to observe behavior.

Debug Tools

• Twitter Card Validator
• Facebook Sharing Debugger