Check out this result of debugging an article using Facebook debugger.
It comes up with this warning:
og:image should be larger. Provided og:image is not big enough. Please use an image that's at least 200x200 and preferably 1500x1500.
But if you open the image displayed in the "og:image"-field below, you can clearly see that the image is big enough - 700x350 px.
This results in Facebook picking random images when I'm publishing articles on my wall.
Any idea why this happens?
Edit: Could the problem be caused by my CMS redirecting the url of the image?
I had
in the meta tags.
Removed that line and it worked, so current tags look like this:
I just ran into this problem and tried saving as a JPEG with slightly lower quality as another answerer suggested. Once I'd referenced that and tried again on the debugger page Facebook told me that, again, my image was too small, and instead it would use the old image, meaning the one it complained about the first time.
So I simply submitted the same URL once more and it stopped complaining. Basically it's one debug behind. Try refreshing the debug and see if it doesn't fix it for you.
It's a bit late, but I had this issue for after creating a new open graph image in photoshop. It didn't make any sense because in the debugger it still displayed the image that was found, which was 359x379. It still complained it was smaller than 200x200, though.
I did not try changing any other header tags, as I did not believe that was the issue.
Instead, I opened photoshop again and saved the image again. I saved it as a JPG at 85% quality -- and the difference was that I used "Progressive" instead of "Optimized". This fixed the issue immediately, although I'm not positive the "Optimized" setting was the issue.
If the image url is https:// and Facebook has problems reading your SSL certificate, it will produce this rather unhelpful error message. To test, see if a http:// url for the image works. If it does, your CA certificate may need some tweaking. Try Googling "Curl Error : SSL_CACERT SSL certificate problem: unable to get local issuer certificate"
Note: Even if your page has no problem displaying with a https protocol, Facebook digs deeper to confirm your identity. I think this is relatively recent. Considering their whole fake news debacle I'm not going to be too upset.
Try to add this:
Another issue that could cause this is the use of characters like # in the filename.
Allthough browser will show them correctly, facebook will give an error stateting the img is to small, while infact it isn't able to read it.
So make sure you image filename only uses the standard characters A to z, _, -, 0-9