What's the issue?
Your og:image URL uses HTTP instead of HTTPS. In today's security-conscious web, many platforms block or refuse to load images served over insecure HTTP connections.
Why HTTPS matters for OG images
Platform compatibility
- Facebook — Strongly prefers HTTPS; HTTP images may not display in previews
- Twitter/X — Requires HTTPS for card images
- LinkedIn — May block HTTP images
- Discord — Shows a warning for mixed content
- Slack — May not unfurl HTTP images
Security
- HTTP images can be intercepted and modified by man-in-the-middle attacks
- Browsers display "mixed content" warnings when HTTPS pages load HTTP resources
- Users are increasingly aware of security indicators
SEO
- Google favors HTTPS sites and resources
- Mixed content issues can negatively impact your search rankings
How to fix it
Simply change your image URL from HTTP to HTTPS:
<!-- Before -->
<meta property="og:image" content="http://yoursite.com/og-image.jpg" />
<!-- After -->
<meta property="og:image" content="https://yoursite.com/og-image.jpg" />What if your server doesn't support HTTPS?
- Get a free SSL certificate — Use Let's Encrypt for a free, automated SSL certificate
- Use a CDN — Services like Cloudflare, Vercel, or Netlify provide free HTTPS
- Use an image hosting service — Platforms like Cloudinary, Imgix, or AWS S3 serve images over HTTPS by default
- Set up redirects — Configure your server to redirect HTTP to HTTPS
Additional tip: Use og:image:secure_url
For maximum compatibility, you can also specify the HTTPS URL explicitly:
<meta property="og:image" content="https://yoursite.com/og-image.jpg" />
<meta property="og:image:secure_url" content="https://yoursite.com/og-image.jpg" />