Leaving JSPs in the dust: moving LinkedIn to dust.js client-side templates

Post by bigiain » Thu, Dec 15, 2011, 6:57 AM UTC

keltex wrote: post #36

bigiain wrote: post #17

Earlier quoted context omitted.

Not only caching, but right now I suspect this approach could have _serious_ SEO implications. It seems to run directly against the guidelines against cloaking here: http://support.google.com/webmasters/bin/answer.py?hl=en&#38... (Not that I suppose LinkedIn are too worried about search engine discoverability of a lot of their "dynamic, login required" content, but I'll bet they're _not_ using this technique on all t…

It wouldn't have SEO implications because using javascript to load content isn't considered cloaking. (Cloaking is where you present something different to googlebot vs. a live user). It's well known that googlebot does run javascript now: https://twitter.com/#!/mattcutts/status/131425949597179904 There's also some speculation that googlebot actually runs Chrome and can render anything that Chrome does: http://ipullr…

Post by pspeter3 » Thu, Dec 15, 2011, 8:56 PM UTC

bigiain wrote: post #41

keltex wrote: post #36

Earlier quoted context omitted.

It wouldn't have SEO implications because using javascript to load content isn't considered cloaking. (Cloaking is where you present something different to googlebot vs. a live user). It's well known that googlebot does run javascript now: https://twitter.com/#!/mattcutts/status/131425949597179904 There's also some speculation that googlebot actually runs Chrome and can render anything that Chrome does: http://ipullr…

Yep. I've seen that (and I've seen evidence googlebot executing javascript in my own logfiles). BUT - If I have a client relying on SEO/organic ranking for their money right now, there's no way I'd be suggesting they move to a "html template with javascript loaded content" style site - not until I've seen a few other similar/competitor sites ranking well with those techniques.