Google searches and how they appear in your weblogs...

[Ed Witles]

Gang -

Today, I followed a link in my weblog and saw my website in several locations but did not actually click on it.

The logs later revealed that I had 'searched' for it as well.

I have seen this before and not much happy about it.

It makes it look like all Google searches actually visit your site when this scenario shows that is not always the case.

So, for those that see dozens of Google searches and wonder why not getting any calls/contact, chances are the results page triggered a 'hit'', w/o actually landing on your page.

So unless you have a compelling or relevant result, it won't get acted upon - but Google will still let you think it was.

 

[sparkieg]

Gang -

Today, I followed a link in my weblog and saw my website in several locations but did not actually click on it.

The logs later revealed that I had 'searched' for it as well.

I have seen this before and not much happy about it.

It makes it look like all Google searches actually visit your site when this scenario shows that is not always the case.

So, for those that see dozens of Google searches and wonder why not getting any calls/contact, chances are the results page triggered a 'hit'', w/o actually landing on your page.

So unless you have a compelling or relevant result, it won't get acted upon - but Google will still let you think it was.

Ed,

Sometimes, when analyzing and number crunching where your hits came from, you have to dig into the line of code to see what the search term was that was plugged in by the potential client.

For instance, I have greyed out the search term lines from my 15 day weblog as an example below. Sure, if you click on the link yourself, your hit is going to be recorded, but you just subtract that number from your actual logs to get a realistic number.

 

[Dan The Man]

I've noticed this too and haven't done enough research yet but I think has to do with Google's new Instant Search feature. My best guess is that when someone runs a search where one of your pages come up as the top result Google caches a snap shot of that page for mouse over.

 

[Jeff Romard]

I've noticed this too and haven't done enough research yet but I think has to do with Google's new Instant Search feature. My best guess is that when someone runs a search where one of your pages come up as the top result Google caches a snap shot of that page for mouse over.

I was reading about this yesterday Dan that is exactly what it is. I'll see if I can dig the article up again