SEO ROI

SEO Services For Serious ROI. Blog Posts For Serious SEOs.

Google Crushes Session IDs In Battle To The Death

Author: Gabriel Goldenberg, July 1, 2008

You often hear best practices saying that Google won’t index your pages if they force Googlebot to take a sessionId. Is that really true?

How does Googlebot treat session IDs?

http://www.google.com/search?q=inurl%3A%22sessionID%3D%22

Found while looking for folks using Blue Martini, which seems to output some nasty long URLs featuring BM user IDs and “J sessionIDs”: http://www.google.com/search?q=inurl%3A%22bmuid%3D%22

Like this post on session IDs? Get my RSS feed.

StumbleUpon It!

Related posts

Comments

  1. Google will index session ids no problem. Google won’t accept cookies, so some sites automatically parse the session ID into the url instead.

    Google will index that, then when it comes back again it will be given another session id, hence index the same page under different urls each visit.

    Basically meaning big dup content problem.

    Reply

    Comment by PPCblogger — July 1, 2008 @ 3:11 pm

  2. 8 million results of session id results! take a look – though where all this horrid, duplicated stuff actually ranks is anyones guess.

    Not handling session id’s properly, as a webmaster is just plain lazy!

    Reply

    Comment by richard baxter — July 2, 2008 @ 8:36 am

  3. what’s really interesting is when i signed out of google, the results went up to 31 million!

    Reply

    Comment by richard baxter — July 2, 2008 @ 8:37 am

  4. PPC Blogger – excellent point. Will add a dofollow link to you later.

    Rich, that’s an astronomial amount. Crazy how much crap is published, huh?

    Reply

    Comment by Gabriel Goldenberg — July 2, 2008 @ 5:52 pm

  5. Indeed it is, indeed it is!

    Reply

    Comment by Richard Baxter — July 3, 2008 @ 2:43 pm

  6. What’s the best way to deal with this? By creating cookies instead? How can I create friendly URL’s if a site already uses session id’s?

    Reply

    Comment by Caffeine Blog — November 24, 2008 @ 5:58 pm

Post a comment.