Skip to main content

Google rel="author" and rel="publisher" Conflicts

How to fix rel="author" tag image that is no longer appearing.

Today I noticed that Google stopped showing my head shot next to the Kingston Web Design search result; having this is crucial as it does increase click through rate for obvious reasons we do not need to go into. My authorship has been working and headshot was appearing in search results since mid April of this year.

After lengthy debugging with Google’s Rich Snippets Testing Tool I was able to determine that rel="publisher" and rel="me" now seem to conflict with each other when on the same page; a verified rel="publisher" link makes the rel="author" link fail verification.

Surprisingly and unexpectedly having a plain link to your Google+ brand page prevents your head shot from appearing - the author profile is being reported as verified yet the profile image is no longer displayed. One must completely remove any links to a Google+ Brand Page for the head shot to funciton.

Until Google starts displaying G+ brand page profile images or fixes the above issues I have pulled Danols Web Engineering G+ link from the home.

Is Google getting ready to extend the rel="publisher" functionlaity?

My spider senses are tingling and I am going to say a definite "yes". It is only logical that rel=publisher and Google+ brand pages would function similar to author pages. The positive effect of a head shot next to a search result on the click through rate is significant and there are over 1M Google+ brand pages waiting to benefit from it.

Another peculiar thing that I have noticed upon that supports the above is that if one crates a rel="publisher" that links to a personal G+ page it acts as a rel="author", that is the Rich Snippet Testing tool shows the author’s head shot; it seems rel="publisher" has precedence over rel="author".

I do look forward to Google displaying Danols Web Engineering logo rather then my own face, and I hope it will be sooner than later.

Comments

  1. Daniel SokolowskiJuly 12, 2012 at 8:52 AM

    After 7+ days of waiting the author head shot was not appearing. I then reactivated the publisher code and verified the authorship tag using an email at my domain (recall having publisher disabled "rel=me" or "rel=author" from working in the rich snippet tool).

    Within 3 days after doing that my nugget started appearing. So if you are having issues verifying your authorship try the email at the domain in question method.

    Interestingly I think there is something funky going on with the tool as re-checking right after email verification method would still report that the authorship was not verified.

    ReplyDelete

Post a Comment

Popular posts from this blog

Duplicate value found: duplicates value on record with id: <unknown>.

System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>. The above error is triggered in the database layer and caused by a trigger or workflow outside of your main code of block that is bubbling this exception. This is rather difficult to track down especially if you are unfamiliar with the code, I am sharing my procedure in the hopes this saves you time - if you find this helpful drop me a line or follow me on twitter @danielsokolows . This error is caused by unique field constraint on the object, so the first step is to examine the object and locate the API names of all unique fieds. You can do this through SF direclty 'Setup < Customize &lt <object being inserted> &lt Fields' or by downloading the `src/objects` metadata information and searching for <unique> ; I preffer the latter and actually download ALL matadata i...
3 comments
Read more

Softeher 'Error occurred. (Error code: 2)' sollution

Protocol error occurred. Error was returned from the destination server. The Softether server by default to run on port 443 , if you server also hosts normal https then 443 is already taken and so Softether can't bind to it. When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server. By default Softether also listens on 992 , 1194 , and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows .
6 comments
Read more

How to child proof a fireplace

DIY - Do it yourself fireplace child guard Our wonderful 8.5 month old Sofia has become a crawling race car with an untamed thirst for exploration. And so with the cold nights approaching we needed to child proof the fireplace. This however proved to be more difficult than would reasonably expect, I've checked the local Toys "R" Us, Walmart, and even a Canadian Tire with no success for a ready to use product. Internet search was more fruitful and returned a few online stores one could order from, however in all honestly they didn't look too sturdy to me. So I build my own relatively quickly and inexpensively. Materials needed is a privacy plastic lattice - the smallest hole pattern - a few screws and anchors; tools needed are a drill, and a handsaw if you don't have the lattice cut at the store - that’s it. The construction consits of screwing the lattice into the wall and the final product is easiest explained through following pictures. ...
11 comments
Read more