View Full Version : Google: t
it' something i keep coming across when checking stats. who on earth searche for T on google? and it's always only google they seem to use.
the blog i am just looking at had 2670 uniques supposedly looking for T this month alone. and 17 uniques for F.
anyone got any ideas what that could be?
Willie_Ekkerslike
07-27-08, 11:09 PM
http://i76.photobucket.com/albums/j30/kimtassstic/MrT15.jpg
Just a thought !!!
plotting a black bear site as we speak.
any recommandations for F?
T for tits but they are so over excited they cant bother to type the entire word?
any recommandations for F?
http://costumzee.com/view/wp-content/uploads/2007/09/freddy.jpg
Scotty.T
07-28-08, 12:00 AM
I get it too. I did see someone offer an explanation for it a while back but I can't remember what it was :)
it' something i keep coming across when checking stats. who on earth searche for T on google? and it's always only google they seem to use.
the blog i am just looking at had 2670 uniques supposedly looking for T this month alone. and 17 uniques for F.
anyone got any ideas what that could be?
never get it, least it's never jumped out at being searched for. although if your ranking well for the letter T I take my hat off to your SEO skills,
I get that, also, wtf is with all the hits from the zoo?
Atomic Playboy
07-28-08, 08:26 AM
http://se.inf.ethz.ch/people/leitner/erl_g/image/tea_cup_small.jpg
redwhiteandblue
07-28-08, 05:50 PM
I had thiis some time ago and I think I can explain. Normally in the search query string for Google, you look for the "q" parameter to get the search terms. But sometimes, the "q" parameter only contains the letter "t", and the search terms are instead contained in the "as_q" parameter.
So you have to check for a "as_q" parameter first, before checking the "q" parameter. Don't ask me why.
Scotty.T
07-28-08, 05:56 PM
I had thiis some time ago and I think I can explain. Normally in the search query string for Google, you look for the "q" parameter to get the search terms. But sometimes, the "q" parameter only contains the letter "t", and the search terms are instead contained in the "as_q" parameter.
So you have to check for a "as_q" parameter first, before checking the "q" parameter. Don't ask me why.
I don't know what you just said :)
redwhiteandblue
07-28-08, 06:10 PM
I don't know what you just said :)
Neither do I, I just made it up.
Scotty.T
07-28-08, 06:12 PM
Neither do I, I just made it up.
Sounds good though :) Next time someone asks me I am going to use that :)
redwhiteandblue
07-28-08, 06:29 PM
Ah, I just had a quick look through and I wasn't quite right with that. The problem comes from having a script that just looks for the string of characters "q=" in the query string. This works most of the time as it will usually find the bit that reads e.g. "&q=the+search+terms". But sometimes there's a parameter "aq" before that, which usually reads "aq=t". The search for "q=" will find that and grab the "t" as the search term.
For example:
http://google.com/search?sourceid=navclient&aq=t&ie=UTF-8&rlz=1T4ADBF_enGB254GB255&q=uk+outdoor+sex
What the script really should do is split the query string on the "&" character but most don't bother.
never get it, least it's never jumped out at being searched for. although if your ranking well for the letter T I take my hat off to your SEO skills,
hijacking t-mobile sites does pay off. :blush:
Ah, I just had a quick look through and I wasn't quite right with that. The problem comes from having a script that just looks for the string of characters "q=" in the query string. This works most of the time as it will usually find the bit that reads e.g. "&q=the+search+terms". But sometimes there's a parameter "aq" before that, which usually reads "aq=t". The search for "q=" will find that and grab the "t" as the search term.
For example:
http://google.com/search?sourceid=navclient&aq=t&ie=UTF-8&rlz=1T4ADBF_enGB254GB255&q=uk+outdoor+sex
What the script really should do is split the query string on the "&" character but most don't bother.
FWD'ing this bit of info as we speak, cheers.
Scotty.T
07-28-08, 07:01 PM
Ah, I just had a quick look through and I wasn't quite right with that. The problem comes from having a script that just looks for the string of characters "q=" in the query string. This works most of the time as it will usually find the bit that reads e.g. "&q=the+search+terms". But sometimes there's a parameter "aq" before that, which usually reads "aq=t". The search for "q=" will find that and grab the "t" as the search term.
Now I understand. Thanks.
I don't think this was the explanation I was offered before. If it was, I definately didn't grasp it the last time.
"t" has "accounted" for 1.33% of our SE traffic here this month... but then I've never been of fan of the old webair stats script thing.
Infact looking at the SE stats, surprised how many people are still looking for Lea Walker :geek:
vBulletin® v3.7.2, Copyright ©2000-2012, Jelsoft Enterprises Ltd.