This post is mainly about what happens when you implement rel="author" twice on a webpage and the confusion and potential mistrust it carries in Google’s eyes. However it also covers the following areas:
- The best and easiest way to implement rel="author" on a WordPress blog,
- How to handle rel="author" if your blog allows guest posts (whether it’s on WordPress, another blogging platform or a self-hosted blog).
- Discrepancies between what the Rich Snippets Preview Tool shows and what actually shows up in Google’s SERPs (search engine result pages).
What is rel="author"?
rel="author" is a type of rich snippet whereby your Google+ profile picture and links to your profile appear in Google’s search results. While you may not know it by name, if you’ve been using Google at all in the past year or so (which I’m guessing is extremely likely!) then you’re bound to recognise this:
Rather than simply showing a standard search result, the following is added:
- A Google+ profile pic, which studies have shown can improve CTR (click-through rate). One of my favourite studies talks about how optimising the picture (of all things!) can further increase CTR.
- A “by [name]” link, which links to the person’s Google+ profile.
- The number of G+ circles that the person is in.
Although it’s not shown above, I’ve also seen some instances where it says “More by [name]” in place of #3.
In addition to improving CTR, Eric Schmidt recently revealed that it could even lead to higher rankings, which is something that many had previously speculated and that Jeff Sauer has recently investigated.
AJ Kohn has written an epic guide on how to implement rel="author", so I don’t want to cover old ground. What I want to talk about is what happened when I started introducing guest posts on SEOno (since January 2013) on a blog that had previously featured site-wide implementation of rel="author", my potential ‘screw up’ (by having two different forms of verification – of two different authors – on one page), what I did to fix it and the unusual aftermath it has caused since then.
rel="author" implementation on SEOno before guest blogging
Firstly, a brief bit of back-story before I delve into the specifics…
I can’t remember when exactly I first implemented rel="author" on SEOno, but I think it was about a year ago. It’s definitely been since at least August 2012, as I wrote a post back then that included a screenshot containing authorship (similar to the one shown above). Suffice to say that it’s been implemented for a while.
Back then, I believe the main (and possibly only) way to implement rel="author" on a site was to add a line of HTML code to each relevant page’s header. For me, being the sole author on a WordPress blog, it was easy enough to implement, even with my limited HTML knowledge – I simply added the line of code to my WordPress theme’s header.php file like so…
…which looked like this in the actual source code:
While this method of implementation still works, Google doesn’t seem to endorse it any longer – if you look at their rel="author" guidelines, they no longer mention it as a way to implement it.
Enter: the guest blogger
But I had a problem… In my guest blogging efforts, I’d previously been victim to having someone else’s rel="author" profile attributed to a post I’d written, which is a bit annoying. I didn’t want this to happen to Emma, Mike (my second guest blogger) or any other guest bloggers in the future. So I had to find a way around my site-wide rel="author" implementation so that Emma’s profile – not mine – would appear for her post.
What happened next had an odd effect on the SERPs (search engine result pages) for SEOno, which I’m still seeing now, weeks later…
I wondered if Google would be smart enough to know which profile to show alongside a result if you were to provide an additional rel="author" link to a post that had already had site-wide implementation. In other words, I kept the site-wide implementation intact (for my profile) while also adding ‘?rel="author"’ to the end of the link to Emma’s G+ profile, which appeared in the intro blurb that I’d written for her guest post.
My two theories were that:
- Google would think “ok, so you have site-wide implementation of Steve Morgan, but one page also has implementation of Emma Barnes, so this post must in fact be by Emma, not Steve” – therefore attributing Emma’s profile to it.
- Alternatively, as my implementation was in the page’s header and Emma’s was within a link in the content, I wondered if Google would see my authorship first and assume that I’m the author that way – therefore attributing my profile to it.
The end result was… different.
While the rich snippet seemed to be attributed to me (which I could see using the Structured Data Testing Tool, aka the Rich Snippets Preview Tool)…
(Notice how both profiles are picked up: my G+ profile number ends “7076” while Emma’s ends “6044”.)
…In actuality, it was showing neither of us in the real-life SERPs:
I thought this was odd, especially the discrepancy between the fact that the preview tool and the actual SERP differs. It’s almost as if the double implementation has confused Google – even though it knows that at least one of them can be attributed to the post, because it’s not sure, it’s deciding to show neither.
I guess this was to be expected. Only one can be shown alongside a result, so if you have two or more instances of rel="author" on a page, instead of showing one or the other, Google will decide to show neither/none of them. To an extent, it reminds me of keyword cannibalisation, which can cause Google to show neither page if two pages on a site are competing for the same keyword (e.g. a blog post and a blog’s tag page). I’d call it ‘author cannibalisation,’ but that sounds as though it involves real people, so… no.
Another factor that I think did more harm than good was my roundabout implementation of Emma’s user/author profile on the blog itself. Emma was happy for me to upload the post on her behalf – and being the control freak that I am, I was happy with that! However I didn’t want to create an entirely new user profile for her if it could be helped. I found an alternative using Custom Fields (here’s a guide) – however while it showed “…by Emma” on the post, her name actually linked to my author section. I have a feeling that that might’ve also played a part in the confusion in Google’s eyes.
On 6th February – about a week after Emma’s post was published – I decided to fix things properly…
Firstly, I removed the Custom Field band-aid I’d placed on Emma’s post. Instead, I created a Guest Posts user, attributing Emma’s post to that instead.
Secondly, I removed the site-wide header implementation and realised that the excellent Yoast SEO plugin – which I’d been using for a while previously – now offers rel="author" implementation, if you add G+ info to a user’s profile and tick a few boxes. Here’s what I did:
- For my user (steviephil), I added my G+ link to my user profile and asked Yoast SEO to assign it to all my posts, main pages (About and Contact) and the homepage. Boom. Done.
- However, for Guest Posts, I didn’t do this… Instead, I would manually include a G+ link (with ‘?rel="author"’ added) for each individual guest post.*
* If I had implemented individual users for Emma and Mike (rather than a Guest Post author category) then I could simply repeated the first step: adding their G+ profile links to each of their user profiles and using Yoast SEO to implement it. Something to think about if that’s the approach you’re thinking of taking instead.
Anyway, the Rich Snippets Preview Tool seemed to like this:
Hooray! As I said to Emma:
— Steve Morgan (@steviephil) February 6, 2013
But… what of the SERPs?
It’s now 17th February when I type this, 11 days after my fix. While 11 days may not be enough time to fully assess what has happened, it’s still a considerate amount of time since I implemented the fix…
Not only does Emma’s post still not show her (or any) authorship…
…But my whole site has been negatively affected. It used to be the case that all of my pages would show authorship, but now…
…Including old individual posts (which used to)…
However, that said, not all posts/pages have been negatively affected, with some still showing authorship…
…And Mike’s post (my second guest blogger) is displaying perfectly – although bear in mind that I published his post after I’d implemented the fix, with his authorship attributed to the post from the get-go…
This is bearing in mind that all pages/posts should now have rel="author" implemented 100% correctly, with the Rich Snippets Preview Tool showing the right authors attributed to the right content in every applicable instance. It might be the case that Google hasn’t re-crawled the site in its entirety yet and therefore that the full recovery is yet to come and will happen in due course.
Either way, I only had double implementation on one page: Emma’s post. So it seems odd to me that most pages on my site were negatively affected – why not just Emma’s post? That said, it could be my Custom Field implementation (referred to above) that caused a problem here.
Whatever the case, it’s almost as if Google’s having trouble trusting SEOno after the incorrect implementation and therefore would rather show nothing than risk showing something wrong, e.g. the wrong profile. A different type of penalty…?
Do you know what the oddest thing is though? My Author Stats in Google Webmaster Tools for SEOno. Impressions (the blue line) have mostly been higher since 28th January (the date Emma’s posted was published; marked by the vertical red line in the screenshot below), regardless of the fact that that’s when the incorrect rel="author" implementation kicked in. Whether it’s truly the case or a bug in Google Webmaster Tools data (which is known to be unreliable in other areas), it’s very intriguing indeed…
Conclusion / TL;DR
The moral of the story is to be very, very careful when implementing rel="author". Don’t piss off the Google Gods by having more than one author attributed to a page (like I did), as it may negatively impact the authorship of your whole site, not just the relevant/affected pages.
A few other observations, facts and recommendations:
- Sometimes there are discrepancies between what the Rich Snippets Preview Tool shows and what Google will actually show in its SERPs. It’s almost as if the preview suggests that Google acknowledges the markup, but it will have its final say when it comes to showing the results in the SERPs. Use it as a guide – and certainly not as a guarantee.
- If you have a WordPress blog, get the Yoast SEO plugin and follow its steps for rel="author" implementation. Even if you are the only author on your blog, it’s pretty much the same level of effort as implementing the code site-wide in your site’s header, but it also future-proofs things if you change your mind and decide to introduce guest bloggers in the future (like I did).
- Regardless of whether you have WordPress or another blog, use the ‘?rel="author"’ method of implementation for guest posts (which is what Google recommends anyway). This can be done whether you have a Guest Posts author category (like I do) or individual author categories for each of your guest bloggers.
- Watch out for the Author Stats in Google Webmaster Tools. The impressions data does not seem to marry up with what I’ve seen in the SERPs, with impressions going up, even though my face is showing less. It could be the case that impressions have gone up – or is it a bug…?
What are your experiences? Have you had similar problems or had a different experience entirely? If you’ve been in a similar position or seen anything to the contrary then I’d love to get your thoughts in the comments below.
Update – 19th February: Two days after the above screenshots, I discovered that the homepage and the Tweetbot post are now showing my authorship in the SERPs. Maybe it was just a matter of time? However, Emma’s post is still showing neither of us…
[Question image credit: Shannon Hauser]