October 27, 2013 at 1:05 pm #69285
All of a sudden, sharing my blog posts on Google+ shows my author name as the link title and not the post title. This is only for Google+, not other platforms. I do use the Yoast SEO plugin but I’m not aware of this ever happening before and I’ve changed no settings. I don’t know if this is a Genesis issue or not. Here is my latest link below.
Any ideas? Thank you.http://bigrockinvestments.com/help-a-homeowner-friend/October 27, 2013 at 4:04 pm #69307
I just went to your Google+, the Link showing your name is pointing to a LISTING and not a POST. There isn’t any POST INFO with your Author name assigned there – at least it doesn’t look that way.October 27, 2013 at 8:02 pm #69366
Hi – thanks for helping me with this. Which link specifically are you referring to and on which page? I looked at the source code of the blog post itself and found: <meta
property=”og:title” content=”Can You Help a Homeowner Friend in Need?”/>
Maybe I’m looking at something that’s not related…?October 27, 2013 at 8:05 pm #69367
On your Google Plus – the second one down is labeled, “Back on market – HOT neighborhood! #honolulu #realestate #hawaii” and has your name. When I click it – it goes to a Listing – http://bigrockinvestments.com/listings/large-single-family-house-moanalua-gardens/.October 27, 2013 at 8:12 pm #69368
Yes, that’s a prime example of the problem. Any time I post a link, whether a post or the homepage, from that website onto Google Plus, the title shown is my author name and not the post time. I don’t know why it’s doing this. I don’t have this problem on Facebook, Twitter or LinkedIn, nor do I have this problem posting links from other websites onto Google+.
There’s something wrong with my website at the moment.October 29, 2013 at 7:13 pm #69810
I meant not the “post TITLE” in the above. It shows my name as the title, not the page/post title as it should be. It tried deactivating the Yoast WordPress SEO plugin, deleting both the site cache and CDN pull zone and trying again, but no change.October 30, 2013 at 1:44 am #69856
Perhaps google is doing a little too much google foo ?
Sometimes, I have to re-save things in Yoast SEO; for example after WP updates or even some plugin updates I notice my sitemaps will not work. So I just re-save Yoast SEO options.
Also, very rarely, I’ve seen clearing open graph cache for sites fix things, such as for facebook http://facebookhelpdisk.blogspot.com.au/2013/07/facebook-open-graph-not-clearing-cache.html
Note sure how google implements a cache or if they do however.
October 30, 2013 at 2:02 pm #69972
Thanks – I’ve opened up a support ticket with stackoverflow. Looks like I’m not the only one this has happened to. The Yoast article is about this happening in the SERPs. I’m ok in the SERPs (for now) – it’s just sharing on G+.
Some things I’ve ready seem to point to schema markup. I was looking into this but I don’t think I actually implemented any schema markup on the site. BUT – when I load the page source of my homepage, I do see one section about schema and points to my user/author profile. I don’t recall how it would have gotten there.
Would this cause it to happen and, if so, what exactly would I do about it?
- This reply was modified 2 years ago by mborger.
November 1, 2013 at 10:03 pm #70443
- This reply was modified 2 years ago by mborger.
Any other info? I posted on another site and got this feedback:
He recommends further work to (seemingly) undo some schema.org markup? How would the schema line even get there – is it part of AgentPress??
Sounds like this might be a band-aid approach for another option that might be there. But — I don’t really understand schema.org implementation enough to really assess the viability of this solution.
Thoughts?November 2, 2013 at 12:32 am #70448
Both Yoast and Genesis Framework / Child themes (depending on version) implement schema markup, in fact that’s one of their pluses.
You can see what structured data Google finds via the testing tool http://www.google.com/webmasters/tools/richsnippets?q=http%3A%2F%2Fbigrockinvestments.com%2Fhelp-a-homeowner-friend%2F
What version of the Framework, Agent Press and Yoast are you using? Also, are you using any other significant plugins?
November 2, 2013 at 2:16 am #70450
I don’t deny there’s value in schema, I just don’t know how it got in my site the way it is. I also manage http://funthingsapp.com and that doesn’t have any schema in the page source. But – both sites are running the most recent versions of Genesis, AgentPress and Yoast SEO.
On bigrockinvestments.com , I just disabled all the plugins, deleted my browser cache as well as the CDN pull zone. The page source still showed the schema markup line. I just don’t know what’s putting it there — and what I can do about it, either deleting it or altering it in someway.November 2, 2013 at 2:32 am #70451
Are you implementing page caching or other caching tools? I still see all of the Yoast OG markup in your source.
November 2, 2013 at 3:12 am #70456
I have W3TC on both sites. Yes, the Yoast markup is there – I turned my plugins back on after testing the site without any plugins. W3TC was also disabled when I tested it, so it does not appear to be the result of any caching or plugins.November 2, 2013 at 3:16 am #70458
Here are some links worth taking a look at for the Schema. I don’t see where you can remove it, but you can customize, edit or use a plugin. The new schema came with 2.0. If you can’t get it to work the way you want, you could always revert back to 1.9.2 as a last resort.November 2, 2013 at 4:10 am #70464
Thank you – I will try to make the plugin work. However, I’m still mentally stuck at the place where the funthingsapp.com site does not show the markup yet it runs the same exact parent/child theme versions and Yoast SEO plugin. It just seems like that one line of schema markup has to be coming from somewhere….
Another thing is that IF this is by default, then I can’t help but consider it a bug that needs fixing. Sharing posts on Google+ should retain the post name for sharing, not pull the author name as the title.
You must be logged in to reply to this topic.