RSS Feed

All-Knowing Google? Or Coincidence?

One of my Facebook friends posted that they were located at Los Muertos beach in Puerto Vallarta (of course, having just come back home from there, I grew instantly jealous and happy at the same time).

It got me to thinking of how Los Muertos beach got its name – and I couldn't quite remember the details, so thought I'd look it up. Well, the one place I KNOW I've read of the history of this Puerto Vallarta beach is on my parents' condo website (on the History of Puerto Vallarta page, of course). I typed the website address directly into a new tab of my Chrome browser and navigated to said page to read about it (again).

Then I thought, I wonder what The Google will show me when I search for it? So I performed a search for "los muertos beach puerto vallarta."

After scrolling through the first page results I glanced down at the related searches list...and gasped:



"View ANOTHER Puerto Vallarta vacation condo rental" ??? How'd you know I was even looking at a vacation rental? A lot of times Google will throw in related search queries or "related to" items after you've already searched something, but in this case, I didn't search! 

Curious.

But, of course then I realized how Google knew: 


Even though I hadn't searched for a condo rental in Puerto Vallarta, what I'd done was opened up a new tab and typed the address to my parents' condo website in directly (yes, they rent it out); then when I "left" that website I typed Google directly into the address bar and performed a (related) search.

Now, here's the kicker – did Google really "know" where I'd been or is it just coincidence? I was signed into my Google account, after all...is Google more "aware" of what you're doing and therefore will show me more relevant material?

I tried the search again after signing out...I still get that "related to" list item, but I've never seen that verbiage before in the related searches area.

Mystery? Coincidence? Or does Google just really know THAT much about what we're thinking and what we're doing on the WWW?



0 comments: