WPIntell

Source evidence

Jetpack is sharing Facebook posts but not the image

Jetpack Social · support · 2026-04-02T05:21:00+00:00

mixedsentiment
highseverity
0.95relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 25 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
sirrah resolved
I’m using Jetpack to share posts to socials. It is working fine with LinkedIn and Instagram, but for Facebook is sharing the post, but not the image. The Meta debugger tool has ‘bad response code’ – URL returned a bad HTTP response code’. 403 code saying it could be due to the robots.txt. I’ve added the allowlist rule though and asked google to crawl the robots.txt file again but no success. It also doesn’t seem to have any data on the scraped url, so clearly isn’t talking properly to the site. Are you able to assist? The page I need help with: [ log in to see the link] Hi there, Sebastian here, I hope you are doing well! Thank you for reaching out about Jetpack Social not including the image when sharing to Facebook. I can see you have already done some troubleshooting on the robots.txt side, so I want to make sure we get to the bottom of this properly. When I tried to access your site (bureaucracybeat.com) to review the setup, I found that it is currently not responding. A site that is down or returning errors would also explain why Facebook’s crawler is unable to scrape the Open Graph image, which is what gets pulled in when sharing a post. Could you check with your hosting provider to confirm the site is back up and accessible? Once the site is reachable, please let me know and we can take a closer look at the Facebook connection, verify the Open Graph tags are set correctly, and check if there is anything at the server or plugin level blocking Facebook’s crawler. In the meantime, here is our Jetpack Social documentation if you’d like to review the setup: https://jetpack.com/support/jetpack-social/ Looking forward to helping you get this sorted out! Hi Sebastian, Thanks for the help – the site is live. Hi @sirrah , Thanks for confirming the site is back up! I took another look on my end. When I first checked your URL in the Facebook debugger, I also saw the 403 error you mentioned. However, after running a fresh scrape now, it’s returning a 200 response, so that part seems to have been resolved in the meantime, possibly due to a hosting or security rule change. That said, I’m still seeing an issue with the Jetpack connection itself. Some of the requests Jetpack relies on are timing out or not completing properly, which can affect Social sharing, including sending the image to Facebook. This usually points to something on the server side, like a firewall, security plugin, or hosting-level rule, blocking or slowing down those requests (especially ones related to XML-RPC or Jetpack communication). Could you check the following? Any security plugins (Wordfence, Sucuri, etc.), try temporarily disabling them If you’re using Cloudflare, check Firewall/WAF rules for anything blocking requests with parameters like ?for=jetpack With your host, confirm that XML-RPC and external requests from WordPress.com aren’t being blocked or rate-limited You can also check the connection status here: https://jptools.wordpress.com/debug/?url=https://www.bureaucracybeat.com/ Once that’s sorted, I’d recommend reconnecting Jetpack and then trying to share the post again. Let me know how it goes! Hi thanks again for your reply. I think this is resolved now. There were a couple of issues – firstly the images were too small, so I’ve put in larger ones and Facebook now seems to be able to see them. Secondly, our host was having issues with server load so they’ve moved us to another server. I think that was causing issues as the site kept dropping offline or being very slow to process requests. I’ll keep an eye on it all but that seems to have fixed the issues. Hi @sirrah , Thanks for the detailed update, that helps a lot! That all makes sense, both the image size and the server instability can definitely affect how Facebook is able to scrape the page and pick up the Open Graph image. Glad to hear moving to a new server and updating the images did the trick. If anything comes up again or you notice sharing behaving oddly, feel free to open a new thread and we’ll take another look. Thanks again for circling back with the fix!

Comments

5 shown
Chatoxz (a11n) 2026-04-06T16:10:00+00:00

Hi there, Sebastian here, I hope you are doing well! Thank you for reaching out about Jetpack Social not including the image when sharing to Facebook. I can see you have already done some troubleshooting on the robots.txt side, so I want to make sure we get to the bottom of this properly. When I tried to access your site (bureaucracybeat.com) to review the setup, I found that it is currently not responding. A site that is down or returning errors would also explain why Facebook’s crawler is unable to scrape the Open Graph image, which is what gets pulled in when sharing a post. Could you check with your hosting provider to confirm the site is back up and accessible? Once the site is reachable, please let me know and we can take a closer look at the Facebook connection, verify the Open Graph tags are set correctly, and check if there is anything at the server or plugin level blocking Facebook’s crawler. In the meantime, here is our Jetpack Social documentation if you’d like to review the setup: https://jetpack.com/support/jetpack-social/ Looking forward to helping you get this sorted out!

sirrah 2026-04-12T21:42:00+00:00

Hi Sebastian, Thanks for the help – the site is live.

Alin (a11n) 2026-04-15T11:14:00+00:00

Hi @sirrah , Thanks for confirming the site is back up! I took another look on my end. When I first checked your URL in the Facebook debugger, I also saw the 403 error you mentioned. However, after running a fresh scrape now, it’s returning a 200 response, so that part seems to have been resolved in the meantime, possibly due to a hosting or security rule change. That said, I’m still seeing an issue with the Jetpack connection itself. Some of the requests Jetpack relies on are timing out or not completing properly, which can affect Social sharing, including sending the image to Facebook. This usually points to something on the server side, like a firewall, security plugin, or hosting-level rule, blocking or slowing down those requests (especially ones related to XML-RPC or Jetpack communication). Could you check the following? Any security plugins (Wordfence, Sucuri, etc.), try temporarily disabling them If you’re using Cloudflare, check Firewall/WAF rules for anything blocking requests with parameters like ?for=jetpack With your host, confirm that XML-RPC and external requests from WordPress.com aren’t being blocked or rate-limited You can also check the connection status here: https://jptools.wordpress.com/debug/?url=https://www.bureaucracybeat.com/ Once that’s sorted, I’d recommend reconnecting Jetpack and then trying to share the post again. Let me know how it goes!

sirrah 2026-04-16T01:59:00+00:00

Hi thanks again for your reply. I think this is resolved now. There were a couple of issues – firstly the images were too small, so I’ve put in larger ones and Facebook now seems to be able to see them. Secondly, our host was having issues with server load so they’ve moved us to another server. I think that was causing issues as the site kept dropping offline or being very slow to process requests. I’ll keep an eye on it all but that seems to have fixed the issues.

Alin (a11n) 2026-04-16T06:05:00+00:00

Hi @sirrah , Thanks for the detailed update, that helps a lot! That all makes sense, both the image size and the server instability can definitely affect how Facebook is able to scrape the page and pick up the Open Graph image. Glad to hear moving to a new server and updating the images did the trick. If anything comes up again or you notice sharing behaving oddly, feel free to open a new thread and we’ll take another look. Thanks again for circling back with the fix!