Sharing Not Showing

@atolmaprod If you are seeing unexpected behavior or appearance for one of your site’s social previews when sharing it on social media, this can be caused by the social media site caching old metadata for that page. This is why you may not immediately see the new values you set up for the page reflected in the page’s preview when you share it (image, title, description, etc).

To resolve this, we would first recommend to try checking your page’s link using Facebook’s Sharing Debugger tool located at https://developers.facebook.com/tools/debug/sharing/. Can you please try running the Facebook Sharing Debugger on the page you are experiencing the issue on, and under ‘When and how we last scraped the URL’ clicking the ‘Scrape Again’ option and letting us know whether this resolves the issue? The ‘Scrape Again’ option will force Facebook to update it’s cache for your page’s link.

Please note that to successfully update the cache it may require re-scraping your page several times as whether the page’s data can be read may take several requests between Facebook and the server your website is hosted on. Also, this guide includes more information on this and explains in detail how to do this: https://kb.yoast.com/kb/facebook-sharing-updated-details/

Thanks @devnihil!

Did you guys make any updates to the open graph? I haven’t changed anything and always keep things updated, but the debug tool is showing the following:

Could Not Connect To Server –
Check that the webserver is running, and that there are no firewalls blocking Facebook’s crawlers.

Inferred Property – The ‘og:image’ property should be explicitly provided, even if a value can be inferred from other tags.

Missing Properties – The following required properties are missing: og:url, og:type, og:title, og:image, og:description, fb:app_id

Hi @atolmaprod,

We’re not seeing the og:image error you mentioned. See the Facebook Debugger results.

There haven’t been any recent changes to the Open Graph meta tags. See the changelog for more details.

The “Could Not Connect To Server” error you mentioned is usually caused by a problem with your server, not with any specific plugin. If it’s not a temporary issue, your web host should be able to check into this and provide more guidance.

These results vary each time they’re scanned. This is strange, but thanks for your assistance.