Featured image for posts are not on Twitter or Facebook

Your post looks good in source. Meaning the open graph tags are all present and look good.

I am seeing this on the facebook debugger though: Curl error: 35 (SSL_CONNECT_ERROR)

I don’t think this is a Yoast SEO problem, but something else. Maybe another plugin or an issue with curl on the godaddy servers.

Good luck

Thank you. I’ll call GoDaddy on Tuesday and see if they can and will do anything about that. Would that affect Twitter as well as Facebook?
I did not choose any of the plugins — they did, and now my period of their premium “care” is over. They said I should have asked for that functionality, but as a member of the general public, how was I to know to do that?

Hi @automatters

Upon checking the page source of the URL you’ve mentioned, we do see that the Yoast SEO plugin is outputting the correct open graph and twitter tags that are being used for social sharing.

However, when we run the URL through Facebook’s sharing debugger tool, as confirmed in an earlier reply, it’s showing an error of Curl error: 35 (SSL_CONNECT_ERROR), which is why the social preview isn’t working as expected. We expect that this would affect the social preview on Twitter as well, which you can test using the Twitter Card Validator.

We recommend reaching out to your web host for assistance on this, as it’s likely an issue with your SSL connection. Once this is resolved, we would expect that when sharing your URL on Facebook’s sharing debugger tool, it would then generate the correct social preview.

Hi Michael,

My sincere thanks to you and Blazeman for running diagnostics to figure out the likely technical reason why my new WordPress website, that was professionally built by GoDaddy and recently taken live by them — including activating SSL.

I am very relieved that what you’ve discovered is likely what is preventing my posts’ feature images to not appear in my Facebook and Twitter posts, that I send out on social media to announce my weekly “AutoMatters & More” columns on my new website.

When I phoned GoDaddy yesterday asking for their 24/7 help that is included with their website hosting service, their primary initial response was to push for me to pay them extra for their premium professional care — as the agent said most of their customers do. I had understood that the purpose of that premium professional care is supposed to be for those GoDaddy customers who do not want to make their own changes to their website or add new posts themselves. I intended, and still intend, to do that myself.

I had trusted GoDaddy and paid them a lot of money to build me, as an individual, a WordPress website, set it up properly and keep my website working with their 24/7 customer service at no extra charge, included as part of the hosting that I pay them for my website.

I will phone GoDaddy today and insist that they fix the technical problem that both you and Blazeman have identified when you ran diagnostics on my new website.

I am very disappointed with GoDaddy’s not being able to figure this out, despite asking one of their builder/ technical experts to look into the cause of the problem. After the builder was consulted, the agent that had initially taken my call (after several unsuccessful attempts to connect with an agent at their incoming call center) told me that they have tried everything on their end, and that it likely will just take time for the Twitter and Facebook settings that they had me do, to ‘take.’

I am very concerned about going forward with the level of technical support that I can now expect from GoDaddy’s hosting service. A fairly recent update already crashed my website once a few weeks ago, while my website was still under development by them. Yesterday, they informed me that unless I pay for their premium website care, they will no longer perform required or recommended updates for me, and that they will consider fixing any problems that may result from updates on a case-by-case basis.

Corrected first paragraph of my reply above:

Hi Michael,

My sincere thanks to you and Blazeman for running diagnostics to figure out the likely technical reason why my tweets and Facebook social media posts, that include links from my new WordPress website, do not include my feature images. That website was professionally built by GoDaddy and recently taken live by them — including activating SSL

Hi Michael and Blazeman,

You were 100% CORRECT!!! Thank you.
I just spent two hours on the phone with GoDaddy. I got them to look at what you identified and then one of their builders they fixed the problem. Now my feature images show up in my new post announcement tweets and Facebook posts for my weekly posts at AutoMatters.net.
THANK YOU!!!

Jan
AutoMatters & More syndicated lifestyle columnist
AutoMatters.net

Hey Jan!

I’m having the exact same issue. My featured images, which have been working find for YEARS, now aren’t showing up Both the FB and Twitter debuggers/validators indicate an Https connection/timeout error.

I strongly suspect GoDaddy has horked something, possibly after their recent WordPress version update. Or they’re just way underprovisioning their servers.

Do you know what GoDaddy did to “fix” this?

Hi,
My issue with Social Media not displaying the featured image from each of my columns/posts was due to a different error (Curl error: 35 (SSL_CONNECT_ERROR)), as discovered by the Facebook debugger tool used by both Michael and Blazeman (see their responses above). Why GoDaddy did not know enough to find that when I called them first, but instead just had me change some settings in WordPress, I don’t know.
Armed with this new information from Michael and Blazemen, I phoned GoDaddy again, rejected their initial suggestion that I needed to pay for their premium website care beyond what I already am paying them for hosting, and instead insisted that they try what Michael and Blazeman suggested to get my new website working correctly. That should be what their 24/7, phone-in technical support is for, right?
I was quite insistent, as you can probably imagine. The lucky recipient of my wrath contacted his GoDaddy supervisor and a GoDaddy builder, who apparently removed and redid the SSL stuff that they had done very recently to take my site live. Eureka! That fixed my problem.
My advice to you is to not take no for an answer when you call GoDaddy. The person who you reach in their inbound call center has limited authority, and may need to ask for approval from a supervisor. Also, post your question on this Forum. The responses saved my website.
Finally, do NOT put your featured image in more than one place in your post. Just put it in the featured image section to the right of your post in WordPress Adding it to the Twitter and Facebook sections of Yoast SEO will generate a new error in the Facebook dubugger, and will slow down your tweets and Facebook posts from displaying that featured image.
This took days of me going back and forth with GoDaddy to resolve. I wish you Good luck!
Jan

• This reply was modified 3 years, 4 months ago by automatters.