Hi all,
We’ve had an ongoing issue where our meta links show the wrong image when we send them. We’ve verified that the OG:image tag is correctly installed and is recording the correct image, as shown below. To make sure it works, we’ve even moved it to the very top of the section, so it’s the first thing that renders:
However, for some reason, Meta is instead using the default website logo as our OG:image, and saying it isn’t defined:
Does anyone have any experience fixing these sort of issues? Any help would be appreciated!
Thanks,
Jake
Hi @Tactica_Jake ,
Hi @Tactica_Jake ,
After you update OG:image you need to wait some time for the Goole raw data and update.
Hope my solution works perfectly for you!
Best regards,
Oliver | PageFly
1 Like
Thanks for the advice Oliver! Unfortunately, we’ve been dealing with this back-and-forth since July, and still no progress. I’m finally getting around to fixing it now, but it’s been in this position for over 2 months and hasn’t fixed, so I doubt it’s a matter of waiting.
Hello @Tactica_Jake 
Use og:image:secure instead of og:image for https
Try this meta tag
1 Like
Hi there! Thanks for the suggestion, I tried it and it didn’t work. Still the exact same error, even with the page recognizing the og:image:secure.
Any more ideas? Thanks!
Sorry, I forgot https in the url, please try this
1 Like
Thanks again, but no luck either. Still throwing an error in the debug tool.
We don’t have any apps for our social media specifically, but could an app be interfering with it? I’m pretty lost for solutions.
There should be no colon after og:image
Please try correct it to og:image

After this change, if it still does not work I think there must be a bug with the Facebook system that fails to recognize the og image.
1 Like
That did it! Thank you so much, we’ve been dealing with this for months! I can’t believe it was something that small.
To be fair, I must have left that colon in there after an edit, because it wasn’t there in my initial post. A combination of fixing this and adding the og:image:secure seems to have fixed it.
Thanks again!
Glad that it works now. Hope you the best!