LinkedIn expects `name="image"` within the `<meta/>` tag

[kiwikilian]

LinkedIn expects `name="image"` within the `` tag

[KiwiKilian]

Thanks for your input! Does it detect the og image of your example in the post inspector? I think it's just an example, how they try to find the og image. It works successfully for me with the current output (without name="image", or did I miss another difference?). They also document it like without name.

The name attribute doesn't appear on most articles and docs on this topic. So I would rather opt for an option to overwrite the HTML output. This could look like this, allowing anybody to change the output HTML:

generateHTML: (outputUrl) => `<meta property="og:image" content="${outputUrl}" />`

[ddamato]

Does it detect the og image of your example in the post inspector?

No it uses the one for the homepage instead. Try with my latest post.

The og-image should have the title of the specific article rendered in the image, but it's using the homepage og-image instead. However, it's entirely possible it's just LinkedIn scraping my metadata incorrectly. I have the same problem with the title and description even after adding the name attributes as they've recommended.

[ddamato]

Ok yeah, issue is on my end. It wasn't rendering the correct absolute url. However, I'd appreciate your suggestion since the twitter metatags are different but I'd like to send the same image there also. Rendering the outputUrl in my template would be better than rendering the entire HTML, in my opinion.

[github-actions]

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[KiwiKilian]

@ddamato I've added the generateHTML option. You could just modify the markup generated by the shortcode. If you really just want to get the output path and generate the markup in your page templates you can use the capture approach. Or as most customizable variant, create a custom shortcode.