Blog

Google Authorship and rel=author is no more

August 29, 2014 By Dan Thornton

One of the main benefits of signing up for a Google+ profile as a writer, blogger and author has been the Google Authorship program, which began back in 2011 with the launch of Google’s own social network. And in a Google+ post, Google’s John Mueller has confirmed that not only will the search results no longer show any Authorship results, but data will no longer be tracked from the rel=author markup.

Since the start of 2014, Authorship has carried slightly less benefits for those who implemented it correctly with first a reduction in the amount of author photos shown per query, and then a complete removal of author photos, leaving only bylines. Now that’s gone as well.

Should you remove Authorship markup?

Although the markup is no longer being utilised for authorship, Mueller has confirmed that it will be treated just like any other markup (e.g. Schema), and won’t cause any problems.

Part of the reason given for Google Authorship ending has been the low take-up and correct implementation of the process. Given that Executive Chairman Eric Schmidt has stated the importance of real identity and information tied to online profiles, it’s unlikely that Google won’t continue to try and complete the link between people and their work in a less public way in the future.

What about Publisher markup?

Although the links between an individual and their articles won’t be correlated and highlighted any more, there’s been no explicit mention of Publisher markup between a brand and their Google+ page. It’s always been slightly easier to implement, and obviously only has to be done once for potentially hundreds of authors working for a brand, so the future is potentially brighter for Publishers than Authors.

Why was it ended?

The reasons given for Authorship ending at Google are:

Low numbers implementing it, and even fewer implementing it correctly.
Low value to searchers. Mueller stated ‘Unfortunately, we’ve also observed that this information isn’t as useful to our users as we’d hoped, and can even distract from those results’ – partly this may be down to the need to display properly on mobile devices, and there have been conspiracy theories about the impact on paid search advertising, as well as the possibility Authorship didn’t offer an increase in click through rates after the initial novelty had worn off.

What now?

So for the time being, we’d recommend that if you have Authorship in place, you don’t rush to remove it. And you continue to link your Google+ page with your website.

Mueller also mentioned an expansion of support for structured markup such as Scheme.org, which we recommend all clients look at to see how it can be implemented.

And Google+ posts and pages will still appear in searches where relevant, so there is still some reason to post on the network, even if it’s lost one compelling reason for a lot of journalists, authors and bloggers.

Proud Sponsors of DPiP May 2014 event

May 8, 2014 By Dan Thornton

I’m pleased to say that in addition to personally being one of the organisers of local digital gathering ‘Digital People in Peterborough’, TheWayoftheWeb Ltd is also sponsoring the May 2014 event.

It’s a great way to informally meet up with a diverse range of people who share an interest in digital technology, whether it’s a personal interest, a career or their business.

There’s more details on the DPiP website. And although we’re still a small company, it’s great to be able to start supporting initiatives and getting more involved in our local community.

If you’re in Cambridgeshire, we’d definitely recommend checking it out

Security Update for Jetpack WordPress Plugin

April 11, 2014 By Dan Thornton

Joining the news of the Heartbleed vulnerability that affects much of the internet, and a security update for WordPress itself, now comes the news that there is a critical security update for the Jetpack WordPress plugin.

Jetpack 2.9.3 contains a fix for a bug which allows an attacker to bypass access controls and publish posts, which could be combined with other attacks to escalate access. It’s existed since the release of Jetpack 1.9 in October 2012, and as yet there is no evidence of it being used in the wild.

However, now it has been made public, you need to make sure your site is updated asap – the team behind Jetpack have been working with hosting and network providers to reduce the problem, and have made updated releases for all 11 vulnerable versions of Jetpack from 1.94 through to 2.9.3.

So if you’re running Jetpack on one or more of your sites, make sure you’re either updating it now through your WordPress dashboard, or visit the Jetpack site to manually grab the updated releases and install the appropriate one for your website.

WordPress 3.8.2 now available to download and install

April 8, 2014 By Dan Thornton

The latest version of WordPress is now available to download and install. It’s an important security release which solves some important security issues, along with fixing a number of bugs.

The security list is:

Potential authentication cookie forgery. CVE-2014-0166.
Privilege escalation: prevent contributors from publishing posts. CVE-2014-0165.
(Hardening) Pass along additional information when processing pingbacks to help hosts identify potentially abusive requests.
(Hardening) Fix a low-impact SQL injection by trusted users.
(Hardening) Prevent possible cross-domain scripting through Plupload, the third-party library WordPress uses for uploading files.

There’s more information available in the WordPress Codex. If you’re already allowing automatic updates, the release will apparently install throughout the next 12 hours, or you can update manually now. As always, before any significant WordPress or plugin update, it’s always best to back up your site.