When you share a post on Facebook, or when Jetpack Publicize publishes a post to your Facebook page, Facebook crawls the page and looks for Open Graph meta tags in the head to build a complete post preview (with an image, title, description, …).
Jetpack automatically creates these Open Graph Meta tags for you unless you already use another Open Graph plugin, in which case we let the other plugin handle things.
You can see what Facebook sees by entering one of your posts’ URLs in Facebook Debugger:
https://developers.facebook.com/tools/debug
If you’re not happy with what Facebook sees, I’d suggest checking what plugin generates the Open Graph Meta Tags on your site, and if it’s not Jetpack, make sure your Open Graph plugin is configured properly.
Let me know if it helps. If you continue to experience issues, do not hesitate to post your site URL here, so I can have a look!
If you want it to remain private, you can also contact us via this contact form:
http://jetpack.me/contact-support/
Jeremy
thank you for your help. Sorry that I STUPIDLY did not provide the link! My blog is here:
http://www.james-baker.com/news/
the debugger is definitely confuse by the front page but even a single post is showing the wrong image:
http://www.james-baker.com/news/the-boxtrolls/
But my next question (probably a silly one) is why this is so and what I’ve done wrong? I have chosen preferred images for each post but now do i have to do that again with TAGS? and if so is there a way of speeding up/automating this somehow? my blog is vast.
Thank you for any help!
James
@jamiebaker I see you’re using the All In One SEO plugin to manage Open Graph Meta tags on your site, and consequently to control the look of your posts on Facebook. You can configure the tags and check that everything is properly set up by going to All In One SEO > Social Meta in your dashboard.
Looking at that post in Facebook Debugger, Facebook seems to be confused when browsing your site and looking for information:
http://i.wpne.ws/ZCst
og:image was not defined, could not be downloaded or was not big enough.
But it is there, All In One SEO does its job properly:
http://i.wpne.ws/ZD1a
It is big enough:
http://i.wpne.ws/ZCgV
And I’m able to download it, so Facebook should too. I’m not sure what’s causing the issue here. It would be worth checking your active plugins and services for any security plugin that may restrict access to your site, and may block Facebook from download the image. Image hotlinking protection services and security plugins can do that, for example.
If none of this helps, I’d suggest contacting Facebook for help:
https://developers.facebook.com/bugs/trending/
I am discovering that my web host has installed a WORDPRESS LOCKDOWN that denies JETPACK access to my xmlrpc.php file. Apparently this was done in the past few months but I did not know until I uninstalled JETPACK for a few moments (to check for a plugin incompatability) and when i tried to reinstall it i got this message:
“Your website needs to be publicly accessible to use Jetpack: site_inaccessible”
This is perhaps why my images are currently blocked. My host is rather terse and unhelpful, would you mind telling me the correct syntax to add to my .htaccess file to allow JETPACK access to my xmlrpc.php file? Do I allow specific JETPACK IP addresses or some sort of referral from JETPACK. WORDPRESS.COM?
I see you also contacted us via email about this, and my colleague Ryan replied with some tips to help fix this.
However, if your host is blocking access to your site’s XML-RPC file, it’s probably best to turn to them for help: you might not be able to override their block without their help. Since we don’t know how your hosting provider blocked access to the file, we won’t really be able to tell you how to work around the problem.
