Chuck Reynolds

Easy answer right now: no.

Real answer, is soonish. The way the Facebook prioritized images presented on the timeline when this version was released, everything was peachy keen. They defaulted to the first one presented in the array and you could click arrows to select others available. A while back they removed that functionality and now choose an image they decide to use. Now… most of the times that’s the first image you offer them given the image size is appropriate to their suggestions, however this too is sometimes hit or miss. In the newer version of this plugin, on github and needs more testing before release, I have it set up so the featured image will be the only one suggested for open graph, if not it’ll look for a content image, then use the fallback. That should ‘fix’ most use-cases out there.
I’m finishing client work still but I’m looking to jump back into that new version to release it by december probably.
Cheers
/end ramble

Do you have a cached output? There’s no sort of cache-busting built into this plugin as there’s just no need for that but that could be why that’s happening.
Have you used the Facebook Debugger to clear THEIR cache? https://developers.facebook.com/tools/debug/og/object/

Other than that I’d need your site url to at least look at it. Try the debugger first… add in your home page url and scrape it, then do it for one of your posts too. Then lmk. Cheers

this plugin can’t change it in your settings; it has no access to that; only reads what the settings have and displays that on the front.

So few things.
General statement here but just because there are Open Graph tags in your site doesn’t mean any other site will behave and listen to them the way you intended. Unfortunately every site is different and they all do whatever the hell they want most of the time.
That said; the code output by this plugin is working as you intended and outputting your logo on the home page. FB crawler shows that and they ‘SHOULD’ use that image but even they may not.

So first thing is that image is pretty small… it’s 200px square. On your page that’s fine but for open graph you should probably have a larger image to make sure it’ll work on all sites as they all have different image size requirements. I have a public repo that helps with that here: https://github.com/chuckreynolds/social-profile-image-sizes

Okay aside from that. Linkedin says they listen to OGP tags… but if my experience proves anything… they too can be full of it. So one thing that MAY be happening is that you put your URL into Linkedin and they cached the other image prior to you having open graph tags with your logo url present. They cache information for 7 days with no way to flush it (like FB’s debugger linter). So if that happened then you’ll just have to wait it out. Otherwise, bumping the image size may help them pick that up after their cache is cleared.
Source on that: https://developer.linkedin.com/docs/share-on-linkedin

Nothing else you can do about it really. Just wait for their cache to clear and hopefully they abide by the image you put in your code.

Cheers

I am on twitter @chuckreynolds if you want to dm the domain.

OK. You have a few problems you need to fix.

First off this: “Bad Response Code URL returned a bad HTTP response code.” and this: “Response Code 404” means you have a problem with your site and/or hosting. (see the second thing below)

Secondly you have the Yoast SEO plugin active and you’re blocking robots… see your page source code: <meta name="robots" content="noindex,follow"/>
The problem with that is…. well Facebook scraper is a robot soo… you need to fix that.

Thirdly… you have the Yoast SEO plugin ALSO doing OGP tags… you need to choose one plugin to do that.. having more than one set of OGP tags will throw errors and give you odd results.

Fourthly (is that a word?) you have yet another plugin doing OGP in there… all it shows in source is this: <!-- OG: 2.4 -->

and Fifthly… whatever… you don’t have THIS plugin, you’re filing a support request on, even active.

So… there you go. Free support for a problem that has nothing to do with this plugin at all.

Cheers.