Hello,
This is a known issue with google+ as id does not handle open graph (OG) tags properly. You can follow these topics here to find the solution:
https://forum.tagdiv.com/topic/photo-incorrect-sharing-google/
https://forum.tagdiv.com/topic/social-share-and-yoast/
Thank you!
There should ideally only be *one* image open graph (OG) tag in your meta data in your <head></head> area when viewing your “page source” for a post on the web. This ONE image tells Google WHICH specific image to use for sharing, as it would do for FB, etc.
Google help on this issue:
https://developers.google.com/+/web/snippet/article-rendering
Hi there,
Till now that problem has not been solved !!
I tried installing theme again, disabled plugins, did the code changes but of no use.
I may be missing some fundamental settings to do.
I saw lots of other people using same theme are able to share full image with descriptions on Google plus.
Can someone from tag div team look into my theme?
I will share the details to access the site.
Note Google+ is rebranding and reorganizing as of this week (Nov. 18), many things are not working right like #tags, and they are pushing folks to move to new layout.
Not much you can do except ensure you have the correct OG tags in your meta data. I’ve been manually submitting my most important items, but even then it’s just headline and image – no description. Even sharing from Google News does not pick up the description — so that should tell you something, their own sharing button doesn’t grab the snippets properly from their own site!
Their own sharing button in Google news ALERTS only picks up image; also again their own tech can’t resolve their own content properly.
-
This reply was modified 10 years by
simchris.
Hi,
It seems that google + does not take OG tag sin consideration and it grabs the first image it stumbles upon.
You did not mention removing the itemprop=”image” from here: http://screencast.com/t/Ua5FRoCtBKg as I suggested above. Did you remove this code and test again? This worked for other users that had the same problem.
Thanks!