Hi @leanderbraunschweig
When you share a post on Facebook or LinkedIn, or when Jetpack Publicize publishes a post to those social media pages, Facebook & LinkedIn will crawl the page and look for Open Graph meta tags in the head to build a complete post preview (with an image, title, description, …). Jetpack automatically creates these Open Graph Meta Tags for you unless you already use another Open Graph plugin, in which case we let the other plugin handle things.
Looking at your site, I see you have the Yoast SEO plugin installed and active, which also adds OG tags. As mentioned before, we automatically disable our open graph tags when this happens as some social media platform doesn’t always like duplicate tags.
If you would rather just use Jetpack’s open graph tags, you can use this plugin to keep them on: https://wordpress.org/plugins/always-use-jetpack-open-graph
If you don’t want to use this plugin, but you continue to have issues with your open graph tags, you will need to contact Yoast support for further help: https://yoast.com/help/support
Alternatively, if you want to temporarily disable Yoast SEO, this can also help us test. If you then share a new post and this issue reoccurs, please do let us know, and we can investigate further.
Hi @leanderbraunschweig
It has been more than one week since we have heard from you, so I’m marking this topic as resolved. But If you have any further questions or need some more help, you’re welcome to reply here or open another thread.
Hi @bizanimesh,
thanks for your reply and sorry for not getting back earlier, I was away on vacation…
I totally understand the handling of the Open Graph meta tags but this is not the issue we’re facing. The problem lies in the sharing itself, meaning that although the post shows up correctly with the og:image in the source code when testing with LinkedIn’s Post Inspector tool, the post isn’t being shared properly on LinkedIn and misses the preview-image.
So my questions prevail:
- Could there be a problem with us scheduling a post vs. regularly posting one?
- How can we properly debug the content / post / URL that is being sent to LinkedIn? Is there a filter that we can utilize in order to ‘read’ the output?
- Anything else you can think of that could be done?
Sorry for re-iterating…
Another thought: Is it possible to introduce a delay before auto-posting so that we can make sure that no other plugin / cron job or similar interferes and the URL is ‘ready’?
Many thanks for taking the time!
In addition one specific example:
Any ideas on how this discrepancy can come about?
Hello, there.
Would you be able to use Animesh’s troubleshooting to see if there is a difference at all, just to make sure nothing is getting tangled in the sharing process?
I mentioned this because it looks like you’re right – the og:image tag is present, and the LinkedIn inspector can see it just fine. Because of that, this should be working normally.
Other than Animesh’s ideas to ensure only one tag is present when the sharing happens, I also wanted to ask if this happens on every post, or just randomly? If randomly, I wonder if perhaps the shares work on smaller filesize images and doesn’t work on larger ones, and if you could test that as well.
However, if it is -all- shares, then I would most definitely recommend Animseh’s steps next.
Please let us know the results of this troubleshooting and we can go from there. Thanks!
Anonymous User 18700194
(@anonymized-18700194)
Hi @leanderbraunschweig –
We have looked into this more and can confirm an issue affecting the Publicize module’s connection to LinkedIn.
We have a bug report here, and our development team will be looking into this:
https://github.com/Automattic/wp-calypso/issues/53978
We’ll post an update as soon as we can.
Thanks again for the report and your patience as we look into this.
Glad to hear that you found the culprit! Thanks for the efforts and for keeping us posted.
Anonymous User 18700194
(@anonymized-18700194)
Hi @leanderbraunschweig –
We have deployed an update and this should now be resolved.
