Share G+

When we share an article on Google+ with G+ button does not appear the right image associated with this article but an image at random, look here -> https://dl.dropboxusercontent.com/u/22334399/Schermata%202015-04-09%20alle%2020.59.11.png

Make sure you set a featured image and make sure you’re using a plugin like Yoast SEO or similar to ensure proper OG image tags are being added; otherwise Google may try to load the “first image” it sees on page above a certain size.

Are we all, whether that featured image and SEO Yoast. Everything is ok but the image (only on G+) is wrong. It always gives one on all items when you share on G+.

G+ “scrapes” the image sometimes and doesn’t always use the meta data. Nothing you can do about that, except make sure the “featured” image you select at bottom right of the post panel matches the image you want them to grab. No guarantee they will … nothing you have 100% control over, unfortunately.

I tested a link with the Google Validator. Shows me how this picture -> https://dl.dropboxusercontent.com/u/22334399/Schermata%202015-04-12%20alle%2012.47.25.png

Is precisely what i shared on Google+, the photo of the last published article. Why?

Link tested -> http://overpress.it/2015/04/10/intervista-esclusiva-sandro-mazzola-il-nostro-calcio-ha-bisogno-dei-giovani/

Google has problems with scraping and grabbing content sometimes.

As long as the proper image is showing in your meta data (the head of your post page), they normally “should” grab that image. But, sometimes they have bizarre hiccups unrelated to anything you’re doing. I have had this happen a couple of times, and it was usually due to using a “giant” image as a background behind the text without having the same image in the body someplace (I often double the image, once for the giant background top of page, then mid-point at normal full width of post, plus set as featured image).

Not really a bug or anything – just some inconsistencies in how Google “scrapes” the content from your page, and whether they go with your “hinting” or just run off the rails.

The MAIN issue I’ve found is when you top-load the “mega menu” with links and images for your posts, and that can throw off the G+ scraper as they may go for the “first large image” on the page. Which is why I don’t use the mega-menu on posts (among other issues, like speed, etc.). Also, using “large” images in the sidebar, especially those using a “left” sidebar.

Not sure that helps, but that’s been my own experience with G+ weirdness.

I’m still trying to figure out why some posts they grab the whole first paragraph and others they don’t.

And how can we fix this thing? Because it occurs only on Google+.

You can’t …. Google is not being paid to scrape your content, so they can do whatever they want. Same with Facebook.. I have one story from yesterday that FB won’t scrape… just sits there … no good reason for that. Nothing unusual about the page. They just hiccup on that particular item.

Only thing you can do is look at difference between the page they are not scraping properly and one they are, and try to make sure the “wrong” one is setup like the “right” one.

I’m using Newsmag 1.6, so 1.7 might have entirely different problem due to the lazy load problems.

If you come up with some “solution” to making sure Google grabs correct image/paragraph, would love to know. I’ve been trying to sort that out across 4 themes for almost 2 years without any clear “make it always work” solution.

We now have photos working right every time. But like I said, we sometimes trick them on that with ensuring the featured image is in the body and in the meta, and not using mega menu.

Sorry don’t have better answer.

But I have this problem on all articles. I can’t post on Google+ because of wrong images. Use the 1.7 version without lazy.

I would go back to 1.6, personally. 1.7 has a whole slew of issues which is why I reverted my test site back, and left the others at 1.6.

Works. But to me the mega-menu serve.

As I said, the “mega menu” can cause issues with Google as you’re “front loading” images and headlines “ahead” of the actual story headline and photo; and Google+ can sometimes grab that element as “first large photo on page” vs “first image part of post…”

We used to see this with self-hosted ad banners sometimes where the banner would show up as it was larger image than the post image. The OG tags “mostly” helped with that but not always.

So, it’s a trade off … you basically need to “tailor” the page load on how Google’s bot actually scans it, and often the way your mega-menu or other top of page content is setup can “confuse” that. Trial and error.

I face same problem in 1.7
Hope it can be fixed in 1.8

Not really a theme problem. No theme developer can force Google to do anything with your content. They scrape the content based on “how their bot” sees the page. Your OG tag settings impact “hinting” for them, but they don’t always follow that.

So you have to build your page so that it works with Google’s bot; some sites will have this problem depending no how *you* setup your mega menu and post content, and featured image. You need to experiment with the menu layout to see what works with Google’s bot, unfortunately.

I believe the problem is due to the data structure not fit with Google.
As the test tools show, wordpress had created lots of articles link with a very small photo, which not associated with the shared post.
I think Google will read Schema.org microdata first, then OpenGraphic.
But the Schema format was wrong, so Google Plus have wrong image problem, Facebook doesn’t

I will appreciate if anyone know how to fix this problem. Is there any plugin can fix it?
Thanks

http://www.screencast.com/t/AkbmTNdzAzs

Sorry for my bad English.