You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client reports Facebook is not using the appropriate image. It falls back to a default, it seems.
Message
Oh - hang in there with me . . . backstory. We have an issue with Facebook pulling in the correct image (randomly it seems) from blog posts from the OregonsAdventureCoast.com website. The actual share buttons we have on the site seem to be working properly - I think. This is about our blog writer using a tool called Loomly.
It appears that when she schedules the posts to be added to FB, it is pulling the correct image. The OregonsAdventureCoast.com website has all the appropriate OG tags and from what I can tell, they are all applied correctly. But some of the posts she schedules, once they get pushed live, use that blue wave graphic that is up below the header photo. The blue wave is in none of the previews for the post, we only notice it once it goes live. (First Screen shot showing live post with blue wave for photo).
I have been researching this and found a FB Debugger (a link Regis may have sent too, when he was fixing all the share buttons on the site). When I plug in the url of the blog into the debugger, the preview shows the correct image. I did notice one “Warning that Should Be Fixed”. I have no idea what it is, but it may help solve the issue because it’s the only error we’re seeing on the debugger.
Error we saw on the Debugger: Missing Properties: The following required properties are missing: fb:app_id
I’m not sure if there is anything you guys can do to help, but I’ve hit the wall. We’ve reached out to Loomly for support and this was their answer:
Thank you very much for your reply and for reporting this.
Our way to retrieve metadata images can be more powerful than Facebook, and this can lead to this difference. Unfortunately, we cannot change how Facebook works, but if you know the webmaster of the website, you might want to ask them to check the way their metadata was created to make sure Facebook can find the feature image.
Ok that is all I have. Thanks for your time reading this novel.
The text was updated successfully, but these errors were encountered:
Client reports Facebook is not using the appropriate image. It falls back to a default, it seems.
Message
Oh - hang in there with me . . . backstory. We have an issue with Facebook pulling in the correct image (randomly it seems) from blog posts from the OregonsAdventureCoast.com website. The actual share buttons we have on the site seem to be working properly - I think. This is about our blog writer using a tool called Loomly.
It appears that when she schedules the posts to be added to FB, it is pulling the correct image. The OregonsAdventureCoast.com website has all the appropriate OG tags and from what I can tell, they are all applied correctly. But some of the posts she schedules, once they get pushed live, use that blue wave graphic that is up below the header photo. The blue wave is in none of the previews for the post, we only notice it once it goes live. (First Screen shot showing live post with blue wave for photo).
I have been researching this and found a FB Debugger (a link Regis may have sent too, when he was fixing all the share buttons on the site). When I plug in the url of the blog into the debugger, the preview shows the correct image. I did notice one “Warning that Should Be Fixed”. I have no idea what it is, but it may help solve the issue because it’s the only error we’re seeing on the debugger.
Debugger URL: https://developers.facebook.com/tools/debug
Blog Post we had problems with: https://www.oregonsadventurecoast.com/blog/where-to-find-razor-clams-on-oregon-s-adventure-coast/
Error we saw on the Debugger: Missing Properties: The following required properties are missing: fb:app_id
I’m not sure if there is anything you guys can do to help, but I’ve hit the wall. We’ve reached out to Loomly for support and this was their answer:
Thank you very much for your reply and for reporting this.
Our way to retrieve metadata images can be more powerful than Facebook, and this can lead to this difference. Unfortunately, we cannot change how Facebook works, but if you know the webmaster of the website, you might want to ask them to check the way their metadata was created to make sure Facebook can find the feature image.
Ok that is all I have. Thanks for your time reading this novel.
The text was updated successfully, but these errors were encountered: