Welcome to WebmasterWorld Guest from 50.17.5.36

Message Too Old, No Replies

Extended listing links. The sa=X parameter causes a Google Bug!

     
10:41 am on Apr 25, 2006 (gmt 0)

New User

5+ Year Member

joined:Apr 25, 2006
posts:2
votes: 0


I found a Bug in Google's additional Links that are shown sometimes for the top ranked site (Navigation Links).
Whe you click on it Google appends '?sa=X' on every Deeplink.
Try it.
Most of the webpages have no problem with this additional parameter but in some case it leads to a broken link.
Even Google itself is affected by this bug!
Examples:
[google.com...] The Link 'New features!' and 'Google Accounts'
or
[google.com...] The Link 'Valid XHTML 1.0!'

Maybe we can find some more famous examples where this bug causes trouble

6:41 pm on Apr 25, 2006 (gmt 0)

Senior Member

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:May 26, 2000
posts:37301
votes: 0


Welcome to the forums, InsideSEO.

This sa=X business was mentioned a while back, but I hadn't noticed that it actually breaks some links -- even for Google itself. Good observation!

Why they are keeping that part of the query string, even after passing the click through their own tracking script, is very confusing to me. I sure hope they don't start indexing those urls.

10:35 pm on Apr 25, 2006 (gmt 0)

Full Member

10+ Year Member

joined:Aug 22, 2003
posts:333
votes: 0


Huh, that explains some 404 errors I've seen in my logs.

Has anyone written an .htaccess rule to redirect people to the proper URL?

6:54 am on Apr 26, 2006 (gmt 0)

New User

10+ Year Member

joined:Dec 15, 2005
posts:2
votes: 0


I'm also affected. It seems the old google behaviour was to make these hrefs as follows:
/url?<google-parameters>&q=<an_extended_listing_url>

Now they malform the url with two "?" by constructing it like this:
/url?q=<an_extended_listing_url>?<google-parameters>

I would love (and kind of expect) a fix at their end.

7:54 am on Apr 26, 2006 (gmt 0)

New User

5+ Year Member

joined:Apr 25, 2006
posts:2
votes: 0


Wow, that was fast.
Seems like Google fixed this bug.
No problems with my sites and the above mentioned any more.
But I haven't checked every datacenter
10:00 am on Apr 26, 2006 (gmt 0)

New User

10+ Year Member

joined:Dec 15, 2005
posts:2
votes: 0


Fixed for me too. Google now encodes the second?. Which is a very good thing...