Social Shared Content Not Displaying Image

January 7, 2013 at 3:07 pm (Facebook, LinkedIn, social media, website management) (, , )

Share an Update LinkedInRecently, I was social sharing some original content that a client had produced. When I pasted the URL into the “Share an Update” box, I was frustrated to see that the image from the content page didn’t carry over.  It appears that Linkedin is no longer picking up the images from content pages when I share them (using the full URL) via Linkedin.  Note: I’m not using an API.  I’m copying the URL and pasting it into the “share an update…” box.

Side Note: I always try to include an image with content online, mainly because content shared via image-supported Social Media (i.e. LinkedIn, Facebook) is more engaging if there is an image associated with it to attract traffic.

So, I found a developer forum online that clarified “setting display tags for shares.”  Like many others, Open Graph Protocol is new to me.  So, I called my website support engineers and googled about a bit.

Add OG Tags to Head Tags of Your Website

It appears that website managers have to add the Open Graph Protocol meta properties—as you would like them to appear when shared–to the head tag.   Reference the links above for more, but I basically added the follow to my head tag b/c the image was the bone I was picking.

<meta property="og:image" content="" />

<meta property="og:image:type" content="image/jpeg" />

<meta property="og:image:width" content="180" />

<meta property="og:image:height" content="128" />

Great, I did that.  Now here’s the hiccup!

LinkedIn Caches for a Week

If you share a URL, the LinkedIn system will store the page data for a week.  Thus, the page can’t get re-scraped for 7 days and there’s no way to force a quicker re-scan.  As far as I can tell, this is current information as of Dec 2012, but LinkedIn is “working on” a way to give users the ability to flush the cache yourselves…  Check out the LinkedIn Forum cache conversation for any updates and to commiserate. Chime in and share the forum to make sure this enhancement remains a priority.

Work Around

  1. Correct your metadata as desired using Open Graph Protocol
  2. Change the url for the page (LI caching is case sensitive so simply convert character(s) to Upper case)
  3. Redirect old url to new url
  4. Then re-share.

Permalink Leave a Comment

%d bloggers like this: