Have a question that I hope you guys can help me with. We are in the process of redesigning a long-time client's site. We would really like to use cookieless sessions on it, but have read conflicting reports about weather that would be search engine friendly. Any thoughts would greatly be appreciated.
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!

www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
Cookieless Sessions
Started by
texasmarketer
, Jul 28 2005 10:12 AM
6 replies to this topic
#1
Posted 28 July 2005 - 10:12 AM
#2
Posted 28 July 2005 - 10:39 AM
That would be a no, if the sessionID is appended onto the end of the url that is.
The basket would not be spiderable, but then why would you want it to be? So long as your products pages dont use sessions and you just use them for your store basket, you should be fine.
The basket would not be spiderable, but then why would you want it to be? So long as your products pages dont use sessions and you just use them for your store basket, you should be fine.
#3
Posted 28 July 2005 - 11:23 AM
We’re thinking of using ASP.NET cookieless sessions. Unfortunately, there is no way to turn them off on particular pages, and the Session ID is embedded in the URL. For example…
www.somewhere.com/(dal5s355ma5eij453prnhjr0)/product.aspx?id=223
I have the sneaky suspicion that search engines won’t like this (since the session ID would be different each time the spider came back). That is unless search engines have technology built in to allow for session IDs like that and ignore them.
www.somewhere.com/(dal5s355ma5eij453prnhjr0)/product.aspx?id=223
I have the sneaky suspicion that search engines won’t like this (since the session ID would be different each time the spider came back). That is unless search engines have technology built in to allow for session IDs like that and ignore them.
Edited by Jill, 28 July 2005 - 12:40 PM.
#4
Posted 28 July 2005 - 12:06 PM
Your sneaking suspicion is 100% correct in my experience texasmarketer.
One of two things usually happens. Either the engines recognize that the url contains an SID and refuse to index the page, which means it never gets indexed unless you offer them a clean version; or they don't realize an SID is involved and you end up with thousands or hundreds of thousands duplicate pages indexed.
Neither is a good thing.
One of two things usually happens. Either the engines recognize that the url contains an SID and refuse to index the page, which means it never gets indexed unless you offer them a clean version; or they don't realize an SID is involved and you end up with thousands or hundreds of thousands duplicate pages indexed.
Neither is a good thing.
#5
Posted 29 July 2005 - 04:56 AM
Also, have you considered how your Web metrics system will be affected by the ever-changing URLs? At least the log-based systems may feel confused...
W3c says it the best.
http://www.w3.org/QA/Tips/uri-choose
Cheers!
//Henri
W3c says it the best.
http://www.w3.org/QA/Tips/uri-choose
Cheers!
//Henri
#6
Posted 29 July 2005 - 10:42 AM
You might be able to get round it with a decent site map and a load of no-follow attributes - but only if you don't rely heavily on internal linking.
I'm not an expert though so I'd wait for one of the big guns to confirm what I say before taking any action on it...
I'm not an expert though so I'd wait for one of the big guns to confirm what I say before taking any action on it...
#7
Posted 29 July 2005 - 11:52 AM
QUOTE(texasmarketer @ Jul 28 2005, 08:12 AM)
Have a question that I hope you guys can help me with. We are in the process of redesigning a long-time client's site. We would really like to use cookieless sessions on it, but have read conflicting reports about weather that would be search engine friendly. Any thoughts would greatly be appreciated.
Why do you want cookieless sessions? This is a perfect application of them.
mla
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users








