October 11, 2016
Hello, I am trying to troubleshoot LinkedIn not displaying preview images when we share pages of our site with AIOSEOP running 220.127.116.11 on WP 4.7.3, social meta module active and configured. I don’t think the problem is any AIOSEOP “bug” but I don’t really know where else to turn. Stackoverflow is all over the place.
Debug String: OCI1OQ8WV03S+ZOEYECCOWCGVTQ
First, I am aware that the LinkedIn end is a PITA because of a 7-day cache. Unfortunately, I’m being pushed hard to hard to figure this out “ASAP.” I’m trying to create new custom posts to work around any potential caches.
Things I have checked:
- og:image meta is displaying the correct image address
- Image size is large enough (1260 by 960px) … pretty sure
- Only one og:image meta*
The og:type was set to website for all of my custom posts and pages. I changed that to article for custom posts in the interface, but it’s not changing in the source code. Not sure why that would be a problem anyhow.
The og:url of the page is http://www while og:image content is on a CDN, http://cdn. This isn’t a problem on a sister site on the network, so not sure why it would be here.
Website og:title and title tag don’t match. Title tag shows a hyphen, og:title shows a pipe as a separator. Not sure why this would be a problem with image previews and not the title, but jotting it down.
*There is only one og:image meta but there are multiple metas regarding images displaying:
They all show the same image URL, so I don’t think that would be it. It’s also all ahead of the AIOSEOP end comment, so it looks like it’s supposed to be there to me.
I run w3tc but I run it on all my sites and only the main site has an issue, which it has with 6 different custom post types and pages.
Besides wait 7 days, I’m not sure what else to review.
The Facebook Debug button was really helpful, btw.
October 11, 2016
The one thing I’d suggest is look at the page load times and the image filesize as LinkedIn tends to have a low timeout and doesn’t like images over a certain filesize…
If you can share the URL for the post you’re having issues with we can take a look.
Thanks, Steve. My crew and I definitely do not keep our pages as slim as I’d like them to be, but I’m just not seeing any consistent difference between pages that do load image previews when shared and pages that do not.
My coworkers are toggling settings as I write this, so hopefully these examples are still solid in 10 mins.
LinkedIn loads preview images for our homepage: http://www.callisonrtkl.com/
LinkedIn loads preview images for a publications page: http://www.callisonrtkl.com/pu…..port-2015/
LinkedIn does not load images for an office page: http://www.callisonrtkl.com/of…..singapore/
LinkedIn does not load images for a person page: http://www.callisonrtkl.com/pe…..es-mellor/
LinkedIn does not load images for a project page: http://www.callisonrtkl.com/pr…..ts/appian/
Any page on our blog is fine and we don’t even use the social meta add-on there: http://www.callisonrtkl.com/yo…..-mobility/
Furthermore, I noticed that LinkedIn does not look at the og:title or title tag. It seems to prefer the h1 on the page. It does not cache it either. If I change the post title and refresh, LinkedIn follows the change … even when the title tag and og:title are something completely different.
My guess is that whether or not a preview image loads has to do with where the first image is located in the page vs. render-blocking scripts or some other element. It seems to not cache the HTML but definitely does cache the image.
If you can mark this post as private, much appreciated.
October 11, 2016
Thanks, Steve. On the LinkedIn issue, I made a lot of changes over a few days. Unfortunately, things started to work seemingly randomly. I cleared a number of stock WordPress stuff out of the header and that seemed to help but I can’t be sure. It makes me think that the “LinkedIn share 7 day cache” is real. It’s terribly confusing if that’s the case because they appear to cache both the title tag and image, but separately. I also can’t tell if they pick up the image from any share of the website made or a crawl or both.
So, good luck to the next person who has this issue. This too shall pass, I expect.