- Joined
- Jun 28, 2012
- Messages
- 13,313
- Reaction score
- 4,148
Pigeon Analysis - New Insights about this Crazy Google Local Algo & the Constant Flux
Alternate title: "What the Flux? Why the Google Pigeon Algo Keeps Changing and is So Tough to Figure Out"
Google "Pigeon" flew the coup on 7/24, but this bird has still not landed! If you've been following the "Pigeon" news or if you do ranking checking at all in the US, you know this crazy Pigeon algo is still not settled in and changes every time you turn around. Major flux continues and I'll share some reasons why.
As I was working on the new 2014 Local Search Ranking Factors for David Mihm, which is due to be published in September, it occurred to me Pigeon is one month old. The LSRF timing is really unfortunate, since the algo hasn't settled down enough for any of the experts working on the LSRF to even begin to figure it out.
We've been getting reports at the Google forum from users saying their ranking is rotating back and forth every day. OR they tell us they used to rank B, but dropped out of the pack. We check and they are still B.
I have a new discovery that helps make sense of the flux and could help you, if you are diagnosing rank drops during this uncertain time.
I've had a Pigeon theory for awhile now. I've floated bits and pieces out there, but wanted to try to lay it all out in one place. And now I have PROOF my theory was correct!
After doing lots of Pigeon analysis, I've been convinced for awhile now that Google is testing 2 -3 versions of Pigeon on different datacenters and is rotating results. (Likely for AB testing.)
I say this in part, because all the Google datacenter IPs I can find like THIS ONE (I've tested tons more) are ALL still showing the old pre-Pigeon results. (Check it out at that link and compare to the Pre-Pigeon shot below. Even though many of the results are the same - David H. Lee and Matt Brown-Ruegg only ranked PRE-Pigeon, never POST-Pigeon.)
Classic Google maps is showing the old ranking order too, because it’s still using an old datacenter so that's why results don't match Google search. (David H. Lee and Matt Brown-Ruegg still rank in classic, same order as the 6/22 Pre-Pigeon shot below.)
Plus many of the pack tracking tools I use are still showing the old algo ranking order as well. That's because they are all using older datacenter or maybe I should say non Pigeon DCs.
So anyway, rotating different versions of the new algo on a couple specific new datacenters would account for the crazy constant flux we are seeing. Depends on which datacenter you hit. I repeat - the Pigeon has not landed!
Well yesterday I discovered proof that my theory is correct and I want to show you what I discovered via screenshots.
I've been sharing rank tracking screenshots for "Seattle Chiropractor" since Pigeon hit.
See: Tracking Google Local Pigeon Flux Over Time
Yesterday when the results changed radically again, I dug deeper and will show you what's up. Skipping a bunch of in-between ranking screenshots which you can see at the link above and only showing you the Pre-Pigeon results and 8/23 and 8/26 results.
8/23 - just showing the one to contrast and show the difference post-Pigeon, although as you can see in the Pigeon Flux link above, it's changed daily.
OK now this is where it gets interesting...
Yesterday, like I said, I noticed the pack changed pretty drastically again.
Some significant shifts. (I note them all in the Ranking Flux Over Time post.)
I checked Chrome - results were totally different - normally FF & Chrome match pretty well.
So went back to Firefox in a new window, searched again to compare browser results and saw this.
So I had 2 different results, both using FF. (And double checked, both with location set to Seattle.)
So next I did what any good geek would do and hit hard refresh. And sure enough - not every time, but quite often, I could get the results to rotate between the 2 datacenters/algos.
AND that 2nd algo is the one that Chrome was showing too.
So that crazy bird is flipping back and forth testing! She's definitely rotating datacenters!
Don't like what you are seeing? Hit Ctrl F5, do a hard refresh and check the other version.
Note: does not always work. Sometimes you have do it several times before it will switch over. And I think if the results don't change, then maybe that particular pack does not have the factors that the different versions of this algo affects. I tested a bunch of different results. Some changed and some did not.
No way to know which datacenter and which version of the algo is going to win out. But it's interesting to see and compare the different versions to try to get a preview of what may be coming!
GOOGLE MAPS MISMATCH
I mentioned above that Classic Google maps is showing the old ranking order too, because it’s using a different datacenter than Google search.
FYI new maps WAS on the old datacenter but was recently upgraded. So now new maps correlates with the new Pigeon ranking order, but Classsic does not. Which means Classic and new maps ranking order does not match, which is causing lots of problems here and with users at the Google forum.
SEE NEXT POST FOR DETAIL ABOUT MAP RANKING ISSUES & INCONSISTENCIES.
(Splitting to new post, so this post does not get too long.)
Now you know when you are troubleshooting, doing rank tracking OR trying to reverse engineer this crazy Pigeon algo - it totally depends which browser you are using and which version of maps you are checking. Because it depends on which datacenter you hit.
Many tracking tools are still hitting the old datacenter and showing the old results.
Non US Google search like: Google Germany is on the old datacenter too. (So you can use that or Classic to see/compare the old results.)
So anyway everything is just all jumbled up and it does not make a good user experience for anyone. And it makes it super hard for people like me to try to figure this algo out.
IN SUMMARY
.:. Google Search - rotating datacenters and ranking order
.:. New Google maps - same as above so normally mirrors search results
.:. Classic Maps - old pre-Pigeon results
.:. Many tracking programs - old pre-Pigeon results
.:. Checking US results from - google.ca or .de or other countries - old pre-Pigeon results
So if you don't like the results you see, or if you are seeing something different than your client sees, above may be the reason. Just blink or switch browsers or switch maps or hit hard refresh and you may see something totally different.
Miriam Ellis from Moz asked me to weigh in on an article she's doing there. She asks top experts what their best Pigeon advice is. Here's an excerpt of what I told her...
My advice? The Pigeon has flown the coup, but has not landed yet! There is too much flux for any of us to make sense of yet. All I can say is that hopefully by the time this bird is tested and/or trained, it will settle into something equitable for users and business owners alike.
But no solid advice can be given now, except to keep working on best practice strategies, which will always help in the end.
Tons more info about Pigeon at our #Pigeon Hashtag.
What do you think about all this???
Note: This is all theory based on my limited testing, so feel free to shoot holes. That's how we all learn!
(Next post covers map inconsistencies in more detail)
<meta property="og:type" content="article"><meta property="og:title" content=""><meta property="og:description" content="Google Pigeon flew the coup on 7/24, but this bird has still not landed! Major flux continues and I'll share some reasons why.">
<meta property="og:image" content="">
Alternate title: "What the Flux? Why the Google Pigeon Algo Keeps Changing and is So Tough to Figure Out"
Will the REAL 'Pigeon' please come forward???
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/pigeonRealDC.jpg" alt="pigeonRealDC" width="65%" />
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/pigeonRealDC.jpg" alt="pigeonRealDC" width="65%" />
Google "Pigeon" flew the coup on 7/24, but this bird has still not landed! If you've been following the "Pigeon" news or if you do ranking checking at all in the US, you know this crazy Pigeon algo is still not settled in and changes every time you turn around. Major flux continues and I'll share some reasons why.
As I was working on the new 2014 Local Search Ranking Factors for David Mihm, which is due to be published in September, it occurred to me Pigeon is one month old. The LSRF timing is really unfortunate, since the algo hasn't settled down enough for any of the experts working on the LSRF to even begin to figure it out.
We've been getting reports at the Google forum from users saying their ranking is rotating back and forth every day. OR they tell us they used to rank B, but dropped out of the pack. We check and they are still B.
I have a new discovery that helps make sense of the flux and could help you, if you are diagnosing rank drops during this uncertain time.
I've had a Pigeon theory for awhile now. I've floated bits and pieces out there, but wanted to try to lay it all out in one place. And now I have PROOF my theory was correct!
After doing lots of Pigeon analysis, I've been convinced for awhile now that Google is testing 2 -3 versions of Pigeon on different datacenters and is rotating results. (Likely for AB testing.)
I say this in part, because all the Google datacenter IPs I can find like THIS ONE (I've tested tons more) are ALL still showing the old pre-Pigeon results. (Check it out at that link and compare to the Pre-Pigeon shot below. Even though many of the results are the same - David H. Lee and Matt Brown-Ruegg only ranked PRE-Pigeon, never POST-Pigeon.)
Classic Google maps is showing the old ranking order too, because it’s still using an old datacenter so that's why results don't match Google search. (David H. Lee and Matt Brown-Ruegg still rank in classic, same order as the 6/22 Pre-Pigeon shot below.)
Plus many of the pack tracking tools I use are still showing the old algo ranking order as well. That's because they are all using older datacenter or maybe I should say non Pigeon DCs.
So anyway, rotating different versions of the new algo on a couple specific new datacenters would account for the crazy constant flux we are seeing. Depends on which datacenter you hit. I repeat - the Pigeon has not landed!
Well yesterday I discovered proof that my theory is correct and I want to show you what I discovered via screenshots.
I've been sharing rank tracking screenshots for "Seattle Chiropractor" since Pigeon hit.
See: Tracking Google Local Pigeon Flux Over Time
Yesterday when the results changed radically again, I dug deeper and will show you what's up. Skipping a bunch of in-between ranking screenshots which you can see at the link above and only showing you the Pre-Pigeon results and 8/23 and 8/26 results.
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/dividermulti.jpg" alt="dividermulti" width="550" height="4" />
<span style="font-size: large;"><b>PRE Update 6/22</b></span>
<img src="http://localsearchforum.catalystemarketing.com/attachments/google-local-important/1824d1406258461-major-google-local-algo-update-google-pigeon-seattlechiro6.22.jpg" width="60%" />
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/dividermulti.jpg" alt="dividermulti" width="550" height="4" />
<span style="font-size: large;"><b>PRE Update 6/22</b></span>
<img src="http://localsearchforum.catalystemarketing.com/attachments/google-local-important/1824d1406258461-major-google-local-algo-update-google-pigeon-seattlechiro6.22.jpg" width="60%" />
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/dividermulti.jpg" alt="dividermulti" width="550" height="4" />
8/23 - just showing the one to contrast and show the difference post-Pigeon, although as you can see in the Pigeon Flux link above, it's changed daily.
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.23.jpg" alt="SeattleChiro8.23" width="65%" />
OK now this is where it gets interesting...
Yesterday, like I said, I noticed the pack changed pretty drastically again.
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/dividermulti.jpg" alt="dividermulti" width="550" height="4" />
<span style="font-size: large;"><b>Update 8/26</b></span>
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.26.jpg" alt="SeattleChiro8.26" width="65%" />
<span style="font-size: large;"><b>Update 8/26</b></span>
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.26.jpg" alt="SeattleChiro8.26" width="65%" />
Some significant shifts. (I note them all in the Ranking Flux Over Time post.)
I checked Chrome - results were totally different - normally FF & Chrome match pretty well.
So went back to Firefox in a new window, searched again to compare browser results and saw this.
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/dividermulti.jpg" alt="dividermulti" width="550" height="4" />
<span style="font-size: large;"><b>8/26 Same FF browser and time frame as result above</b></span>
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.26DC21.jpg" alt="SeattleChiro8.26DC2" width="65%" />
<span style="font-size: large;"><b>8/26 Same FF browser and time frame as result above</b></span>
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.26DC21.jpg" alt="SeattleChiro8.26DC2" width="65%" />
So I had 2 different results, both using FF. (And double checked, both with location set to Seattle.)
So next I did what any good geek would do and hit hard refresh. And sure enough - not every time, but quite often, I could get the results to rotate between the 2 datacenters/algos.
HERE IS A SIDE BY SIDE COMPARISON
<img src="http://marketing-blog.catalystemarketing.com/wp-content/uploads/2014/08/SeattleChiro8.26differentDCs1.jpg" alt="SeattleChiro8.26differentDCs" width="75%" />
AND that 2nd algo is the one that Chrome was showing too.
So that crazy bird is flipping back and forth testing! She's definitely rotating datacenters!
Don't like what you are seeing? Hit Ctrl F5, do a hard refresh and check the other version.
Note: does not always work. Sometimes you have do it several times before it will switch over. And I think if the results don't change, then maybe that particular pack does not have the factors that the different versions of this algo affects. I tested a bunch of different results. Some changed and some did not.
No way to know which datacenter and which version of the algo is going to win out. But it's interesting to see and compare the different versions to try to get a preview of what may be coming!
GOOGLE MAPS MISMATCH
I mentioned above that Classic Google maps is showing the old ranking order too, because it’s using a different datacenter than Google search.
FYI new maps WAS on the old datacenter but was recently upgraded. So now new maps correlates with the new Pigeon ranking order, but Classsic does not. Which means Classic and new maps ranking order does not match, which is causing lots of problems here and with users at the Google forum.
SEE NEXT POST FOR DETAIL ABOUT MAP RANKING ISSUES & INCONSISTENCIES.
(Splitting to new post, so this post does not get too long.)
Now you know when you are troubleshooting, doing rank tracking OR trying to reverse engineer this crazy Pigeon algo - it totally depends which browser you are using and which version of maps you are checking. Because it depends on which datacenter you hit.
Many tracking tools are still hitting the old datacenter and showing the old results.
Non US Google search like: Google Germany is on the old datacenter too. (So you can use that or Classic to see/compare the old results.)
So anyway everything is just all jumbled up and it does not make a good user experience for anyone. And it makes it super hard for people like me to try to figure this algo out.
IN SUMMARY
.:. Google Search - rotating datacenters and ranking order
.:. New Google maps - same as above so normally mirrors search results
.:. Classic Maps - old pre-Pigeon results
.:. Many tracking programs - old pre-Pigeon results
.:. Checking US results from - google.ca or .de or other countries - old pre-Pigeon results
So if you don't like the results you see, or if you are seeing something different than your client sees, above may be the reason. Just blink or switch browsers or switch maps or hit hard refresh and you may see something totally different.
Miriam Ellis from Moz asked me to weigh in on an article she's doing there. She asks top experts what their best Pigeon advice is. Here's an excerpt of what I told her...
My advice? The Pigeon has flown the coup, but has not landed yet! There is too much flux for any of us to make sense of yet. All I can say is that hopefully by the time this bird is tested and/or trained, it will settle into something equitable for users and business owners alike.
But no solid advice can be given now, except to keep working on best practice strategies, which will always help in the end.
Tons more info about Pigeon at our #Pigeon Hashtag.
What do you think about all this???
Note: This is all theory based on my limited testing, so feel free to shoot holes. That's how we all learn!
(Next post covers map inconsistencies in more detail)
<meta property="og:type" content="article"><meta property="og:title" content=""><meta property="og:description" content="Google Pigeon flew the coup on 7/24, but this bird has still not landed! Major flux continues and I'll share some reasons why.">
<meta property="og:image" content="">
