Missing og:image Properties on some posts

Hi Chris,

There can be a few reasons why there isn’t an og:image tag appearing in the page source. We have the details and possible ways to fix the problem available in this guide: Why doesn’t Facebook display an image?.

Can you let us know if any of the recommendations solve the problem?

If you’ve taken the suggested steps, but the og:image tag doesn’t appear, there may be a conflict with another plugin or your theme.

We have a step-by-step guide for checking for conflicts here:?How to check for plugin conflicts.

Hello Priscilla,

Thanks for your reply!

I try the recommendations and:

-Did you enable Open Graph tags?
Yes

-Does the Facebook debug tool provide any errors about your image?
Yes as I mentioned in the previous post, Missing Properties – The following required properties are missing: og:image

-Does the image meet the Open Graph image recommendations?
Yes, 2 example images where I had a problem: dimensions 963 width x 541 height pixels and 37 KB size.
Another image has 750 width x 430 height pixels and 49 KB size.

-Try clearing all your caching
I clear the cache.

-The Social tab in Yoast SEO!
As I mentioned in the previous post problem appears 2 times in 10 posts. I haven’t that problem in every post.
In the post that works correctly, I didn’t use the Social tab in Yoast.
Now, after I upload a post and the image didn’t come into Facebook, I go into Yoast Social Tab and add manually the image. The problem didn’t solve.

I didn’t check the plugin conflicts yet, but I wonder why I face that problem in 2 of 10 posts? And not all of my posts?

Thank you!

Hi @xristos84,

Could you please provide us those affected posts where the issue occurs so that we can take a look at them?

@xristos84

We understand that on URLs like https://porto-rafti.gr/%CE%B1%CE%BD%CE%B7%CF%83%CF%85%CF%87%CE%B7%CF%84%CE%B9%CE%BA%CE%AE-%CE%B7-%CE%BA%CE%B1%CF%84%CE%AC%CF%83%CF%84%CE%B1%CF%83%CE%B7-%CE%BC%CE%B5-%CF%84%CE%BF%CE%BD-%CE%BA%CE%BF%CF%81%CE%BF%CE%BD%CE%B1/ you have directly added an image via the Yoast Social tab and it still fails to appear in the source code.

That sounds like a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:

1. Are all your non-Yoast plugins and themes also updated?

2. If all are updated please Check for conflicts. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

You can also check the source code your self by reviewing it and search for the tags. This guide explains more about how to do that: https://yoast.com/help/view-page-source-site/

If there is a conflict with a plugin or a theme, you can create a new GitHub issue?for our developers. Please report the issue to a third party developer as well.

If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium?and receive our Premium email support and we can help you further.

Hello, @pcosta88 @suascat_wp and @priscillamc

Here what I did, I migrate the website into different domain name so I can do my test without affecting the live website then deactivate all the plugins and switch into Twenty Twenty theme.

Clear all the cache of my browser, and open a post with the known problem. Then I look into the source code. I didn’t see any og: meta tag property (that’s normal because Yoast plugin is deactivated)

Then I activate the Yoast plugin and go again into source code of the post, I can see og:locale, og:type, og:title etc… but I can’t see the og:image property.

Notice that enabled theme is the Twenty Twenty and enabled plugin is only the Yoast.

Thank you!

Hi @xristos84,

We’re not sure why the og:image tag is not appearing for this page, but we noticed that there is also a missing canonical tag. Since the og:url tag is pointing to “https://porto-rafti.gr/?p=50303” and that redirects to another URL, there’s an error somewhere else related to this page.

To see if this is a problem with the SEO data for certain pages, please try the following steps to reindex the SEO data on your site:

1. Install and activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Click the “Reset indexables and migrations” button
4. Go to SEO -> Tools and under SEO data, click the “Speed up your site” button.

Does the og:image or the canonical tags appear?

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Hello @devnihil and @priscillamc

The problem didn’t solve, I was making some test that’s why I was late to reply.
After I tried Priscilla guide it solved all previous og:url and og:image.
But when I create new posts again 2 of 10 posts have the same problem.

Thank you!

Hi guys

I am experiencing a similar issue.
I have followed your instructions till here:

Install and activate the Yoast Test Helper plugin
Go to Tools -> Yoast Test
Click the “Reset indexables and migrations” button
Go to SEO -> Tools and under SEO data, click the “Speed up your site” button.

but when I get to SEO –> Tools ”SEO DATA optimization” it returned
‘Oops, something has gone wrong and we couldn’t complete the optimization of your SEO data. Please click the button again to re-start the process.’
I clearly tried several times with no success.

I have a staging environment with identical configuration, so I tried the SEO DATA optimization before any changes and worked fine.
I then installed Yoast Helper, cleared the tables, launched again the SEO DATA optimization and got the same error as the production site.

So I guess something is wrong in Yoast Test Helper? Or the SEO DATA optimization when rebuilding those tables?

Finally, no og:imagine was added, although all the other OG meta descriptors are present.

Any ideas?

Hello @wlsfh, personally the only solution that works for me, was to change SEO plugin.

Hi @xristos84 it seems that was my only option well.