Fix Facebook shares missing images or showing 403 Forbidden

If your Revive Social posts are published to Facebook without images, the issue is often that Facebook cannot access your page or image URL while scraping the link preview.

Symptoms

You may notice one or more of these signs:

• Your Facebook post is published as text-only, without a featured image preview.
• The shared URL appears, but the image does not load.
• Facebook Sharing Debugger returns a 403 Forbidden scrape error.

Why this happens

Revive Social sends the post link to Facebook, but Facebook still needs to fetch your page metadata (Open Graph tags) and image URL with its crawler.

If your site blocks Facebook's crawler, Facebook cannot read the page or image, so the preview image will not appear.

📝 Info: A 403 Forbidden in Facebook Sharing Debugger usually means the block happens on your server, firewall, or CDN layer, not inside Revive Social.

Test the URL in Facebook Sharing Debugger

1. Open Facebook Sharing Debugger.
2. Paste the exact post URL that Revive Social shared.
3. Click Debug.
4. Check the scrape result for errors, especially 403 Forbidden.

Allow Facebook's crawler

Allow Facebook's crawler user agent, usually facebookexternalhit, through your security layers.

If your system supports allowlists by bot name, user agent, or IP reputation rules, add an allow rule for Facebook crawler traffic so it can access both:

• Your post URL
• Your image URL

Places to check for blocks

Check each layer where traffic might be filtered:

• WordPress security plugins
• Hosting firewall or WAF rules
• CDN firewall and bot protection rules
• Hotlink protection or image protection rules
• robots.txt rules that may disallow Facebook crawler access

⚠️ Warning: If hotlink or bot rules block image URLs, Facebook may read the page but still fail to fetch the preview image.

Verify the fix

1. Return to Facebook Sharing Debugger.
2. Click Scrape Again for the same URL.
3. Confirm there is no 403 Forbidden error.
4. Confirm the debugger now shows the expected image preview.
5. Share the post again from Revive Social and check the new Facebook post.

When to contact hosting or CDN support

If the debugger still returns 403 Forbidden after checking plugin and WordPress-level settings, contact your hosting or CDN support and ask them to confirm why Facebook crawler traffic is blocked for that URL.