Yoast using wrong image for og

Hello @kateamann

Thanks for reaching out about your og:image. Indeed, the og:image in the page source is https://thelacquercompany.com/wp-content/uploads/sites/2/2023/04/BELLES-RIVES-SIDE-TABLE-CHOCOLATE-1-e1680853119313.jpg

Please share a screenshot of your Facebook image in the Social tab of the Yoast SEO meta box when you edit that specific product. You can use any image-sharing service like https://pasteboard.co/, https://snag.gy/, https://imgur.com/, https://snipboard.io/, or even upload the screenshot to your own website. Once you upload it to an image-sharing service, please share the link to the image here.

Thanks Maybellyne. We’re not using the specific social image for facebook or twitter, so there is nothing in those fields. This is just the image yoast is marking as the default og.

Thanks for the feedback. Do you have an image defined as the product image?

Yes, the product image is set to?https://thelacquercompany.com/wp-content/uploads/sites/2/2023/04/BELLES-RIVES-BAR-CART-BOTTLE-GREEN-1.jpg

While testing this, I deleted it and re-added it just to make sure. Also to see if Yoast would then recognise the update. It didn’t work.

As far as I can see the image that it is using for the og here is not connected to this page or product in any way. Not in the product gallery, not in the variations, not even linked to the upsells.

I ask because the Yoast SEO plugin follows the hierarchy below to pick the?og:image:

• A user-defined image “Facebook image” in the Social tab of the Yoast SEO meta box.
• A user-defined “Featured image” for the product page
• A prominent image from the page’s content.
• The default “Social image” for products in Search Appearance.
• The site’s fallback/default social image (set at SEO > Social > Facebook > Default image).

So, if the plugin is picking that unwanted image as the og:image, it means it’s defined somewhere. You mentioned that the product was copied as a template. Can you share the URL of the template product page?

We don’t have a template. It was just a theory I had, as I’m seeing this happen on other pages with completely different combinations of images. My client may have set up the product by copying a similar one and changing the content. However, all of the content does appear to have been changed, especially the images.

By your hierarchy, I see that Yoast should be using the product image if there is no user-defined facebook image, which is what I would expect. So if we have defined the product image (which is also showing correctly in the google preview on the yoast panel), why is Yoast defining the og as something else?

You mentioned that you’ve set this image (image1) as the product image, but it is showing up this image (image2) on the OG:IMAGE tag output. We would suggest clearing the cache, and if that didn’t help, please perform a conflict check.

Please test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.

Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty-Two.

If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.

Can you please inform us of the results, so we can help you figure out what the problem is?

It’s quite a large undertaking to do a full conflict test just for this, so I have tried using the facebook specific image to see if that could at least be a quick fix, but even after clearing caches, Yoast is still using the random image as the og, not the product image I have now also set as the facebook image.

I have found info on the test helper plugin, so I used that to try resetting the indexables. This is the sort of thing I was looking for. It seems to have worked. So for anyone else who runs into this, try that first.

Thanks for sharing how you were able to eventually resolve the issue, @kateamann.

This thread was marked resolved as the original poster confirmed the issue no longer occurs on their site.