It’s been nearly 3½ years since Google first announced their usage of RankBrain (October 26th 2015, but it had started being rolled out early 2015, in multiple languages).

In that time, there’s been little in the way of details coming from G about what it is or how it works.

The result is that numerous SEOs have stepped up to fill that void with their own speculations and opinions, and in doing that, have caused all sorts of confusion.

This is my attempt to correct and clean up some of that mess.

(There is a TL:DR at the bottom if you want to skip the verbiage :D)

What does RankBrain do?

Though there isn’t much publicly available, what we do have is fairly specific:

“If RankBrain sees a word or phrase it isn’t familiar with, the machine can make a guess as to what words or phrases might have a similar meaning and filter the result accordingly, making it more effective at handling never-before-seen search queries.”

Google receives a fair percentage of queries per day that it hasn’t seen before: 15% at last check.

These may include misspellings and typos, elisions/omissions, unusual phrasing/syntactic structures, the wrong word(s) being used, negations (“not x”), things that have only just happened etc. etc. etc.

RB receives these weird, wonderful, and new searches, and attempts to identify existing searches and results that are probably suitable for the searcher’s query.

How does RankBrain work?

Again, we aren’t exactly given a guided tour by G on this, but there are a few bits and pieces.

“… RankBrain uses artificial intelligence to embed vast amounts of written language into mathematical entities — called vectors — that the computer can understand. If RankBrain sees a word or phrase it isn’t familiar with, the machine can make a guess as to what words or phrases might have a similar meaning and filter the result accordingly, making it more effective at handling never-before-seen search queries. …”

So, rather than looking at words and attempting to parse them and understand the semantics (traditional Natural Language Processing [NLP]), it converts them into numbers and plots them on a chart (with multiple dimensions, not just X and Y).

Items near each other possess some form of relationship. The type of relationship will be reflected by each term’s position and distance from its neighbors.

If that sounds vaguely familiar, that’s because it sounds very similar to Word2Vector.

So when G receives a query it doesn’t quite recognize, it can find semantically related pieces, and look at the results.

But, what if it’s wrong?

Well, that’s where Gary Illyes’s answer to a question on his recent Reddit AMA may come in:

“…

RankBrain is a PR-sexy machine learning ranking component that uses historical search data to predict what would a user most likely click on for a previously unseen query. It is a really cool piece of engineering that saved our butts countless times whenever traditional algos were like, e.g. “oh look a “not” in the query string! let’s ignore the hell out of it!”, but it’s generally just relying on (sometimes) months old data about what happened on the results page itself, not on the landing page. Dwell time, CTR, … those are generally made up crap. Search is much more simple than people think.

Example of what RankBrain may be doing

How about we walk through a simple demo of the type of thing that RB does?

Query: How Nemee 2020

Google receives that query, and has nothing that appears to be a match and little that seems above a weak relevance.

So, it needs to do some work.

It can identify the type of query by the use of “how”.

It can identify a time factor by “2020”.

Or it can identify several potentials for “nemee”, including “meme”.

The query is vectorized, and the nearest neighbors for those vectors are found.

Included in the results are vectors that represent:

“How to”

“how do I”

“how do people”

“create a meme”

“pronounce meme”

“say meme”

So we have two probable query types:

A question of how to say …

A question of how to make …

But we have a 3rd factor, the “2020”. When we look at the result groups, there are barely any pre-existing queries or results that include time with pronunciation, where are there are a moderate number of “how to” queries and results that do.

RB decides that the most likely results that match this query are those from the “how to make” queries, and so the results you would receive would match;

“how to make a meme 2020”.

Does RankBrain use user experience signals?

No.

And that’s what this post is about — clearing up all the baloney some people have been pushing about “Dwell Time” and “Click Through Rate” and “Bounces” etc.

RankBrain doesn’t use UX signals from your pages.

For quick confirmation;

“… Dwell time, CTR, … those are generally made up crap …”

That’s from Gary’s AMA response I quoted above.

But, you can use a little common sense yourself at this point.

Ask yourself the following question:

Why would a system that is built to try to encapsulate relationships between text-strings be looking at how long someone spent on a page, or how fast they left?

When you stop and look at it that way, and consider the example above, you can see how site based UX signals have no relevance for RankBrain.

The only such metric we know they may use are SERP-based clicks to identify what type of results appeared relevant to that type of query.

Can you optimize for RankBrain?

Yes.

Google has even told us that we can 😀

“…Optimizing for RankBrain is actually super easy, and it is something we’ve probably been saying for fifteen years now, is – and the recommendation is – to write in natural language. Try to write content that sounds human. If you try to write like a machine then RankBrain will just get confused and probably just pushes you back. But if you have a content site, try to read out some of your articles or whatever you wrote, and ask people whether it sounds natural. If it sounds conversational, if it sounds like natural language that we would use in your day to day life, then sure, you are optimized for RankBrain. If it doesn’t, then you are “un-optimize…”

But, if you roll back a bit, G have actually spelled out how to optimize for RankBrain!

“… If RankBrain sees a word or phrase it isn’t familiar with …”

“… making it more effective at handling never-before-seen search queries …”

“… predict what would a user most likely click on for a previously unseen query …”

All you have to do is fly in the face of standard SEO practices, and aim for the exact opposite of what you would normally go for — high search volume.

Instead, look at all the queries, and then generate variants that aren’t in the lists.

I know, that’s even lamer!

(But, be honest, you did want to know :D)

But there is more — particularly for those that deal with time-relevant content; events and occurrences.

As these are “new”, the queries likely will be too (at least partially). To gain an advantage here, you might be able to look at similar searches yourself, and look at the patterns they possess. Once you have some samples and associated search volume data, you can pick and choose the ones you feel are most advantageous and relevant, and then weave them into your content.

Disclosure

This site is owned and operated by Tyconia International, Inc. We are a professional review site that receives compensation from the companies whose products we review. We have reviewed the web hosting sites ranked here.

We are independently owned and the opinions expressed here are our own and of our visitors.