How Google’s new keyboard for iPhone is changing SEO

The launch of Gboard — Google’s new keyboard for iOS is flipping how SEO content is ranked on its head !!

For those using GBoard, when comparing search results versus regular mobile search, despite being largely based around the same algorithms, users may be surprised to note some differences.

Rajan Patel, a principal engineer at Google explains:

“It’s really early, so we’re kind of experimenting with what the ranking is for the right use case,” Patel said.

Patel said that Gboard may give preference to moving direct answers higher up the results. For example, a Knowledge Graph answer about a company might come midway in mobile results but move to the first listing with Gboard.

Patel also went on record saying News listings are likely to be shown higher in Gboard listings. He explains this is because keyboard-based searchers “may be doing some type of sharing activity”. In such cases, Google’s making an assumption that recent information such as news stories may be more useful. This is not new or surprising and has been known for a long time the “in the news” block on Google Search has been treated differently across devices.

Lets take a look at some of the differences. In this search for “Amazon” we can see some huge differences in the results.


All those crossing arrows make it clear that Google hasn’t just presented its mobile search results in a horizontal format. There are a number of ranking changes, as well as various blocks of listings not shown at all.

Here’s another example, one for “weather,” that shows how news listings get elevated within Gboard


As you can see, both give you the local weather first, but Gboard then moves news stories higher than web listings. In addition, the news stories it shows aren’t the same as with the mobile search results.

So how about local results? For the two local searches we did, results were largely unchanged. Special local results at the top of the mobile listings, which have star ratings and options to call businesses or get directions, also got the same treatment in Gboard

Gboard is fairly unique for Google search products in that it has no long-term memory of who someone is, which in turn reduces the personalisation of search results — another reason why mobile search results and Gboard results might differ.

Someone who is logged into Google builds up a long-term history of things they’ve searched for (unless they opt out), which is used to help customise the results received. This history is associated with the person’s account, so they’re identified even if they use different devices, as long as they’re logged in on those devices.

Gboard has no such memory. Any searches done within Gboard are not recorded to your account, even if you’re logged into Google in some other way, such as within your browser. This means Gboard also cannot tap into any search history you’ve accumulated, in order to personalise your results.

Vulnerability in Yoast SEO

Less than 3 days after WordPress core pushed a security update fixing some vulnerabilities comes another security release this time for Yoast SEO plugin. We use this plugin on all of our SEO customers websites and it is immensely popular among website owners with over 1 million active installs.

On Tuesday Panagiotis Vagenas from WordFence Security discovered a security hole in the plugin that would allow any user level within WordPress to access the import and export features of the plugin. In effect this could allow a commenter on your site to download your Yoast SEO settings, change a few things and upload new ones.

This security hole is not dangerous to your website however it could be used to cause harm to your search rankings and undo months of SEO work on your website.

WordPress 4.5.2 patches security vulnerabilities

Over the weekend the WordPress COE team released version 4.5.2 of the popular content management system fixing 2 security vulnerabilities found in third party libraries used within WordPress.

The first is a Same-Origin Method Execution in Plupload, the third party library WordPress uses to handle file uploads. The second is a reflected cross-site-scripting vulnerability in MediaElement.js, the third-party library used for media players.

WordPress’s new automatic update feature will apply this update to your site over the next week as the release is marked medium risk but if you can’t wait you can manually apply the update from within WordPress under Dashboard > Updates.