CMS item Linkedin sharing error (no preview)

Publishing help Project settings
1

Hi there,

So far a client had no problems with sharing e.g. blog posts on Linkedin, but suddenly the preview is not generated:

This exact URL has been shared before without any problems.

Opengraph.xyz shows that everything is fine, and there are no problems with publishing on any other platform:

Homepage sharing on Linkedin works perfectly fine:

So far I’ve tried:

  • disabling HTML and JS minification
  • disabling Cookies management
  • manually setting up og metadata in < head > instead of using CMS field
  • switching between www.* and * as default domains

Ideas:

  • problem with SSL/TLS handshake (I’m using Webflow SSL)
  • LinkedIn out-of-the-blue bug

Has anyone experienced / is experiencing same issues, and maybe found a solution?

Cheers!

2

not working for me either.

I tested with a TechCrunch article and it worked.

I tested with one of your CMS pages and it’s broken. This seems to be a platform wide issue. Can you please confirm?

Post Inspector 2024-06-27 at 9.34.51 AM
Post Inspector 2024-06-27 at 9.34.51 AM3116×1438 174 KB

Post Inspector 2024-06-27 at 9.37.24 AM
Post Inspector 2024-06-27 at 9.37.24 AM2390×1466 181 KB

3

We’re having exactly the same issue - all our CMS posts are suddenly returning a 500 server error on Linkedin’s Post Inspector (and cannot show preview when attempting to share on LinkedIn), including many posts that have previously been successfully shared on LinkedIn.

Like the OP, Opengraph.xyz shows no issues, publishing on all other platforms works without issues, and LinkedIn Post Inspector can preview static pages from the site.

Read-only link

Any help would be appreciated!

4

Same issue here. Following…

5

I have the same issue …

6

I have the same issue… Linkedin show no preview and the post inspector shows error… Has anyone experienced / is experiencing same issues, and maybe found a solution?

7

Same exact issue here. Guessing it’s system wide and want to confirm. the site is here: Wevr at AWE USA 2024 and when I post link to Linkedin, it gives me an error for the preview.

8

I’m having the same issue as well. Previously shared links that have been cached work on LinkedIn, but anything new comes back with an error on post inspector and produces no preview.

9

Same issue. 500 failure. Seems isolated to CMS pages, but not 100% sure. It’s strange. Enterprise sites don’t seem to be having this issue.

10

@dspinco - The og:url meta tag appears to be missing from your site. LinkedIn requires it. Make your website shareable on LinkedIn | LinkedIn Help.

No one else shared a URL so :person_shrugging:

11

@webdev Here’s one example!
Google Tag Manager & Google Analytics 4: Using Data to Your Advantage

Still no luck on LinkedIn’s Post Inspector

We manually added og:url to code using
meta property=“og:url” content=“https curiodigital io/blog/{CMS Slug}”

12

From Support:
Thank you for contacting Webflow - Max here 👋 from the Support team. We appreciate you reaching out regarding your concerns with blog post

Currently Webflow sites meets the Open Graph protocol standards and tests we are conducting via tools like www.opengraph.xyz work as expected: Brix Agency Blog Open Graph and since we aren’t blocking LinkedIn’s requests to crawl this data, it appears to be an issue on LinkedIn’s end.

This could be because Linkedin has not currently implemented the latest version of TLS (Transportation Layer Security). Webflow runs TLS 1.3 as announced in August of 2022 and Linkedin is still running TLS 1.2. This is confirmed by comparing us with the site CDN77 a public TLS checker:

Firstly, I recommend reaching out to LinkedIn support for assistance if you have not done so already just to confirm there are not any issues originating from their end.

That being said your report is not the first we have received regarding this concern and we are currently monitoring this issue more broadly.

13

@lucasramalho - WebP is not supported by LinkedIn.

14

Hey guys, the issue has been resolved for our site. We tried different solutions without any luck until yesterday. As a final possible solution, we disabled HTML minification. Not sure if it’s done the trick, but the problem is gone.